• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 1124 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.

Original question:

TPS65983B: Singelport Thunderbolt device selvepowered detection

TPS65983B: Full Flash image doesn’t work

Patrick Schade
Prodigy 70 points

Part Number: TPS65983B

I have a Problem by creating the Thunderbolt 3 NVM.

 

I use:

  • Application-Customization 3.17
    • FM 6.43
  • Imaginarium2_AR-NVM-Customization-Tool_4.4.3
    • FM rev33

 Hardware:

  • TPS 65983b
  • Alpine Ridge SP (JHL6340)
  • Winbond W25Q80D

  

If I create the image with the low region file and the Imaginarium2 tool the result works.

If I use the Full Flash image (Region 1 offset: 0x2000 Region 2 offset: 0x20000 or 15000) the result doesn’t work, this means the Thunderbolt devices were not found.

TPS65983b_test.pjtCan you help me with that problem?

Thank you, 

Patrick

  • 0
    TI__Mastermind 36756 points

    Hi Patrick,

    You are supposed to be using the Low Region file when merging the firmware with imaginarium. It sounds like you are doing everything correctly. Do not use the full flash when merging the firmware.

    If this answers your question, PLEASE select This resolved my issue

    Thank you,

    Eric

  • 0 in reply to Eric Beljaars
    Prodigy 70 points

    Hello Eric,

    thank you for the response.The reason why I try to build an image with a secondary FM is these requirement:

    4.4 Firmware Update (Required)

    The USB PD Controller must support a secure firmware update mechanism. The firmware update is performed over the Thunderbolt link. Firmware update is for both the Ridge and the USB PD Controller if the flash is shared or the Ridge may write to the USB PD Controller internal memory.  

    TBT3 FW Update Requirements

    • Secured (signed) 
    • Redundant  TBT3 Device shall not be made unusable if the FW update fails
      •  Full copy of RAM for first FW update image. This can be patch if a ROM based part.
      • Ideally a full second copy of the FW 
      • If not a full second copy, there must be a second version sufficient to enable a USB PD Controller to boot and load FW. 
    • FW shall be able to update the USB PD VIDs, PIDs, XIDs, and billboard strings
    • FW shall be able to update additional SVIDs and modes for CIO
    • FW shall be able to incorporate bug fixes
    • FW shall be able to update the USB2 billboard if integrated or external billboard device

    An OEM proprietary mechanism for TBT3 Device FW update in an OEM Dock connected  to a non-TBT host is allowed.

    I thought the full Flash includes a secondary FM as backup if the first image is corrupt. If there is no possibility to create an image with a second copy of the FM, is there another mechanism to make sure that the TBT3 Device shall not be made unusable if the FW update fails.

    Thank you,

    Patrick

  • 0 in reply to Patrick Schade
    TI__Mastermind 36756 points

    Hi Patrick,

    When the flash is shared between the PD controller and the Ridge. The Ridge handles the secure update of the shared flash used for the PD controller and the ridge. This is done using one of the Intel GUI tools. For more questions on this mechanism, please reach out to your Intel support.

    If this answers your question, PLEASE select This resolved my issue

    Thank you,

    Eric