• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 672 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMDXRM46CNCD communication through FTDI chip

Jules Patru
Intellectual 380 points

Hi,


I am currently writing some source code linked to TPS and safety initialization of an RM46 Hercules chip.
I use the TMDXRM46CNCD control board to debug my source code. As per my first tests, I initialize and handle the TPS as per expectations (ACTIVE state is reached as it should, stop feeding the watchdog makes the MCU reset, ...).

My investigation next step was to uses the serial communication between the Hercules microcontroller and a PC. However, I remarked that I am not able to see the virtual COM port among the list of available peripheral in Windows.

I have checked that:
 - there is no DIP switch to enable/disable the FTDI chip,
 - there is no particular TPS configuration to reach to enable the FTDI chip.

For your information, I also tried to disable the source code linked to TPS companion chip and trying running my software in an other eval board (TMDXRMHDK) and the COM port was working as per my expectations.

Could you please tell me where I am wrong? Which kind of initialization could I miss?

Thanks for help,

Jules

  • 0
    TI__Guru 72500 points

    Make sure that SW1-H is in the off (up) position as shown in this diagram:

  • 0 in reply to Bob Crosby
    Intellectual 380 points
    Hi Bob,

    I missed your reply !!!
    I just tried the configuration you mentioned without success.

    However, I tried somehting more that finally solved my issue.
    Until now, i was able to see the board among my windows HW peripherals under the reference "XDS100 Channel A" and "XDS100 Channel B"; I uninstalled the corresponding driver for both references, then disconnected the board from my computer and finally reconnect it.
    Now I can see the COM port initialized by FTDI driver...
    Looks like it was more a windows driver issue.
    Good to know :)

    Anyway, thanks for your reply and sorry to provide you feedback only now...

    Jules