LPC Microcontrollers中的主题 Synchronous Abort " handler error

Synchronous Abort " handler error

utkarsh — Thu, 14 Mar 2024 11:04:51 GMT

Hi all

I am having Xilinx Zynq UltraScale+ MPSoc Cortex R5 target board.

U-boot is ported successfully, but while porting Vxworks image I am facing error.

Following command I am running

1. tftpboot 0x7810000 vxWorks.bin

2. go 0x7810000

This I have tried with other address also 0x2000000 result is the same .

Does anyone is having solution for loading vxworks binary .

Thanks

Re: Synchronous Abort " handler error

yipingwang — Mon, 25 Mar 2024 06:21:42 GMT

For Vxworks problem, please contact Wind River.

Re: Synchronous Abort " handler error

Thierry_LOUSSOT — Mon, 10 Jun 2024 22:28:45 GMT

Sorry no solution but similar error at the end, on booting, after succeeding the loading

else : two documents are important :

-> the readme file defined into BSP of the board witch specified a supplement guide for a board

-> eg : the vxwork_<board name> bsp_supplement_guide....pdf

else I get this on my board, similar issue : LX2160A-RDB-B shematics rev c

bootargs=dpni(0,0)host:vxWorks h=10.24.10.161 e=10.24.10.169:ffffff00 u=target pw=vxTarget f=0x1

-> so set f = 0x1 to use the Standard DTB and not the legacy DTB (requested in the documention

bootcmdarm=wdt dev watchdog@23a0000; wdt stop;tftpboot 0x85000000 images/nxp_lx2160a/uhypervisor; tftpboot 0x84000000 images/nxp_lx2160a/fsl-lx2160a-rdb.dtb; fsl_mc apply DPL 0x20d00000;bootm 0x85000000 - 0x84000000

=> run bootcmdarm
Using DPMAC18@rgmii-id device
TFTP from server 10.24.10.161; our IP address is 10.24.10.169
Filename 'images/nxp_lx2160a/uhypervisor'.
Load address: 0x85000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##################
7 MiB/s
done
Bytes transferred = 5025896 (4cb068 hex)
Using DPMAC18@rgmii-id device
TFTP from server 10.24.10.161; our IP address is 10.24.10.169
Filename 'images/nxp_lx2160a/fsl-lx2160a-rdb.dtb'.
Load address: 0x84000000
Loading: ##
9.2 MiB/s
done
Bytes transferred = 28957 (711d hex)
fsl-mc: Deploying data path layout ... SUCCESS
## Booting kernel from Legacy Image at 85000000 ...
Image Name: vxworks
Created: 2024-06-05 9:19:06 UTC
Image Type: AArch64 VxWorks Kernel Image (uncompressed)
Data Size: 5025832 Bytes = 4.8 MiB
Load Address: 80100000
Entry Point: 80100000
Verifying Checksum ... OK
## Flattened Device Tree blob at 84000000
Booting using the fdt blob at 0x84000000
Loading Kernel Image
Using standard DTB
Loading Device Tree to 000000009fff5000, end 000000009ffff11c ... OK

Starting kernel ...

"Synchronous Abort" handler, esr 0x02000000
elr: 00000000063ea000 lr : 0000000082005fd0 (reloc)
elr: 0000000080100000 lr : 00000000fbd1bfd0
x0 : 000000009fff5000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000080100000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 00000000fbb0e718 x9 : 0000010000000000
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 00000000fbdfffff
x14: 000000009fff5000 x15: 00000000fbd18be8
x16: 00000000fbd702b0 x17: 0000000000000000
x18: 00000000fbb11d90 x19: 00000000fbde6c98
x20: 0000000000000000 x21: 0000000000000400
x22: 00000000fbdad648 x23: 00000000fbb200c7
x24: 00000000fbb200c7 x25: 0000000000000003
x26: 00000000fbb17188 x27: 0000000000000001
x28: 0000000000000001 x29: 00000000fbd1bf98

Code: 00000000 00000000 00000000 00000000 (00000000)
Resetting CPU ...

### ERROR ### Please RESET the board ###

all seems OK for loading vxworks (uhypervisor is a link to uVxWorks binary !), loading the DTB, applying the DPAA2 DPL memory setting for

DPAA2 driver configuration

but like you, at the end, still blocked on starting VxWorks !!!

how analysing this output, how defining a diagnotic about this ?!?

WindRiver is working with us on this .... no found yet the reason

VBR

Thierry LOUSSOT

Re: Synchronous Abort " handler error

Thierry_LOUSSOT — Wed, 19 Jun 2024 08:50:06 GMT

Hi All

Finally the solution of issue on booting VxWorks image is relevant to the Uboot version as the Uboot version is not correct to boot later VxWorks image

Please need to report to the step described into this post, to update Uboot version from SD card device (as available on my board LX2160A-RDB-B), not too complex.

LX2160ARDB – How to update composite firmware in FlexSPI NOR Flash and SD/eMMC card using an SD card - NXP Community

From readme file defined into BSP for my board LX2160A-RDB-B, it is specified the lsdk2012

So take care to specify the correct Uboot binary version, as .../lsdk<number>/...

wget https://www.nxp.com/lgfiles/sdk/lsdk2012/firmware_lx2160ardb_rev2_uboot_sdboot.img

and after follow the description specified into previous link (LX2160ARDB – How to update co...)

From booting on SD card : all works fine now !!!! : so I can use my board under VxWorks !

but I get an issue to launch Uboot from XSPI device BANK 0

_____________________________________________

Resume : I have tried under Uboot shell to flash the xspiboot device (only on BANK)... to boot from "XSPI BANK 0" device instead of the SD card but it doesn't work (DEL 19 under my board is lighted all the time ????

what's wrong ???

______________________________________________________

Description of all steps to update XSPI device :

get binary under web :

wget https://www.nxp.com/lgfiles/sdk/lsdk2012/firmware_lx2160ardb_rev2_uboot_xspiboot.img

copy the binary (from USB key) under SD card at an offet 150500 block of 512 bytes :

dd if=firmware_lx2160ardb_rev2_uboot_xspiboot.img of=/dev/sdb bs=512 seek=150500

Get size of binary data :
size memory of firmware_lx2160ardb_rev2_uboot_xspiboot.img = 52.531.420 bytes (=32190DC)

So I have then typed this command, from uboot (well launched from SD cartd)

mmc read 0xa0000000 24be4 190d2
(offset of 150500 blocks of 512 octets -> 150500 => 0x24be4)
(190d2 as 52.531.420 bytes/512 = 102600 => 0x190C8, and I add 10 blocs (+0x0a) => 0x190d2

Outpu Results :

MMC read: dev # 0, block # 150500, count 102610 ... 102610 blocks read: OK

And Just to finish to write into the NorFlash "Bank 0"

=> sf probe 0:0
SF: Detected mt35xu512aba with page size 256 Bytes, erase size 128 KiB, total 64 MiB

=> sf erase 0 +32190DC
SF: 52559872 bytes @ 0x0 Erased: OK
=> sf write 0xa0000000 0x0 32190DC
device 0 offset 0x0, size 0x32190dc
SF: 52531420 bytes @ 0x0 Written: OK

So XSPI erase+write seems OK but when I try to boot on XSPI BANK 0

DEL 19 is lighed, FAN is running a lot ???? and nothing is written ou serial console : the Uboot is not correctly launched, why ?

If someone has an idea how to write correctly on XSPI BANK 0 from uboot shell ?

I don't see my mistake ....

Thanks for any help

VBR

Thierry LOUSSOT