• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 63 subscribers
  • Views 187 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.

TPS25750: GPIO Registers, binary mismatch

Ambroise Suter
Expert 4110 points
Part Number: TPS25750

Hello,

We are preparing the TPS25750 for production. We have the json and the binary from this config. However there are some bits that are different that we cannot explain.
The mismatched bits are in the "reserved" regions. Can you indicate us what the difference is and where these different bits come from?

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/20220831_5F00_092118_5F00_EEPROM_5F00_24256.bin

Fullscreen 1216-02-SW703-c-SOURCE-GPIO1_43.json Download 
{"questionnaire":{"version":"7.0.3.13","answers":[1,0,0,0,1,2,1,null,1,null,null,null,null,null,null],"options":{},"configID":"0000","vendorID":"0000"},"configuration":{"data":{"selected_ace":[{"register":6,"data":[0,0,0,0,0,0,0,0]},{"register":22,"data":[10,48,48,77,0,0,0,0,0,0,3]},{"register":50,"data":[1,168,42,44,145,1,38,44,209,2,0,44,177,4,0,244,65,6,0,0,0,0,0,0,0,0,0,0,0,0,0]},{"register":51,"data":[1,44,145,1,0,44,209,2,0,44,177,4,0,244,65,6,0,69,65,6,0,0,0,0,0,0,0,0,0]},{"register":92,"data":[0,0,0,0,1,0,0,0,0,16,0,0,0,0,0,0,48,0,0,0,1,0,0,0,0,12,0,0,0,0,0,0,0,0,0,0,43,0,0,0,0,0,0,0,0,0,0,0,0]}]}}}

Best regards,

Ambroise

  • 0
    TI__Mastermind 34076 points

    Hi Ambroise,

    What are the customers using to compare the bits? Which register(s) doesn't match the settings they configured through the GUI? 

    Thanks and Regards,

    Raymond Lin

  • 0 in reply to Raymond Lin
    TI__Expert 4110 points

    Hi Raymond,

    not sure on the exact tool they are using but you can use 

    objcopy -I binary -O ihex fileA.bin testA

    in powershell to convert the files to Hex and then

    fc.exe .\testA .\testB

    to compare the files.

    I created a binary from the previously attached JSON and compared them this way (see files attached).

    Somehow there are a few lines (2001 - 2048) missing in the "testB". Otherwise I don't see any differences. Do you know why this difference occurs?

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/testAhttps://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/testB

    Thank you and best regards,

    Ambroise

  • 0 in reply to Ambroise Suter
    TI__Mastermind 34076 points

    Hi Ambroise,

    Let me look into this and get back to you by the end of the week. 

    What is the current production schedule? 

    Thanks and Regards,

    Raymond Lin

  • 0 in reply to Raymond Lin
    TI__Expert 4110 points

    Hi Raymond,

    Thank you for checking, they are planning to start production in November. Have you found anything that could cause these different binary files?

    Best regards,
    Ambroise

  • +1 in reply to Ambroise Suter
    TI__Mastermind 34076 points

    Hi Ambroise, 

    Which test file (testA and testB) was generated from the online GUI and how was the other binary generated?

    Based on the difference, it seems like the additional binaries in testA (additional F's) are included for padding purposes. If functionality wise both binaries work fine, then this should not be an issue. 

    Thanks and Regards,
    Raymond Lin