"Synchronous Abort" handler, esr 0x96000004 with AGL (Yocto Based)

[Sole Mendi Carles (PS-EC/ECC7)]

Dear u-boot mailing list,

As no one has provided any feedback regarding my question I am trying my luck again. 

As described below depending on the DT's I overlay using an AGL build for RPi4 I get a "Synchronous Abort" handler error. Any hints on what this error means and why u-boot cannot load the overlays would be much appreciated.

I provided the log files of the boot process with CONFIG_LOG enabled. I can send them again if required.

Best Regards,
Carles

Mit freundlichen Grüßen / Best regards

 Carles Sole Mendi

Engineering Customer Platform Ford Diesel, Customer Projects Ford Diesel EU (PS-EC/ECU2)
Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY | www.bosch.com
Tel. +49 711 811-20593 | Fax +49 711 811 | Carles.SoleMendi at de.bosch.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Prof. Dr. Stefan Asenkerschbaumer; Managing Directors: Dr. Stefan Hartung, 
Dr. Christian Fischer, Filiz Albrecht, Dr. Markus Forschner, Dr. Markus Heyn, Rolf Najork

-----Original Message-----
From: U-Boot <u-boot-bounces at lists.denx.de> On Behalf Of Sole Mendi Carles (PS-EC/ECC7)
Sent: Montag, 25. Juli 2022 11:31
To: u-boot at lists.denx.de
Cc: andrei at gherzan.com
Subject: "Synchronous Abort" handler, esr 0x96000004 with AGL (Yocto Based)

Dear U-boot mailing list,


My name is Carles and I have been trying for a while to use a Yocto based distribution (AGL) image for RPi4 to control automotive HW using pwm signals. Unfortunately I have been struggling with this when the boot procedure is configured to use u-boot.



I am basically building the minimal image doing following change in the configuration to enable pwm.dtbo:



In /conf/machine/include/rpi-base.inc<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.yoctoproject.org%2Fmeta-raspberrypi%2Ftree%2Fconf%2Fmachine%2Finclude%2Frpi-base.inc%3Fh%3Dkirkstone%26id%3Dad6ebc053abff98725c0a852c412e9bafaae53de&data=05%7C01%7CCarles.SoleMendi%40de.bosch.com%7C9bb78f2bc1e34723dcd008da6e2da07c%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637943439539546367%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5yJibco1paC1JmGr%2FZHcNKRlSHqNMK9FLPAjy2MX9h0%3D&reserved=0> I add the pwm dtbo’s.



RPI_KERNEL_DEVICETREE_OVERLAYS: Add following dtbo‘s:

   overlays/pwm.dtbo

   overlays/pwm-2chan.dtbo



With this changes the image builds and boots without issues. However once I add dtoverlay=pwm in config.txt the boot process does not work anymore and shows following error:



mmc0 is current device

Scanning mmc 0:1...

Found U-Boot script /boot.scr

262 bytes read in 5 ms (50.8 KiB/s)

## Executing script at 02400000

"Synchronous Abort" handler, esr 0x96000004

elr: 00000000000a2afc lr : 00000000000a2b34 (reloc)

elr: 000000002ef6fafc lr : 000000002ef6fb34

x0 : 000000002eb5a780 x1 : 1218121712161215

x2 : 000000002eb48e50 x3 : 0000000000000015

x4 : 1224122312221221 x5 : 0000000000000015

x6 : 000000002efc3b88 x7 : 000000002efc3b88

x8 : 0000000000000001 x9 : 0000000000000008

x10: 0000000000000006 x11: 000000002eb529d0

x12: 0000000000002022 x13: 0000000000000001

x14: 0000000000080000 x15: 000000002eb3cfb0

x16: 000000002ef77858 x17: 0000000000000000

x18: 000000002eb48d90 x19: 0000000000000000

x20: 0000000000000006 x21: 0000000000000006

x22: 0000000000000000 x23: 000000002eb3ac68

x24: 000000002efac8a8 x25: 000000002eb615c0

x26: 0000000000bff800 x27: 000000002ebe3d40

x28: 0000000000001800 x29: 000000002eb3abe0



Code: 54000061 d2800000 d65f03c0 f9400401 (b9400821)

Resetting CPU ...



If I disable U-boot using RPI_USE_U_BOOT = „0“ then all works good and I can use the pwm driver and generate pwm signals, but I would really like to be able to use u-boot.


I am not sure how I need to update the u-boot addresses with the added dtbo’s so that u-boot is able to recognize these and boot successfully. Any hints from your side would be much appreciated.

I have enabled logging in u-boot and stored the boot process without dtoverlay=pwm vs.with dtoverlay=pwm. I attach both files for reference. I hope this is helpful.

Mit freundlichen Grüßen / Best regards

Carles Sole Mendi

Engineering Customer Platform Ford Diesel, Customer Projects Ford Diesel EU (PS-EC/ECU2) Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY | www.bosch.com Tel. +49 711 811-20593 | Fax +49 711 811 | Carles.SoleMendi at de.bosch.com<mailto:Carles.SoleMendi at de.bosch.com>

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000; Chairman of the Supervisory Board: Prof. Dr. Stefan Asenkerschbaumer; Managing Directors: Dr. Stefan Hartung, Dr. Christian Fischer, Filiz Albrecht, Dr. Markus Forschner, Dr. Markus Heyn, Rolf Najork ​