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.

AM5718: device freezes when accessing PRU registers

Part Number: AM5718


Tool/software:

Hello TI,

 

In our design we are using SITARA AM5718/48 devices, and in some cases, we are having an issue (device freezes) when reading PRUSS registers.

 

The symptom is that the device sometimes freezes when starting up. After analyzing it and looking for where it was freezing, we found that it was when loading the drivers related to the PRUSS. Specifically, in the icss_iep driver when reading a register.

 

What we have tried so far:

  • Starting without loading the driver and reading the register from the console with “devmem2 0x4b22e000”: the device freezes.
  • Booting without loading the driver and reading the register from the console with “devmem2 0x4b22e000”: the device freezes.

 

Looking for similar information in the forum, we found the following posts that refer to the same problem:

 

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1016508/am5708-a15-dsp1-hangs-if-try-to-access-any-register-of-iep-of-pru-icss1-omap_l3_noc-44000000-ocp-l3-application-error-target-5-mod-1-unclearable

 

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1222731/am5718-iep-register-access-leads-to-crash-or-hang-of-a15

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1240949/am5718-am5718-iep-register-access-leads-to-crash-or-hang-of-a15?tisearch=e2e-sitesearch&keymatch=IEP%2520register%2520access#

 

In the latter, Josué recommends trying a patch. This post is from three years ago, so we would expect to see it already applied in the version of the SDK based on Kirkstone that was released in December 2024, but we do not see that it has been applied.

 

In the errata document added in 2024 (AM572x SitaraTm Processors Silicon Revisions 1.1, 2.0 Errata Literature Number: SPRZ429N):

And then in the description and workaround:

 

 

If you have detected it, then why not incorporate the patch to the mainline? What can we do to fix this problem?

 

Thank you in advance for your support.

 

Best regards,

Gonzalo