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

RM48 USB Dev Kit MCU Safety Demo Comms Problem in Windows 7 Pro under VMWare

Stephen Braham
Prodigy 20 points

Hi, I've installed the RM48 USB key Dev Kit software (full install, Windows 7 Pro image under VMWare under Mac OS X). Installed as Admin, with UAC off, as advised. The RM48 USB board then registers fine with Windows 7 when plugged in. When I run the MCU Safety Demo app (as Admin), the audodetect runs ok. When I go to install any demo, the flash is updated, and JTAG lights flash, and HET15 and HET14 LEDs come on, and I get a SUCCESS message. Reset as told, and then try to execute the demo. For each demo, nothing happens. For the Safety features demo, the two self-tests both generate a "comms lost with microcontroller" message, and the demo advises a reset. Try that, but with no improvement. Even I go back into the same demo, the demo software says the demo code is not on the microcontroller flash (even with the SUCCESS message earlier), and asks to reflash. Same situation after that reflash. 

Best Wishes,

Steve

  • 0
    TI__Expert 7650 points

     

    Hi Stephen,

    Sorry that you are seeing this issue with the demos.  I have forwarded your question to one of our experts.

    A simple question, for you:  which RESET are you using?  Be sure to use the PORRST switch when you reset the board per the demo instructions.  This is the switch that is closest to the front (towards the SD connector) of the board.

    Best Regards,

    Brian

  • 0 in reply to Brian Fortman
    Prodigy 20 points

    Thanks Brian,

    Yup, been using PORRST (indeed, tried both!). Interestingly, I get exactly the same pattern of start lights that I got right out of the box, when I do that, which suggests to me that Flash hasn't really been written to by the loader. Also, even what should be the smallest demo code takes several minutes transferring to the MCU before the Success message, which seems improbable for JTAG via the fast FTDI USB chip on-board. I've noticed what looks like both a solder spot and a second spot that could be flux or even a melt mark on that FTDI chip, so it could be possible that there's been a manufacturing problem on this particular unit, with damage to the FTDI chip, which would probably be consistent with this behaviour, eh?

    Will be bringing up a vanilla Vista Ultimate box in the lab today (no VMWare), just to eliminate the possibility that it's some issue with, say, FTDI, JTAG, etc, drivers running in Windows 7 under VMWare.

    Best Wishes,

    Steve

  • 0 in reply to Stephen Braham
    TI__Guru**** 197306 points

    Hi Steve,

    Have you solved the problem with the USB stick COM port? Since you can program the demo code to the flash, the FTDI chip should be fine. It may be caused by the COM port configuration on your local machine (FTDI driver). Thanks

    Regards,

    QJ.