• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 213 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.

DLPLCRC900DEVM: DLPLCRC900DEVM and DLPLCR90EVM Cannot Connect to GUI

TI-CSC
Genius 14120 points
Part Number: DLPLCRC900DEVM
Other Parts Discussed in Thread: DLPLCR90EVM

Tool/software:

Hello E2E Experts,

Good day.

Our lab has been used DLPLCRC900DEVM and DLPLCR90EVM pair. However, suddenly the Lightcrafter9000 shows disconnected status from few days ago.
What I tried so far is switching cables and PC, J11 capping for bootloader, reinstalling SW and FW.
Mainboard has a good heart beat flashing, and display board shows default pattern when powered on.
The screenshot image of the lightcrafter9000 status display is attached here. 
Could you please diagnose the problems? 
 
Regards,
TICSC
  • 0
    TI__Guru 54705 points

    Hello Jonard,

    Have they restarted the host computer, or another USB cable?  That is the first place to start.

    Fizix

  • 0 in reply to Fizix
    TI__Genius 14120 points

    Hello Fizix,

    Good day.

    Yes, have tried restarting the host computer and changing USB cable.

    Any other advise for us?

    Regards,

    TICSC

  • 0 in reply to TI-CSC
    TI__Guru 54705 points

    Hello TI-CSC,

    Since you were able to reprogram by putting the bootHOLD jumper on, then it must be showing "connected" for the reprogramming to work.

    Now try the boothold jumper again except this time set the firmware page as follows:

    Complete image and do NOT skip the bootloader area.

    Fizix

  • 0 in reply to Fizix
    TI__Genius 14120 points

    Hello Fizix,

    Good day.

    I’d like to clarify what I’ve done and what I’m seeing now:

    • Previously, setting the BootHOLD jumper on J11 allowed me to reprogram the board without issues.

    • Suddenly, the system began reporting “Disconnected,” despite power and USB being connected.

    • I tried the BootHOLD procedure again—jumper on J11 → power cycle → connect USB → upload firmware—if this procedure including uploading firmware is the correct procedure of bootHOLD jumper.

    Could you confirm whether my understanding of the BootHOLD reprogramming flow is correct? If it is, what’s the likelihood that the USB port or related components have failed?

    Regards,

    TICSC

  • 0 in reply to TI-CSC
    TI__Guru 54705 points

    Hello TICSC,

    If the system no longer shows connected when the BootHOLD jumper is on then the FW will have to be loaded via JTAG.  This usually indicates that the bootloader has somehow become corrupted.  Please refer to the DLPU102 [https://www.ti.com/lit/ug/dlpu102/dlpu102.pdf] section 4.12 JTAG Flash Programming.

    You will need to obtain the FTDI USB to JTAG chip and make the programming cable as described there.  Follow the instructions in the guide.

    Fizix

  • 0 in reply to Fizix
    TI__Genius 14120 points

    Hello Fizix,

    Good day.

    If I understand correctly, you meant the BootHOLD jumper can restore connectivity to a system that is currently unresponsive? When I first set up the system, I recall it connected automatically as soon as the cables were plugged in, regardless of whether the BootHOLD jumper was used.

    Could you kindly confirm whether the initial connection status is irrelevant, and that the BootHOLD jumper can indeed be used to recover a non-responsive system? If so, I will proceed with purchasing the FTDI USB as per your instructions.

    Regards,

    TICSC

  • 0 in reply to TI-CSC
    TI__Guru 54705 points

    Hello TICSC,

    I am saying that if the system does not connect when the BootHOLD jumper is installed, then the BootLoader is corrupted or the FLASH is damaged.  The first item to try is to use the FTDI UM232H.

    So in answer to the question.  The initial connection showed that everything was working.  But the subsequent connection that did not connect even with the BootHOLD jumper indicates that the bootloader is not working (possibly corrupted).

    Sometimes it is the case that the application is corrupted and will not connect after the application starts.  In that case it will connect when the BootHOLD jumper is installed.  This case allows the firmware to be reloaded over USB.

    In your case it seems the BootLoader is corrupted and requires using JTAG (UM232) to reload.  I have run across this several times.  Usually this restores it.  I have had only one board where the FLASH was defective.

    Fizix