umiddelb

What UART parameters have you set, especially flow control?

There is an implicit timeout built into uboot which triggers this error messages. I suppose that the newer firmware will circumvent this timeout.

X-Ref:

The ArchLinuxARM-utilite-latest.tar.gz image comes with a 3.0.x kernel, with must be u-booted with bootm instead of bootz.

[alarm@alarm ~]$ sudo networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether degraded configuring 3 eth1 ether routable configured 3 links listed. eth0 (fec) stays at level degraded, when it is getting connected.

and you are right, dhcpcd is not needed at all.

Honestly, I have no idea. I haven't used the fec interface for a while. Now I realized the fec interface doesn't work at all, only the igb interface is usable (neither armbian nor arch).

systemctl enable dhcpcd systemctl start dhcpcd

I've played a little bit with ArchLinuxARM-utilite-latest.tar.gz with following observations: the stock kernel is very old (3.0.X) and uses the traditional bootm scheme (combined kernel+dtb) the linux-armv7 packages provides an up to date kernel (6.2.10), but needs some love in order to comply with the Armbian boot script there was no configuration for eth1 like /etc/systemd/network/eth0.network dhcpcd was disabled, needs to be enabled flash memory access has returned doesn't seem to crash, unlike 6.1.63

igb -> end1 fec -> end0 what is the output of ip a ?

What is the output of dmesg ?

/boot/armbianEnv.txt != /etc/fstab If /etc/fstab was empty, something went wrong. You max extract the contents of Armbian_23.8.1_Cubox-i_bookworm_current_6.1.50.img.xz once again.

The original /etc/fstab from Armbian_23.8.1_Cubox-i_bookworm_current_6.1.50.img.xz looks like this: UUID=8e42c01d-846b-4090-b69e-1b45502b6cc4 / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 As mentioned before, you will need to adjust the UUID unless you have passed it to mkfs.ext4.

Have you checked the UUID for '/' in /etc/fstab ?

Very good! Usually the bootscript doesn't need to be modified if the u-boot environment looks more or less like the one I've posted above (only the MAC addresses should differ) . The 6.1.50 kernel runs smoothly, just extract the 6.1.50-current-imx6.tgz in /

This looks like the original boot environment, bootz won't work there. Do you think you would be able to adopt my boot environment? You may prepare it in the same format like /boot/armbianEnv.txt and load it according to /boot/boot.cmd. Before making these changes permanent (# saveenv) you can try them in advance (# run bootcmd).

If you post the your u-boot environment here I can have a look on it. Some u-boot variables may interfere with bootz. The Utilite default console is ttymxc3, not ttymxc0. If the kernel command line refers to ttymxc0 you won't see any output. Btw. the latest kernel (6.1.63-current-imx6) doesn't seem to be a good choice, the kernel crashes after a while.

