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.

Lightcrafter Evaluation Board doesn't respond

To whom it may concern,

We are using the Lightcrafter with a Laser, therefore we removed the lightengine which worked quite nice for a few days. But after uploading an image with Matlab (always worked till this point), the image suddenly began to flicker. We tried rebooting, but it got stuck at the last bootscreen. After some more booting attempts the image now is always the same, it looks like the mirrors are randomly set to on- or off-state.

We tried to reinstall the firmware, the GUI connects but prompts "Command FAILED". The Firmware version are shown as:

DM365: 5.0

FPGA: XXX.XXX

MSP430: XXX.XXX

Updating the FPGA seems to work, since it says "Command SUCCESS", but its doesn't change anything. Updating the MSP430 doesn't work, its says "Command FAILED".

The LEDs seem to be ok. The one next to the DM365 blinks green/red, the other one on the top board is green, as is the one on the lower board.

The LightCrafter used ~0.2 A before, since the flickering it uses ~0.6A at 5V. The Voltage at the test points on the lower board are all as they are supposed to be.

We also tried the UART log and followed the instructions like this http://e2e.ti.com/support/dlp__mems_micro-electro-mechanical_systems/f/850/p/176873/701728.aspx , but didn't get any information in tera term.

The last thing we tried was the I2C Software Reset, but just as our other attempts this had no effect. Here we are not completely sure we sent the command correctly, since it was the first I2C command we used, before we only used TCP/IP with USB.

I would appreciate your assistance since we have a deadline approaching shortly for which the DLP needs to function.


Thank you,

Dr. Benjamin Deissler

University of Ulm, Institute for Quantum Matter

  • Hello Dr. Benjamin,

    Welcome to TI DLP E2E Community!

    Looking at the problem description, my strong guess is that the DM365 fimrware somehow got corrupted in the process of uploading an image from Matlab. The DM365 code basically talks to FPGA and MSP430 to send I2C commands as to get the Version back which is then displayed in the gUI when you say "get Version". This code running on DM365 also is responsible for sending I2C commands to read the splash images while the board is booting up.

    However, if the DM365 firmware is now corrupted, then none of the I2C writes or reads will work and I think that is what is happening in this case.

    You will have to re flash the NAND with DM365 firmware using the instruction in the section 2.13.2.2 of the LighTcrafter Users guide. Then reboot the system and try connecting it to the GUI and read the Versions.

    One other thing to try is making sure that connections between the driver board and the light engine are intact while you replaced the LEDs with the Lasers. You can refer to the following E2E post for the instructions to disassemble and reassemble the boards and check the connections:

    http://e2e.ti.com/support/dlp__mems_micro-electro-mechanical_systems/f/850/t/322842.aspx

    Let me know if you have any more questions. 

    Regards

    Manasi

  • Hello Manasi,

    Thank you for your response. I tried installing the DM365 firmware into the NAND and directly booting from the SD card. Either way no bootscreen appears and the GUI still displays only the DM365 firmware version. I also disassembled and reassembled the LightCrafter to check the connections, yet I can't check the connection to the light engine, since it was completely removed. I followed this post to remove it: http://e2e.ti.com/support/dlp__mems_micro-electro-mechanical_systems/f/850/t/159950.aspx

    Regards,

    Dr. Benjamin Deissler

    University of Ulm, Institute for Quantum Matter

  • Hi,


    Can anyone help us with this issue? We have not gotten a response even after 3 weeks and our deadline is approaching fast.


    Thanks,

    Dr. Benjamin Deissler

    University of Ulm, Institute for Quantum Matter

  • Hello Benjamin,

    If the Lightcrafter always worked fine with the LEDs and stopped working suddenly when you replaced the LEDs with Lasers, then I suspect that the problem could be due to an improper driver for the Laser.

    Have you modified the driver circuit for the lasers? I would encourage you to look at the reference schematics for Lightcrafter's driver board to understand how the LEDs are driven.

    Also, it would be helpful if you could send us the schematics for your driver board and the various voltage values (Vbias,  Vreset) used on your board.

    Regards

    Manasi

  • Hello Manasi,


    I'm afraid I was unclear about describing the modification we performed. I took a photo to make clear how we are using the LightCrafter. As you see we simply removed the light engine according to the directions, no other changes were made. The laser and its controller are independent of the LightCrafter. The board worked fine with the LEDs and also initially after removing the light engine for several days.

    As mentioned previously, after uploading an image with Matlab, the image suddenly began to flicker. We tried rebooting, but it got stuck at the last bootscreen. After some more booting attempts the image now is always the same, it looks like the mirrors are randomly set to on- or off-state.

    I would appreciate your help in solving this issue, or discussing alternate repair possibilities.

    Thank you,

    Dr. Benjamin Deissler

    University of Ulm, Institute for Quantum Matter

  • Hi,

    Did you manage to solve this issue? I am facing the same (even worse) problem with my set up. I removed the (LED) ribbon cable and it does not boot anymore.

    Thanks for answering,
    Pepe
  • Hi,

    An update for this e2e thread as of Dec 21st, 2015:

    The LightCrafter (with version DM365 5.0, FPGA 2.6.43, MSP430 3.0) boots and communicates even after removing the RGB LED flexcable from the J9 connector.

    Pepe (user4566018) was able to solve the problem himself and shared his findings on this other e2e thread.

    Regards,

    A214529