• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 659 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.

DLPC900 Programmer's Guide: Ambiguous I2C commands?

Robocop
Prodigy 70 points
Other Parts Discussed in Thread: DLPC900

Document file name: dlpu018a_DLPC900 Programmer's Guide (Rev. A).pdf

In the DLPC900 Programmer's Guide (Rev. A) I found two identical READ commands for I2C. Chapter "1.5.1 Read Error Code" states, that 0x32 is the command byte to use if an error code must be retrieved. However, chapter "2.4 Start Address", which refers to DLPC firmware programming, denotes exactly the same command byte in order to read flash start addresses. This isn't  the case for the USB command counterpart which fortifies my opinion, that all DLPC command identifiers shall be unique. An error in the documentation?


Regards,
Robert

  • 0
    TI__Expert 6370 points
    Hi Robert,

    First, thanks for your very clearly written question!

    Section 1 of the DLPC900 Programmer's Guide covers DLPC900 Status Commands and Section 2 covers DLPC900 Firmware Programming Commands. This means that the commands covered in section 2 are only valid in "program mode." There is more detail about this in the fine print at the beginning of section 2, but Program Mode has it's own set of commands. So, the Status Commands from section 1 are invalid in program mode (and would be interpreted as their program mode counterparts), and vice versa.

    Let me know if you have any other questions!

    Best regards,
    Trevor
  • 0 in reply to Trevor Dowd
    Prodigy 70 points

    Hi Trevor

    thank you for the explanation. I have seen the note, where commands are valid for the appropriate context only. On the other hand, 0x32 is the only duplicated command (for I2C) as far as I can see. Having a brief look at the USB commands, there are no doubles at all. So, this raised my question. That much said, with regards to I2C, I have to keep the context in mind. Ok, accepted.


    Best regards
    Robert