• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 27 subscribers
  • Views 1225 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Booting problem with Light Crafter version 1

Mahdi khamoushi
Prodigy 50 points

Hi,

I have a LCr version 1. Last week, even though I connected it to an improper power supply (5-V, 980-mA), it worked and after a short time it showed a red screen (D1 LED was blinking red and green). After that I pressed input selecting button several times and I saw RGB patterns and so on. However, after some times turning on and off, I mentioned that it stuck in booting final step. I changed the power supply to 5-V 2.25-A, but it was the same.

So, I tried to update the firmware using  DLP LightCrafter Firmware and Software Bundle - Windows V3.0 and Transcend 2GB micro SD card.

For lcr_dm365_v5_sd.dat the D1 LED remains red. The log in this case:

SD card boot and flashing tool for DM355 and DM365 Online manual: wiki.davincidsp.com/.../SD_card_boot_and_flashing_tool_for_DM355_and_DM365 based on TI DM35x FlashAndBootUtils 1.10 SFT, TI flash_utils and SpectrumDigital evmdm355, evmdm365 Compiled on Sep 17 2013 at 12:12:58 with gcc 4.4.1 SYSTEM->DEVICE_ID=0x8B83E02F sdcard_init MMCSD_cardIdentification 00000000sdcard_read sdc_src=0x00001000 dst=0x80000000 len=0x00000200 dst + len=0x80000200 *data0=0xA1ACED00 flasher_data=0x00060000 sdcard_read sdc_src=0x00068000 dst=0x80000000 len=0x00000200 dst + len=0x80000200 *data0=0x00010000 check_pattern_123 sdcard_read sdc_src=0x000D0000 dst=0x810AD000 len=0x00000200 dst + len=0x810AD200 *data0=0x61636473 sdcard_boot u-boot sdcard_read sdc_src=0x00080000 dst=0x81080000 len=0x0002D000 dst + len=0x810AD000 *data0=0xEA000012 kernel sdcard_read sdc_src=0x000E0000 dst=0x80700000 len=0x00300000 dst + len=0x80A00000 *data0=0x56190527 root FS sdcard_read sdc_src=0x00560000 dst=0x82000000 len=0x00300000 dst + len=0x82300000 *data0=0x08088B1F U-Boot 2010.12-rc2 (Sep 16 2013 - 13:35:08) Cores: ARM 297 MHz DDR: 243 MHz I2C: ready DRAM: 128 MiB GPIO Config NAND-WP : GPIO76 as output (1) GPIO Config DVI-I2C-EN : GPIO73 as output (0) GPIO Config DVI-ENA : GPIO74 as output (0) GPIO Config CAM-RESETZ : GPIO102 as output (0) GPIO Config CAM-RESETZ : GPIO102 as output (1) GPIO Config CAM-DENABLE : GPIO93 as output (1) MMC: davinci: 0 Using default environment Net: No ethernet found. Hit any key to stop autoboot: 0 LCr > LCr > LCr > LCr > U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>>

For lcr_dm365_v5_nand.dat the D1 LED changes from red to green but the screen is still stuck. The log in this case:

