Hi bodhi, at the moment I don't care about the network booting 'recovery' option as implemented by the stock uboot. Quotebodhi But, since you are apprently want to use them as headless production servers now :), I will show you how to change the envs to make it resilient, and fall through the execution paths correctly from the 1st to the last device. yes I've becomby Koen - Debian
I've tried to setup a boot sequence where the device first tries to boot from SD, then USB and eventually the internal memory. I've used the following settings: setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x3000000 /boot/uImage; ext2load usb 0by Koen - Debian
Hi bodhi, thanks for the advice. The thinpro setup uses root=/dev/sda1 so that 's why I set it up like that. However I've now changed the label and used the same configuration as booting from USB stick to keep things consistent. I did already change the hostname of the rescue system such that it is easy to see in my router settings which system is running. This should now be quite aby Koen - Debian
Thanks for your help bodhi. I've copied the 'hybrid' USB system to the internal memory. Next I've set the following additional uboot environment variables. set_recovargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 ${mtdparts} splash quiet earlyprintk=serial bootcmd_recov=ide reset; ext2load ide 0:1 0x2000000 /boot/uImage; ext2load ide 0:1 0x3000000by Koen - Debian
Hi bodhi, I didn't realise this was possible but after reading https://wiki.debian.org/Multiarch/HOWTO it is a bit clearer. I guess it is similar to running 32 bit packages on a 64 bit system. At the moment I've got a working USB minimal 'hybrid' armel / armhf Debian jessie system based on 4.4.0 kirkwood rootfs with 4.18.5 mvebu kernel. Removing the old kernel and cleaniby Koen - Debian
Executing this command adds armhf and makes it possible to install the new kernel. dpkg --add-architecture armhf Koenby Koen - Debian
Hi bodhi, I've tried the following steps but run into an issue. I've created the 4.4.0 rootfs and used it to boot my iomega iconnect. Then I've run 'apt-update' and 'apt-upgrade' to update the jessie system. I've re-booted the iomega iconnect and run 'apt-get clean' to remove the cache files. The size of the system is then ~390MB so should fitby Koen - Debian
Hi bodhi, stock uboot loads an image from the 2nd partition to display on screen during boot. I can't find it anywhere in the uboot environment variables so I assume that this behavior is hard coded. This happens before you get to the uboot prompt so I am afraid that removing the 2nd partition may result in a brick. The 1st partition can't be mounted in Debian so I'm not sure whby Koen - Debian
OK the steps above have worked. I've created backups of the original partitions to an external drive and removed most of the files. Then I've resized the filesystem and partition mmcblk1p2. I've removed the old mmcblk1p3 partition and re-created it with the rootfs label. Then I used the following commands in serial to boot from the internal memory: setenv set_bootargs 'seby Koen - Debian
I've tried this latest dtb but can't get the SD card to show up so I've reverted back to the .dtb from 26 September. I've cloned the USB stick to a SD card and plugged it into the device. I then change uboot environment from serial using the following commands: setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlypby Koen - Debian
Ok that one is for kirkwood architecture but I guess I can try this one: Debian-4.9.0-mvebu-tld-9-rootfs-bodhi.tar.bz2 which may just fit. Koenby Koen - Debian
I've backed up the stock system on the internal memory and wiped it with the plan to install a minimal Debian image as a rescue system. The USB stick would be the primary boot option with the minimal Debian on the internal memory as a rescue / recovery system. However I've realized that the 4.12 rootfs is too big to fit on the internal memory. Is there a way to trim this down or is thisby Koen - Debian
Hi bodhi, I've had another look through the Dell Wyse Ubuntu files and found some more stuff related to SD card in the file 'dove-rd-avng-setup.c'. There is a section called 'Board Init' which includes some SD card setup calls: /***************************************************************************** * Board Init **************************************by Koen - Debian
This latest .dtb file doesn't fix mmc0 but makes mmc1 disappear as well :-) Koen MIC>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' MIC>> setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x3000000 /boot/uImage; ext2load usb 0:1 0x4000000 /boot/uInitrd' MIC>> setenv booby Koen - Debian
That is the soldered on 2 GB internal memory chip. This has been working OK since the start. The SD card should show up as mmcblk0 like it does when I boot the device with the card in place. Koenby Koen - Debian
Here the boot log from serial console. When I plug in the card there is no new output to console. MIC>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' MIC>> setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x3000000 /boot/uImage; ext2load usb 0:1 0x4000000 /boot/uInitrd' MIC>> sby Koen - Debian
Temporarily changed the boot command to include the same 'poke' as the stock system. bootcmd_usb=usb start; mw 0xf10a239c 0x4025; ext2load usb 0:1 0x2000000 /boot/uImage; ext2load usb 0:1 0x3000000 /boot/uInitrd However I don't see any change in the boot log or dmesg so I'm not sure what this does. Koenby Koen - Debian
bootlog: MIC>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' MIC>> setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x3000000 /boot/uImage; ext2load usb 0:1 0x4000000 /boot/uInitrd' MIC>> setenv bootcmd_exec 'run set_bootargs; run bootcmd_usb; bootm 0x3000000 0x4000000'by Koen - Debian
Hi bodhi, I've appended the new dtb and booted the device but when I insert a microSD card it is not recognised. After that I've used the following instructions to add gpio 12. https://elinux.org/GPIO Seting it to either high or low does not make the microSD card show up. The debugfs output does show that the value of gpio 12 is being changed. A bit more poking around in dby Koen - Debian
I've been reading a lot of old posts on the forum of different boxes and there was one where it took a lot of time to get the 2nd hard drive to work. This required a 'poke' in the memory before booting to power up the 2nd hard drive. In the original uboot environment variables of this device there is a similar 'poke': mw 0xf10a239c 0x4025 Would this help to power uby Koen - Debian
Hi bodhi, Should I plug in a micro SD card and start activating gpio pins from Debian and see when it shows up in dmesg? Or is there the risk of breaking things? I decided to do a quick sysbench of this dove board and also on my pogo E02 to see how they compare. It is 2.5x faster in the sysbench test as shown by the results below. Koen pogo E02: koen@debian:~$ sudo sysbench --by Koen - Debian
Below is the serial log of powering down the device: root@debian:~# poweroff Broadcast message from root@debian (ttyS0) (Fri Sep 28 12:44:44 2018): The system is going down for system halt NOW! INIT: level: 0 INIT: Sen Using makefile-style concurrent boot in runlevel 0. [ ok ] Shutting down ALSA...done (none loaded). [....] Stopping busybox' klogd implementation: klogd2523 (klby Koen - Debian
I'll get the serial log later today. There is a little pin hole with reset button on the device so it could be that the current gpio is triggering the reset instead of power down. Koenby Koen - Debian
Ok I may have spoken too soon. Power off works better than before as it interrupts the power button led and seems to stop the device however a second later the led comes on again and the boot sequence starts. Koenby Koen - Debian
The first time I booted the device with the new .dtb the microSD card was still in the slot and is recognised by the system during boot. [ 3.315946] sdhci: Copyright(c) Pierre Ossman [ 3.345031] sdhci-pltfm: SDHCI platform and OF driver helper [ 3.419395] mmc0: SDHCI controller on f1090000.sdio-host using DMA [ 3.508580] mmc1: SDHCI controller on f1092000.sdio-host using DMAby Koen - Debian
Hi bodhi, thanks for the new .dtb file. Power off works which is great. The spi stuff works but shows it is expecting a different chip. I uses the following in my .dtb file copied from another device which uses the same chip and that doesn't show this message in dmesg: spi-flash@0 { compatible = "mxicy,mx25l1606e"; spi-max-by Koen - Debian
Hi habibie, I'm not sure if this is the same for any board but a default / generic .dtb file is available for the dove board in the mainline kernel files. This file is used as a starting point and is modified based on the different chips on the board. I just look at the .dtb files from different arm devices with similar chips / hardware and copy paste sections and see if things start workby Koen - Debian
When I put a microSD card in the slot and run mmcinfo it shows up in uboot. (mmcinfo 0 = 2 GB internal memory, mmcinfo 1 = 16 GB microSD card) MIC>> mmcinfo 0 Device: MV_SDHCI Manufacturer ID: 45 OEM: 100 Name: SEM02 Tran Speed: 25000000 Rd Block Len: 512 MMC version 4.0 High Capacity: No Capacity: 1958739968 Bus Width: 4-bit MIC>> MIC>> mmcinfo 1 Device: Mby Koen - Debian
I don't own one and it is a bit confusing since they made quite a few different versions. However the wiki page seems to indicate that it has SPDIF. https://en.wikipedia.org/wiki/CuBoxby Koen - Debian
I've looked through the Dell Wyse Ubuntu files and came across this dove-rd-avng-setup.c file. It may well be related to this LXD8941 thin client since it shows 'Machine: Marvell MV88F6781-RD Avengers MID Board' in the stock dmesg log. A quick google shows a slightly different file with similar name here: https://github.com/rabeeh/linux-2.6.32.9/blob/master/arch/arm/mach-dove/dby Koen - Debian