readme.htm

代码是基于ti公司DM642

            target flash memory.</li>
        </ul>
      </li>
    </ul>
  </li>
  <li>Version 1.10 Release 14 August 2001
    <ul>
      <li>Added CCS Connected/Not Connected icons to the FormView (DDTS
        #SDSsq21254).</li>
    </ul>
    <ul>
      <li>BUG FIX
        <ul>
          <li>Changed the Set Memory Address Dialog (used by ShowWindow) default
        button from the Help button to the OK button.</li>
        </ul>
      </li>
    </ul>
  </li>
  <li>Version 1.00 Beta 09 July 2001
    <ul>
      <li>This version was made available through CCS v2.0's Update Advisor for
        Beta Testing.</li>
      <li>Modified FBTC54 and FBTC62 by sprinkling-in a few <i>volatile</i>
        keywords. Now user can use optimizer when compiling. Previously these
        would only work if compiled with optimization turned off.</li>
      <li>BUG FIX
        <ul>
          <li>Fixed: FlashBurn would crash if user used File-&gt;New, then quit
            application.</li>
        </ul>
      </li>
    </ul>
  </li>
  <li>Version 0.30 Alpha 02 May 2001
    <ul>
      <li>Redesigned to eliminate RTDX. Messages are now written directly into
        the target memory using CCS COM services. This speeds up the
        communications considerably.</li>
      <li>Added a new allowed hex file format for burning data into flash: CCS
        Saved Data Hex format (.dat file). This is a hex code file created from
        a memory image using CCS File-&gt;Data-&gt;Save menu and specifying Hex
        format.</li>
      <li><font size="3">BUG FIXES:</font>
        <ul>
          <li><font size="3">There was an error in editing the flash memory,
            which caused loss of communications with the target whenever user
            attempted to change a memory value. This edit feature now works
            correctly.</font></li>
        </ul>
        <p>&nbsp;</li>
    </ul>
  </li>
  <li>Version 0.21 Alpha 21 March 2001
    <ul>
      <li>Changed default Flash Address and Size values for New Document so that
        the fields are left blank, instead of being filled-in with bogus values.
        Now when you create a new document, then fill-in an FBTC name and
        download the FBTC to the target system, the Flash Address and Size
        fields will be filled-in with values returned by the FBTC.</li>
      <li><font size="3">Reworked Document and App handler classes to process
        new -t and -r test features; this helps with Perl Script testing.</font></li>
    </ul>
    <ul>
      <li><font size="3">Expanded RTDX buffering from 256 data bytes per message
        block to 768 bytes. This speeds up the data exchange, but also requires
        FBTC program changes. Also added Flash Memory Edit feature. These required updating
        the Exchange Communication Protocol Specification to Version ID 2. Also
        updated the FBTC Programmer's
        Reference Manual and modified the existing FBTC programs. Older&nbsp;
        FBTC programs which expect 256 bytes per data block will still work, so
        long as they respond to the Query Version ID command with Protocol ID 1.
        The new Protocol Version ID is 2.</font></li>
      <li><font size="3">BUG FIXES:</font>
        <ul>
          <li><font size="3">There was an error in reading .cdd document
        Target Type (m_TargType). The error caused an incorrect default target
        type to be used when creating a new document with no board connected.
        Fixing it necessitated a new CDD document version ID, since I had to
        change the format of one of the serialized values. This does not
        invalidate older CDD files, merely requires reformatting when they are
        opened.</font></li>
          <li><font size="3">Fixed error in Hex file reader which prevented proper
        reading of Motorola Hex records that contained just a single data byte.</font></li>
          <li><font size="3">Fixed a memory leak which occurred if the app
            exited abnormally.</font></li>
          <li><font size="3">Fixed processing of ASCII-Hex formatted hex files.
            Former versions would display a message box if a comma character is
            encountered. Now the comma character is simply ignored.&nbsp;</font></li>
        </ul>
        <p>&nbsp;</li>
    </ul>
  </li>
</ul>

<ul>
  <li><font size="3">Version 0.20 Alpha 26 February 2001</font>
    <ul>
      <li><font size="3">Same as 0.12 Beta, with some directory/path and
        cosmetic changes that resulted from unit and integrated testing.</font></li>
      <li><font size="3">Released for use in integration testing for evm5510 and
        CCS2.0 rollout.</font></li>
      <li><font size="3">NOTE: This version was released to 5510 development
        group, but for test use only. This is not a blessed release!</font></li>
    </ul>
    <p>&nbsp;
  </li>
  <li><font size="3">Version 0.12 Beta 22 February 2001</font><ul>
      <li><font size="3">Moved COM initialization from main module to doc class.</font></li>
    </ul>
    <ul>
      <li><font size="3">Removed SafeArray from WaitForMessage to remove a memory leak.</font></li>
      <li><font size="3">When a .cdd document is opened the current directory is changed to that
        of the .cdd document. This allows the FBTC and Download file fields to specify the files
        using relative paths (e.g. &quot;..\..\foo\test\myfbtc.out&quot;).</font></li>
      <li><font size="3">When user creates a new .cdd document or modifies a .cdd document, then
        selects Program/Download FBTC, FlashBurn will prompt with the Save As... dialog before
        attempting to download the FBTC. This allows FlashBurn to set the current directory to
        that of the .cdd document prior to download. If user answers &quot;Cancel&quot; to the
        Save As... dialog, then no download will take place.</font></li>
      <li><font size="3">Added support for 5510 EVM board, based on a 5510
        prototype. Final release of the 5510 is not guaranteed to be compatible
        with this version of FlashBurn, but there's a really good chance it will
        be OK. Also, only tested JTAG cable connection.
        No testing was done using PCI interface, so don't get your hopes up too
        high....</font></li>
      <li><font size="3">Modified 6211/6711 support to allow more general
        writing to flash memory. No longer restricted to multiples of 128 bytes
        aligned on flash sector boundaries. This is done using a
        read/modify/write of flash sectors which will only be partially
        modified.</font></li>
      <li><font size="3">Added a Register-only switch to allow running the app
        at installation time without disrupting other installation procedures.</font></li>
      <li><font size="3">Added a readback switch for testing purposes.</font></li>
      <li><font size="3">Rearranged the installed FlashBurn folder by DSK board,
        rather than by function.</font></li>
    </ul>
  </li>
</ul>

<ul>
  <li>Version 0.10 Beta&nbsp; 30 January 2001<ul>
      <li>First Beta release</li>
      <li>Added Help and Context Help</li>
      <li>Increased timeout for FBTC download from 10 secs. to one minute to ease a problem with
        parallel port DSK connection and Windows 2000.</li>
      <li>Added support for 6711 DSK.</li>
      <li>Changed GUI:<ul>
          <li>The System Command field in the .cdd document is changed to Conversion Cmd File. In
            earlier versions, FlashBurn interpreted this field as a DOS command. With this release,
            FlashBurn will instead assume it is a command file (.cmd) for the CCS Hex Conversion
            utility, and will start up the appropriate hex converter (viz. hex6x.exe for C6000,
            hex500.exe for C5000) with this command file.</li>
          <li>Added a toolbar</li>
          <li>Only a single document may be open at a time<br>
          </li>
        </ul>
      </li>
    </ul>
  </li>
  <li><font size="3">Version 0.00.5</font>&nbsp; 02 January 2001 <ul>
      <li><font size="3">Initial release.</font></li>
    </ul>
  </li>
</ul>
<font size="3"><b>

<p>[ <a href="ReadMe.htm#Top">Top of Page</a> ]</b> <br>
</font></p>

<hr>

<h2><font size="3"><a NAME="Limitations"></a>6. Known Limitations</font></h2>

<ul>
  <li>FlashBurn will run if you are connected to a C2X DSP board, but no testing
    has been done, and no example FBTC code is provided.</li>
</ul>
<font size="3"><b>

<p>[ <a href="ReadMe.htm#Top">Top of Page</a> ]</b> <br>
</p>

</font>

<hr>
</body>
</html>