RobVanSchelven Posted April 22, 2016 Posted April 22, 2016 Hi All, A question from a linux newbe i want to build a custom image for an A13-SOM-512 from Olimex. I followed the next instructions from page www.armbian.com/using-armbian-tools/: apt-get -y -qq install git git clone --depth 1 https://github.com/igorpecovnik/lib cp lib/compile.sh . nano compile.sh # alter if necessary ./compile.sh After selecting linux-som-a13 from the dialog "Select one of the supported boards" i receive a messages [ error ] ERROR in function source [ main.sh:103 ] [ error ] Board configuration does not define valid kernel config [ o.k. ] Process terminated Is the A13 not supported or do i need to create a kernel config file myself? To make sure all software was setup correctly i repeated the step for an A20 device and that went fine. Thanks, Rob
zador.blood.stained Posted April 22, 2016 Posted April 22, 2016 Building kernel for some boards was temporarily disabled recently - it will be enabled back soon.
Guest RobVanSchelven Posted April 22, 2016 Posted April 22, 2016 Thanks for the reply. I am looking forward and continue to study linux in the meantime
RobVanSchelven Posted May 2, 2016 Author Posted May 2, 2016 Hi All, I discovered that the build utility is working again for the A13, thanks for that !! I tried build an SD card image but the build script ended with errors. (see attachment) Settings: Full SD image, for A13, next (Latest stable kernel), Jessie Debian 8, Image with console interface Any advice to solve this is welcome! Thanks, Rob
RobVanSchelven Posted May 2, 2016 Author Posted May 2, 2016 Thanks for your hint. This helped !. An image is now created, however an error is displayed during boot of the board The message is: U-Boot SPL 2016.01-armbian (May 02 2016 - 17:11:20) DRAM: 512 MiB Failed to set core voltage! Can't set CPU frequency Could not determine boot source Some "warning/error" message are display during the execution of script. See attached image I am not sure if those messages are the source of the problem, or if i have to do something myself
zador.blood.stained Posted May 2, 2016 Posted May 2, 2016 Something is still wrong. Did you alter any build settings? Can you please post contents of "debug/output.log" on pastebin or similar service? Edit: Also please test this prebuilt image.
Igor Posted May 2, 2016 Posted May 2, 2016 Perhaps cache is broken? Remove: output/cache/rootfs and run again with CLEAN_LEVEL=""
zador.blood.stained Posted May 2, 2016 Posted May 2, 2016 Perhaps cache is broken? Remove: output/cache/rootfs and run again with CLEAN_LEVEL="" Not only cache, but also kernel package was not found without failing earlier at compilation stage, so it's hard to say anything without seeing the debug log.
RobVanSchelven Posted May 2, 2016 Author Posted May 2, 2016 Ok.. I will clear the cache and try again and let you know. btw.. The image you send me won't boot too, at least same message as my build. Probably my SD write / remove procedure is not correct. (sorry, i am still new to Linux) Do i have to unmount the SD card after the image is written, before i remove the SD card from my PC?
zador.blood.stained Posted May 2, 2016 Posted May 2, 2016 If you have message like this with my prebuilt image U-Boot SPL 2016.01-armbian (May 02 2016 - 17:11:20) DRAM: 512 MiB Failed to set core voltage! Can't set CPU frequency Could not determine boot source then it's possible that SPL/u-boot is broken for some boards (in addition to your building issues), another SPL related issue was reported today for another board. Probably my SD write / remove procedure is not correct. (sorry, i am still new to Linux)Do i have to unmount the SD card after the image is written, before i remove the SD card from my PC? It's better if you unmount the card if it gets automounted after writing image to it, but this should not affect SPL/u-boot in any case.
RobVanSchelven Posted May 2, 2016 Author Posted May 2, 2016 Ok.. A little step further set CLEAN_LEVEL="" deleted output/cache/rootfs Here's the boot result: U-Boot SPL 2016.01-armbian (May 02 2016 - 19:43:33) DRAM: 512 MiB Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC U-Boot 2016.01-armbian (May 02 2016 - 19:43:33 +0200) Allwinner Technology CPU: Allwinner A13 (SUN5I) I2C: ready DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 1024x768 vga console (overscan 0x0) In: serial Out: vga Err: vga Net: No ethernet found. starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 scanning bus 0 for devices... 2 USB Device(s) found Hit any key to stop autoboot: 2 1 0 switch to partitions #0, OK mmc0 is current device bad MBR sector signature 0xb1b3 bad MBR sector signature 0xb1b3 Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2426 bytes read in 212 ms (10.7 KiB/s) ## Executing script at 43100000 Wrong image format for "source" command SCRIPT FAILED: continuing... USB device 0: unknown device No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. =>
zador.blood.stained Posted May 3, 2016 Posted May 3, 2016 Hm. Just to be clear, how exactly do you write your images to SD card?
tkaiser Posted May 3, 2016 Posted May 3, 2016 Hm. Just to be clear, how exactly do you write your images to SD card? And in case you're using Rufus please check image writing process through verify (or better follow the recommended test procedure if the card hasn't been tested before. Either using H2testw or f3)
RobVanSchelven Posted May 3, 2016 Author Posted May 3, 2016 I started a new build this morning with a change in the compile script. as: CLEAN_LEVEL="make, alldebs, images, cache, sources" This time the build ended without any error or warning Using an USB card reader / writer and a original Sandisk Ultra 8GB uSD card (checked and also used with original Olimex image) I tried 2 options. - card formatted as FAT32 - unformatted card (partitions removed with Gparted program) Final results are however the same. Insert USB/SDcard in Linux PC (Ubuntu 14 running in VMWare) Ubunti shows USB device in left menu. Under devices says 7.9GB volume Start terminal and using dmesg to check device name .. which is sdc issue command: dd bs=1M if=Armanian...raw of=/dev/sdc wait.. message 1223+0 records in 1223+0 records out 1282408448 bytes (1.3 GB) copied, 131.057 s, 9.8 MB/s Remove SD card-reader from USB port while SD still in the reader/writer Insert card in A13 board and power up. Below is the bootlog.. although finaly stuck in Starting kernel.... I must admit that in this build i made some changes to the kernel .. like enabled and disabled drivers.. I will retry with an original file. Thanks, Rob U-Boot SPL 2016.01-armbian (May 03 2016 - 09:15:50) DRAM: 512 MiB Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC U-Boot 2016.01-armbian (May 03 2016 - 09:15:50 +0200) Allwinner Technology CPU: Allwinner A13 (SUN5I) I2C: ready DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 1024x768 vga console (overscan 0x0) In: serial Out: vga Err: vga Net: No ethernet found. starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 scanning bus 0 for devices... 2 USB Device(s) found 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 2426 bytes read in 213 ms (10.7 KiB/s) ## Executing script at 43100000 0 bytes read in 152 ms (0 Bytes/s) 0 bytes read in 162 ms (0 Bytes/s) 18096 bytes read in 567 ms (30.3 KiB/s) 4039123 bytes read in 585 ms (6.6 MiB/s) 6047000 bytes read in 856 ms (6.7 MiB/s) Kernel image @ 0x46000000 [ 0x000000 - 0x5c4518 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4039059 Bytes = 3.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 49000000 Booting using the fdt blob at 0x49000000 Loading Ramdisk to 49c25000, end 49fff193 ... OK Loading Device Tree to 49c1d000, end 49c246af ... OK Starting kernel ...
zador.blood.stained Posted May 3, 2016 Posted May 3, 2016 So you are writing SD from VMWare? What is your host OS? Please find and enable "Early printk" in kernel config and change "console=tty0" to "console=ttyS0,115200" in boot script, it should help getting output from the kernel.
RobVanSchelven Posted May 3, 2016 Author Posted May 3, 2016 Host OS = win7/64 Thanks, i will !! and let you know
zador.blood.stained Posted May 3, 2016 Posted May 3, 2016 Host OS = win7/64 Then please transfer images to your host and write them with Rufus, it should be more reliable.
tkaiser Posted May 3, 2016 Posted May 3, 2016 Sandisk Ultra 8GB uSD card (checked and also used with original Olimex image) My advise was to check the process and not only rely on 'card worked a while ago'. For a reason: Several card readers (or even USB ports, eg. front ports that are not attached to the MB but with unshielded wires) might be responsible for data corruption. Using H2testw or f3 checks for this also when used in absolutely the same way as the image is burned. And when you use Rufus simply take the time to let Rufus verify the burning process.
RobVanSchelven Posted May 3, 2016 Author Posted May 3, 2016 Thanks, just a question. Is the .raw image generated by the script the same format as .img used by Win32Diskimager?
RobVanSchelven Posted May 3, 2016 Author Posted May 3, 2016 Ok.. completed a new build without modifactions to the kernel Written image to sd card using win32diskimager Same boot output as above... Tonight i will start a rebuild with early printk and see what happens Thanks all !
RobVanSchelven Posted May 3, 2016 Author Posted May 3, 2016 Update.. rebuild again from scratch.. Enabled Early printk and changed the console settings in boot.cmd The boot remains stuck in Loading Kernel.. unfortunately no extra info is send to the console. Actually the same result as in thread #16 I have been playing a lot over the last week with a number of different build tools and installed a lot of software. Would it be advisable to start over with a plain and clean linux? Thanks, Rob
zador.blood.stained Posted May 4, 2016 Posted May 4, 2016 I have been playing a lot over the last week with a number of different build tools and installed a lot of software. Would it be advisable to start over with a plain and clean linux? This shouldn't be a problem Update.. rebuild again from scratch.. Enabled Early printk and changed the console settings in boot.cmd The boot remains stuck in Loading Kernel.. unfortunately no extra info is send to the console. Actually the same result as in thread #16 Are you sure that you updated boot script correctly? Where/how did you changed it? Please post your script here and check that you don't have additional u-boot messages compared to post #16 Edit: Just remembered, you also need to add "earlyprintk" to kernel command line too for it to activate.
RobVanSchelven Posted May 6, 2016 Author Posted May 6, 2016 Hi, following is what i did and checked again to be sure. at the generated SD card i modified the text line in the file boot.cmd as follows setenv bootargs "console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 cgroup_enable=memory swapaccount=1 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=${verbosity}" i also enabled Early printk in the linux configuration before a new build.
zador.blood.stained Posted May 6, 2016 Posted May 6, 2016 at the generated SD card i modified the text line in the file boot.cmd as follows Did you recompile it to boot.scr with "mkimage" as stated at the end of file? Also, as I said, please append "earlyprintk" to bootargs string, i.e after "console=ttyS0,115200"
michalaco Posted July 4, 2017 Posted July 4, 2017 Any development in this topic? I'm stuck with the "Starting kernel . . ." on the LCD i have armbian logo and probably the same output (i was unable to change the resolution) as on the serial console..... i am using the fresh image generated with Igor's great compiler. Olimex A13 SOM 512mb with Samsung ram Kind Regards, Michal
Recommended Posts