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.

Hercules Launchboard FTDI and sefty demo problem

Other Parts Discussed in Thread: TMS570LS0432, TMS570LS1224

I have a similar problem as this guy https://e2e.ti.com/support/microcontrollers/hercules/f/312/t/323472. I just need a right .xml file for a Hercules Launchpad TMS570LS0432 (FTDI FT2232HL) for FT Prog.

Another problem is: if I open Hercules Safety MCU Demos it opens but it doesn't find the board (launcpad TMS570LS1224) I didn't try the ls0432 yet. It says

No Demo Boards Found.
Plug in a Hercules Development Board and try again.

but the board is connected with a loaded program from a (C:\ti\Hercules\Hercules Safety MCU Demos\4.0.0\TMS570LS1x_target_sources) source files.

  • Hello Mihael,

    Were you able to run the application on the other thread to verify there was no information programmed into the FTDI chip on the LS0432 Launchpad? Can you post some screen shots of the results?

    The issue with the Safety MCU Demos may be a version issue. You should install the latest version to make sure it has support for the LS122X Launchpad. You can get is here: www.ti.com/.../hercules_safety_mcu_demos demo&tisearch=Search-EN-Everything

    If you already have version 4.0.0 of the Safety Demo SW, can you startup CCS and see if you can connect to the device in a debug session?

    As an alternative to the LabView based safety demo that you are trying to run, have you tried the Project 1 out of box safety demo code that is stand alone (No PC interface). A description of how to use it (including reinstalling the binary) is located here: processors.wiki.ti.com/.../LAUNCHXL2_TMS57012:_Project_1
  • about LS0432: FTDI chip was empty (with FFFFFs shown in FT Prog and error -151 in CCS) and it didn't find right drivers. Next thing: I flashed a FTDI chip with a wrong .xml file. Now my launchpad recognises drivers (now I have drivers from texas instruments in a device manager) but when I want to connect it gives me an error: Error connecting to the target:
    (Error -183 @ 0x0)
    The controller has detected a cable break far-from itself.
    The user must connect the cable/pod to the target.
    (Emulation package 6.0.83.0)
    So I think that I need a right .xml file. But I can't find it. I also noticed it must be special .xml for ftdi chip. I cannot import every .xml file into the FT prog.

    about LS1224: I have installed the latest verson and I have already launched the Project 0 and the Demo Project 1 and it works but I want to try this safety demo sw. Where can I find source code for the Project 1? I just found an .out file but I want to see the code :)

  • Hello Mihael,

    I'll forward your issue with the FTDI chip to our expert on this device so that they can guide you through getting this up and running.

    For the Safety Demo with the LS1224 Launchpad, the developer of the LS1224 LP has stated that this was not natively supported when the board was released so I am not certain about what might be going on with it. I will forward this to the developer of the safety demo application and see if they might be able to assist.

    In regard to the source for project 1 on the LS1224 LP, the source was never authorized for release so it is not provided as you have noted. However, there is a similar project on the LC4357 LP and the wiki on this LP has instructions how to build the project and source. Basically, the project uses the SAFETY Library to implement the safety functions in the demo so you would need to download the source for the project and install the safety library (with source) and link the two project. Because the project is developed for the LC4357 Launchpad, you would need to port to the 1224 to build and run on your Launchpad if this is what you want to do. Otherwise, it would allow you to, at least, see how the safety library is used and get a framework for the project. The LC4357 LP wiki is located at this link: processors.wiki.ti.com/.../LAUNCHXL2-570LC43

    Hope this helps.
  • Mihael,

    I have done some investigation and the source code and application for the MCU Safety Demo is not compatible with the LS1224 Launchpad since it uses the XDS110 emulator on board. It was designed to work with the HDKs and other evaluation modules/kits using the XDS100v2. This is why it is showing up as unrecognized by the demo software.
  • Thank you for all your answers.

    I just need a little help with the LS0432. I need that .xml file to flash the FTDI chip. 

    Or do you have another solution to make this launchpad work?

  • Hello Mihael,

    I apologize for the delay in getting you a solution. I have reached out to my colleagues once again to see if they can help. I know in at least one case, they are currently traveling so it might take some time for them to get back to you. If time is of the essence, you may want to consider reaching out to the distributor or point of purchase to work out an exchange for a new Launchpad with a properly programmed FTDI device.
  • Michael,

    You can look here: processors.wiki.ti.com/.../XDS100

    It explains how to build your own XDS100v2 - but you could follow the FTDI programming steps for the FTDI chip on the launchpad.

    Don't use the SXVF file for the CPLD that is included in the reference design though -- so in other words try not to program the Xilinx device too. (It would be a different program on the PC side, and different step - so you can pretty easily avoid doing this by mistake. Just be aware when you read through the instructions that you should first try to avoid this step of the CPLD).

    If you reprogram the FTDI chip but the emulator doesn't work then you would try to program the CPLD but the file that is included in the reference design you will download is for the VQ44 package.
    You would need to use the Xilinx tools (WebPack ISE) to rebuild this for the BQ56 BGA package that the launchpad used. And you would need to update the pin locations in the RTL source file to match the launchpad board. Alternatively someone here may be able to provide the correct SXVF file for the launchpad - but I think this is probably who Chuck is reaching out to.

    In any case hopefully it's only the FTDI EEPROM that was erased and hopefully you can skip the CPLD programming step .. I think the safety demos were doing something to the EEPROM on that FTDI chip for sort of a board ID so hopefully it's all that got erased.

    -Anthony