Valk

Well got some feedback from SolidRun regarding the emmc issues. Apparently there's a firmware issue currently with the 4GB emmc (8GB is fine) which they're working to get a resolution. Hopefully when my next batch of boards with the 8GB emmc come the issue will be sorted. Really thanks for your help, while not an Armbian issue a lot of useful changes / fixes got done for the clearfog Oh and the resize code works fine now.

Yeah I had improvements with the latest version in that the issue with the emmc throwing heeps of write errors seems to be fixed. Down side is now if I reboot the system it will no longer restart. I'm using the SolidRun image because I'm trying to get technical support from them. Unfortunately the official image gives me emmc write issues. The only one which works perfect is the 3.X kernel but that's both out of date and lacking kernel support for my 3G modem. By stable I only meant working reliably with the clearfog. Anyway hopefully the next batch of clearfogs arrive soon so I can test if it's these last 2 boards I have are faulty or there's an issue.

-- Deleted -- Thought SolidRun's image was faulty but I think I might have broken it so restoring their system image. On a side note I used the 3.10.104 (4.9.5 wouldn't boot) armbian kernel image to get the dtb and vmlinuz files to boot and they managed to boot fine (haven't reset the device). I'm thinking there's a software issue during boot.

Ok well that's annoying... Talking with Solidrun they insisted I try their compiled version of debian to help with resolving the issues. I haven't got back to them yet but I can't fault the solidrun image. I'm at the situation now where I'm using the solidrun u-boot and trying to boot the system via tftp: setenv serverip 192.168.1.240 setenv ipaddr 192.168.1.1 setenv fdt_high 0x07a12000 ( or setenv fdt_high 0xffffffff ) setenv bootargs "selinux=0 cgroup_disable=memory scandelay root=/dev/sda1 rw rootfstype=ext4 console=ttyS0,115200 loglevel=7 rootwait" tftp ${fdtaddr} 4.9/armada-388-clearfog.dtb tftp ${loadaddr} 4.9/vmlinuz-4.9.4-mvebu bootz ${loadaddr} - ${fdtaddr} The system will stall at Starting kernel .... after I can hit the hardware reboot and let the emmc boot (solidrun official image) and it loads fine. https://images.solid-build.xyz/A38X/sr-a38x-debian-jessie-20161101-testing.img.xz https://images.solid-build.xyz/A38X/u-boot.mmc Considering the system is using the solidrun u-boot that crosses it off the list (not that there's really any difference between the armbian one except it has a few nice tweaks) So that leaves the an issue with the dtb file or vmlinuz image. Just went through the dts between the solidrun repo: https://github.com/SolidRun/linux-stable/tree/linux-4.4.y-clearfog/arch/arm/boot/dts and I can't see any meaningful changes. Leaves the last part the image it boots and that's a much bigger needle to solve. Do you experience any issues booting the system if it has been running for say 30 minutes? Going to try the 4.9.5 branch which I just compiled then try specifying the solidrun repo https://github.com/SolidRun/linux-stable/tree/linux-4.4.y-clearfog and see how they go. Really want to get it going with the current kernel stable so the system can be easily kept up to date in the future.

Ok a little difficult. Do you know how I can repair the partition enough to get the file off it? root@clearfogpro:~# ls root@clearfogpro:~# ls /media/ root@clearfogpro:~# mkdir /media/emmc root@clearfogpro:~# mount /dev/mmcblk0p1 /media/emmc/ [ 243.366150] UDF-fs: warning (device mmcblk0p1): udf_fill_super: No partition found (2) [ 243.377055] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x1102d4b) [ 243.384864] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 1th superblock [ 243.394112] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x6b636170) [ 243.401972] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 2th superblock [ 243.409723] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x1102d4b) [ 243.417513] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 1th superblock [ 243.425211] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x6b636170) [ 243.433095] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 2th superblock mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so.

ah sorry after the first reboot, one moment

Ok got the log file: http://sprunge.us/CjIS

While I get it ready as a quick side note. Now when the system boots the leds for Ethernet ports on the switch stay on all the time.

as for spi I get nothing from dmesg and have no mtd devices in /dev

Hmm well usb boot works wonderfully. Got a feeling my problems might be to do with the resize script I can: - boot to USB - dd the system image over - boot the emmc system and do login sequence if I immediately reboot the system (as the system recommends) it fails to boot from emmc with: Trying to boot from MMC Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type **

