• State Resolved
  • Locked Locked
  • Replies 23 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 2305 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.

DLP2010EVM-LC: I installed a new custom DLP engine, but the EVM does not work properly.

JONGKEUN YUN
Prodigy 155 points

Part Number: DLP2010EVM-LC

Currently, I am testing the operation of various DLP engines with DLP2010EVM-LC.

The main phenomenon is that the changed DLP engine does not operate differently from the existing Ti DLP engine.

1. EVM <- new DLP engine (DMD, LED cable connection)
2. Power cable connection, power on
3. DLP engine does not work
4. Get EVM information on Information
     Error message:
     Get video information Error!
     'Read Operating Mode Select' command execution failed.
     Error Details: Please make sure that the system is connected, power on, and the setting are correction.
5. Error message on EVM: !EVM Status: Connected, powered off
6. Event on Debug:
     Get EVM Information Error!
     'Read Short Status' command execution failed.
      Error Details: Please make sure that the system is connected, powered on, and the settings are correct.
      Warning! EVM DMD Device ID does not match GUI Product ID!

Please advise on what can I do to deal with this phenomenon.

YUN

  • 0
    TI__Genius 10925 points

    Hi JONGKEUN, 

    Welcome to TI E2E Forums! Kindly give us some time to look at this and get back. Thanks for your patience!

    Thanks & Regards,

    Hirak.

  • 0 in reply to Hirak Biswas
    TI__Genius 9971 points

    Jongkeun,

    Can you check if the EVM working properly with the previous optical engine?

    Also, do you know the part number of the DMD which is used in the optical engine that is not working?

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    Prodigy 155 points

    Yes, EVM worked properly with the previous optical engine.

    DMD part number is DLP ® 0.2 WVGA DMD(u206a DLP engine, elepn company)

    Regards,

    Yun

  • 0 in reply to Hirak Biswas
    Prodigy 155 points

    Ok thanks a lot.

  • 0 in reply to JONGKEUN YUN
    TI__Genius 9971 points

    Yun,

    Can you please let us know the firmware version that you are currently using?

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    TI__Genius 9971 points

    Yun,

    If you are using the latest firmware (v8.0.0), then that firmware will work only with LC DMDs (part number - DLP2010LC)

    Kindly refer to the following e2e FAQ for more information regarding this - https://e2e.ti.com/support/dlp/f/94/t/923731 

    Let me know if you have any additional queries. 

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    Prodigy 155 points

    So, where can I download the firmware version for the previous DMD part number to work?  Does it work if it is version 7.x?

  • 0 in reply to JONGKEUN YUN
    Prodigy 155 points

    The picture above is the pin mapping sent by the manufacturer.
    Can the pin mapping be specified when applying the previous firmware requested above?

    In conclusion, what is expected is that we need a firmware that can be driven by DLP2010EVM-LC + DLP2010 0.2 DMD + pin mapping3.

  • 0 in reply to JONGKEUN YUN
    Prodigy 155 points

    Also, I am curious what the Option means in Pin Mapping.

    Yes; Each data path? Or the DLP resolution change according to the option, etc.

  • 0 in reply to JONGKEUN YUN
    TI__Genius 9971 points

    Yun,

    1. Yes, I can share the required firmware with you ( DLP2010EVM-LC + DLP2010 0.2 DMD + pin mapping3). Please share you email ID linked to myTI account.

    2. Also, I am curious what the Option means in Pin Mapping. >> Each option corresponds to a different datapath.

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    Prodigy 155 points

    My email is teamdoc@cowellmedi.co.kr

    I update New informations

    DMD 　 DLP2010A, 0.2" DMD
    DLPC DLPC3470
    PMIC/LED Driver DLPA2005
    EVM DLP2010EVM-LC(7.3.1)
    Pin mapping Option 3
    Firmware version Cannot be confirmed because communication is not available
    DLP Engine Ti Asiaoptic DLP(Option 3)
    　 Iview 830L-ZB
    　 Elepn U206A
    GUI 　 V2.2.0.6
    Problem 1 Host IRQ does not go low (compared to normal operation Asia DLP)
    ASIC auto-initialization failed?
    　 2 DMD Device ID Matching X
    Get EVM Information Error!
    'Read Short Status' command execution failed.
    Error Details: Please make sure that the system is connected, powered on, and the settings are correct.
    Warning! EVM DMD Device ID does not match GUI Product ID!
    　 3 Firmware update unavailable
    　 3-1 Update firmware
    step 1/3-Erasing flash data has been running for a long time and does not move to the next step
    　 　 Firmware Update Failed

    Normal operation DLP and LED status comparison
    　 D1 Host IRQ D2 Resetz D3 PROJ_ON
    Ti(asia DLP) OFF OFF ON
    E Company ON OFF ON
    i Company ON OFF ON

    Please let me know how I can do it in this matter.

  • 0 in reply to JONGKEUN YUN
    TI__Genius 9971 points

    Yun,

    Thanks for the detailed explanation. I will reach out to you soon.

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    Prodigy 155 points

    Dear 

    Thanks for the kind answer.

    We look forward to your solution.

    In addition, we have measured the voltage and waveform of the Test Point using our equipment this morning, and we will share it with you.

    1. Comparison between Ti's ASIA Optic Engine and Elepn.

    Ti社 Asia.pdf

    2. It also shares voltage measurements for each TP of the DLP2010EVM-LC (3470).

    EVM Power ON 　 　 　 EVM Power OFF 　 　 　
    Test Point Asia elepn iview Test Point Asia elepn iview
    VBIAS 12.48V 4.3V 4.321V VBIAS X X X
    VOFFS 9.946V 4.3V 4.319V VOFFS X X X
    VRST -7.765V 408mV 399mV VRST X X X
    MISO X X X MISO X X X
    CLK X 1.367V X CLK X X X
    MOSI X X X MOSI X X X
    CSZ 3.212V X 3.21V CSZ 3.178V 3.179V 3.179V
    SENS2 1.126V 1.125V 1.125V SENS2 X X X
    THERM 1.122V 1.121V 1.125V THERM X X X
    V6V 6.197V X X V6V X X X

    <Question> 

    1. It is said that AsiaOptics DLP Engine of DLP2010EVM-LC sold by Ti company is no longer produced. We would like to use the Asia Optics DLP engine. Other than that, is there no equivalent DLP Engine? May I ask you to check?

    2. When connecting alternative engines (Elepn, iview), DLPA2005 does not operate due to low voltages of Reset, VOFF, VBIAS, and VRST. How to solve can be solved with the above solution?

    Currently, we are looking for solutions to problems from multiple angles. Even if it's annoying, we ask for help for you and our win-win.

    Regards, 

    YUN

  • 0 in reply to JONGKEUN YUN
    TI__Genius 9971 points

    Yun,

    Thanks for the detailed explanation. I will release a firmware to you via mySecure, kindly download it and let me know whether you are able to boot up the system or not.

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    TI__Genius 9971 points

    Yun,

    I have released v7.3.1 firmware to you via mySecure. Kindly let me know whether you are able to boot up the system using this firmware.

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    Prodigy 155 points

    Dear 

    Thanks for sending the firmware.

    In the GUI Software 2.2.0.6 we used previously, the update was not possible because the DMD connection was not available. I went to the Ti Forum and tried to install the firmware as there was a way to update the damaged firmware image from DLP Lightcrafter 7.4 to SPI.

    The update installation process is EVM+DLP Engine connection, Data Cable connection -> Switch Off -> Power Supply ON -> Lightcrafter 7.4 execution -> Firmware update

    The result is as follows.

    　 Firmware Version Ti 7.3.1 F/W(option3) iview 7.3.1 Option 3 Elepn 7.1.3(option 1)
    dpp343x_7.1.3    		 Elepn 7.1.3(option 3)
    dpp343x_7.1.3
    Ti
    Engine    		 F/W Update O O O O
    Whether DLP works O O X X
    Elepn
    Engine    		 F/W Update X(Verify Failed) X(Verify Failed) X(Verify Failed) X(Verify Failed)
    Whether DLP works X X X X
    Iview
    Engine    		 F/W Update X(Verify Failed) X(Verify Failed) O O
    Whether DLP works X X X X

    The current problem is that the firmware is not updated in the two 3rd party engines themselves.

    Then, I am curious about what variables we can check.

    In addition, there is a difference in the DMD ID sent by the manufacturer, so please contact us.

    Name DLP2010EVM-LC by Ti Iview(DLP & EVM)
    Controller Device ID
    = ASIC Device ID    		 0xF(DLPC3470) 　
    DMD Device ID 0x0 DMD device ID 1761611104(decimal) 1761611104
    60 0d 00 69(hexadecimal) 　
    　 　
    DMD Byte 1: 96(60) 96
    DMD Byte 2: 13(0d) 13
    DMD Byte 3: 0(00) 0
    DMD Byte 4: 105(69) 105
    　 0x1 DMD FUSE GROUP1 409087893(decimal) 479642983
    95 2f 62 18(hexadecimal) 　
    　 　
    DMD Byte 1: 149(95) 103
    DMD Byte 2: 47(2f) 197
    DMD Byte 3: 98(62) 150
    DMD Byte 4: 24(18) 28
    　 0x2 DMD FUSE GROUP2 3540025344(decimal) 2625667072
    00 80 00 d3(hexadecimal) 　
    　 　
    DMD Byte 1: 0(0) 0
    DMD Byte 2: 128(80) 128
    DMD Byte 3: 0(0) 128
    DMD Byte 4: 211/(d3) 156
    　 0x3 DMD FUSE GROUP3 - 　
    　 0x4 DMD FUSE GROUP4 - 　

    0x0 is the same, but there is a difference between 0x1 and 0x2. Could this be a problem? Also, I am curious about what DMD FUSE GROUP means.

    Regards, 

    YUN

  • 0 in reply to JONGKEUN YUN
    TI__Genius 9971 points

    Yun,

    Thanks for the detailed information.

    The answer to some of your queries are as follows -

    1. I am curious about what DMD FUSE GROUP means. >> DMD FUSE GROUP IDs are used by TI for internal debugging purposes. Kindly ignore the differences between these IDs.

    2.  In the GUI Software 2.2.0.6 we used previously, the update was not possible because the DMD connection was not available.

    >> I would recommend you to use the GUI itself to flash the firmware. It is possible to update a corrupted/ non-working firmware using GUI also. Just make sure the SW1 Switch is in off position.

    3. I am curious about what variables we can check. >>

    Can you please test v7.3.1 firmware that I had shared with you on Elepn optical engine by updating it via GUI. If you are able to boot up, can you please share the DMD device IDs and DMD FUSE GROUP IDs for that as well.

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    Prodigy 155 points

    Dear Mayank

    Always thank you for your kind answer.


    1. I understood well.

    2. In the case of DLP2010LC 2.2.0.6, I watched the Erasing Flash Data process for more than 20 minutes with SW1 turned off as follows, but the update is not possible because it does not proceed to the next step.

    Therefore, I tried the firmware in DLP Lightcrafter 7.4, which can be directly updated to SPI, and the result was (1/3 Pass -> 2/3 Updating -> 3/3 Verifying = Verify failed).

    To summarize the problem largely

    1) DMD ID mismatching

    2) Firmware update unavailable (DLP2010LC GUI 2.2.0.6 & DLP Lightcrafter GUI 7.4)

    3) Host_IRQ remains high

     

    Separately, a continuity test was conducted to check if there was any problem with the physical connection of the flash memory.

    Manufacturer 　 Ti(Asia) Engine FM Iview Engine FM Elepn Engine FM
    Continuity test 1Pin O O O
    　 2Pin O O O
    　 3Pin O O O
    　 4Pin  O O O
    　 5Pin O O O
    　 6Pin  O O O
    　 7Pin O O O
    　 8Pin  O O O

    One by one, we are removing impeccable factors.

    Please advise.

  • 0 in reply to JONGKEUN YUN
    TI__Genius 9971 points

    Yun,

    I am not sure why the firmware update is failing when it is done via DLPDLC-GUI v2.2.0.6

    Let me think through the issue in detail, I will get back to you within a day.

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    Prodigy 155 points

    Dear Mayank

    As a result of testing using a common Ti(asia) DLP engine's flash memory (using Ti flash), it was confirmed that the firmware could not be updated due to a problem with the No. 1 DLP manufacturer and No. 2 DLP manufacturer flash.

    Also, one company's DMD did not work, and the other company's DMD worked, so the following results were obtained.

    　 Ti Optic Engine No. 1 DLP Manufacturer (I) No. 2 DLP Manufacturer (E)
    DMD operation O X O
    Flash memory operation O X X
    Flash memory  64Mbit 16Mbit 16Mbit
    Flash memory clock frequency 1 I/O: 104MHz with 8 dummy cycles
    2 I/O: 86MHz with 4 dummy cycles for 2READ instruction
    4 I/O: Up to 104MHz    		 104MHz clock rate for Standard SPI
    80MHz clock rate for two data bits
    80MHz clock rate for four data bits O31:O32    		 133MHz Single, Dual/Quad SPI clocks
    266/532MHz equivalent Dual/Quad SPI

    <Question> 

    1. Like the data sheet above, 16Mb, 36MHz is supported, but is there a reason to use a specially higher specification flash memory?

    2. Since there is a problem with the flash memory, I try to replace the flash memory on the EVM board or the DLP engine (both manufacturers 1 and 2 have flash memory attached to the FPCB cable). Are there any recommended products?

    3. If the specification is higher than the above data sheet, is there any problem with what kind of flash memory is installed? (Similar size)

    please answer about my question.

    Regards, 

    YUN. 

  • 0 in reply to JONGKEUN YUN
    TI__Mastermind 28005 points

    Yun,

    I believe the team is still working this issue and should get back to you within a few days. Thanks for your patience.

    Regards,

    Philippe Dollo

  • 0 in reply to Philippe Dollo
    TI__Genius 9971 points

    Yun,

    Thanks for sharing this information. I am glad that you have somewhat found out the root cause of the issue.

    Please refer to the attached image which lists down the flash devices which are compatible with DLPC3470. The image also gives a detailed information of the SPI Flash compatibility requirements -

    My responses to your queries are as follows - 

    1. Like the datasheet above, 16Mb, 36MHz is supported, but is there a reason to use a specially higher specification flash memory? >> I might not have understood this query clearly. Higher Size and speed can be the reason behind this. 

    2. Since there is a problem with the flash memory, I try to replace the flash memory on the EVM board or the DLP engine (both manufacturers 1 and 2 have flash memory attached to the FPCB cable). Are there any recommended products? >> Please refer to the above image to see the list of recommended products.

    3. If the specification is higher than the above datasheet, is there any problem with what kind of flash memory is installed? (Similar size)

     >> I would recommend you to choose a flash device from the list mentioned in the image as they have been validated with on the EVM. We cannot guarantee the compatibility of the flash devices that have not been validated with the EVM reference design.

    Let me know if you have any more queries.

    Regards,

    Mayank

  • 0 in reply to Mayank Khandelwal
    Prodigy 155 points

    Dear Mayank

    I'm glad to finally know how to fix it.

    The reason was that the size of the FLASH installed in the DLP engine (2MB) was too small to update the large firmware (2.31MB).

    The manufacturer sent a reduced firmware (1.63MB) and tested it, and it works.

    Therefore, we plan to proceed with the development by directly installing the large-capacity FLASH on the EVM.

    I am curious to see which data can be referred to for additional ways to change and modify the firmware (reduction of firmware capacity, system settings, etc.)

    If you know, please let me know.

    Thank you for your help.

    Regards, 

    YUN.