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.

DLPC3439: firmware FWSel_DLPC3439_DLPA3005_pm2_i2c0x36_v7p7p0.img reports error in communication status

Part Number: DLPC3439
Other Parts Discussed in Thread: DLPA3005, , DLP4710

Hi,

I'm actually testing new TI firmware FWSel_DLPC3439_DLPA3005_pm2_i2c0x36_v7p7p0.img. Working just well, but compared to firmware dpp3439-dual-ASIC_7.3.2.img communication status (and short status as well) reports approximately every second Invalid Command Error (bit 0). The invalid command op-code is zero. It seems that error showed up after posting commands Write RGB LED Enable (52h) and  Read RGB LED Enable (53h). In our aplication firmware every data written to DLPC3439 are verified a and communication (and other) status periodically checked, so new firmware doesn´t comply.

Next issue related to reading system temperature (D6h). Power of the temperature sensor normally comes from GPIO11, but in new firmware is off. After writing "1" to corespond GPIO using system commands is possible to power it up, but system command Read System Temperature (D6h) returned still the same value 6.5 degrees Celsius. Old fw works well.

Please TI help find a solution

Thank you very much

Regards,

Zdenek Zechovsky

  • Zdenek,

    Thanks for your report on the above issues. Are you testing this firmware on a DLP4710 EVM, or a custom board you and your team designed?

    Regards,

    Philippe Dollo

  • Hi Phillipe,

    We are testing on custom board based on DLP4710EVM-G2, pin mapping option is 2. DLP chip-set is controlled by microcontroller using TWI (clock rate is 100kHz). The temperature sensor connection is completely the same as on EVM.

    Regards,

    Zdenek Zechovsky

  • Hi,

    I took a deeper look at the status issue and found that only the temperature reading showed a communication error. After reading the temperature, always with a result of 0, a communication error appears (and still invalid command op-code is zero). The other commands I use are no longer errors. So the difference in functionality compared to the previous firmware is only in the implementation of temperature measurement, including power supply from the GPIO11 pin, which is turned off here.I think I can do without this value for now.

    Regards,

    Zdenek Zechovsky

  • Hello Zdenek,

    Could you please run similar experiment on a TI EVM  (with current firmware configuration) and see if it reproducible on TIE EVM too?

    regards,

    Vivek

  • Hi Vivek, 

    unfortunately I don't have a newer version of G2, only the older one and it is incompatible with this firmware.
    However, our design is more or less the same as the G2 version as far as the chip set is concerned. With older versions
    it has been working without errors for maybe 2 years (including system temperature reading) . As I wrote, after setting up GPIO11 using system commands,
    I turn on the power to the resistance divider with a thermosensor, I also measure the voltage on the thermosensor with an external A / D converter,
    so I don't need to get a command to read the temperature.
    The only communication error jumps immediately after system startup, the operation code corresponds to the image crop write, code 0x10.
    This command is not supported in the DLPC3439 according to the documentation, however it is part of a batch file run after system initialization. I plan to adjust this batch file to our needs.

    Regards, Zdenek
  • Hello Zdenek,

    I'm glad to hear that you can work around the system temperature reading and that your previous system has served you well.

    Please feel free to reach out if there is any further assistance we might offer.

    Regards,

    Austin