(5510 EVM) C:\ti\cc\gel\c5510evm.gel     "C5510EVM_EMIF_Init"
   (6416 TEB) C:\ti\cc\gel\6416teb.gel      "Reset Breakpoints and EMIF"

General Description
-------------------
FlashBurn provides a user-friendly way to program the Flash
  Memory in a DSP system. The user creates and maintains one
  or more Configuration Details Documents (CDD documents) to
  specify the characteristics of the target system and its
  Flash Memory. Once the required fields have been filled-in,
  the document may be used to burn a program into the target
  system's flash memory. A document may also be saved and
  used for future programming.
  FlashBurn also runs in command line mode.
  
FlashBurn works in concert with a (F)lash(B)urn (T)arget
  (C)omponent, or FBTC.
  The FBTC is a DSP program written in C Language and
  tailored by the user to a specific target configuration.
  The FBTC is automatically downloaded to the Target System
  when you open a document. If you modify the document to
  change the FBTC file, then use the Program/Download FBTC
  menu to ensure that the Target system is running the
  desired FBTC. 
  You might create several FBTC programs to handle variations
  from one target configuration to the next.

Another FlashBurn feature is interactive memory display and
  patch. You can apply patches to individual flash memory
  bytes in interactive mode.
  
Example FBTC programs are shipped with FlashBurn:
     FBTC54.out for TI's TMS320C5402 DSP Starter Kit
     FBTC5416.out for TI's TMS320C5416 DSP Starter Kit
     FBTC55.out for TI's TMS320C5510 EVM and DSK Kits
     FBTC55.out (in a different folder) for TI's
            DSK5510 Kit.
     FBTC62.out for TI's TMS320C6211 DSP Starter Kit
            (also works with TI's TMS320C6711 DSP Starter Kit).
     FBTC6416.out for TI's TMS320C6416 TEB board.

Source code and documentation are provided to allow
  customizing, should you need to change memory map,
  flash memory type, etc.
  Each FBTC folder has a project file (.pjt)
  for use with CCS v2.1.

  The communications protocol between FlashBurn PC Host
  application and the FBTC is defined in the document
     "FlashBurn Project Exchange Communications Protocol"
  which is in file SpecCommProtocol.htm.

FlashBurn requires Code Composer Studio to download the FBTC to
  the Target DSP's memory and run it. FlashBurn then
  exchanges data with the FBTC via CCS services to read and
  write the target memory.


What FlashBurn Does
-------------------
Flash memory in a DSP system is often used as the program memory
  for the system, replacing the more traditional ROM memory.
  The advantage of flash memory is that it's possible to change
  the contents of the memory (thus the program) without removing
  the actual chip from the system and placing it in a special
  programming tool, as must be done with erasable ROM memories.
FlashBurn takes advantage of features available through Code
  Composer Studio and the XDS 510 emulator to make reprogramming
  a flash memory chip easier during development and test, when
  target system configurations and components may be changing,
  and during target system testing, when a succession of different
  target programs must be downloaded to the flash memory to
  exercise special test cases.
Unfortunately, the algorithm for programming a flash memory chip
  differs from brand to brand, and from type to type within a
  given brand's various silicon implementations. Thus delivering
  a new program from the Host PC to the target system is only half
  of the job. The other half, the programming of the flash memory
  chip itself, must be performed by the FBTC, which is a DSP
  program you must create for running on the target system.
  Example FBTC programs with source code are provided for you
  to use as a starting point.
  For example FBTC54.out is an FBTC program which runs on the
  5402 DSK and may be used to program the flash memory on the
  DSK board.
  The FBTC is also expected to provide the base address of the
  flash memory on the target system.

To program a flash memory, FlashBurn does the following:
  0) FlashBurn, the PC application, connects with Code
     Composer Studio via a COM interface;
  1) Based on the information in a document (.cdd extension)
     FlashBurn requests CCS to download an FBTC program to the
     target system. After downloading is complete, CCS is
     commanded to run the FBTC.
  2) FlashBurn requests the FBTC to send the base address of the
     flash memory (in Target system units). This value will
     be used to compute Logical Addresses when reading
     Motorola, ASCII Hex, or CCS Saved Data files.
  3) FlashBurn reads the named hex file (as generated by TI's
     proprietary hex conversion utilities), converts the hex file
     records to binary, and downloads one block at a
     time to the FBTC. The FBTC uses the Logical Address plus
     its knowledge of the actual flash memory address and
     carries out the programming algorithm to burn the block
     of data into the flash memory.

FlashBurn can run in the background, for example as part of a
  batch file, or interactively via a forms-style interface.

FlashBurn also provides the following:
  - Erase the Flash Memory,
  - View the contents in 256-byte blocks,
  - Interactively edit the contents of the flash memory.
 


