Stephen P, > did a nand scrub to 'recover' the bad block -that > *seems* to have worked. Cool! great that you have scrubbed and recovered that bad block. The bad block is exactly at the envs location 0x000c0000 :) So now you need to watch that block. And it goes bad again, then the boot log will show: *** Warning - bad CRC, using default environment Then you wilby bodhi - uBoot
> Now Debian 9 with Linux Kernel 4.12.1 is booting > on my Zyxel NSA325v2 and I can go on create a > backup box. Cool! and very good that you have documented a summary of these steps, too. It will be handy to help others in the future!by bodhi - uBoot
Hi Ray, First, thanks for your works! > Did you include the pull request that added MMC > support to SheevaPlug? No, I did not. Because I've waited too long to rebase to 2017.07, I've found that in this mainline version there is a better MMC driver that works for all Kirkwood and MVEBU. So I have removed the patched MMC driver, and now use the mainline driver for Pogo V4by bodhi - uBoot
Update your wget packge. Quote- ------------------------------------------------------------------------- Debian Security Advisory DSA-4008-1 security@debian.org https://www.debian.org/security/ Moritz Muehlenhoff October 28, 2017 https://www.debian.org/security/faq - ------------------------------------------------------------by bodhi - Debian
Hi feas, > I was bored since some of my other projects have > stalled until my money tree grows. We don't want you to be bored :) I've released u-boot-2017.07-tld-1: https://forum.doozan.com/read.php?3,12381 For the Dreamplug, I have not written installation instruction for it, so here is the pre-released binary (This is the final version when I can post instruction toby bodhi - Debian
I've uploaded 2017.07-tld-1 U-Boot images. Please see 1st post for download link. QuoteNew/updated in 2017.07-tld-1 version: - Rebase u-boot code to track mainline 2017.07. - Incorporated patch to fix "EHCI timed out on TD" error with USB drives. - Switched the MMC driver to use mainline version for Pogo V4/Mobile and Sheevaplug. - Improve internal defautl envs.by bodhi - uBoot
Stephen P Wrote: ------------------------------------------------------- > P.S. How do I get the leds working in Debian > please? I've tried all three dtbs but no luck... Look at the /etc/rc.local in your rootfs for example how to set LEDS. You need to identify which NSA310 model do you have and use the correct DTB. After that, see the names of the LEDs in ls -l /sys/clasby bodhi - uBoot
Hans Peter, > Okay bodhi same error but with the new u-boot > image. The DTB can't be the problem, because now I > have the new uboot installed. It is still DTB related problem. See this error: > *** Warning - bad CRC, using default environment The reason is because you did not flash the default envs image while installing new u-boot. Quote8. Flashing defauby bodhi - uBoot
pritamcharan, You should post in this thread to get LEDE instalation helps from bobafetthotmail: https://forum.doozan.com/read.php?4,29966by bodhi - Rescue System
Hans Peter, First, please use code tags when posting log output or any commands. It helps people to read it correctly. Without code tags, the post is usually not readable. And when the log is short such as a boot log, include it in the post with code tags. Don't attach it. ------------- OK so now the problem solution. This error becaus the kernel file /boot/uImage does not hby bodhi - uBoot
kt97679 Wrote: ------------------------------------------------------- > Hi Bodhi, > > thanks a bunch for your help! I finally completed > updating of the uboot today and everything worked > ok. > > Thanks, > Kirill. Cool! glad I can help.by bodhi - uBoot
Snarky, At this point, I need to see the actual log of what going on. How you executed them, and all the outputs. So after you execute these commands, please copy everything on your terminal begining here until the end and post here. Your u-boot envs are incorrect, so I need to know why. In Debian. ls -lart /boot cat /etc/fw_env.config cat /proc/mtd ls -lart /boot/dts/kirkwood-pogby bodhi - uBoot
Stephen P, > stock u-boot + these variables + stock firmware > boots ok automatically. > stock u-boot + any variables + Debian will not > work because drive is GPT etc. Expected. > kw u-boot + these variables + Debian boots ok via > manual boot command. Expected. > kw u-boot + these variables + stock firmware hangs > as shown - this is what I want toby bodhi - uBoot
Please use code tags next time to post log. It is very hard to read without it. Hope you know how to use code tags?by bodhi - uBoot
Snarky Shutdon, power up, interrupt serial console and printenv boot Let it boot all the way to Debian. Log in as root, and cat /etc/fw_env.config cat /proc/mtd ls -lart /boot/dts/kirkwood-pogoplug_v4.dtb And try to set them again fw_setenv preboot_nc 'setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done;by bodhi - uBoot
Last post moved here: https://forum.doozan.com/read.php?3,39894by bodhi - uBoot
Hi feas, Everything in the env value needs to wrapped in single quotes (to ensure spaces and = are taken as literal). For example, setenv load_dtb 'echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file'by bodhi - uBoot
Stephen P, Kwboot again. Interrupt serial console, and execute: printenv And proceed to try booting as you did before. I need to see what envs you attempted to set, in order to point out the errors and suggest what to do to get more information if necessary. Post the entire serial console log, from kwboot banner until the kernel stuck at "done, booting the kernel".by bodhi - uBoot
Last post moved here: https://forum.doozan.com/read.php?3,39859by bodhi - uBoot
kalilhabib, > Everything worked. Cool! > Now I'm super ready to put the DEBIAN in this box. > Could you tell me a step by step for this > procedure. Thanks a lot. Create rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 https://forum.doozan.com/read.php?2,12096 Scroll down to section: QuoteUpdated 24 Jul 2017: Basic Debian stretch Kirkwoodby bodhi - uBoot
CfromEarth, feas was right. Your box envs are all messed up. That was because you did not flash the default envs image. Quote8. Flashing default u-boot envs image: As described in step 1, u-boot envs must be defined in etc/fw_env.config as # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 A special section (B. Flashiby bodhi - uBoot
See here for the USB error explanation: https://forum.doozan.com/read.php?3,38859,39004#msg-39004 Use a Sandisk USB flash drive, and it will be OK. To salvage this drive, take it to another Linux box and fsck it. Plug it back in the USB port right next to the ethernet port in the back. And power up. If you keep getting this error, use a new Sandisk drive and clone this rootfs over. Anby bodhi - Debian
uboot.2015.10-tld-2 u-Boot image for Pogoplug V3 Oxnas has been uploaded. Please see 1st post for download link. QuoteUpdated in this u-boot version: - Fixed preboot missing in previous version. As a result, netconsole is now starting automatically if set up. - A more robust new default envs image.by bodhi - uBoot
hughe, Everything looks good! Now it's time to remove the uEnv.txt. Consider your current envs are already that way. fw_printenv root@debian:~# root@debian:~# root@debian:~# fw_printenv bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; elseby bodhi - Debian
Baldmarbles, Power up, interrupt serial console at count down, and execute: setenv bootargs_end ':::DB88FXX81:eth0:none earlyprintk=serial' boot Please post the entire serial console log again here.by bodhi - uBoot
> I don't have mtdparts in the environment, what I > should use for the value? For the Pogo V4 and Pogo Mobile: fw_setenv mtdparts 'mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)' > My current environment is very different from the > default environment I'm going to write, is this a > concern? > In current environmby bodhi - uBoot
Kirill, Quote> Per guidelines I need to clear dtb_file: > > > fw_setenv dtb_file > That's correct, to boot with DTB appended to uImage. After you've installed new u-boot and its default envs, you can boot either way. The best way is with separate DTB. This give us the most flexible configuration. IOW, you could replace the DTB with a better one offline eaby bodhi - uBoot
Toddy Cangica Wrote: ------------------------------------------------------- > Bodhi, > > I bought another serial module (a ft232rl) and now > it's working. I booted with a usb stick with the > recovery image and after some time, the device > booted and showed the IP. > > thank you all your help Cool!by bodhi - uBoot
hughe, When you're done, you should post the serial console log and with the envs listing.by bodhi - Debian
And the devices should be devices=usbby bodhi - Debian