Hello, happy new year !
I've downloaded A13-OLinuXino-bullseye-minimal-20220928-143706.img.7z from the https://images.olimex.com/release/a13/ location
I uncompressed and copied the image to a micro SD Card, and powered A13. Monitoring it through a serial/USB cable attached to UART1, to my laptop, using command
screen /dev/ttyUSB0 115200
A13 get stuck as the following shows
U-Boot SPL 2021.04+olimex-1-20220927.105322 (Sep 27 2022 - 10:54:20 +0000)
DRAM: 512 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
A13 Board no eeprom found!
PMIC found board is A13-OLinuXino/ A13-OLinuXino WIFI !
Trying to boot from MMC1
U-Boot 2021.04+olimex-1-20220927.105322 (Sep 27 2022 - 10:54:20 +0000) Allwinner Technology
CPU: Allwinner A13 (SUN5I)
ID: A13-OLinuXino Rev.AI2C: ready
DRAM: 512 MiB
MMC: mmc@1c0f000: 0
Loading Environment from EXT4... *** Warning - bad CRC, using default environment
Loading Environment from FAT... ** No device specified **
Setting up a 1024x768 vga console (overscan 0x0)
In: serial
Out: vga
Err: vga
Allwinner mUSB OTG (Peripheral)
Net:
That's at the first boot. When pushing Reset button, at second boot it say's
U-Boot SPL 2021.04+olimex-1-20220927.105322 (Sep 27 2022 - 10:54:20 +0000)
DRAM: 512 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
A13 Board no eeprom found!
PMIC found board is A13-OLinuXino/ A13-OLinuXino WIFI !
Trying to boot from MMC1
U-Boot 2021.04+olimex-1-20220927.105322 (Sep 27 2022 - 10:54:20 +0000) Allwinner Technology
CPU: Allwinner A13 (SUN5I)
ID: A13-OLinuXino Rev.AI2C: ready
DRAM: 512 MiB
MMC: mmc@1c0f000: 0
Loading Environment from EXT4... *** Warning - bad CRC, using default environment
Loading Environment from FAT... ** No device specified **
Setting up a 1024x768 vga console (overscan 0x0)
In: serial
Out: vga
Err: vga
Allwinner mUSB OTG (Peripheral)
Net: eth0: usb_ether
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 3 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2022 bytes read in 3 ms (658.2 KiB/s)
## Executing script at 43100000
Checking for /uEnv.txt...
Checking for /boot/uEnv.txt...
400 bytes read in 3 ms (129.9 KiB/s)
Loaded environment from /boot/uEnv.txt
Loading FIT image...
15811123 bytes read in 1262 ms (11.9 MiB/s)
## Loading kernel from FIT Image at 58000000 ...
Using 'config-4432' configuration
Trying 'kernel-1' kernel subimage
Description: Linux kernel 5.10.105-olimex
Type: Kernel Image
Compression: uncompressed
Data Start: 0x580000d4
Data Size: 6533568 Bytes = 6.2 MiB
Architecture: ARM
OS: Linux
Load Address: 0x40080000
Entry Point: 0x40080000
Hash algo: crc32
Hash value: 07bbff0b
Hash algo: sha1
Hash value: 61e0951c1f96b692559776eea6464ee2d09fb02c
Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading ramdisk from FIT Image at 58000000 ...
Using 'config-4432' configuration
Trying 'ramdisk-1' ramdisk subimage
Description: Ramdisk for kernel 5.10.105-olimex
Type: RAMDisk Image
Compression: Unknown Compression
Data Start: 0x5863b3c8
Data Size: 9207329 Bytes = 8.8 MiB
Architecture: ARM
OS: Linux
Load Address: 0x4fe00000
Entry Point: 0x4fe00000
Hash algo: crc32
Hash value: 1f6cea65
Hash algo: sha1
Hash value: 1e17fbe5de901a7e71b051e09c960b5d890456b0
Verifying Hash Integrity ... crc32+ sha1+ OK
Loading ramdisk from 0x5863b3c8 to 0x4fe00000
WARNING: 'compression' nodes for ramdisks are deprecated, please fix your .its file!
## Loading fdt from FIT Image at 58000000 ...
Using 'config-4432' configuration
Trying 'fdt-1' fdt subimage
Description: unavailable
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x58f032d8
Data Size: 23020 Bytes = 22.5 KiB
Architecture: ARM
Load Address: 0x4fa00000
Hash algo: crc32
Hash value: fe1e1efe
Hash algo: sha1
Hash value: 0d226f727ca4493b9350ba2eb9ea4f28667dfaec
Verifying Hash Integrity ... crc32+ sha1+ OK
Loading fdt from 0x58f032d8 to 0x4fa00000
Booting using the fdt blob at 0x4fa00000
Loading Kernel Image
Loading Ramdisk to 49738000, end 49fffe21 ... OK
Loading Device Tree to 4972f000, end 497379eb ... OK
Starting kernel ...
Third time I try to boot is different (sorry I can't get the whole output)
...
Device 0: unknown device
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-de-ad-be-ef-00-01
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi-a13_olinuxino
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.Config file not found
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.=>
At the second output I can read:
WARNING: 'compression' nodes for ramdisks are deprecated, please fix your .its file!
But I don't know what that means neither how to fix or where that files are
Please any help is welcome
Thanks
It appears the board is attempting to boot from the network but fails (which is normal since the board is not meant to boot from the network). What is more important is that this means it also failed to boot from other sources (like the microSD card).
I believe it is some sort of issue with the microSD card or the image or how it was prepared.
1. Can you try with the base image instead? Namely "A13-OLinuXino-bullseye-base-20220928-143706.img.7z".
2. Can you try to prepare the card with the free version of balenaEtcher software?
Hello, thanks
I did try what you suggested
the base image and using BalenaEtcher
get similar results
I've not a new sd card to try by now, hopefully by the weekend I get one and try again
I'd like to say that I also tried (same sd card) the A13_debian_34_90_mainline_u-boot_release_11_3.7z image and it starts ok
Thanks
Hello
Sorry to say I tried a new SD card, same results
Please any news or advise about are very welcome
Thanks
Hmm, it seems it hangs here too, I found two revision F boards. Same behavior. Investigating it.
Seems to boot fine with this older Armbian-based image:
https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/1.latest_mainline_images/bionic/Armbian_5.92_Olinuxino-a13_Ubuntu_bionic_next_5.3.8_desktop.zip
So it is likely a software configuration issue between latest image and older board revisions.
Edit: It seems to also work with the even older sunxi image from here: https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_mainline_u-boot_release_11_3.7z
Thank you @LubOlimex
I've installed Armbian_5.92_Olinuxino-a13_Ubuntu_bionic_next_5.3.8_desktop.zip and it works, boot ok
And I was able to install node-red, which was my goal
Hopefully bullseye become available sometime. Above all a headless distro.
Thanks
I've notified the developers. I guess RAM memory was changed between revisions and the latest image would not boot on all older revisions. Will see what the Linux guys come up with. Hopefully it would be a quick fix.