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.

DLPC350: GUI Program froze during firmware update; now can't connect to the device

Part Number: DLPC350

Hello,

I was trying to test out my IR DMD by uploading my own image image to the flash memory. I followed the instructions to combine the image with the latest firmware, which I downloaded from TI.com. I then tried to upload the firmware to the device. The GUI showed the firmware getting deleted successfully, but then at 4% of uploading the new firmware, the GUI crashed, becoming unresponsive for upwards of 30 minutes. Eventually I restarted the gui, hoping that I could simply restart the firmware upload process, but after this episode my computer now does not recognize the board, giving the "USB device not recognized" error, and the GUI program cannot connect to the device. The device LEDs look perfectly normal, so I surmise that it is still booting fine (I had the skip bootloader update box checked). What can I do to fix this? Do I have no option but using the JTAG tools?

  • Mark,

    Welcome to the E2E forums, and thanks for your interest in our DLP technology.

    Are you using Windows 10? I am aware of some driver issues users have encountered when operating on Windows 10. Please try again with a different PC/OS if possible.

    I hope this helps.

    Best Regards,
    Philippe Dollo
  • Hi Philippe,

    Thanks for the suggestion. I was indeed using windows 10, but after trying to connect to the board with a different windows 7 computer, I get the same issue. More specifically, the computer tries to install 3 drivers, one "USB Hub", one "USB Input Device" (This originally showed up as LC4500, but the text changed after it finished) which both succeed, and one "unknown device" which fails. I think this "unknown device" is the DLPC350 processor on the board. Thanks for your time.
  • Mark,

    It is possible that your first attempt to program the system corrupted your flash memory. I recommend you use JTAG to directly program the system before trying again.

    I hope this helps.

    Best Regards,
    Philippe Dollo