SD card boot and flashing tool for DM355 and DM365 Online manual: wiki.davincidsp.com/.../SD_card_boot_and_flashing_tool_for_DM355_and_DM365 based on TI DM35x FlashAndBootUtils 1.10 SFT, TI flash_utils and SpectrumDigital evmdm355, evmdm365 Compiled on Sep 17 2013 at 12:12:58 with gcc 4.4.1 SYSTEM->DEVICE_ID=0x8B83E02F sdcard_init MMCSD_cardIdentification 00000000sdcard_read sdc_src=0x00001000 dst=0x80000000 len=0x00000200 dst + len=0x80000200 *data0=0xA1ACED00 flasher_data=0x00060000 sdcard_read sdc_src=0x00068000 dst=0x80000000 len=0x00000200 dst + len=0x80000200 *data0=0x00010000 check_pattern_123 sdcard_read sdc_src=0x000D0000 dst=0x810AD000 len=0x00000200 dst + len=0x810AD200 *data0=0x73616C66 nand->devID=0x000000F1 nand->dataBytesPerPage=2048 nand->pagesPerBlock=64 nand->numBlocks=1024 nand_size=134217728 Erasing block 0x00000001 through 0x000003FB. Bad Block 0x0000029E Erasing is skipped sdcard_install * Flashing UBL sdcard_read sdc_src=0x00070000 dst=0x80001248 len=0x00007800 dst + len=0x80008A48 *data0=0xEE190F31 Erasing block 0x00000001 through 0x00000001. Writing header data to Block 00000001, Offset 00020000 * Flashing u-boot sdcard_read sdc_src=0x00080000 dst=0x81080000 len=0x0002D000 dst + len=0x810AD000 *data0=0xEA000012 Assuming GNU UBL UBL_GNU_ENTRY=0x00000100 Erasing block 0x00000019 through 0x0000001A. Writing header data to Block 00000019, Offset 00320000 * Flashing kernel sdcard_read sdc_src=0x000E0000 dst=0x80700000 len=0x00300000 dst + len=0x80A00000 *data0=0x56190527 nand_write dst_nand=0x00400000 block_idx=0x00000020 len=0x00300000 Erasing block 0x00000020 through 0x00000038. * Flashing Root FS sdcard_read sdc_src=0x00560000 dst=0x82000000 len=0x00300000 dst + len=0x82300000 *data0=0x08088B1F nand_write dst_nand=0x00800000 block_idx=0x00000040 len=0x00300000 Erasing block 0x00000040 through 0x00000058. 1 - boot; 2 - install; 3 - erase flash, 4 - nand boot, 5 - test first 16MB of RAM u - install ubl only, e - flash env variablesd - nand flash dump DONE 1 - boot; 2 - install; 3 - erase flash, 4 - nand boot, 5 - test first 16MB of RAM u - install ubl only, e - flash env variablesd - nand flash dump DONE 1 - boot; 2 - install; 3 - erase flash, 4 - nand boot, 5 - test first 16MB of RAM u - install ubl only, e - flash env variablesd - nand flash dump DONE 1 - boot; 2 - install; 3 - erase flash, 4 - nand boot, 5 - test first 16MB of RAM u - install ubl only, e - flash env variablesd - nand flash dump DONE

When I start it on NAND Flash itself,  the situation is the same as previous time, except that D1 changes faster to green. Corresponding log:

nand_size=134217728 u-boot src=0x00320800 nand_read block_idx=0x00000019 page_idx=0x00000001 len=0x0002D000 block=0000001A kernel src=0x00400000 nand_read block_idx=0x00000020 page_idx=0x00000000 len=0x00300000 block=00000038 file-system src=0x00800000 nand_read block_idx=0x00000040 page_idx=0x00000000 len=0x00300000 block=00000058 Jummping to nand bootloader U-Boot 2010.12-rc2 (Sep 16 2013 - 13:35:08) Cores: ARM 297 MHz DDR: 243 MHz I2C: ready DRAM: 128 MiB GPIO Config NAND-WP : GPIO76 as output (1) GPIO Config DVI-I2C-EN : GPIO73 as output (0) GPIO Config DVI-ENA : GPIO74 as output (0) GPIO Config CAM-RESETZ : GPIO102 as output (0) GPIO Config CAM-RESETZ : GPIO102 as output (1) GPIO Config CAM-DENABLE : GPIO93 as output (1) MMC: davinci: 0 Using default environment Net: No ethernet found. Hit any key to stop autoboot: 0 LCr > LCr > LCr > LCr > U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> U-Boot 2010.1>>>> 

Note: LED D3 and one which is near power socket are always green during booting procedure. 

What may be the problem regarding the logs?

Is hardware damage possible because of suing an improper power supply at first?

Is  DM365 v5 suitable for Light Crafter version 1?

Thanks a lot for your time.

Best regards,

