ptar100 Posted April 17, 2019 Posted April 17, 2019 Hello , I'm new to Armbian, I'm trying to create an SD image for an Olimex A13 Som card (https://www.olimex.com/Products/SOM/A13/A13-SOM-512/) + A13 Som WIfi (https: //www.olimex.com/Products/SOM/A13/A13-SOM-WIFI/open-source-hardware). After successfully executing the build and transferring the image to SD with Etcher, the boot starts correctly but hangs on Starting Kernel ... Do you have any idea how to solve the problem? Thanks in advance! Board: Not on the list
martinayotte Posted April 17, 2019 Posted April 17, 2019 50 minutes ago, ptar100 said: the boot starts correctly but hangs on Starting Kernel ... This is usually the symptom of wrong DT. Also, make sure to have "verbosity=7" and "console=serial" and use USB-TTL Serial Debug to look the details of boot process.
ptar100 Posted April 17, 2019 Author Posted April 17, 2019 51 minutes ago, martinayotte said: This is usually the symptom of wrong DT. Also, make sure to have "verbosity=7" and "console=serial" and use USB-TTL Serial Debug to look the details of boot process. Thanks for the reply, I tried again to make a build but the result is always the same! I noticed, however, that the card that is called from the config file is Model: Olimex A13-Olinuxino and at the start there is an error! U-Boot SPL 2019.04-armbian (Apr 17 2019 - 17:05:21 +0200) DRAM: 512 MiB Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC1 I have not made any changes I have only set Olimex A13 Som as the type of card ... is there a problem with the DT of origin? I searched a bit in the various folders and I don't see any other references to the SOM A13 but only to the A13 olinuxino and olinuxino micro board. The boot log: U-Boot SPL 2019.04-armbian (Apr 17 2019 - 17:05:21 +0200) DRAM: 512 MiB Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC1 U-Boot 2019.04-armbian (Apr 17 2019 - 17:05:21 +0200) Allwinner Technology CPU: Allwinner A13 (SUN5I) Model: Olimex A13-Olinuxino I2C: ready DRAM: 512 MiB MMC: mmc@1c0f000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** Setting up a 1024x768 vga console (overscan 0x0) Error: no valid bmp image at 66000000 In: serial Out: vga Err: vga Allwinner mUSB OTG (Peripheral) Net: Warning: usb_ether using MAC address from ROM eth0: usb_ether ** Reading file would overwrite reserved memory ** There is no valid bmp file at the given address starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3798 bytes read in 3 ms (1.2 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 155 bytes read in 2 ms (75.2 KiB/s) 4927321 bytes read in 648 ms (7.3 MiB/s) 7481128 bytes read in 980 ms (7.3 MiB/s) Found mainline kernel configuration 23300 bytes read in 8 ms (2.8 MiB/s) 2266 bytes read in 4 ms (552.7 KiB/s) Applying kernel provided DT fixup script (sun5i-a13-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4927257 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49b4d000, end 49ffff19 ... OK Loading Device Tree to 49ade000, end 49b4cfff ... OK Starting kernel ...
martinayotte Posted April 17, 2019 Posted April 17, 2019 29 minutes ago, ptar100 said: and at the start there is an error! I don't think this error is the source of the problem. Unfortunately, searching in the forum did not reveal any people getting success with this Olimex A13 Som. Since I don't have such board, I can't even trying it myself ... Your chances are tiny, maybe you should stick with Legacy image provided by Olimex.
ptar100 Posted April 17, 2019 Author Posted April 17, 2019 2 hours ago, martinayotte said: I don't think this error is the source of the problem. Unfortunately, searching in the forum did not reveal any people getting success with this Olimex A13 Som. Since I don't have such board, I can't even trying it myself ... Your chances are tiny, maybe you should stick with Legacy image provided by Olimex. Unfortunately I had also tried a solution on the forum but with a negative result. I will try to experiment the same in case I have to come to a solution I will put it here at the disposal of the community. Thanks anyway for the answers Martinayotte. Thanks to the Armbian team for the wonderful job.
Recommended Posts