cancel
Showing results for 
Search instead for 
Did you mean: 

Out of order STM32MP157CAC. PANIC at PC : 0x2fff2d17 Exception mode=0x00000016 at: 0x2fff2d17

DFomi.1
Associate II

Hello.

I developed my own board based on A-DK1 board using STM32MP157CAC and MicroSD, PMIC, Ethernet and DDR periphery. When I connect my plate to the usb with sd-card (st-link 2.1) I always receive the message:

PANIC at PC : 0x2fff2d17

Exception mode=0x00000016 at: 0x2fff2d17

Only these 2 strings.

My power and clock schematics exactly the same as -dk1 board.

I have only one difference. There is a STM32MP157AAC on the dk-1 and I use STM32MP157CAC...I have one sd-card for the both boards. My MPU just doesn't wake up and I don't understand what should I doing

1 ACCEPTED SOLUTION

Accepted Solutions
PatrickF
ST Employee

Hi,

may I suggest you to check for classic pitfall/debug steps:

https://community.st.com/s/article/FAQ-STM32MP1-bring-up-troubleshooting-guide

https://community.st.com/s/article/FAQ-STM32MP1-Bring-up-procedure

Going from STM32MP157A to STM32MP157C should not be the root cause of your issue.

By experience, one of the first frequent pitfall is using an HSE Crystal with a Device Tree set for HSE bypass (BootROM has autodetect, but TF-A used Device Tree settings)

Then once first verification steps are not solving your issue, please share the Device Tree you used to compile your SD-Card binaries and the complete TF-A log.

Note that I wonder if the Starter Package SD-Card of STM32MP157A-DK1 will work on a custom board (as in Starter Package there is probably some automated board detection based on custom OTPs sets only on ST development boards).

Btw, I will put your precedent ticket as 'answered'

Regards,

Patrick

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

View solution in original post

2 REPLIES 2
PatrickF
ST Employee

Hi,

may I suggest you to check for classic pitfall/debug steps:

https://community.st.com/s/article/FAQ-STM32MP1-bring-up-troubleshooting-guide

https://community.st.com/s/article/FAQ-STM32MP1-Bring-up-procedure

Going from STM32MP157A to STM32MP157C should not be the root cause of your issue.

By experience, one of the first frequent pitfall is using an HSE Crystal with a Device Tree set for HSE bypass (BootROM has autodetect, but TF-A used Device Tree settings)

Then once first verification steps are not solving your issue, please share the Device Tree you used to compile your SD-Card binaries and the complete TF-A log.

Note that I wonder if the Starter Package SD-Card of STM32MP157A-DK1 will work on a custom board (as in Starter Package there is probably some automated board detection based on custom OTPs sets only on ST development boards).

Btw, I will put your precedent ticket as 'answered'

Regards,

Patrick

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
DFomi.1
Associate II

Thank you very much! I had a mistake in my I2C4 schematic.