AM6442: U-boot SPL failed starting k3_system_controller

Stefan Blattmann

Part Number: AM6442

Tool/software:

Hello TI Team,

we are facing an issue on a custom board based on a TI am6442 SoC.

Roughly once every 300 reboots, the U-Boot SPL hangs while attempting to start the k3_system_manager after loading the SYSFW via rproc.

The error happen at:

static void k3_start_system_controller(int rproc_id, bool rproc_loaded, ulong addr, ulong size)

---------------------------------------------------------------------------------------------------------------------------------------------------------

U-Boot SPL 2021.01-sickpca-08470-g4578b21c59 (May 18 2023 - 23:32:05 +0200)
k3_system_controller sysctrler: k3_sysctrler_start: Boot Notification response failed. ret = -110
Firmware init failed on rproc (-110)resetting ...

---------------------------------------------------------------------------------------------------------------------------------------------------------

So far, we haven’t observed any anomalies on the Power Good signals during these occurrences.

Do you have any suggestions on what might cause this behavior? Are there any specific registers or debug mechanisms we can use to verify whether the k3_system_manager is running correctly or has encountered a failure?

Any guidance or pointers would be greatly appreciated.

HW/SW:

am6442

eMMC raw boot

sysfw: v08.05.03 (Chill Capybar')

u-boot: 2021.01

Stefan

1 month ago

0 Nick Saulnier 1 month ago

TI__Guru** 101130 points

Hello Stefan,

Several notes:

1) Please make sure you are using DMSC firmware from SDK 10.0 or later to avoid PLL instability

Refer to section "PLL Programing Sequence Update" for details:
https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/10_01_10_04/exports/docs/devices/AM64X/linux/Release_Specific_Migration_Guide.html

2) is this GP silicon, HS-FS silicon, or HS-SE silicon?

For more details, refer to the GP to HS-FS Migration guide:
https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/10_01_10_04/exports/docs/linux/Foundational_Components_Migration_Guide.html

I am surprised to hear that you are only seeing this issue once every several hundred boots. Usually when I see that terminal output, it is because boot files intended for GP silicon are being used with HS/FS silicon, or boot files intended for HS/FS silicon are being used with GP silicon. Like in this thread:
e2e.ti.com/.../sk-am64-sk-am64-default-images-do-not-boot

Regards,

Nick

0 Stefan Blattmann 1 month ago in reply to Nick Saulnier

Prodigy 150 points

Hi Nick,

Thanks a lot for your support!

We'll proceed with updating the DMSC firmware. Is there any documentation available that outlines the changes or release notes for the different firmware versions?

We're currently using the 6.1.xx kernel, are there any compatibility issues with the TISCI protocol from sysfw version 10.xx.xx?

For context, we're working with HS-FS Version 2.0 silicon.

Do you have any insights into what might cause the DMSC to hang? Is there a way to enable debug output for the System Firmware to help with troubleshooting?

Best regards,
Stefan

0 Nick Saulnier 1 month ago in reply to Stefan Blattmann

TI__Guru** 101130 points

Hello Stefan,

Thanks for confirming the silicon version.

Let me check on your questions. If I have not responded within a few business days, please ping the thread to make sure you get a response.

Regards,

Nick

+1 Nick Saulnier 1 month ago in reply to Nick Saulnier

TI__Guru** 101130 points

Hello Stefan,

SYSFW for SDK 10.0 was tested with u-boot 2021 (SDK 8.6) and Linux 6.1 (SDK 9.2)

The SDK 10.0 version of the SYSFW was validated with both SDK 8.6 and SDK 9.2, as discussed in the migration guide above. So that version of SYSFW is safe for your design.

Release notes for SYSFW are available starting with SDK 11.0

They are in Linux SDK docs > Release notes > Component version > TIFS firmware
https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/11_00_09_04/exports/docs/devices/AM64X/linux/Release_Specific_Release_Notes.html

So unfortunately there are not release notes for SDK 10.0 that I can point you to.

I was told that the latest version of SYSFW should work with your design, but we have not specifically tested it with previous SDK versions.

Any insights into what might be causing the DMSC to hang?

At this point, not really (I have spent a lot more time with the DM R5F core on AM62 family devices than the DMSC on AM64x). But if the behavior is still seen after updating the SYSFW, we should be able to enable debug output to take a look at what the code is doing in a fail case.

Regards,

Nick

0 Stefan Blattmann 1 month ago in reply to Nick Saulnier

Prodigy 150 points

Hi Nick,

Thank you very much for your support!

Just a quick note regarding the hang issue: it appears that DSMC firmware version 8.xx.xx fails to start or boot correctly, which causes the rp driver to be unable to initialize.

After updating to a newer firmware version, the issue is resolved, the system can now reboot hundreds of times without any hangs.

Thanks again!

Best regards,
Stefan

+1 Mukul Bhatnagar 1 month ago in reply to Stefan Blattmann

TI__Guru* 83895 points

Hello Stefan

Additionally, for the SYSFW PLL issue is also captured in our silicon errata

https://www.ti.com/lit/er/sprz457i/sprz457i.pdf

i2424:PLL: PLL Programming Sequence May Introduce PLL Instability

So it was important that you picked or redeployed SYSFW that comes along with SDK10.x or later.

the corresponding JIRA in release notes

2.1. Release Notes — Processor SDK AM64X Documentation

SYSFW-7485

Update the PLL driver in TIFS boot flow to follow correct sequence

Hope this helps. Let us know if you have more questions

Regards

Mukul

Processors

Processors forum

AM6442: U-boot SPL failed starting k3_system_controller