getstarted.txt

代码是基于ti公司DM642

         The 2nd example is for a 6211 or 6711  DSK. It creates a
         DummyHex.hex file which, when downloaded via FlashBurn to a
         6211 DSK, will burn the numbers 0-15 in 256 bytes starting
         at Logical Address 0 (Physical Address 0x90000000).  



FlashBurn Document Fields (shown in the document's window)
-------------------------

  Hex Command File: If not blank, then the contents of this edit
                  field are assumed to simply be a Hex conversion
                  command file name, such as "FlashBlink_hex.cmd".
                  The Hex Converter is invoked when you select
                  File/Start Programming, and prior to burning data
                  into the flash memory. The system PATH variable
                  must be set properly for this to work.
                  FlashBurn will invoke the Hex conversion utility
                  for the current target as follows:
                        hex6x  <contents>    (for 62x/64x/67x target)
                        hex500 <contents>   (for 54x target)
                  If this field is blank, no action is taken.
                  The Browse button is a convenient way to enter a
                  command file path.
                  Note that the hex conversion utility's directory
                  must be in your PATH environment variable.
                  Note also that if the Hex conversion utility does
                  not return a failure code, then FlashBurn assumes
                  that it succeeded.

  File To Burn    This is a hex file name, usually with type
                  .hex,or .dat. Use the Browse button to
                  locate the file, or type it in. The file format
                  must be either Motorola (S1S9, s2s8, or S3S7),
                  or ASCII Hex, or CCS Saved Data Hex.
                  TI provides Motorola and ASCII Hex hex conversion
                  utilities with its DSK systems.
                  A file in the CCS Saved Data Hex format is created
                  from a DSP memory image using the CCS menu
                  File->Data->Save and specifying the Hex format.
				  
                  NOTE: for Motorola Hex files, FlashBurn assumes
                  that addresses contained in the file are physical
                  Target addresses. To see how FlashBurn converts
                  these to logical addresses before sending them to
                  the Target, see the next section, Logical Addr.
                  For CCS Saved Data files, the beginning address
                  specified in the header is ignored.

  Logical Addr    When FlashBurn sends a block of data to the
                  FBTC for burning, it uses a Logical Address to
                  specify where in the Flash Memory chip to burn
                  the data. Logical Address ranges from 0 (zero) to
                  whatever the number of bytes in the Flash Memory
                  is shown in the #Bytes field.
                  Thus an offset of 0 means that the
                  data should be burned-in starting at the lowest
                  location in the flash memory.
                  Specifying a positive non-zero Logical Address
                  will cause the data to be burned-in at a higher
                  flash memory address.
                  The FBTC is expected to add the actual base address 
                  (the physical address) to the Logical Address
                  prior to burning data into the flash.
                  The Logical Address, the Flash Base Address,
                  plus the address provided in the hex file are
                  all used by FlashBurn to determine where the
                  downloaded data are to be stored in the flash
                  memory.
                  
                  If hex file is Motorola, then the Logical
                  Address sent to FBTC is
                  (hex file address) - (Flash Base Address) + (Logical Addr)
                  and the FBTC will burn the data into location
                  (FBTC Flash Base Address) + (Logical Addr sent by
                  FlashBurn).
  
                  If hex file is ASCII Hex then offset sent to FBTC is
                         (Logical Addr) + (hex file address)
                  and the FBTC will burn the data into location
                  (FBTC Flash Base Address) + (Logical Addr from FlashBurn).
  
                  If hex file is CCS Saved Data Hex, then offset sent to
                  FBTC is
                         (Logical Addr)
                  and the FBTC will burn the data into location
                  (FBTC Flash Base Address) + (Logical Addr from FlashBurn).
                  This means that the address specified in the one-line
                  file header is ignored.

  Verify Write    If checked, FlashBurner will use a checksum
                  calculation on every block of data sent to the
                  FBTC. After the block is written, Flashburn will
                  then request the FBTC to read back the block
                  of data from the flash memory and calculate the
                  checksum of the data.
                  Flashburn will then compare the two checksums and
                  notify you if they do not match.
                  This slows down the burning-in significantly, but
                  increases reliability.

  Write Boot Addr (dsk5402 only)
                  If checked, FlashBurn will write the 16-bit Flash Base
                  Address at the end of Memory Page Zero (0xffff in the
                  5402 DSP page zero data space).
                  On the 5402 DSK system, this corresponds to
                  Logical Addr 0x7fff in the flash memory chip, since the
                  flash memory base address is 0x8000.
                  Data address 0xffff is where the C5000 series
                  on-board bootloader will expect to see
                  the address of the boot table (see SPRA618).
                  Uncheck this if the data you are writing to the flash
                  memory is not a bootable program, or if the downloaded
                  program already writes to that location.
                  *** NOTE *** The DSP's boot loader also expects to
                  see register initialization values beginning at the
                  location secified at address 0xffff. To insert these
                  values at the base address, enter "548" or "549"
                  as the processor type in the Code Gen (II)
                  portion of the CCS Project Options. This will place
                  a -v548 or -v549 in the code generator command line.

  FBTC Version ID The version identifier of the FBTC program running
                  on the target DSP. This is mainly for TI's reference,
                  but you may want to change it if you change the FBTC
                  program to customize it for your system. 

  Target DSP Type This is the family type of the target DSP.
                  Before FlashBurn tries to access the target
                  system, it will verify that this matches the
                  target system's DSP type.

  FBTC Program File
                  This is the .out file to download to the target
                  DSP memory and start running. FlashBurn performs
                  the CCS equivalent of File/Load Program to download
                  this file, followed by Debug/Run.

  Flash Base Address
                  The target system's Base Address of the flash
                  memory. This is normally filled-in using the
                  address returned by the FBTC program, but you
                  may change it. If the FBTC indicates a different
                  base address than this field shows, you will be
                  warned.

  # Bytes         The size of the flash memory, in bytes, defaulted
                  to 0x20000 bytes.       


Preparing Hex Files for FlashBurn
---------------------------------
The example applications FlashBlinkxx (xx = 54, 5416, 55, 62)
show examples of applications which can be built using
Code Composer Studio and its utilities to create
downloadable hex files.

Note that you may have to change the paths to the Library
files, if your installer created Code Composer Studio
in a directory other than C:\ti\. Use the Project/Options
Menu, Compiler and Linker tabs to set the corect paths
for library files and include path.

Two different hex file formats are demonstrated:
    Motorola Hex  for the c5000 (hex500.exe with -m1 switch)
    ASCII Hex     for the c6000 (hex6x.exe with -a switch)

FlashBurn can read hex files in four possible formats:
   Motorola S1S9 (16-bit addresses)
   Motorola S2S8 (24-bit addresses)
   Motorola S3S7 (32-bit addresses)
   ASCII Hex     (16-bit addresses)
   CCS Saved Data Hex (DSP family-dependent addressing)

   ASCII HEX
   ---------
   FlashBurn makes the assumption that when a hex
   file in ASCII format is used, the addresses are
   relative to the beginning of the Flash Memory.
   Thus if a FlashBurn document (.cdd file) specifies
   a Flash Base Address as 0x8000 and Logical Address
   as 0, and the hex file begins with an address specifier
   of "$A0100" then the first byte of data will be
   written at address 0x8100. The FlashBlink62.hex
   example has no $A... address specifier, therefore
   zero is assumed as the starting address.

      Hardware        CDD Document    Hex File
   Flash Base Addr    Logical Addr    S1xxAAAA    Effective Address
   ---------------    ------------    --------    ----------------
       0x8000            0x0000       $A0100          0x8100
       0x8000            0x1000       $A0100          0x9100
   
   Therefore the effective address is
   FlashBaseAddr + Logical Addr + Address value in ASCII hex file


   MOTOROLA HEX (16-, 24-, or 32-bit)
   ----------------------------
   FlashBurn makes the assumption that when a hex
   file in Motorola format is used, the addresses are
   the desired actual memory addresses.
   Thus if a FlashBurn document (.cdd file) specifies
   a Flash Base Address as 0x8000 and Logical Addr
   as 0, and the Motorola hex file record specifies
   an address of 8100 then the first byte of data will be
   written at address 0x8100. Using a non-zero value for
   Logical Addr will move the data up in the Flash memory.

      Hardware        CDD Document    Hex File
   Flash Base Addr    Logical Addr    S1xxAAAA    Effective Address
   ---------------    ------------    --------    ----------------
       0x8000            0x0000       S1108100...     0x8100
       0x8000            0x1000       S1108100...     0x9100
   
   Therefore the effective address is
       Logical Addr + Address value in Motorola hex file.


   CCS Saved Data HEX
   ------------------
   FlashBurn makes the assumption that when a hex
   file in CCS Saved Data format is used (usually in
   a file of type .dat), the addresses are
   relative to the beginning of the Flash Memory.
   Flashburn ignores the address field specified in the
   one-line file header.
   Thus if a FlashBurn document (.cdd file) specifies
   a Flash Base Address as 0x8000 and Logical Address
   as 0, then the first byte of data from will be
   written at address 0x8000.

      Hardware        CDD Document
   Flash Base Addr    Logical Addr                Effective Address
   ---------------    ------------                ----------------
       0x8000            0x0000                       0x8100
       0x8000            0x1000                       0x9100
   
   Therefore the effective starting address is
   FlashBaseAddr + Logical Addr