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.

DLPC900: Error descriptive string doesn't match expectation

Other Parts Discussed in Thread: DLPC900

I am currently working with a DLPLCR6500EVM, the communication is done via I2C.

Sending the command 0x32 (USB counterpart: 0x0100) tells me, that the system is currently free of errors. With command 0x33 (USB counterpart: 0x0101) I am trying to extract the error string, which should be something like "No error" (as denoted in table 12 in the Programmer's Guide) or similar. But I get no description at all. In fact, it looks like the very first character of the response is the "0x0" termination byte. Could someone from TI (or anyone else with a running I2C communication) please check this? Not sure, whether its a bug in my implementation or in the DLPC900 firmware...

Thanks
Robert

  • Hello Robert,

    For, No Error condition the DLPC900 firmware is returning 0x00. Not the error string "No Error".

    You can either not read the error string if the I2C:0x32 command says 0x00. i.e. NO ERROR occured.

    OR

    You can treat the response for I2C:0x33  USB:0x0101 command  for NO ERROR as string with just 1-byte 0x00.

    Regards,

    Sanjeev

  • Hello Sanjeev

    thanks for replying. So, in the end, the result is correct and not a bug in my implementation. Strange though...

    Other question: Do error strings correspond somehow to the error descriptions of table 12 in the Programmer's Guide?
    Or are these completely different?

    Regards,
    Robert
  • The error strings exactly match to Table #12.

    New Error code being added in the next firmware version v2.0, Error Code 17. for command USB:0x1A39 I2C:7F, this will return error is the user provided index cannot be decoded to proper address on the flash for downloading the image.

    Regards,
    Sanjeev'