• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 103 subscribers
  • Views 206 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320C6455: Flashing external Flash Device with JTAG for TMS320C6455 processor

Daniel Wyss
Prodigy 30 points
Part Number: TMS320C6455
Other Parts Discussed in Thread: TMDSEMU200-U, TMDSDSK6455

Hello Ti-Support

Due to a PC crash we have lost our programming environment to Flash the Bootloader 
Program via JTag  to the external FLash of a TMS320C6455 processor.

The setup was as follows:

CCS 3.3 running under Windows XP.
XDS200 Debug Probe (TMDSEMU200-U) we also have XDS510USB and XDS110USB.

hex bootload program
FBTC645x Program to Flash the external Flash Device via FlashBurn  FBTC protocol.

In the meantime we have also found the FlasBurn Program working with CCS3.2.


1) We cannot reproduce the Windows XP environment because Windows XP is not supported any more.
    We have ported the FBTC645x Program ro CCS6.2.
    The FlashBurn Program also works under Windows 10 but it tries to start an instance of CCS3.2
    Unfortunately we did not succeed to install CCS3.2 under Windows 10.

    We have a copy of a valid XP installation on a Windows 10 system.
    But trying to start it gets an error: Library xerces-c_1_7_0.dll. is missing.
    And because this installation copy has not been registered communication with the FlashBurn program will probably fail.

  2) We have many devices to be flashed.
  3) We have many customers who wait for the devices.



What we need:

There are several possible solutions.

1) Any Flasing solution that can flash the external flash of the TMS320C6455 processor via JTAG connection under Windows 10.
2) Any Flashing solution that supports the FBTC protocol via JTAG that runs under Windows 10.

3) A CCS3.2 Version that runs under Windows 10 will probably work with the existing FlashBurn program.
    (Note the FlashBurn installation is also a copy of the XP installation but runs pretty well.
             Can the Flasburn Program be configured to communicate with a specific CCS version?)

4) A FlashBurn Program Version that installs and runs under Windows 10 and communicates with a valid CCS6.2 installation.

Note: We also have CCS10.4 and CCS11.2 installed but CCS > 8 does not support the TMS320C6455 processor .
          So the target CCS Version for a solution is CCS6.2

Note:
    A debugging License for CCS6.2 and the XDS200 Debug Probe (TMDSEMU200-U) will not solve the
    problem but will be very helpful.

    Currently we cannot load programs with the CCS6.2 debugger because of license restrictions.
    We got the CCSV6.2 free license. (XDS510 also fails only XDS110 works)

Kind regards
    Daniel Wyss

  • 0
    TI__Guru 72835 points

    Hello Daniel,

    I am going to send your thread to the CCS team first to see if they can help resolve some of your issues above (e.g., finding a way to get CCS3.2 or equivalent working again). They can send back to the processors team as needed.

    Regards,

    Nick

  • 0
    TI__Guru**** 421740 points

    Hello,

    Daniel Wyss said:
        Unfortunately we did not succeed to install CCS3.2 under Windows 10.

    Please see the below article regarding installing CCS 3.x under Windows 10. Note that this is NOT an officially supported environment.

    https://dev.ti.com/tirex/explore/node?node=A__AJFNkk2jUAyMIAplYIu0cg__ccs_devtools__FUz-xrs__LATEST

    Daniel Wyss said:
    Can the Flasburn Program be configured to communicate with a specific CCS version?

    FlashBurn is from a 3rd party company called SDS. I suggest contacting them for support:

    https://softwaredesignsolutions.com/

    Daniel Wyss said:
    4) A FlashBurn Program Version that installs and runs under Windows 10 and communicates with a valid CCS6.2 installation.

    Again, please contact SDS for further support.

    Daniel Wyss said:
    Note: We also have CCS10.4 and CCS11.2 installed but CCS > 8 does not support the TMS320C6455 processor .

    Current versions of CCS support C6455:

    Daniel Wyss said:
        A debugging License for CCS6.2 and the XDS200 Debug Probe (TMDSEMU200-U) will not solve the
        problem but will be very helpful.

    To obtain a license, please see:

    https://www.ti.com/design-resources/embedded-development/ccs-development-tools/ccs-faq.html

    Nick Saulnier said:
    They can send back to the processors team as needed.

    I will send this back to the processors team for questions #1 and #2.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru 72835 points

    Hello Daniel,

    I will give you time to test out things on your side. If you need additional assistance, feel free to reply back.

    Just to set expectations: C6455 is a very old part, and we can no longer answer hardware or software questions about the part as per the banner on the product page: https://www.ti.com/product/TMS320C6455 . So I can point you to the software and hardware pages that I am aware of, but we will not be able to offer much help beyond that.

    Regards,

    Nick

  • 0 in reply to Nick Saulnier
    Prodigy 30 points

    The actual solution of the "howto flash external flash ROM via EMIFA"
    problem is still missing in this forum article.

    I will add a short summary of how i got a working solution.

    1. We dropped restoration of WindowsXP
    2. We dropped using CCS3.3 (CCS3.2 was wrong in the documentation)
         We used CCS6.2 because we have a "full license" that is needed for the XDS200 DEBUG PROBE.
    3. A Copy (not installed) of FlashBurn was running perfectly under Windows 10
       However it tried to open an instance of CCS3.3 (The copy we had)
       There was no other version of FlashBurn available fom the Ti Support pages.
    4. So we also dropped using FlashBurn.

    Flasburn uses a FBTC Protocol Program in our case FBT645x.out (its for the TMS320C6455 processor)
    This program has all the knowledge about how to READ, ERASE and FLASH the external Flash ROM.
    The program sources are part of the examples for the Evaluation boards (in our case the TMDSDSK6455 Evaluation board)

    The FBTC program is loaded by the FlashBurn Program and gets commands by the debugger of what to do with the external Flash ROM.

    I changed the FBTC program to be independant of FlasBurn and CCS3.3 
    and loaded it using the Debugger of CCS6.2.

    Instead of getting commands via FBTC Protocol i changed the main program to load our binary to be flashed
    into some spare RAM, modify the ram according to our needs an burn the RAM contents to the external Flash ROM.

    The changes were easy to do because all the needed functionality allready existed in the example program
    I only had to use it in the way we needed. It took me two days of programming to implement the changes.
    I had to do some minor changes because the original  Flash Rom Type was not the same like we used in our Target.

    We solved 4 Problems:
    We got rid of Windows XP that is nomore supported by Microsoft.
    We got rid of FlashBurn that needs CCS3.3
    We got rid of CCS3.3 that can't be installed under Windows 10.
    We got a program that is able to Flash external Flash ROM of our Target according to our needs.
    (Actually the binary is a BootLoader that can load programs via Ethernet)


    Texas Instruments Tech Support and Texas Instruments E2E Forum did a good job
    in that they provided me in a kind way hints and don'ts that helped finding me the solution presented above.
    The case may be closed.

    Kind Regards
        Daniel Wyss