Yap, i have written them again. But the chinese new year is still running until tomorrow. Thecus also answered my first mail within one day last time. Maybe they don't get email replies? Also Thecus somewhat tries to supply GPL sources for all their boxes. But they seemed to have mixed them up for the Armada boxes. Right OS Image version, but wrong architecture. I will write, if i hearby lordzahl - Debian
rayknight Wrote: ------------------------------------------------------- > GPL source for this unit should be available at > http://www.thecus.com > > Ray Hi, thanks for the link. While this >should< be the GPL source, it is not. As the filename states, it is a x86_64 source, does not include the used arm dts. Also it is a 4.x kernel source - not a 3.10.x as used in tby lordzahl - Debian
Hi bodhi, Thanks for explaining. So There is USB power, in uboot, so there kernel image can be loaded, but it is gone in kernel again? If this happens with the stock kernel and stock dtb, then there might be a program after booting, which enables it? Boot to stock with USB driver in the "next to RJ45 port": BootROM - 1.73 Booting from SPI flash General initialization - Veby lordzahl - Debian
Hello bodhi, > I think you need to ask Thecus to provide GPL > source for u-boot and kernel Yes, i already did that, but i will try again on the public forum. > Looking the boot log in this post above. None of > the USB were initialized. Like there are no > power. > https://forum.doozan.com/read.php?2,50829,51059#msg-51059 Where do you read that USB were not initialiby lordzahl - Debian
So uboot does not recognize the internal (USB2?) port, neither the other USB3 port in the back. The USB drive is only available on typing "usb start" in the one next to the RJ45 port. I have also tried another USB stick in either ports, but the result is the same. For the mw commands: I don't know what the first one mw 0xf1018104 0xfecf3fff does, but the second one blinks two oby lordzahl - Debian
The box has two normally reachable USB 3.0 ports on the back. I used the one next to the LAN port, since this one was recommended by the rescue_fw manual. But it has a third port, which is normally not reachable from outside, which is probably USB 2.0. I will not be home until sunday. I will test it then.by lordzahl - Debian
Yes: [****@**** ~]$ sudo e2label /dev/sdb1 rootfs [****@**** ~]$ sudo e2label /dev/sdb sdb sdb1 [****@**** ~]$by lordzahl - Debian
I tried again booting the stock kernel with your modified boot command. I got another error - it could not find the rootfs. See the log at the end of this message. I tried to find the stock kernel config, but had no luck. Nothing in /proc/config* /boot. Neither could i extract it with extract-ikconfig. The gpl sources are still useless, since they are for a completely different NAS. While seaby lordzahl - Debian
Hello bodhi, Yes it fails with the same error. Using these uboot cmds (I introduced dtbfilename for convenience): setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x2900000 setenv load_image_addr 0x02000000 setenv dtbfilename 04_dtbdump_Marvell_Armada_385_Development_Board.dtb setenv usb_set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10by lordzahl - Debian
Hi, I have tried several different dtbs now: armada-385-db-ap.dtb armada-385-synology-ds116.dtb armada-385-wd-ex2100.dtb 04_dtbdump_Marvell_Armada_385_Development_Board.dtb I could extract the last one from the rescue_fw bzImage with extract-dtb. The ubifs.img in rescue_fw (dumped with ubidump) has also a bzImage with the same dtb. I extracted the dts from this dtb with "dtc"by lordzahl - Debian
I did nanddump: N2350:~# nanddump --noecc --omitoob -f mtd0_N2350 /dev/mtd0 Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x20000000... N2350:~# and copied it with scp on my laptop. Using kwboot from here i tried ./kwboot-x86_64 -t -B 115200 /dev/ttyACM0 -b mtd0_N2350 -p mtd0_N2350: Invalid image. but it did not work. The resuby lordzahl - Debian
Hi bodhi, Thanks for helping! Btw. ext2ls on the usb stick with your image is working. I guess from here on i could input something like ex2100 install to uboot, but replace the initrd address with 0x3000000? But i am not sure, so i will wait for your answer. The printenv output is: Marvell>> printenv CASset=max MALLOC_len=5 MPmode=SMP autoload=no baudrate=115200 boot_orderby lordzahl - Debian
One other observation for the future: The GPL sources provided for the NAS by Thecus only includes one dts file, which matches the "model" string shown by my kernel boot up dump "Marvell Armada 385 Development Board". I will attach it here for future reference. Note that the mainline 3.16 kernel has a dts with the exact same model string: https://git.kernel.org/pub/scm/liby lordzahl - Debian
Hello, I have bought a Thecus N2350 NAS. It is a Marvell Armada 385 based NAS with 2xSATA and 1GB Ram. I would like to run Debian on it and was very happy that you guys run Debian on very similar devices: "Linux Kernel 4.14.1 MVEBU package and Debian armhf rootfs" Since i am new to hack embedded devices, i need some help. I have opened the box to look for UART, but none was markby lordzahl - Debian