@MisterD, To get the right serial module converter, look in the Wiki thread: https://forum.doozan.com/read.php?2,23630 QuoteSerial Console & JTAG console Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD Serial Port connector - what are people using to make it work Serial Console hookup - GoFlex Net (external link) Serial Console hookup - Pogoplug E02 and Pogoplug Pro V3 (by bodhi - uBoot
Quoteflash@d0000 { status = "okay"; num-cs = <1>; marvell,nand-keep-config; marvell,nand-enable-arbiter; nand-on-flash-bbt; nand-ecc-strength = <4>; nand-ecc-step-size = <512>; mtd1@00000000 { label = "U-Boot-img"; reg = <0x00000000 0x00100000>; };by bodhi - Debian
Here is version 9 DTS for testing. We need to adjust the boot envs to not using NAND. This will rearrange the mtds, but it is OK for now. setenv mtdparts 'mtdparts=spi0.0:0x00100000(uboot),0x00010000@0x00100000(uboot_env)' setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x2900000 setenv load_image_addr 0x02000000 setenv dtbfilename armada-385-thecus-n2350.dtb setenvby bodhi - Debian
Hi Manuel, You are correct that my kernel config took care of that issue. It is a SMP PREEMPT kernel. I would not settle for a non-PREEMPT kernel if I can manage to do that :) The NAS326 and other MVEBU boxes such as My Cloud EX2100/4100 use the same NAND driver without this timeout problem. However, NAS326 uses Macronix NAND, while the Thecus uses Hynix NAND. So perhaps one size can'by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > I saw this > USB > 4 Port Print Server Access Points Network > Fax and started to think perhaps we can do > this using a rather inexpensive Seagate Dockstar > and/or a Pogoplug Mobile. Anyone? If you have a USB printer. And either a Dockstar or the Pogo Mobile already running in your network, thenby bodhi - Off-Topic
You can download the tarball from the released thread https://forum.doozan.com/read.php?2,12096 And look at the diff patch in there. Also the config file (diff the mainline config file with it). There are too many additional modules that l configured in, listing the diferences in plain text is not easy! Most notable would be Sound and Network.by bodhi - Debian
> I went ahead and created the new > boot usb , I was able to log back into debian Cool!by bodhi - uBoot
leitmotiv, > Dunno, this dock works fine on my > Windows PC on both USB 2.0 and 3.0, does not get > detected as anything weird, despite being a > cloning dock. This situation is normal. U-boot don't use the same driver as Windows, or even Linux laptop/dekstop. > If the ASMedia bridge cannot be trusted to work > reliably with the Dockstar, then I am in a bind.by bodhi - Debian
As I mentioned, wrong NAND defintion was not supposed to stop the kernel from booting. So I think stock GPL has the wrong cs. [ 0.958494] pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device [ 0.966103] pxa3xx-nand f10d0000.flash: invalid number of chip selects [ 0.974099] libphy: Fixed MDIO Bus: probed [ 0.978671] libphy: orion_mdio_bus: probed [ 0.9by bodhi - Debian
> I wrote the Debian-4.12.1 tarball on the USB key > again...I remembered that I have changed the > uImage file yesterday in the evening... > Now the box is up and running again. > > Thank you, bodhi for your help. > > greets > -andy- Cool! you're welcome.by bodhi - uBoot
Let's get our status in one post. Please boot with version 7 and your ethernet cleanup version. Interrupt serial console and enter the envs, boot into Debian. uname -a mount cat /proc/cpuinfo ethtool eth0 And post the entire serial console log here.by bodhi - Debian
> No, that was v7 already. I just was the only time > you did not post bootcmds (which are of course > still the same). I just referenced them for other > people/future. > > > So far I'm happy with the kernel running shown > in > > your log: > > > https://forum.doozan.com/read.php?2,50829,55564#msg-55564 > Yeah me too! > > And i hby bodhi - Debian
Quote> Regarding the network problem. > The boot log shows > > [ 0.978941] mvneta f1070000.ethernet eth0: > Using random mac address 2e:cc:86:ec:08:72 > [ 0.989512] mvneta f1030000.ethernet eth1: > Using random mac address a6:00:c8:41:5f:0b > > but the box has only one ethernet port. > > Indeed your dts shows: > > ethernet@30000 { >by bodhi - Debian
Excellent! QuoteUsing (from dts v6, but without the space mentioned a few posts before) Did you mean V7 tarball I've uploaded above? if not, please try V7 and post serial console log here. https://forum.doozan.com/read.php?2,50829,55534#msg-55534 So far I'm happy with the kernel running shown in your log: https://forum.doozan.com/read.php?2,50829,55564#msg-55564by bodhi - Debian
BTW, you should get a listing of CDC related modules runing on your Pi Zero and post here. That will help. lsmodby bodhi - Debian
Sure, it will be in the new stable kernel 4.4.124.by bodhi - Debian
OK here is the DTB V7 for testing. I've corrected some SATA definition. Hopefully, if the kernel hang was because of SATA initialization then this should help us got pass that hurdle.by bodhi - Debian
Manuel, Don't worry about it! I found some new info in various Armada DTS that I've overlooked before. Still look for possible improvement! Will be back to this thread with new DTS.by bodhi - Debian
lordzahl Wrote: ------------------------------------------------------- > Hi bodhi, > > > Please try again without the extra space! > > Here we go: There seems to be a problem with your post. Nothing showed up inside the code tags.by bodhi - Debian
The USB bridge itself. The Dockstar might not like this USB 3.0 bridge. QuoteU-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700) Seagate FreeAgent DockStar gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop autoboot: 0 starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage deby bodhi - Debian
Manuel, Just now, I've noticed a typo in the v6 run posted in this post: https://forum.doozan.com/read.php?2,50829,55134#msg-55134 Marvell>> setenv mtdparts 'mtdparts= armada-nand:-(ubifs);spi0.0:0x00100000(uboot),0x00010000@0x00100000(uboot_env)' [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts= armada-nand:-(uby bodhi - Debian
andy, The fix is quite simple, you don't need kwboot at all. Your u-boot was flashed successful and you can boot without problem. Since you missed flashing the default envs, current it has problem booting into Debian. You can set it to the right defaults at the u-boot prompt using the default script Iv've created. Let me find the link and come back to edit this post. -------by bodhi - uBoot
echowarrior108, Your envs are messed up. The DTB was not loaded. If you study the boot log you had before with a successful run, and compare with this one. You will see that loading was missing. Power up, interrupt serial console and list the envs: printenv Please post it here if you can't see which env was in error.by bodhi - uBoot
Check your image checksum md5sum u-boot-spl-clearfog-tld-1.kwb d9a8d444342fbf3fc1fcd74206460650 u-boot-spl-clearfog-tld-1.kwbby bodhi - Debian
MisterD, > I have two stora boxes here and one of them is > bricked at the moment. I'm investigating this > awesome forum to see what can be done to fix it. Your best approach is to connect serial console first. Some Stora boxes (not all) also has UART booting capability, iirc, so it can be unbricked even if NANDs are bad.by bodhi - uBoot
echowarrior108, You are trying installing kernel offline on your Ubuntu while the USB is mounted on it (you can not do that). Note: you could do that with chroot, but it is more advance subject, don't try that yet. Boot into to the Pogo, and then run dpkg at the Linux shell terminal to install new kernel. root@debian:~#by bodhi - uBoot
bodhi Wrote: ------------------------------------------------------- > ShapeShifter499 Wrote: > ------------------------------------------------------- > > Hi bodhi, > > > > Can you please compile support for the > "cdc_ether" > > and "cdc_acm" modules in the kernel? I need > it > > so I can make use of ethernet over usbby bodhi - Debian
It is OK. You are running kernel 4.4.54-oxnas-tld-1. -rw-r--r-- 1 root root 111194 Mar 19 2017 config-4.4.54-oxnas-tld-1 -rwxr-xr-x 1 root root 4621760 Mar 19 2017 zImage-4.4.54-oxnas-tld-1 -rw------- 1 root root 4621760 Mar 19 2017 vmlinuz-4.4.54-oxnas-tld-1 -rw------- 1 root root 1712926 Mar 19 2017 System.map-4.4.54-oxnas-tld-1 -rw-r--r-- 1 root root 7378702 Mar 19 2017 lby bodhi - uBoot
The envs are OK. But the uInitrd kernel file was bad. loading uInitrd ... 0 bytes read in 193 ms (0 Bytes/s) loading DTB /boot/dts/ox820-pogoplug-pro.dtb ... 7067 bytes read in 258 ms (26.4 KiB/s) ## Booting kernel from Legacy Image at 60500000 ... Image Name: Linux-4.4.54-oxnas-tld-1 Created: 2017-08-01 4:45:36 UTC Image Type: ARM Linux Kernel Image (uncompressed)by bodhi - uBoot
Let's try kwboot with u-boot SPL for Clearfog. This image should be run with -p option. kwboot-x86_64 -f -t -B 115200 /dev/ttyUSB0 -b u-boot-spl-clearfog-tld-1.kwb -q 0 -s 1 -pby bodhi - Debian