• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 61 subscribers
  • Views 321 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.

TPS65988DJ: Bootflags (0x2D)

Sofian Teja
Prodigy 80 points
Part Number: TPS65988DJ
Other Parts Discussed in Thread: TPS65988

Hi,

My questions regarding TPS65988 bootflagss (0x2D) register in this below.

  1. I read the boott 0x2D the value is f8000000a206000030000000, then swap 00000030000006a2000000f8 , is it need to be swap ?
  2. Based on the above values, could you confirm if the valure read is correct ?
    1. the Bits 3 (bytes 1~4) like the SpiFlashPresent is it the value is 1 is it right ?
    2. the Bit 4 ~7 Region 0 ~ 1, Region 1Invalid ~ Region0Invalid is 1 is it right ?
    3. the Bits (bytes 9~12) like the REV_ID Metal is it the value is 2 ?
    4. the Bits (byte 9~12) like the REV_ID Base is it the value is A ?
    5. In the TPS65988 TRM datasheet the REV_ID metal and REV_ID Base in the bytes 9 ~12, but why in the value read was in the bits 32 ~ 39 ? 

Thanks,
Sofian 

  • +1
    TI__Mastermind 37655 points

    Hi Sofian,

    [1]

    Yes, your "swap" is correct. We return the lowest word first.

    You can reference this figure for bit order.

    [2]

    It looks like bytes 5-8 are hidden and likely reserved. Byte 9, which corresponds to the metal_rev and base from your read is 30, so it would be revision 0, and rev_id base is 3.

    Thanks and Regards,

    Chris

  • +1 in reply to Christopher Lim1
    Prodigy 80 points

    Hi Chris,

    Thank you for your comments, I still got a questions

    1. I read the version offset 0x0F the value is F7071000 ---> byte swap 001007F7 ( the version based on the datasheet..as this below)

    Binary Coded Decimal version number, bootloader/application code version.Represented as VVVV.MM.RR with leading 0’s removed.e.g. 65794d (decimal) -> 0x00010102 -> 0001.01.02 -> 1.1.2 (version). The version information is returned in little Endian format i.e. byte 1 = RR, byte 2 = MM, etc

    so the version actually is 10.7.F7  , is it correct ?

    Thanks,

    Sofian

  • 0 in reply to Sofian Teja
    TI__Mastermind 37655 points

    Hi Sofian,

    The version information should be F707.10.00 for your example.

    When I read register 0x0F over I2C, the return data looked like this: 04 33 12 07 F8

    Byte 1, 04 is just the data payload size(4 bytes) so the data is: 33 12 07 F8

    Following the Table 1-1 description, I obtain a verions of F807.12.33 (I'm using a different version, but we expect the leading "F")

    Thanks and Regards,

    Chris

  • 0 in reply to Christopher Lim1
    Prodigy 80 points

    Hi Chris,

    I still have a register need to confirm with you. as this below snapshots.

    I read the offset 0x00 for VID the value is 0x0 is this correct ?

    then when I read the offset 0x1 for DID  the value is  0x32454341 , is this expected ? 

    Thanks,

    Sofian

  • 0 in reply to Sofian Teja
    TI__Mastermind 37655 points

    Hi Sofian,

    I'll need to check with a team member for this one.

    Thanks and Regards,

    Chris

  • 0 in reply to Christopher Lim1
    TI__Mastermind 37655 points

    Hi Sofian,

    I saw that you created another thread for this issue, so I will close this thread and continue on the new thread.