The script is the standard boot.cmd (https://github.com/armbian/build/pull/3527) # DO NOT EDIT THIS FILE # # Please edit /boot/armbianEnv.txt to set supported parameters # # default values setenv rootdev "/dev/mmcblk0p1" setenv verbosity "1" setenv console "display" setenv bootlogo "false" setenv disp_mode "1920x1080m60" setenv earlycon "off" if test -z "${bootfstype}"; then setenv rootfstype "ext4"; else setenv rootfstype "${bootfstype}"; fi if test "${board}" = mx6cuboxi; then setenv ramdisk_addr_r "0x14800000" if test -z "${fdtfile}"; then setenv fdtfile "imx6q-cubox-i.dtb"; fi if test -z "${cons}"; then setenv cons "ttymxc0,115200"; fi fi if load ${devtype} ${devnum}:${distro_bootpart} ${loadaddr} ${prefix}armbianEnv.txt ; then env import -t ${loadaddr} ${filesize} fi if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=tty1"; fi if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "${consoleargs} console=${cons}"; fi if test "${earlycon}" = "on"; then setenv consoleargs "earlycon ${consoleargs}"; fi if test "${bootlogo}" = "true"; then setenv consoleargs "splash plymouth.ignore-serial-consoles ${consoleargs}" else setenv consoleargs "splash=verbose ${consoleargs}" fi setenv bootargs "root=${rootdev} rootfstype=${rootfstype} rootwait ${consoleargs} consoleblank=0 video=mxcfb0:dev=hdmi,${disp_mode},if=RGB24,bpp=32 coherent_pool=2M cma=256M@2G rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi vt.global_cursor_default=0 loglevel=${verbosity} usb-storage.quirks=${usbstoragequirks} ${extraargs}" load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}dtb/${fdtfile} load ${devtype} ${devnum}:${distro_bootpart} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} ${prefix}zImage bootz ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr You may pay attention to the predefined u-boot variables containing memory adresses and limits.

Hm, I'm using the same firmware but I don't get this error during boot. The default u-boot env doesn't incorporate with Armbian. You need to adjust certain parameters and macros. CM-FX6 # printenv _1=setenv devplist 1;setenv boot_targets sata0; boot _2=setenv devplist 2;setenv boot_targets sata0; boot _3=setenv devplist 3;setenv boot_targets sata0; boot autoload=no baudrate=115200 board=utilite-pro boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_prefixes=/ /boot/ boot_scripts=boot.scr.uimg boot.scr boot_targets=mmc0 usb0 sata0 bootcmd=run findfdt; run distro_bootcmd bootcmd_mmc0=setenv devnum 0; run mmc_boot bootcmd_sata0=setenv devnum 0; run sata_boot bootcmd_usb0=setenv devnum 0; run usb_boot bootdelay=5 bootenv=uEnv.txt bootfstype=ext4 bootscr=boot.scr cons=ttymxc3,115200 console=ttymxc3 cpu=6Q devnum=0 devplist=1 2 3 devtype=sata distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done eth1addr=00:01:c0:13:fb:ef ethact=FEC ethaddr=00:01:c0:13:ed:ea ethprime=FEC fdt_addr_r=0x15000000 fdt_high=0xffffffff fdtfile=undefined filesize=5de findfdt=setenv fdtfile imx6q-utilite-pro.dtb initrd_high=0xffffffff ip_dyn=yes kernel_addr_r=0x10800000 loadaddr=0x10800000 mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi preboot=sata init ramdisk=uInitrd ramdisk_addr_r=0x18000000 sata_boot=if sata dev ${devnum}; then setenv devtype sata; run scan_dev_for_boot_part; fi scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_scripts; done; scan_dev_for_boot_part=for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done scriptaddr=0x10800000 serial=CM-FX6-C1200QM-D2G-N0-ND0-U5-E-A-WB-V100-131028-0001c013edea splashpos=m,m stderr=serial,vga stdin=serial,usbkbd stdout=serial,vga usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi video_dvi=mxcfb0:dev=dvi,1280x800M-24@50,if=RGB24 video_hdmi=mxcfb0:dev=hdmi,1920x1080M-24@50,if=RGB24

very cool!

Mor Winkler <mor.winkler@compulab.co.il>

Hm, the documentations refers to the carrier board, which imho is different to the board used in the Utilite Pro. You may try to get in touch with people from Compulab directly (nice people, very helpful).

Several devices (e.g. BT & Wifi) are using MMC(SDIO)-interfaces as well (p.10, last row & p.42) , I suppose MMC-3 will be wired to the µSD card receptacle, at least on the CoM, hopefully on the Utilite as well.

The standard Armbian kernel has no support for flash memory access, because the Cubox-i has no flash-memory. So you need to build your own kernel with flash memory support. If you are familiar with flash memory access in u-boot, this might be an alternative.

The good thing is: You don't need to modify the contents of the image in order to make it run on an Utilite Pro (This image is supposed to support more or less all imx6 based devices). The nasty thing is: You need to modify the Utilite u-boot environment to make it compatible with the "distroboot-method" and you need to circumvent the limitations of the firmware. The Utilite u-boot cannot read from ext4 filesystems with 64 bit extensions enabled. Download the cubox-image and write it to an usb storage (a) Prepare another usb key (b) with an ext4 filesystem: sudo mkfs.ext4 -O ^64bit /dev/sdxX Mount both and copy the contents from (a) to (b) Adjust the rootfs UUID in /boot/armbianEnv.txt and /etc/fstab Plug-in usb key (b) to your Utilite and check if it boots up.