I was actually looking at the pcb schematic to find the SPI port. Unfortunately if I have to pull apart the heatsink then I'm better off via uart (which is fine). Still "run usbboot" nice touch Thanks for doing that so quick. Hopefully I can get to the bottom of the emmc issues soon. Thanks for all the help.

Yes booting the system properly meant that setting the emmc_fix flag on worked as expected. And yes I didn't need to touch the boot partition in the end. As for the SPI flash you've got me thinking. There's a dip switch for it just need to check where the pins are on the PCB. Hope that's an option because it'll make things much easier. Unfortunately I'm having even more troubles. After installing the system I do an update and install a few packages + hardware (wifi, hostapd, and a few others). I use a script I've had for a while to do the install but unfortunately when it reboots the system it fails to read from the emmc (this .scr file). Hopefully solid-run get back to me with a few details as to what's going on. I've even tried slowing the CPU to 800Mhz with no luck.

Ok well installed via dd root@clearfogpro~# dd if=Armbian_5.24_Clearfogpro_Debian_jessie_next_4.9.4.img 2478080+0 records in 2478080+0 records out 1268776960 bytes (1.3 GB) copied, 1[ 299.354823] mmcblk0: p1 89.472 s, 6.7 MB/s root@clearfogpro:~# sync root@clearfogpro:~# echo 0 > /sys/block/mmcblk0boot0/force_ro root@clearfogpro:~# ifconfig eth0 192.168.0.30 root@clearfogpro:~# ifconfig eth0 netmask 255.255.255.0 root@clearfogpro:~# scp yocto@192.168.0.250:/home/yocto/4.9/u-boot.mmc ./ yocto@192.168.0.250's password: u-boot.mmc 100% 935KB 934.6KB/s 00:00 root@clearfogpro:~# dd if=u-boot.mmc of=/dev/mmcblk0boot0 1869+1 records in 1869+1 records out 957048 bytes (957 kB) copied, 0.143723 s, 6.7 MB/s root@clearfogpro:~# echo 1 > /sys/block/mmcblk0boot0/force_ro root@clearfogpro:~# sync root@clearfogpro:~# mount /dev/mmcblk0p1 /media/emmc/ [ 355.858748] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) root@clearfogpro:~# umount /media/emmc root@clearfogpro:~# poweroff P.S. Forgot to write bs=4M to speed it up Wrote u-boot again because I didn't want to have to restore from uart if it was corrupted. Had it stall again at Starting Kernel ... but I turned it off and let it cool down. Fired it up again and it started working. Not sure what's happening there, need to give solidrun an e-mail.

Yep the customize_image.sh script set emmc_fix=on fine. Be awesome if you could only needing to plugin a usb stick would be a nice setup, that said I'm also grateful that I've been forced to learn how it works instead of trusting magic scripts . Ideally when I get this ready for production I still would prefer to install via Ethernet but USB is still a big improvement

Ok yeah it's probably already patched. I actually was building a clean image to try from scratch and to see if there's any remaining modifications. Currently I'm using rsync because I'm booting from the usb device. fdisk /dev/mmcblk0 d n p 1 16385 <enter> w mkfs.ext4 /dev/mmcblk0p1 ifconfig eth0 192.168.0.30 ifconfig eth0 netmask 255.255.255.0 scp yocto@192.168.0.250:/home/yocto/4.9/u-boot.mmc ./ echo 0 > /sys/block/mmcblk0boot0/force_ro dd if=u-boot.mmc of=/dev/mmcblk0boot0 echo 1 > /sys/block/mmcblk0boot0/force_ro rm u-boot.mmc mkdir /media/emmc mount /dev/mmcblk0p1 /media/emmc rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / /media/emmc/ cp /boot/boot.scr /media/emmc/ umount /media/emmc sync poweroff I do need to find a good way to automate the whole process once I have it working, but that's another day. Hmm I might copy the image to the usb stick and give dd a go

