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

TPS65982: MODE(0x03) stuck in BOOT

Takashi Onawa
Genius 13200 points
Part Number: TPS65982
Other Parts Discussed in Thread: TPS65981

Hi Team,

My customer and I sometimes saw that the mode register of TPS65982EVM was stuck at BOOT in a evaluation. According to your answers, 4CC commands and any read commands should be done after EC gets 'APP'.

1. Could you tell me what kind of situation the mode register will be stuck at BOOT?

2. If TPS65982 gets that situation, how should EC controlling TPS65982 do?

Regards,

Takashi Onawa

  • 0
    TI__Genius 16370 points
    Takashi San,

    The contents of the sFLASH could be corrupted, and in which case, the device wouldn't be able to boot successfully - What is the reading of register 0x2D when the device gets stuck in this state?

    -/Praneet
  • 0 in reply to Praneet Kumar
    TI__Genius 13200 points
    Hi Kumar-san,

    OK, I understood that TPS65982 might be stuck at BOOT when the sFLASH is corrupted.
    They would like to know how EC should do if TPS65982 gets the stuck condition in order to make a code for their app's FW.

    Which flags in the 0x2D register are related to the BOOT stuck?
    Please tell me which registers are likely to be used to determine Flash failure.

    Regards,
    Takashi Onawa
  • 0 in reply to Takashi Onawa
    TI__Genius 13200 points
    Hi Kummar-san ,

    Can I get any comments on this.

    Regards,
    Takashi Onawa
  • 0 in reply to Takashi Onawa
    TI__Genius 16370 points
    The details about each of the bit-fields is documented in Host-Interaface's TRM (www.ti.com/.../slvuan1a.pdf; Title: TPS65981, TPS65982, and TPS65986 Host Interface Technical Reference Manual (Rev. A)), and is self explanatory - I suggest you review the same, and let me know if you have any specific queries.

    'BootOk' indicates whether SRAM is successfully loaded - If it's 0 and if its the primary device, bits 4-13 will have additional details about the error.

    For me to help you better, please provide more details about the issue, and what your customer is trying to do in the EC for recovery. Note that if the 4kB header reasons at 0x0000 or 0x1000 are corrupted, the only recovery option is to reprogram the sFLASH.

    -/Praneet
  • 0 in reply to Praneet Kumar
    TI__Genius 13200 points
    Hi Kumar-san,

    Thanks, I understood about followings.
    > 'BootOk' indicates whether SRAM is successfully loaded - If it's 0 and if its the primary device,
    > bits 4-13 will have additional details about the error.

    > For me to help you better, please provide more details about the issue
    They are just writing a code for their application, it's not Alpine Ridge system. In their evaluation, they sometimes see TPS65982 is stuck in "BOOT" and they need to reconnect or re-write FW to recover that condition.

    Since they noticed there is a possibility that TPS65982 would be stuck in unexpected timing, they need to make a error detect function to indicate the FLASH failure.

    Anyway, I might close this issue by your answer in the following thread.
    e2e.ti.com/.../626759

    Regards,
    Takashi Onawa