bobafetthotmail, Thanks for the info! > binary uboots and kwboot sources for kwbooting a n > on-descript marvell Armada 38x board https://githu > b.com/nitroshift/armada-38x-bootloader-recovery-fi > les > > The patch that added kwboot support for armada 38X > in uboot sources https://patchwork.ozlabs.org/patc > h/510488/ I've seen these files. But havby bodhi - Debian
J. Carlos Wrote: ------------------------------------------------------- > Perhaps CLK is TCK and RES is n_TRST? Please post these questions in Joerg's thread: http://forum.doozan.com/read.php?3,21789. Joerg probably had this thread notification and will hopefully come around and answer them.by bodhi - uBoot
J. Carlos Wrote: ------------------------------------------------------- > But can I use it for a dockstar, and not a Pogo? > > What's the equivalent of J1's Pogo connector in my > dockstar? > > Thanks. You can use the Dockstar cfg from Redox. But the Pogo E02 and Dockstar have the same SoC so it most likely will work using Pogo E02 cfg. The J1 connector isby bodhi - uBoot
J. Carlos Wrote: ------------------------------------------------------- > With that link it seems I have to buy a BusPirate > card. > > But there is also this link: http://forum.doozan.c > om/read.php?3,21789 > > I have a raspberry pi. Am I understanding correctl > y that link shows how to use a raspberry pi as a J > TAG board?? > > Thanks. Yes,by bodhi - uBoot
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > habibie Wrote: > -------------------------------------------------- > ----- > > Hello Joey, > > > > Sorry to hear about that. I hope you will find > > ways to use the DVB-T module here in the US. > > That's the spirit, and Ha > ppy Chinese New Year! :-) Haby bodhi - Off-Topic
Here is the specific post (external link) to unbrick Dockstar: http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirateby bodhi - uBoot
It is in the sticky Wiki thread up above: 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 (external link) OSX Serial/Net Console Use Phone Jack - Phone Jack Serial Consby bodhi - uBoot
J. Carlos, Yes. It is bricked. And the Dockstar does not have UART booting. So the only way you can recover is connecting JTAG. But on the slim chance that it might have worked and something else was the problem, you can try to boot with uEnv.txt in /boot folder. See the instruction in the u-boot installation thread.by bodhi - uBoot
marcogaio, > Ahem... some hint/feedback on how the same kernel > boot from USB and return 'CRC error' on sata? > It usually happens if 1. After the uImage was generated, you forgot to do a sync before reboot. 2. the uImage was a wrong type, e.g. generated for a different architecture.Things like that. This problem would go away if you regenerate it on the ixby bodhi - Debian
> Afaik there is no "ECC ram" chips, ECC ram banks o > n PCs have one additional RAM chip to compensate f > or the space taken up by parity bits, but the ECC > is handled by the ram controller itself. I thought so too. But I did not look at the board for this so I don't really know. > I think (hope) that if you enable ECC on this box > you will lose soby bodhi - Debian
Rob, The DTB boots fine in my Pogo V3. Redownload it and check the md5. See if it is the same file. cd /boot/dts md5sum ox820-pogoplug-pro.dtb 1b4a4eab5eb94563e980c338cc1762ab ox820-pogoplug-pro.dtbby bodhi - Debian
bobafetthotmail Wrote: ------------------------------------------------------- > Random question time: > > Is there anything that can be done to enable ECC? > I've seen Armada 38x have ECC support. > https://origin-www.marvell.com/embedded-processors > /armada-38x/ > > I'm probably a nut, but I'd like to have ECC in a > server, even if it eatsby bodhi - Debian
And the kernel bootargs should include: mtdparts=armada-nand:5m(u-boot),5m@5m(kernel),5m@10m(uRamdisk),185m@15m(image.cfs),15m@200m(rescue_fw),20m@215m(config),10m@235m(reserve1),10m@245m(reserve2) This will hopefully make the envs area write-enable. But be aware that it is not safe to play with them too much yet if you can't do kwboot. Being extra careful not to change anything signiby bodhi - Debian
NAND is usually 128K sector size. And the env is usually 128K size: fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0x00080000 0x20000 0x20000by bodhi - Debian
@Carl, I see. [ 5.335654] 8 ofpart partitions found on MTD device pxa3xx_nand-0 [ 5.341782] Creating 8 MTD partitions on "pxa3xx_nand-0": [ 5.347205] 0x000000000000-0x000000500000 : "U-Boot" [ 5.352740] 0x000000500000-0x000000a00000 : "uImage" I'll take a look at this u-boot GPL. Update: Actually it is right here in the boot log:by bodhi - Debian
bobafetthotmai, > If you are ok with letting me make a "let's add su > pport to LEDE/OpenWRT for kirkwood boxes" thread i > n the Debian section (even if it is not Debian, ju > st for visibility), it's probably enough for me, a > nd it will go dead and can be moved somewhere else > after I'm done. Please go ahead and make a thread for it in Deby bodhi - Rescue System
@Carl, To get access to u-boot envs in Debian, install mtd-utils. apt-get install mtd-utils And then cat /proc/cmdline cat /proc/mtd cat /etc/fw_env.config and compare the output with ones in stock OS. Make sure they are the same (For cmdline, only mtdparts is relevant for this).by bodhi - Debian
Rob, Let me take verify on my Pogo V3.by bodhi - Debian
This is step 4 in the release thread for how to set envs to run the rootfs from USB or HDD without serial console intervention. And please note that this u-boot hack is ony for the Zyxel NAS326, it will not work for different MVEBU NAS, or any NAS :). Doing this on a different box without examining its stock u-boot source code will very likely brick it! Quote4. Enter the following commandby bodhi - Debian
buec65, Some of your NAND flash partitions were corrupted. And nandwrite will not fix them. If you don't really want to run newer kernel and u-boot, and just want to restore stock, you can find instruction at NAS Central: http://zyxel.nas-central.org/wiki/Category:NSA-325 Basically, you will need to use a USB drive to reflash stock FW. If that still does not work, then you willby bodhi - Rescue System
Thanks JT! and @Rob, can you reformat that stick? or use a different one.by bodhi - Debian
rr4m, Thanks! I've figured out a foolproof way to boot from USB (therefore also HDD) automatically without serial console input! I'll post that shortly after some more testing. That's why I want to see telnet/ssh behave so I can write the instruction to allow users without serial console to set up to boot USB. With a giant disclaimer, of course :)by bodhi - Debian
Does anyone know how to enable SSH or telnet in stock OS without using serial console?by bodhi - Debian
Hi Martin, > I think fox_exe wrote some text somewhere on his > drive on where the environment is located in > flash. So one could maybe change it from debian > with the u-boot tools. True. This is the best way. What I usually do first. So: - Get the /etc/fw_env.config from stock OS - Copy it to your rootfs /etc/ - Install mtd-utils - And reboot back into Linux - Checkby bodhi - Debian
@Carl, > hey bodhi, > Env's and I guess every promp from the uboot are > already posted from JanN (first post as well), and > of cause I can stop the boot process (with key > "1"). > > Yes, I think the uboots are very similar, but in > the wd uboot version you can't save env's as there > is no saveenv command. I see. That shouldby bodhi - Debian
@Carl, When you mentioned about the bootloader was locked down, it made me curious! could you post a serial bootlog, and the u-boot envs. Just in case I might think of someway to unlock it.This u-boot is probably the same as the one on NAS326. Update: I got the serial log in the 1st post. So I only need the envs. Can you stop it at countdown? Hit any key to stop autoboot: 0by bodhi - Debian
Rob, This panic was due to the USB drive being messed up. Shutdown the Pogo V3 completely (unplug power cord too). Take this drive to another Linux box and run e2fsck to fix whatever problem it might have. And then cold start the Pogo V3 with it.by bodhi - Debian
bobafetthotmail, > I don't really want to activate it, I want to make > sure that whatever makes it stay dead in my nsa325 > will keep it dead also in others so people can > recover their nsa325 through kwboot fine just as I > can. That's why I said I need to look at my notes to see what's the most friendlay way to reverse this :) there are a few differentby bodhi - uBoot
bobafetthotmail, > @bodhi: thanks for taking the time to help kofec > on this even if it was not an issue of your u-boot > :) No problem :) But I would suggest in the mean time this should be moved to Rescue subforum. And people can continue posting there with problem. I thought that kofec just want to build new u-boot :) I'll ask Jeff if he can create another subforumby bodhi - Rescue System
varma Wrote: ------------------------------------------------------- > Thank you very much again, bodhi > > I tought it was a common file for all the Kirkwood > platform...my mistake My pleasure! ... It does look that way because they are in the same SoC family. But each board must be built separately.by bodhi - uBoot