Thanks for all your help. Unfortunately this board has gone through a lot of trial and error so issues like that are not surprising. I've reset all the env variables env default -a saveenv then rebooted but unfortunately stalled again. BootROM - 1.73 Booting from MMC General initialization - Version: 1.0.0 Detected Device ID 6828 High speed PHY - Version: 2.0 Init Customer board board SerDes lanes topology details: | Lane # | Speed| Type | ------------------------------| | 0 | 3 | SATA0 | | 1 | 0 | SGMII1 | | 2 | 5 | PCIe1 | | 3 | 5 | USB3 HOST1 | | 4 | 5 | PCIe2 | | 5 | 0 | SGMII2 | ------------------------------- PCIe, Idx 1: detected no link :** Link is Gen1, check the EP capability PCIe, Idx 2: remains Gen1 High speed PHY - Ended Successfully DDR3 Training Sequence - Ver TIP-1.39.0 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR3 Training Sequence - Ended Successfully BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** U-Boot 2013.01 (Jan 16 2017 - 07:11:29) Marvell version: 2015_T1.0p11 Board: A38x-Customer-Board-1 SoC: MV88F6828 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 1066 [MHz] L2 @ 533 [MHz] TClock @ 250 [MHz] DDR3 @ 533 [MHz] DDR3 32 Bit Width,FastPath Memory Access, DLB Enabled, ECC Disabled DRAM: 1 GiB MMC: mv_sdh: 0 sdhci_transfer_data: Error detected in status(0x408000)! PCI-e 0: Detected No Link. PCI-e 2 (IF 1 - bus 0) Root Complex Interface, Detected Link X1, GEN 1.1 USB2.0 0: Host Mode USB3.0 0: Host Mode USB3.0 1: Host Mode Map: Code: 0x3fed2000:0x3ff97fa4 BSS: 0x3ffefd5c Stack: 0x3f9c1f20 Heap: 0x3f9c2000:0x3fed2000 U-Boot Environment: 0x000f0000:0x00100000 (MMC) Board configuration detected: Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x00 | | egiga1 | SGMII | In-Band | | egiga2 | SGMII | In-Band | egiga0 [PRIME], egiga1, egiga2 Hit any key to stop autoboot: 0 Trying to load boot.scr from mmc 1738 bytes read in 9 ms (188.5 KiB/s) ## Executing script at 03000000 171 bytes read in 8 ms (20.5 KiB/s) 18864 bytes read in 19 ms (968.8 KiB/s) 3243207 bytes read in 184 ms (16.8 MiB/s) 5394896 bytes read in 298 ms (17.3 MiB/s) libfdt fdt_delprop(): FDT_ERR_NOTFOUND fdt - flattened device tree utility commands Usage: fdt addr <addr> [<length>] - Set the fdt location to <addr> fdt boardsetup - Do board-specific set up fdt move <fdt> <newaddr> <length> - Copy the fdt to <addr> and make it active fdt resize - Resize fdt to size + padding to 4k addr fdt print <path> [<prop>] - Recursive print starting at <path> fdt list <path> [<prop>] - Print one level starting at <path> fdt get value <var> <path> <prop> - Get <property> and store in <var> fdt get name <var> <path> <index> - Get name of node <index> and store in <var> fdt get addr <var> <path> <prop> - Get start address of <property> and store in <var> fdt get size <var> <path> [<prop>] - Get size of [<property>] or num nodes and store in <var> fdt set <path> <prop> [<val>] - Set <property> [to <val>] fdt mknode <path> <node> - Create a new node after <path> fdt rm <path> [<prop>] - Delete the node or <property> fdt header - Display header info fdt bootcpu <id> - Set boot cpuid fdt memory <addr> <size> - Add/Update memory node fdt rsvmem print - Show current mem reserves fdt rsvmem add <addr> <size> - Add a mem reserve fdt rsvmem delete <index> - Delete a mem reserves fdt chosen [<start> <end>] - Add/update the /chosen branch in the tree <start>/<end> - initrd start/end addr NOTE: Dereference aliases by omiting the leading '/', e.g. fdt print ethernet0. ## Loading init Ramdisk from Legacy Image at 02880000 ... Image Name: uInitrd Created: 2017-01-18 21:06:55 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3243143 Bytes = 3.1 MiB Load Address: 00000000 Entry Point: 00000000 ## Flattened Device Tree blob at 02040000 Booting using the fdt blob at 0x02040000 reserving fdt memory region: addr=2040000 size=5000 Using Device Tree in place at 02040000, end 02047fff Skipping Device Tree update ('fdt_skip_update' = yes) Limit DDR size at 3GB due to power of 2 requirement of Address decoding Starting kernel ... is that fdt_err_notfound an issue which would stop it booting?

