• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 28 subscribers
  • Views 529 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.

DLPDLCR3010EVM-G2: Byte order value mismatch when read Splash Screen Header from device

Zhenhua Wang
Prodigy 20 points
Part Number: DLPDLCR3010EVM-G2

Hello,

I'm using the DLPDLCR3010EVM-G2 tool to project some custom images. When I use the command "Read Splash Screen Header (0Fh)" in advance GUI

The last byte I got is 0x53, but in Programmer's Guide. it shows:

My question is how to understand the 0x53 as byte order? Why in advance GUI it gives the "Big Endian" result?

Thanks!

  • 0
    TI__Expert 4610 points
    Hi Wang,

    Yes, i checked at my end. I can also see the 0x53 as last byte.

    It is not expected, i will investigate more at my end and will share the findings soon.

    Do you have any specific application related to byte order ?

    I can confirm that the correct byte order is "0h".

    Thanks,
    Navneet
  • 0 in reply to Navneet Singh
    Prodigy 20 points

    Hi Navneet,

    Thank you for your reply!

    I'm going to customize our own splash images for display some patterns. So I'm querying the default splash header to see the format that can be accept by the device.

    When I check the byte order value it makes me confuse. I don't know how to parse 0x53 to big or little endian.

  • 0 in reply to Zhenhua Wang
    TI__Expert 4610 points
    Hi Wang,

    For changing the Splash images you can use our GUI : www.ti.com/.../DLPDLCR3010EVM-G2

    You can go in advanced mode and select flash image update. There you can add 4 splash image in splash update.

    Note : We found other issue related to splash header read command (13th byte is not required), we will resolve it in our future releases.

    Thanks,
    Navneet