Thanks for the hints. I installed i2c-tools and libgpiod to poke around from user space. I built my own linux kernel based on your config-6.1.66 (including a few extras like CONFIG_USB_UAS and CONFIG_DEVTMPFS_MOUNT). Now I can to insert some more trace printk to investigate. I moved rootfs into my internal scsi drive. The thumb drive gets hot, and the usb-storage task gobbles huge amountsby wibu - uBoot
I agree about u-boot and kwboot with this board, I'm doing some experiments to confirm. kwboot -d worked, but not yet kwboot -b. There are a few spots for headers on the board, and one is quite likely to be a JTAG, so that's one possible avenue. But you've certainly accomplished the initial stated objective, which is to boot modern kernel and rootfs. I found I needed toby wibu - uBoot
I was poking around in the lenovoemc fosskit 4.1.414.34909 which has source and patches for linux 3.2.1.101. I did a grep for the PHY_ADDR and found this: 22 MV643XX_ETH_PHY_ADDR(8) 13 MV643XX_ETH_PHY_ADDR(0) 4 MV643XX_ETH_PHY_ADDR(1) 3 MV643XX_ETH_PHY_ADDR(11) 2 MV643XX_ETH_PHY_ADDR(9) 1 MV643XX_ETH_PHY_ADDR(10) 1 MV643XX_ETH_PHY_ADDR(24) Latest linux kernel for my board fromby wibu - uBoot
It looks like most kirkwood boards used 8 or 11, but it turns out the iomega m1 uses ethernet_phy 1. So now I can ssh to the m1 and continue the discovery and refinement of device tree: rtc mtd buttons leds fan I was able to skip the boot shim.by wibu - uBoot
Honestly this is the first thing I'd like to fix on this board: U-Boot 1.1.1 (Jun 3 2007 - 20:44:19) USI u-boot-1.1.1-DHNSMR03/04-v3.1.0.0 It doesn't have mii, mdio, or even "source"! By the way, here's my flash info. My boot command for 2.6.12 isn't passing any mtd partition information. Support for that chip should be coming with MTD_CFI_AMDSTD. I wishby wibu - uBoot
I didn't forget about this at all. Eventually I got both 5.10.197 and 6.1.66 kernels to boot, and use a bookworm disk image built according to your instructions. My current boot commands are setenv bootargs console=ttyS0,115200 rootdelay=30 root=PARTLABEL=ROOT setenv kaddr 2000000 ; setenv iaddr 2400000 ; tftpboot $(kaddr) bookworm/uImage.buffalo.lsgl ; tftpboot $(iaddr) orion/busyrdby wibu - uBoot
Thanks, I've been continuing to investigate why sometimes the boot succeeds and sometimes not. Having gone through the shim code, I agree with you that it should be reasonable to exclude it. It looks like I'll have to experiment with u-boot under qemu, to understand more of the process. I'll rerun with these parameters at least, to generate a clean image.by wibu - uBoot
I had to add a few more packages than were mentioned in the instructions, but I eventually worked it out and got this far with bullseye. $ sudo ./generate_disk_image.sh image file created partitioning done block devs created /boot/ formatted swap created rootfs formatted format done W: Cannot check Release signature; keyring file not available /usr/share/keyrings/debian-archive-by wibu - uBoot
It's been a long day with some interesting discoveries and remaining puzzles, but some progress. (high 5 emoji) Given 4200's optimistic 90% assessment, I'll call it 92%. (wink emoji) Most disconcerting is that sometimes the boot does not consistently proceed after the initial "Starting kernel ..." message. Without some debugger it's not possible to tell if therby wibu - uBoot
Thanks, 4200. I tried several different configurations memory loading with bodhi's kernel and none achieved anything interesting. I tried your kernel and got the below. My old u-boot doesn't know how to pass command line to newer kernels (all the ones I tried are 2.6 era). I tried your 5.10.197 and it got much farther in boot, but couldn't attach to a root fs. Can you giveby wibu - uBoot
Hi bodhi, Unfortunately neither of those load addresses has made a difference in the progress of the linux kernel. Happy weekends! __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| _by wibu - uBoot
Wonderful, so many 8's and 0's to differentiate! And of course the dtb comes after the kernel, not before. (wink) Anyway, finally got everything to make its way to the target. It looks like it's crashing and burning quietly (thus added earlyprintk) around early_mm_init: ** MARVELL BOARD: DHNSMR03 LE U-Boot 1.1.1 (Jun 3 2007 - 20:44:19) USI u-boot-1.1.1-DHNSMR03/04-by wibu - uBoot
I tried your rootfs Debian-6.5.7, but all binaries give a segfault. I had earlier tried a cross-compile of a simple write(1, "Simple\n", 7) hello world program, and found this behavior seems to be traced to incompatible EABI5. The busybox (v1.00 !) that's in my mtd is EABI4. I didn't find a toolchain yet that will work for that. I did find an update package StorCenterby wibu - uBoot
Thanks, bodhi. I will really appreciate the assist getting this working. Unfortunately this old u-boot doesn't have any usb support. But, I agree with you that chain booting should be enough, at least for now. I found a SATA 1TB drive from an xbox, and uboot's "ide reset" was able to see the device. With use of MBR and ext3 with internal journal, ext2ls and ext2load alby wibu - uBoot
Thanks for the tip, rayknight. I found this good reference https://docs.kernel.org/arch/arm/marvell.html with some pointers to more details about those devices. u-boot mainline support is there also for MV88F5182_REV_A2.by wibu - uBoot
I have an original 1TB (2x500GB) iomega storcenter that I want to get up and going with debian. I was able to get uart console functioning to my nearby linux box, and I can see that it is running a very old u-boot, which does not support usb devices. Marvell Development Board (LSP Version 1.10.3_DB_NAS)-- DB-88F5182-DHNSMR03 Soc: 88F5182 A2 U-Boot 1.1.1 (Jun 3 2007 - 20:44:19) USI u-boby wibu - uBoot