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.

DLPLCR90EVM: controller/DMD incompatible

Part Number: DLPLCR90EVM
Other Parts Discussed in Thread: DLPLCRC900DEVM, DLP670S, DLPLCR67EVM, DLPC900, DLP9000

Tool/software:

Hi Experts,
Good day!
I am posting this on behalf of the customer.
Here is the full details of the inquiry:
I just purchased the DLPLCR90EVM with the DLPLCRC900DEVM. We connected the cables, powered on the DLPLCRC900DEVM. The box labeled "controller/DMD incompatible" is checked. We tried switching to "normal" mode, but after a second, it automatically switches back to "Standby" mode
We cannot switch to pattern on the fly mode
We are using the recommended software bundle. The hardware is sold as a package, according to this page: https://www.ti.com/tool/DLPLCR90EVM
When the DLPLCRC900DEVM was powered on, the correct LEDs were lighting up, indicating normal function
I already instructed the customer to check the cables and DMD. They are properly installed but still having an issue. 
Thank you in advance for your support.
Best regards,
Jonathan

  • Hi Jonathan,

    On the left section of the GUI, I see that this is programmed with a firmware tag, "dlp670s_..."

    This firmware is expecting to see a DLPLCR67EVM rather than the DLPLCR90EVM, causing the controller to go to standby mode. Please have the customer follow these steps I have copied from another recent thread.

    When uploading the firmware to the DLPLCRC900DEVM, they must select both the primary and secondary firmware files at the same time. There is one *.img file per ASIC on board, with the DLPLCRC900DEVM having two total. More information may be found in the Section 3.9 of the user's guide on how to program the board.

    I modified the pictures and text to match the customer's case.

    "

    Let's try the following:

    1. Install a jumper to J12 BOOTHOLD. This puts the system into its bootloader mode. Please ensure the system is fully powered off and not receiving power before installation.
      1. Connect the controller board to the host computer and power the system on with a 12 V, 5 A power supply
      2. Close all instances of GUI and open a new instance
      3. If system comes up in standby and recognizes a DLPC900 plugged in, please select correct DMD type, as the GUI will not be able to determine DMD type while in bootloader mode.
      4. Go to firmware page click 'Browse..."and locate the firmware (*.img) file for the DLP9000. This is typically located under "C:\Texas Instruments-DLP\\DLPR900PROM-x.x.x" for Microsoft Windows machines, where "x.x.x" is just the firmware version.


      5. Delete the FlashLoaderCache directory if it exists. This is created every time you upload a firmware. The GUI caches it so new firmware loads flash quicker, but when building completely new firmware, this may cause errors. Delete this if building or flashing brand new firmware.
      6. Open the *OOB.img firmware files for your DMD. You must select both. Click "Upload" and wait until flashing and verification complete.
      7. When complete, the GUI will let you know programming was successful in the status bar. My image won't show this because I used the "Virtual Connection" option.
         "

    Regards,
    Michael Ly

  • Hi Michael,

    Thank you for your assistance. I'll get back if further assistance is needed.

    Best regards,

    Jonathan

  • Hi Jonathan,

    My pleasure. I'll mark this thread as "Waiting for Customer" until I get an update back from you so that we can confirm the customer's board is in a working condition once more.

    Regards,
    Michael Ly

  • Jonathan,

    Has the customer given any update on whether or not they were able to flash the new firmware and operate their boards?

    Thank you,
    Michael Ly

  • Hi Jonathan,

    It's been nearly a month since the customer has received help from us. I will take the silence as it resolving the issue, and I'll mark this thread closed.

    Thank you,
    Michael Ly