bodhi, seems you are right that it doesnt work this way with sata disk only i added setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' because i used the original rootfs and not the patched version http://forum.doozan.com/read.php?2,34103,34599#msg-34599. Marvell>> setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' Marvell>> setenv bootdev scsi Marby saschadd - Debian
bodhi, prepared another harddrive to boot from it and tested. I boots to debian login prompt but i think the envs are not yet fully correct as i used the usb boot envs. Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd &by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > So if SATA is easy to get working for the EX4100, sachadd should do that test. so i prepare my sata drive for running the rootfs next?! anything i should take care of while doing this or just like i did for the pendrive?by saschadd - Debian
bodhi, here the output from testing ide and scsi Marvell>> ide reset Reset IDE: Marvell Serial ATA Adapter no device found Marvell>> scsi init AHCI init for unit0 SATA link 0 timeout. SATA link 1 timeout. AHCI init for unit1 Target spinup took 0 ms. SATA link 1 timeout. Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found scanning bus for devices... SCSIby saschadd - Debian
bodhi Wrote: > So, now if you put the rootfs on this SATA disk, it will boot into Debian and you'll get a running system. I'll need to write a new set of u-boot envs for you to do that. If this helps to get usb booting to work i would do that. I would prefer to boot from usb to set the harddrive to sleep when not needed. I noticed that on the nsa325v2 which i configured to boot fby saschadd - Debian
bodhi, does'nt the message modprobe: module i8042 not found in modules.dep point to what is missing to get usb working again? tried with one of the sata disks inserted Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenvby saschadd - Debian
okay, next run Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv load_initrd_addr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd 'echo loading uInitrd ...; ext2load $bootdev $device $load_initrd_addr /boot/uInitrd' Marvell>> setenv load_image 'echo loading Image ...by saschadd - Debian
bodhi, here the try with the last recommended envs on rear port Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv load_initr 0x2900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_initrd 'echo loading uInitrd ...; ext2load $bootdev $device $load_initrd_addr /boot/uInitrd' Marvell>>by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > @saschadd, > > Try this again (I would like to see you get past t > he point where the initramfs was unpacked. And the > n if there was anything that stopped the USB in th > e envs). The Ex4100 u-boot might have stopped the > USB, unlike the Ex2100 u-boot that appaently let U > SB be active thby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Please try: > > > setenv load_initrd_addr 0x2900000 > setenv load_image_addr 0x02000000 > > > And then use the rest of envs as same as before to > boot. Not sure if this was only meant for hmartin but tried that, following the output Marvell>> setenv bootdev usb Marvellby saschadd - Debian
Second try with origian uInitrd on back port 1 Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv load_initrd_addr 0xf00000 Marvell>> setenv load_image_addr 0xa00000 Marvell>> setenv load_initrd 'echo loading uInitrd ...; ext2load $bootdev $device $load_initrd_addr /boot/uInitrd' Marvell>> setenv load_imageby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > @all, > > Please try this. And post your serial console log. > > 1. Mount the USB rootfs on another Linux box or in > stock OS. Assuming it is mounted at /media/sdb1. > > > cd /media/sdb1/boot > cp -a zImage-4.9.0-mvebu-tld-12 zImage.fdt > cat dts/armada-385-wd-ex4100.dtb >by saschadd - Debian
bodhi Wrote: > @saschadd, use the back USB port? tried the back ports with replaced /boot/uInitrd with this file https://github.com/cschil/WD-385-initrd/raw/master/uInitrd-wd385 back port 1 output Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' Marvell>> setenv lby saschadd - Debian
saschadd Wrote: > > @saschadd, > > > > Did you try peacemaker's uInitrd ? > > Not yet, will try later today. bodhi, i replaced /boot/uInitrd with this file https://github.com/cschil/WD-385-initrd/raw/master/uInitrd-wd385 following the output Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv dtby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > @saschadd, > > Did you try peacemaker's uInitrd ? Not yet, will try later today.by saschadd - Debian
hmartin Wrote: ------------------------------------------------------- > Janky, but it works! See the photo if this all sounds too confusing. Hehe, got another ugly uart installment which works ; ) I just destroyed an old isdn socket to use the pins for clipping and soldered an old cd connection cable to that to put it on my raspi. ugly but works. ;) Meanwhile i put the cable througby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > When I have a couple hours free, I'll find the GPIO and we should be able to use USB drive. If i can help to research let me know. Just need to know where to look for. ; )by saschadd - Debian
bodhi, > Just for small chance that my thesis was wrong, please try a USB 3.0 stick to see if the behavior is different or not. > > And to add the regulator we need to find the GPIO for USB power in the WD GPL tarball. The keyword to search for is PWREN_USB_REG_OFFSET. Unfortunately with usb 3.0 stick it is not working at all. :( Marvell>> setenv bootdev usb Marvelby saschadd - Debian
has only 3 usb 3.0 ports :( no usb 2.0 ports there but i am using an usb 2.0 stickby saschadd - Debian
bodhi, not yet ;) Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv dtb_file '/boot/dts/armada-385-wd-ex4100.dtb' Marvell>> setenv load_dtb_addr 0x1000000 Marvell>> setenv load_initrd_addr 0x3900000 Marvell>> setenv load_image_addr 0x02000000 Marvell>> setenv load_dtb 'echo loading DTB $dtbby saschadd - Debian
hmartin, > Edit: question for saschadd, if you use the DTB I attached to the post above yours, do you get one SATA controller (f10a8000.sata) initialized and then the kernel panic about VFS? Tested your file, here is the output Marvell>> setenv bootdev usb Marvell>> setenv device '0:1' Marvell>> setenv dtb_file '/boot/dts/armada-385-db.dtb' Mby saschadd - Debian
bodhi, i tried just your last envs as hmartin testet the others. at first i thought "thats it" but then kernel panic again. but it looks a bit more successful to me. ; ) here the complete console output so that you can see which envs i set (see the red part, i dont know if thats normal but it is scanning usb twice.) Marvell>> setenv bootdev usb Marvell>> setenvby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > saschadd, > > Your boot log showed 88F6820 (unless its u-boot wa > s wrong). > > QuoteMarvell HW specs > ARMADA 380 (88F6810) – Single-core ARM CPU > ARMADA 385 (88F6820) – Dual-core ARM CPU > ARMADA 388 (88F6828) – Dual-core ARM CPU > The board seems to be 88F6820by saschadd - Debian
bodhi, welcome back. ;) > Here is the armada-385-wd-ex4100.dtb (attached in this post). thank you, already tried it. Just a little side note: the processor is an ARMADA 388 1.6 GHz dual-core processor. Maybe this is important or have you misstyped the name of the file?! Following the envs i used and the boot log setenv bootdev usb setenv device '0:1' setenv dtb_fby saschadd - Debian
I tried to find it so that it might be of help for bodhi Well then, i can stop searching.by saschadd - Debian
Hi Carl, thanks for that info. Do you remember where you found them? I downloaded the file WDMyCloud_EX4_GPL_v2.11.164_20170321.tar.gz from here http://support.wdc.com/downloads.aspx?p=213&lang=en and couldnt find them inside. In the standard envs there is a reference to fdtfile=armada-38x-modular.dtb which has to be somewhere. I was thinking about the nand but i dont know howby saschadd - Debian
bodhi, okay, so if you are on holiday have fun.by saschadd - Debian
bodhi, here the last envs test run bootcmd_usb (Re)start USB... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found Booting from USB ... (Re)start USB... USB0: Port (usbby saschadd - Debian
peacemaker, do you remember where you got the vendors dts and dtsi files? We are trying to get debian running on EX4100 here http://forum.doozan.com/read.php?2,34103 and at the moment i am trying to find the armada-38x-modular.dtb file on stock rom Peacemaker Wrote: ------------------------------------------------------- > maybe someone here has an idea? > I attached the vendorby saschadd - Debian
bodhi, > It's not possible to boot USB 3.0. We can only use > USB 2.0 for booting. Thanks for the info. I was thinking its the stick. ;) > For now, the next 2 things to try. > > 1. Logging into stock OS and copy the DTB file tha > t the stock kernel uses for booting to the Debian > rootfs /boot/dts/. > > > fdtfile=armada-38x-modular.dtb >by saschadd - Debian