Remember, do not start flashing before I advise you to do that!by bodhi - Debian
stef34280, 1. You do have serial console. So you should try to run kwboot first to make sure you have a rescue path https://forum.doozan.com/read.php?3,12381 QuoteImportant Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction here in this thread. The latest u-boot image released here should bby bodhi - Debian
stef34280, > 1.010000] Scanning device for bad blocks > [ 1.010000] Bad eraseblock 4 at 0x000000080000 > [ 1.050000] Bad eraseblock 697 at > 0x000005720000 Warning: what I advise below only applicable to your specific configuration (in case other users read this and would make a wrong assumption when their configuration is different). You have the Pogo V4, thereforeby bodhi - Debian
Stephen, > I cannot find any refs to sensors either, which is > odd because lm85 shows up in lsmod and playing > around with the sensors command I can get readings > and using the sysfs interface I can poke fan > speeds, so I guess it's working? Yes it is working as expected. I forgot this sensor driver is a loaded module :) So you are OK. Now we know you have lm85.by bodhi - uBoot
Stephen, I did not see any sensor here. Please reboot without systemd. And post serial bootlog.by bodhi - uBoot
Mike, Do you have serial console? Post the entire boot log here if you do.by bodhi - Debian
Last post moved here: https://forum.doozan.com/read.php?2,40304,40304#msg-40304 Pleas do not post booting problem in this thread.by bodhi - Debian
huge Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > huge, > > > > > > > root@PogoV4Debian:/temp# ./kwboot -t -B > 115200 > > > /dev/ttyUSB0 -b > > > uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p > > > > > > > > >by bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > feas Wrote: > ------------------------------------------------------- > > > https://forum.doozan.com/read.php?3,27280 > > The post start with > > QuoteWhile in stock OS... and I'm not so > I don't know if it applies... The binaries work in both stock OS and any other moby bodhi - uBoot
huge, > root@PogoV4Debian:/temp# ./kwboot -t -B 115200 > /dev/ttyUSB0 -b > uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p > When it stuck here, it might mean that your serial connection is not solid. At this point u-boot has not started yet, so don't worry about the envs. Check the wires and try again. Serial console might work OK with marginal connections, but kwboot doesby bodhi - uBoot
Maarten, That's a bummer :) BTW, the solder buttons are quite soft, you can use small pins and push them in temporarily to connect. And then later use a JST header instead of just wires.by bodhi - uBoot
Stephen P, IIRC, the rebrand TDC is NSA310a. But you have to try it to verify. It should boot with either one. But the correct one will give you the right sensor. Boot with the NSA310a DTB and then post the bootlog here.by bodhi - uBoot
Mike, Please start a new thread and post your prolem again with serial boot log, or whatever you want me to take a look.by bodhi - Debian
Thanks musv! I'll take a look and incorporate in the next release.by bodhi - Debian
> Make CMD_CLK "great again!" Are you going to have that on your baseball cap? I'm cleaning up my keyboard :))by bodhi - Off-Topic
Check to see you have which of these 2 boxes: http://zyxel.nas-central.org/wiki/Category:NSA-310 And If you have a red USB LED then it's the 3rd variant.by bodhi - uBoot
kralan Wrote: ------------------------------------------------------- > I am still at 4.9.5-tld-8 and am planning to > upgrade to the latest available kernel soon. > Do I gather correctly from the recent posts that > it's better to wait with the upgrade until the > mvneta issue is sorted out? It's really up to you. If your use case is similar to musv then I'by bodhi - Debian
Snarky, 1. Code tags button is the right most button on top of the text box where you type your post (the B button for bold is the left most). 2. You also did not post the log of commands and their output. When I ask for that, you should copy/paste the entire screen to the post. Don't reformat anything. Since you are new with this, you don't know that the log must be shown aby bodhi - uBoot
kirkwood-nsa310.dts This variant is the "original". This has the sensor adt7476: i2c@11000 { status = "okay"; adt7476: adt7476a@2e { compatible = "adi,adt7476"; reg = <0x2e>; }; }; kirkwooby bodhi - uBoot
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