Before Running FlashBurn
------------------------
    Note that for generality, FlashBurn does not initialize
     any target system registers. Register and timer setup
     must be done by some other means, such as Gel files or
     special-purpose user programs. 
    Connect DSK target system to XDS 510 using JTAG cable.
    Run "Setup CCS" and select the desired driver.
    Code Composer Studio can be left running while FlashBurn
       executes, but that is not a requirement.

Starting FlashBurn for Interactive Use
--------------------------------------
    0. Start by double-clicking the application itself, or a
       FlashBurn document (type ".cdd"). You can also start
       FlashBurn from the CCS Tools Menu.
    1. Use the File/New menu to create a new document, or edit
       an existing document. 
    2. When FlashBurn opens or creates a document, it attempts
       to communicate with Code Composer Studio.
       a) If CCS fails to open, it will stall the application
          for a full minute. Sorry. After the delay, you can
          edit and save documents, but of course no target
          interaction is possible.
       b) If CCS opens, a FlashBurn will fill-in some default
          document items, such as DSP type.
    3. Interactive mode is useful for preparing documents and
       testing the downloads to verify that they work. Once
       a document is complete, it can be used to run
       FlashBurn as a background task, e.g. as part of a
       batch file.


Starting FlashBurn for Background Use
--------------------------------------
Usage:
      >FlashBurn [<document> [<file>...]] [-q [-n] [-e]]

          document is a FlashBurn document, type .cdd
                   FlashBurn will start up, display the document,
                   and await user input, unless the -q switch is used.
          file     One or more filenames is optional, and are only
                   used if -q is specified. See -q for details.
                   If -q is NOT specified, the FlashBurn application
                   is started and runs interactively; therefore any files
                   listed will be ignored.

          -q       is a "quiet" running mode. Application will open
                   the document and attempt to burn a program
                   into the flash memory, then exit when burning is
                   complete.
                   If no document is named, the -q switch has no
                   effect. Otherwise, filenames will be processed in
                   the order listed as follows:

                   -If a file's type is .hex, then the contents will be
                     burned into the Flash Memory.
                   -If a file's type is .dat, then the contents will be
                     burned into the Flash Memory.
                   -If the type is .cmd, then FlashBurn will execute
                     the correct hex conversion utility, passing it
                     the command filename. Hex conversion utilities are
                     hex500.exe for 54x Target System,
                     and hex6x.exe for 62x or 67x Target System.
                     The system PATH variable must be
                     properly set for this to work.
                   -If the type is anything other than .hex or .cmd,
                     then it will be downloaded to the target as a user
                     file, as though the Program Menu/Send User File To
                     Target had been selected; the flash memory will not
                     be affected in any way. You might use this to send
                     your own custom commands to a target running an FBTC
                     which you have customized.

                   If an exception occurs, such as incorrect
                   document field or processing error,
                   the application writes a brief log
                   to file "LogFBurn.txt." and then exits
                   (but see the -n switch description).

          -e       in combination with the -q switch, causes FlashBurn
                   to precede programming by erasing the entire flash
                   memory. Otherwise, FlashBurn will begin programming
                   directly.
                   Erasing is done only once, prior to processing any
                   file listed on the command line.
                   If the -q switch is not present, then this switch
                   has no effect.

          -n       in combination with the -q switch, if an exception
                   occurs during the process, a modal dialog will
                   be displayed describing the problen before
                   the application exits.

  EXAMPLE: >flashburn mysystem.cdd
  EXAMPLE: >flashburn mysystem.cdd -q -e
  EXAMPLE: >flashburn yoursystem.cdd prog1.cmd prog1outa.hex prog1outb.hex -q -e

  ------------------
  ------------------
  --- SPECIAL USAGE:  >flashburn -g addr  nbytes  mau
  ------------------

               addr    Start address for storing data. This is
                       the actual address on the target system.
               nbytes  The number of 8-bit bytes in the simulated
                       data file.
               mau     #bytes per address on target system (memory
                       address units). This would be 2 for 5402 DSK,
                       and 1 for 55x, 6211, 6711, 6416.
		
      This is a test capability which simply creates a file in
      the current directory and then exits.
      The file it creates is called "DummyHex.hex."
      DummyHex.Hex is a simulated Motorola Hex S3S7 File containing
      test data for downloading. The test data is the numbers
      0-15 repeated every 16 bytes.
      EXAMPLE:
         >flashburn  -g  0x8000  32768  2
         >flashburn  -g  0x90001000 0x100 1
			 
         The 1st example creates DummyHex.hex, which, when downloaded
         via FlashBurn to a 5402 DSK, will burn the numbers 0-15
         in the 1st 32768 bytes (16384 words) of the flash memory
         (starting at logical Address 0, Physical Address 0x8000).