Mahdi.

 

  • 0
    TI__Mastermind 30600 points
    Hi Mahdi,

    Welcome to the DLP Forums! Sorry you're having difficulty with the Lightcrafter. I'd like to clarify your problem if I can. You're having issues with the LCr getting stuck during booting. Currently, you're using a 5V, 2.25A supply (which should work).

    A couple questions for you:
    - At any point have you been able to connect the LCr to the GUI?
    - How are the logs you provided being created? Are these logs from UART or JTAG or....?
    - Is D1 solid or blinking?

    It is possible that you've damaged your system with the wrong power supply. The FPGA on board is sensitive to power up and power down and being outside of the spec could have damaged it.

    Thanks,
    Paul
  • 0 in reply to Paul Goedeke
    Prodigy 50 points
    Hi Paul,
    Thanks for your prompt replay.
    - Regarding to your question, I did not to connect the LCr to GUI when it was working. After booting problem, I tried but it was impossible.
    - I got logs with UART cable (RS232) using "Tera term" software.
    - Before booting problem, D1 was blinking, but now it is solid. When I start with NAND flash or from micro SD with dm365_v5_nand.dat, it changes from red to solid green during booting, but screen does not change to RGB pattern.

    How can I find out if FPGA is damaged? What should I do in this case?

    Thanks a lot.
    Mahdi.
  • 0 in reply to Mahdi khamoushi
    TI__Mastermind 30600 points
    Mahdi,

    Let me do a little digging and I'll get back to you.

    Thanks,
    Paul
  • 0 in reply to Paul Goedeke
    TI__Mastermind 30600 points
    Mahdi,

    The FPGA shouldn't be damaged if you can get get any booting at all (even if it gets stuck). Are you trying to boot the device with anything else plugged into it (HDMI, etc)? Try removing those connections and try again.

    Have you done any modifications to the EVM?

    Paul
  • 0 in reply to Paul Goedeke
    Prodigy 50 points
    Dear Paul,

    I mostly tried to boot the LCr without any other cables. But it did not work (except the first 3 times that it worked).

    Regarding modification, one of our colleagues used to work with this LCr several months ago. I think he removed the optical part once. But when I got the LCr, it was not modified. Anyway, LCr was working perfectly, when I tried to work with it for the first times! So it seems that it does not have anything to do with previous modifications, does it?

    Mahdi.
  • 0 in reply to Mahdi khamoushi
    TI__Mastermind 30600 points
    Mahdi,

    If you weren't able to get the LCr to connect to the GUI, then it's never really been "working." If the LCr had the optics removed and reattached, can you make sure the connections are good? Perhaps there is a bad connection or poor solder joint.

    Can you try some of the advice in these threads?

    Helping decode the LEDs:
    e2e.ti.com/.../323798

    I think this one would be particularly useful:
    e2e.ti.com/.../1356356

    General help:
    e2e.ti.com/.../345676

    Thanks,
    Paul
  • 0 in reply to Paul Goedeke
    Prodigy 50 points
    Dear Paul,

    Thanks a lot for your comments.

    Yesterday, something strange happened. I decided to view console massages, again. So, I connected UART cable to my laptop. But this time, as my laptop does not have RS232 port, I used a USB to RS232 adopter and connected it to USB port. When I turned the LCr on, I unexpectedly saw that it finished the booting process and RGB patterns appeared!

    I tried several times. It finishes booting when it is connected by this cable to laptop, but it does not finish booting if I disconnect UART cable from laptop!

    I think the problem should be related to power supply. But one point is still not clear for me. Why it finished booting for the first time I had it, even by using improper power supply (980 mA)? But now it does not finish booting, even with proper power supply (2250 mA)!
    Is possible that there is another problem, which I could not find it?
    Will the problem get solved if we use 3-A power supply?

    Thanks,
    Mahdi.
  • 0 in reply to Mahdi khamoushi
    TI__Mastermind 30600 points
    Mahdi,

    I would definitely try a 3A supply and see what happens. A good power supply typically solves this issue.

    Paul