Olimex Support Forum

OLinuXino Android / Linux boards and System On Modules => A20 => Topic started by: Titomax on January 28, 2020, 05:54:23 PM

Title: [A20-SOM204] New A20-SOM204-1G-M module doesn't boot with latest mainline image
Post by: Titomax on January 28, 2020, 05:54:23 PM
Hi,
we just received a A20-SOM204-1G-M module, the new version without Gigabit PHY and with only the Megabit PHY mounted.
If we try to boot the SOM with the latest official Olimex mainline image:

Armbian_5.92.4_Olinuxino-a20_Ubuntu_bionic_next_5.2.21_desktop

from: ftp://staging.olimex.com/Allwinner_Images/A20-OLinuXino/1.latest_mainline_images/bionic/images/

the system loads U-BOOT but doesn't finalize the booting process.

See the starting log:

U-Boot SPL 2019.04-armbian (Dec 12 2019 - 08:40:57 +0200)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
EEPROM: Ready
Config: Valid
Trying to boot from MMC1
U-Boot 2019.04-armbian (Dec 12 2019 - 08:40:57 +0200) Allwinner Technology
CPU:   Allwinner A20 (SUN7I)
Model:  Rev.C2
Serial:000117A4
MAC:   30:1F:9A:D0:8D:38
I2C:   ready
DRAM:  1 GiB
NAND:  0 MiB
MMC:   mmc@1c0f000: 0, mmc@1c12000: 1
Loading Environment from EXT4... OK
In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Net:   eth0: ethernet@1c50000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 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
3798 bytes read in 2 ms (1.8 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
230 bytes read in 1 ms (224.6 KiB/s)
8426252 bytes read in 471 ms (17.1 MiB/s)
7606112 bytes read in 422 ms (17.2 MiB/s)
Found mainline kernel configuration
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
467 bytes read in 7 ms (64.5 KiB/s)
Applying kernel provided DT overlay sun7i-a20-spi2-spidev.dtbo
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
1005 bytes read in 5 ms (196.3 KiB/s)
Applying kernel provided DT overlay sun7i-a20-spi2.dtbo
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Error applying DT overlays, restoring original DT
## Loading init Ramdisk from Legacy Image at 43200000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8426188 Bytes = 8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3798 bytes read in 2 ms (1.8 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
230 bytes read in 1 ms (224.6 KiB/s)
8426252 bytes read in 470 ms (17.1 MiB/s)
7606112 bytes read in 422 ms (17.2 MiB/s)
Found mainline kernel configuration
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
467 bytes read in 7 ms (64.5 KiB/s)
Applying kernel provided DT overlay sun7i-a20-spi2-spidev.dtbo
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
1005 bytes read in 5 ms (196.3 KiB/s)
Applying kernel provided DT overlay sun7i-a20-spi2.dtbo
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Error applying DT overlays, restoring original DT
## Loading init Ramdisk from Legacy Image at 43200000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8426188 Bytes = 8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
NAND booting is temporary disabled.
scanning bus for devices...
SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Device 0: unknown device
Device 0: unknown device
DMA reset timeout
DMA reset timeout
=>


Using the latest official A20-SOM204 image based on legacy kernel:

Armbian_5.41_Olimex-som204-a20_Ubuntu_xenial_default_3.4.113_desktop

the system boots up correctly but the Megabit Ethernet appears to be disabled (ifconfig shows me only "lo" interface).

How can we test this A20-SOM204-1G-M version ?
Is an image with Megabit PHY enabled and working available to download?

Thanks in advance.


NOTE: Please update the ordering code description on the Olimex Site because following the ordering page indications A20-SOM204-1G-M should be a A20-SOM204-1G with Megabit PHY mounted "in addition" to the Gigabit one and not "instead".

Title: Re: [A20-SOM204] New A20-SOM204-1G-M module doesn't boot with latest mainline image
Post by: LubOlimex on February 14, 2020, 03:00:02 PM
The board variant is very new and not yet added, so you'd have to do some manual configuration. Get this:

http://repository.olimex.com/pool/main/l/linux-u-boot-olinuxino-a20-next/linux-u-boot-olinuxino-a20-next_5.92.5_armhf.deb

wget http://repository.olimex.com/pool/main/l/linux-u-boot-olinuxino-a20-next/linux-u-boot-olinuxino-a20-next_5.92.5_armhf.deb

mkdir aaa

dpkg -x linux-u-boot-olinuxino-a20-next_5.92.5_armhf.deb ./aaa

cd aaa/usr/lib/linux-u-boot-next-olinuxino-a20_5.92.5_armhf/

There is u-boot-sunxi-with-spl.bin inside, find it and write it to the card

dd if=u-boot-sunxi-with-spl.bin of=/dev/sdXXX bs=1k seek=8
Title: Re: [A20-SOM204] New A20-SOM204-1G-M module doesn't boot with latest mainline image
Post by: vopima2188 on February 22, 2020, 09:11:59 AM
Quote from: LubOlimex on February 14, 2020, 03:00:02 PMThe board variant is very new and not yet added, so you'd have to do some manual configuration. Get this:

http://repository.olimex.com/pool/main/l/linux-u-boot-olinuxino-a20-next/linux-u-boot-olinuxino-a20-next_5.92.5_armhf.deb

wget http://repository.olimex.com/pool/main/l/linux-u-boot-olinuxino-a20-next/linux-u-boot-olinuxino-a20-next_5.92.5_armhf.deb

mkdir aaa

dpkg -x linux-u-boot-olinuxino-a20-next_5.92.5_armhf.deb ./aaa

cd aaa/usr/lib/linux-u-boot-next-olinuxino-a20_5.92.5_armhf/

There is u-boot-sunxi-with-spl.bin inside, find it and write it to the card

dd if=u-boot-sunxi-with-spl.bin of=/dev/sdXXX bs=1k seek=8

Hi buddy, is there anyway we can automate the process while it comes to large scale partially.

Regards,
V.Smith WalmartOne (https://walmartone.fyi/)
Title: Re: [A20-SOM204] New A20-SOM204-1G-M module doesn't boot with latest mainline image
Post by: JohnS on February 22, 2020, 09:43:14 AM
Just copy the result of the steps.

John
Title: Re: [A20-SOM204] New A20-SOM204-1G-M module doesn't boot with latest mainline image
Post by: olimex on February 24, 2020, 08:18:55 AM
we will release new A20 image with all boards (57 different versions) later this week, so there will be no need for these steps
Title: Re: [A20-SOM204] New A20-SOM204-1G-M module doesn't boot with latest mainline image
Post by: dpierleo on February 24, 2020, 10:06:07 AM
Quote from: olimex on February 24, 2020, 08:18:55 AMwe will release new A20 image with all boards (57 different versions) later this week, so there will be no need for these steps

Hi olimex,

in another post:

https://www.olimex.com/forum/index.php?topic=7322.0 (https://www.olimex.com/forum/index.php?topic=7322.0)

I warned that an important feature is wrongly missing in kernel build.
I think it is necessary to enable:

<M> X-Powers AXP20X and AXP22X AC power supply driver

in kernel configuration for having the necessary driver axp20x_ac_power enabled, otherwise we can have important issues in battery level recognition.

Thanks