yeah legacy commands which I didn't understand when I first tried to make it work. I just did: env default bootcmd env default bootargs env save then rebooted. Board configuration detected: Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x00 | | egiga1 | SGMII | In-Band | | egiga2 | SGMII | In-Band | egiga0 [PRIME], egiga1, egiga2 Hit any key to stop autoboot: 0 Trying to load boot.scr from mmc 1738 bytes read in 9 ms (188.5 KiB/s) ## Executing script at 03000000 171 bytes read in 7 ms (23.4 KiB/s) ** File not found boot/dtb/armada-38x.dtb ** ** File not found dtb/armada-38x.dtb ** 3243207 bytes read in 184 ms (16.8 MiB/s) 5394896 bytes read in 298 ms (17.3 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC I'll jump in via USB and take a look but I'll call that progress

Sorry I'm still learning everything to do with compiling > installing (which is why I supply the logs like that to highlight mistakes). How should I change the boot commands to use boot.cmd?

Ok well just did a clean image, booted via USB, made sure emmc_fix flag was set to on and copied the files to the emmc. Unfortunately it gets stuck at Starting kerenel ... U-Boot 2013.01 (Jan 16 2017 - 07:11:29) Marvell version: 2015_T1.0p11 Board: A38x-Customer-Board-1 SoC: MV88F6828 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 1066 [MHz] L2 @ 533 [MHz] TClock @ 250 [MHz] DDR3 @ 533 [MHz] DDR3 32 Bit Width,FastPath Memory Access, DLB Enabled, ECC Disabled DRAM: 1 GiB MMC: mv_sdh: 0 sdhci_transfer_data: Error detected in status(0x408002)! PCI-e 0: Detected No Link. PCI-e 2 (IF 1 - bus 0) Root Complex Interface, Detected Link X1, GEN 1.1 USB2.0 0: Host Mode USB3.0 0: Host Mode USB3.0 1: Host Mode Map: Code: 0x3fed2000:0x3ff97fa4 BSS: 0x3ffefd5c Stack: 0x3f9c1f20 Heap: 0x3f9c2000:0x3fed2000 U-Boot Environment: 0x000f0000:0x00100000 (MMC) Board configuration detected: Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x00 | | egiga1 | SGMII | In-Band | | egiga2 | SGMII | In-Band | egiga0 [PRIME], egiga1, egiga2 Hit any key to stop autoboot: 0 Marvell>> Marvell>> setenv bootcmd 'ext2load mmc 0:1 ${fdtaddr} boot/dtb/armada-388-clearfog.dtb;ext2load mmc 0:1 ${loadaddr} boot/zImage;bootz ${loadaddr} - ${fdtaddr}' Marvell>> setenv bootargs 'selinux=0 cgroup_disable=memory scandelay root=/dev/mmcblk0p1 rw rootfstype=ext4 console=ttyS0,115200 loglevel=1 rootwait' Marvell>> saveenv Saving Environment to MMC... Writing to MMC(0)... done Marvell>> boot 18864 bytes read in 18 ms (1023.4 KiB/s) 5394896 bytes read in 298 ms (17.3 MiB/s) ## Flattened Device Tree blob at 01000000 Booting using the fdt blob at 0x01000000 Loading Device Tree to 00ff8000, end 00fff9af ... OK Skipping Device Tree update ('fdt_skip_update' = yes) Limit DDR size at 3GB due to power of 2 requirement of Address decoding Starting kernel ... If you like I'm happy to rebuild the kernel with the earlyprintk flag turned on to see if we can get any debug information because I'd like to not require a patch.

Yeah that's been my experience so far. I'll remove the patch and do a clean build now to see if emmc_fix alone is enough.

