• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 582 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.

TMS570LC4357: Can't feed watchdog while Using TMS570LC4357 communicating with TPS65381A via SPI

Benjamin Zhou
Expert 4000 points
Part Number: TMS570LC4357
Other Parts Discussed in Thread: TMS570LS1227

AHi Team,

  My customer used TMS570LS1227 + TPS65381 in previous project, and the TMS570LS1227 feed the TPS65381A's watchdog, which worked well, but failed while using TMS570LC4357 for feeding TPS65381A's watchdog with the same process.

  Could you kindly provide demo code for TMS570LC4357 to feed TPS65381's watchdog?  expect for your reply, thanks.

Best Regards

Benjamin

  • 0
    TI__Guru 59540 points
    Hello Benjamin,

    Please let us know more about the problem? Are they unable to initialize and use SPI? Is the MCU getting hung up in a particular location within the driver (assuming they are using the TPS driver available as part of the SafeTI Diagnostic Library)? Also, how have they configured the TPS device? Since this is through the same SPI mechanism, can I assume SPI is working and can communicate with the TPS part? Overall, I am not certain about support for the TMS570LC43x device and by the TPS driver included with the SafeTI Diag Lib and I will send a note to our SW team to verify one way or the other.

    Also, please note that the TPS65381A device cannot support the max currents of the LC4357 device without some external circuitry added. If they have not made this change, please let me know so I can reach out to the PMIC team for their guidance on this as well or have a look at this thread for guidance: e2e.ti.com/.../1286509
  • 0 in reply to Chuck Davenport
    TI__Expert 4000 points
    This issue has been closed, which is caused by Bugs of SPI configuration: the time-slot for TPS65381A between the 2 SPI frames is not configured correctly, changed the configuration as TPS65381A configuration, fixed this issue.
    Thanks for your great support.

    Best Regards
    Benjamin