• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 1179 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.

TMDX570LC43HDK: "Hercules Safety MCU Demo" How to Debug

Etantonio
Intellectual 920 points
Part Number: TMDX570LC43HDK
Other Parts Discussed in Thread: HALCOGEN

Hy,

I'm working on a TMDX570LC43HDK board,

I would like to use as much as possible the "Hercules Safety MCU Demos"

regarding this what seems strange to me are the following points:

  1. when I import the CCS project from "C:\ti\Hercules\Hercules Safety MCU Demos\4.0.0\TMS570LC43x_target_sources" I obtain an almost empty project so I've to fill the folder "Halcogen" and "demo-app" manually, but it is ok, after this I can build the project and deploy it to the board
  2. Is not available the Halcogen project to import in Halcogen
  3. When I start the project in debug and then open the labview interface it seems to work fine but it is not, for example the led demo is not working (but I've not a communication error)
  4. If I reset the board with PORRST i can pilot the demo from the LabView interface but I've no more debug available
  5. When I click on Code Composer STudio on Labview interfaceit just open CodeComposerStudio

Finally If possible I'm interested to the Halcogen project and in debug the TMDX570LC43HDK C application driven from Labview interface.

Thanks

Antonio

  • 0
    TI__Guru 59540 points

    Hello Antonio,

    First, I would not recommend using this as a basis for your project. This is intended solely as a demo and the source is included to provide some general access for reference and for understanding. Also the versions of the SafeTI Diag library are not necessarily the latest and best. Is there a specific reason you have interest in the GUI and using it during your project or is merely to excite/command the demo to inject the faults and see the reaction?

    With that stated, I would recommend you download and use the latest SafeTI Diagnostic Library for your project. It also has a demo application but does not have the GUI interface or overhead from the UART messages. It also includes the project related files for import into Halcogen.

    I will address you points in case you continue on your chosen path:

    Etantonio said:
    when I import the CCS project from "C:\ti\Hercules\Hercules Safety MCU Demos\4.0.0\TMS570LC43x_target_sources" I obtain an almost empty project so I've to fill the folder "Halcogen" and "demo-app" manually, but it is ok, after this I can build the project and deploy it to the board

    I believe if you use the same project name as the directory in which the code is located, the files will also show in the project. However, without seeing what steps you tool in creating the project, I cannot know for sure the root cause.

    Etantonio said:
    Is not available the Halcogen project to import in Halcogen

    As this was something that the developer did not include in the distributed package, I am unable to locate it. 

    Etantonio said:
    When I start the project in debug and then open the labview interface it seems to work fine but it is not, for example the led demo is not working (but I've not a communication error)

    What indication is there that the application is working fine? Can you verify that the correct command message is being received by the target? This can be done by putting a break point in the switch in main to see if the LED demo function is called at all? I suspect there is an issue with the SCI use vs. the debug interface since they are shared by means of the FTDI chip.

    Etantonio said:
    If I reset the board with PORRST i can pilot the demo from the LabView interface but I've no more debug available

    This is good. It shows us that the included image file and programmed source are working together fine.

    Etantonio said:
    When I click on Code Composer STudio on Labview interfaceit just open CodeComposerStudio

    This may be due to the fact that the MCU Safety Demo is a legacy product. i.e., it is somewhat dated and was created with an earlier version of CCS. This may results in some issues where the later versions of CCS just don't seem to work exactly right.

  • 0 in reply to Chuck Davenport
    Intellectual 920 points
    Thanks Chuck,
    my scope is just to learn as more as possible about this TMDX570LC43HDK board,
    for example for me is not clear why I can't see any "safety" tab on Halcogen for my device.
    In any case I understand that is not so immediately to debug this safety application due to the fact that it is shared with SCI.
    Antonio
  • 0 in reply to Etantonio
    TI__Guru 59540 points
    Hi Antonio,

    I understand the confusion over the lack of a "safety" tab for the LC435x device. For earlier devices we did not have the SafeTI diagnostic library (SDL) and so we added this tab to allow for some support of safety functions at boot time. Once we developed the SDL, devices that were added after did not include this tabe since safety implementation/supporting code, was included in the SDL demo project and library. This prevents any conflicts between the implementation in Halcogen and the library code. Whether or not this was the right choice is another question and mainly moot at this point in time. My personal view was that the Safety tab was a lot more intuitive even if it was limited in scope to only boot time diagnostics but we can save those discussions for another day.