Synchronous abort handler in boot for le potato

I need an SBC for my duet3d control board and since I’m not using a raspberry pi, I need it to run armbian. I tried both a samsung evo and an evo select but I cannot get past uboot. Normally I’m assuming this is an armbian issue but for some reason my firewall keeps blocking armbian’s pages so I can’t go there for help. I’m hoping there’s some help I can get from here instead.

Using UART, I was able to pull the following from boot up of the potato:

no sdio debug board detected
TE: 1945610
BL2 Built : 11:58:42, May 27 2017.
gxl gc3c9a84 -
set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 3
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x00018400
Load bl33 from SD, src: 0x0003c200, des: 0x01000000, size: 0x000af000
NOTICE: BL3-1: v1.0(release):3348978
NOTICE: BL3-1: Built : 15:44:01, May 12 2017
[BL31]: GXL CPU setup!
[Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07]
68 41 a1 46 8 4e 5a ab 98 ff fb 7f [2.348232 Inits done]
secure task start!
high task start!
low task start!
ERROR: Error initializing runtime service opteed_fast
U-Boot 2022.07-armbian (Nov 02 2022 - 05:55:21 +0000) libretech-cc
Model: Libre Computer AML-S905X-CC
SoC: Amlogic Meson GXL (S905X) Revision 21:d (84:2)
Core: 169 devices, 27 uclasses, devicetree: separate
MMC: mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In: serial
Out: serial
Err: serial
[BL31]: tee size: 0
[BL31]: tee size: 0
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  2  1  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
8147 bytes read in 3 ms (2.6 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: amlogic/meson-gxl-s905x-libretech-cc.dtb
Current variant: 
112 bytes read in 2 ms (54.7 KiB/s)
Current fdtfile after armbianEnv: amlogic/meson-gxl-s905x-libretech-cc.dtb
Mainline bootargs: root=UUID=09c6f05b-ec67-41ab-a7e3-96db592411bc rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=573f299f-01 libata.force=noncq usb-storage.quirks=    cgroup_enable=memory swapaccount=1
22220675 bytes read in 961 ms (22.1 MiB/s)
26530304 bytes read in 1148 ms (22 MiB/s)
39870 bytes read in 7 ms (5.4 MiB/s)
232 bytes read in 4 ms (56.6 KiB/s)
Applying kernel provided DT fixup script (meson-fixup.scr)
## Executing script at 32000000
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    22220611 Bytes = 21.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04080000
Booting using the fdt blob at 0x4080000
Loading Ramdisk to 7aa0b000, end 7bf3bf43 ... OK
Loading Device Tree to 000000007a998000, end 000000007aa0afff ... OK
"Synchronous Abort" handler, esr 0x96000004
elr: 0000000001065468 lr : 0000000001054df4 (reloc)
elr: 000000007dfb4468 lr : 000000007dfa3df4
x0 : 23ce9f9e734c5585 x1 : 000000007dfbc140
x2 : 0000000000000010 x3 : 0000000000000000
x4 : 0000000000000000 x5 : 23ce9f9e734c5585
x6 : 000000007bf54e10 x7 : 0000000000000000
x8 : 0000000000000007 x9 : 0000000000000000
x10: 0000000000006884 x11: 000000007bf40e2c
x12: 0000000000006828 x13: 000000007bf40de8
x14: 000000007a998000 x15: 0000000000000020
x16: 000000007bf3bf43 x17: 0000000000000000
x18: 000000007bf4cdb0 x19: 000000007af41040
x20: 000000007df4fb20 x21: 000000007dfbc140
x22: 0000000000001000 x23: 000000007bf54d60
x24: 000000007dfdac00 x25: 0000000001000000
x26: 0000000001000000 x27: 0000000001000000
x28: 0000000000001000 x29: 000000007bf40de0
Code: eb02009f 54000061 52800000 14000006 (386468a3)
Resetting CPU ...
resetting ...
bl31 reboot reason: 0xd
bl31 reboot reason: 0x0
system cmd 1.

We don’t really support Armbian here outside to very simple stuff. However, their images in the last few days have been buggy so that is probably why. We do recommend that you use our images instead of Armbian due to numerous tweaks we have in our images over what Armbian provides.

I may have no choice, although there are no directions for non-armbian builds with Duet3d boards in SBC mode.

After taking a brief look at it, it seems the only thing you need to do on our images is enable SPI:

sudo ldto enable spicc spicc-spidev 

#test that it is working and if it works, merge it permanently

sudo ldto merge spicc spicc-spidev

The rest of the instructions look fairly standard.

1 Like

Wow, I didn’t even link to the article. Thanks for going out of your way to be so helpful. I’ll try this again tomorrow.

1 Like

Let us know if you encounter any issues with the instructions. We can help you debug it so other people can use this as a reference if they want to do the same.

Is sd_uhs=1 enabled on the raspbian images? Where is that setting? The guide mentioned “DCS uses SPI buffer sizes of 8KiB whereas the default Armbian buffer size is limited to 4KiB.” What is it set for in your raspbian builds? How can that be changed? How do I create a password for the raspbian image from a Mac? the openssl syntax seems different.

  1. SD UHS
  2. Test to see if it works with the default SPI settings. The 4K buffer is a Raspberry Pi thing. You can set buffer size for spidev’s module using:
sudo rmmod spidev
sudo modprobe spidev bufsize=8192
echo "options spidev bufsiz=8192" | sudo tee /etc/modprobe.d/spidev.conf
  1. The password thing applies for Raspbian Lite images only. If you are using the desktop, it does not apply as there’s a GUI on startup to set it. You have to Google how to do it on a Mac because we don’t use anything Apple.

I can’t SSH in. connection is refused. I did the openssl step on a linux machine. UART shows its booted and waiting. I can’t log in via UART either, it wont take my name and password, nor pi:raspberry, nor root:1234. nothing

What image are you using?

I am trying to go with raspbian lite.

There’s a bug with the userconf service in the Raspbian image. We have updated the image generation code and out CI will generate new images in 24 hours. For now, configure the first user and ssh using the GUI setup.

the new image doesn’t resize the partition. UART is also not outputting anything anymore.

1 Like

Fixed the issue, the new build will be on the servers in approximately 2 hours. For your existing image, you can run the follow to fix it:

sfdisk -d /dev/mmcblk1 | sed "s/size=\s\+[0-9]*,\s\+type=83/type=83/" | sfdisk --force /dev/mmcblk1
partprobe /dev/mmcblk1
btrfs fi resize max /