I only have one patch to: arch/arm/boot/dts/armada-388-clearfog.dts ext.patch diff --git a/arch/arm/boot/dts/armada-388-clearfog.dts.rej b/arch/arm/boot/dts/armada-388-clearfog.dts.rej new file mode 100644 index 0000000..86e945d --- /dev/null +++ b/arch/arm/boot/dts/armada-388-clearfog.dts.rej @@ -0,0 +1,11 @@ +--- arch/arm/boot/dts/armada-388-clearfog.dts ++++ arch/arm/boot/dts/armada-388-clearfog.dts +@@ -266,7 +266,7 @@ + + sdhci@d8000 { + bus-width = <4>; +- cd-gpios = <&gpio0 20 GPIO_ACTIVE_LOW>; ++ non-removable; + no-1-8-v; + pinctrl-0 = <&clearfog_sdhci_pins + &clearfog_sdhci_cd_pins>; I also have a line in customize-image.sh to enable emmc_fix Don't touch the u-boot but it definitely doesn't create the u-boot.mmc files after I compile. That said if I don't have CREATE_PATCHES it builds the image fine. As a roundabout solution I put the patch in the userpatches/kernel/marvell-next/ directory

I see that's a shame. Well just as a little extra it was working when the kernel was the 4.8.X

Trying to build an image and having troubles right at the end. When I have CREATE_PATCHES="yes" I get a few errors during the last part. Free space: tmpfs 1.5G 853M 648M 57% /usr/local/dev/Armbian/output/cache/sdcard-next-clearfogpro-jessie-no [ o.k. ] Ending debootstrap process and preparing cache [ jessie ] jessie-ng-armhf.a63...128.tar.bz2: 644MB [ 110MB/s] [=========================================================] 109% [ o.k. ] Applying distribution specific tweaks for [ jessie ] [ o.k. ] Applying common tweaks [ o.k. ] Installing kernel [ linux-image-next-mvebu ] [ o.k. ] Installing u-boot [ linux-u-boot-next-clearfogpro ] [ o.k. ] Installing headers [ linux-headers-next-mvebu ] [ o.k. ] Installing DTB [ linux-dtb-next-mvebu ] [ o.k. ] Installing board support package [ clearfogpro ] Hit http://security.debian.org jessie/updates InRelease Hit http://security.debian.org jessie/updates/main armhf Packages Ign http://httpredir.debian.org jessie InRelease Hit http://apt.armbian.com jessie InRelease Hit http://security.debian.org jessie/updates/contrib armhf Packages Hit http://security.debian.org jessie/updates/non-free armhf Packages Hit http://httpredir.debian.org jessie-updates InRelease Hit http://security.debian.org jessie/updates/contrib Translation-en Hit http://apt.armbian.com jessie/main armhf Packages Hit http://security.debian.org jessie/updates/main Translation-en Hit http://security.debian.org jessie/updates/non-free Translation-en Hit http://httpredir.debian.org jessie-backports InRelease Hit http://apt.armbian.com jessie/utils armhf Packages Hit http://httpredir.debian.org jessie Release.gpg Hit http://apt.armbian.com jessie/jessie-desktop armhf Packages Get:1 http://httpredir.debian.org jessie-updates/main armhf Packages/DiffIndex [6916 B] Hit http://httpredir.debian.org jessie-updates/contrib armhf Packages Get:2 http://httpredir.debian.org jessie-updates/non-free armhf Packages/DiffIndex [736 B] Hit http://httpredir.debian.org jessie-updates/contrib Translation-en Get:3 http://httpredir.debian.org jessie-updates/main Translation-en/DiffIndex [2704 B] Get:4 http://httpredir.debian.org jessie-updates/non-free Translation-en/DiffIndex [736 B] Get:5 http://httpredir.debian.org jessie-backports/main armhf Packages/DiffIndex [27.8 kB] Get:6 http://httpredir.debian.org jessie-backports/contrib armhf Packages/DiffIndex [23.1 kB] Get:7 http://httpredir.debian.org jessie-backports/non-free armhf Packages/DiffIndex [6562 B] Get:8 http://httpredir.debian.org jessie-backports/contrib Translation-en/DiffIndex [6484 B] Get:9 http://httpredir.debian.org jessie-backports/main Translation-en/DiffIndex [27.8 kB] Get:10 http://httpredir.debian.org jessie-backports/non-free Translation-en/DiffIndex [14.2 kB] Ign http://apt.armbian.com jessie/jessie-desktop Translation-en Ign http://apt.armbian.com jessie/main Translation-en Hit http://httpredir.debian.org jessie Release Ign http://apt.armbian.com jessie/utils Translation-en Hit http://httpredir.debian.org jessie/main armhf Packages Hit http://httpredir.debian.org jessie/contrib armhf Packages Hit http://httpredir.debian.org jessie/non-free armhf Packages Hit http://httpredir.debian.org jessie/contrib Translation-en Hit http://httpredir.debian.org jessie/main Translation-en Hit http://httpredir.debian.org jessie/non-free Translation-en Fetched 117 kB in 18s (6318 B/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... hostapd is already the newest version. The following NEW packages will be installed: sunxi-tools 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 34.8 kB of archives. After this operation, 88.1 kB of additional disk space will be used. Get:1 http://apt.armbian.com/ jessie/utils sunxi-tools armhf 1.4.1-1~armbian5.24.161202+1 [34.8 kB] Fetched 34.8 kB in 0s (936 kB/s) perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = "en_AU:en", LC_ALL = (unset), LANG = "en_AU.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). /usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or directory /usr/bin/locale: Cannot set LC_MESSAGES to default locale: No such file or directory /usr/bin/locale: Cannot set LC_ALL to default locale: No such file or directory Selecting previously unselected package sunxi-tools. (Reading database ... 48589 files and directories currently installed.) Preparing to unpack .../sunxi-tools_1.4.1-1~armbian5.24.161202+1_armhf.deb ... Unpacking sunxi-tools (1.4.1-1~armbian5.24.161202+1) ... Setting up sunxi-tools (1.4.1-1~armbian5.24.161202+1) ... [ o.k. ] Calling image customization script [ customize-image.sh ] [ o.k. ] Preparing image file for rootfs [ clearfogpro jessie ] [ o.k. ] Current rootfs size [ 770 MiB ] [ o.k. ] Creating blank image for rootfs [ 1207 MiB ] 1.18GB [ 221MB/s] [===========================================================================================>] 100% [ o.k. ] Creating partitions [ root: ext4 ] flock: unrecognised option '--verbose' Usage: flock [-sxun][-w #] fd# flock [-sxon][-w #] file [-c] command... flock [-sxon][-w #] directory [-c] command... Options: -s --shared Get a shared lock -x --exclusive Get an exclusive lock -u --unlock Remove a lock -n --nonblock Fail rather than wait -w --timeout Wait for a limited amount of time -o --close Close file descriptor before running command -c --command Run a single command string through the shell -h --help Display this text -V --version Display version [ .... ] Creating rootfs [ ext4 ] [ o.k. ] Copying files to image [ sdcard-next-clearfogpro-jessie-no.raw ] 686.32M 99% 119.78MB/s 0:00:05 (xfr#42638, to-chk=0/53327) sent 689.45M bytes received 856.72K bytes 125.51M bytes/sec total size is 690.20M speedup is 1.00 [ o.k. ] Copying files to /boot partition [ sdcard-next-clearfogpro-jessie-no.raw ] 14.67M 99% 208.28MB/s 0:00:00 (xfr#48, to-chk=0/53) sent 14.67M bytes received 946 bytes 29.35M bytes/sec total size is 14.67M speedup is 1.00 [ o.k. ] Free space: [ SD card ] tmpfs 1.5G 770M 731M 52% /usr/local/dev/Armbian/output/cache/sdcard-next-clearfogpro-jessie-no /dev/loop0p1 1.2G 798M 318M 72% /usr/local/dev/Armbian/output/cache/mount-next-clearfogpro-jessie-no [ o.k. ] Writing U-boot bootloader [ /dev/loop0 ] [ error ] ERROR in function write_uboot [ common.sh:447 ] [ error ] U-boot bootloader failed to install [ @host ] [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ debootstrap-ng.sh:525 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated With CREATE_PATCHES set to no it compiles fine. I've checked out the latest version.

So current score: - 3.10.X works but can't see sierra wireless drivers (even though I've turned on all the usb serial and sierra wireless settings) - 4.4.X Boots, can see sierra wireless, issues writing to emmc, e.g. [ 264.795541] EXT4-fs (mmcblk0p1): previous I/O error to superblock detected usr/share/consol[ 264.803940] mmcblk0: error -110 sending status command, retrying efonts/Greek-Ter[ 264.811277] mmcblk0: error -110 sending status command, retrying minusBoldVGA14.p[ 264.818761] mmcblk0: error -110 sending status command, aborting sf.gz - 4.8.X Stalls at Starting Kernel... and no extra output with earlyprintk

Downloaded an old 3.10.102 image and got it to boot up. using vmlinuz-3.10.102-marvell (instead of mvebu) Maybe something to do with the change of kernel source: https://github.com/igorpecovnik/lib/commit/6810758736c18cc3be23778882df5d8109d6ec93 I might try reverting to that point and see if I can get a working system up.