bodhi Wrote: ------------------------------------------------------- > I kept hoping we can resolve this without > installing JTAG (because you are so close to > booting). But in the worse case, JTAG is most > likely going to solve the issue. It seems the > NSA325 serial console might have some flaws that > we don't know about. What is involved with getting JTAG oby nunit - uBoot
bodhi Wrote: ------------------------------------------------------- > Yes. Try vary the -s and -q starting at: q 2 -s 1 Are the arguments for the -q and -s options in milliseconds? If so, then I assume you meant -q 2000 and -s 1000. With values of 2000, 5000, and 10000, the results were the same, i.e. image transferred but no boot. With single digit values for -q and -s, kwboot neverby nunit - uBoot
bodhi Wrote: ------------------------------------------------------- > Now we just need ot make the last handshake happen. > Did you recheck your serial console wires and header? I am new to these serial consoles, so I'm not sure how to verify them. I know the cp2102 converter works with an RPi 3 console (that took a bit of figuring out), but after I suspected the USB converterby nunit - uBoot
bodhi Wrote: ------------------------------------------------------- > Try the debug mode to see if any thing we can see > out of the console: > > ./kwboot -B 115200 -t /dev/serial0 -d root@raspberrypi:/home/pi# ./kwboot.20190228 -B 115200 -t /dev/serial0 -d Sending debug message. Please reboot the target...| > I'm not sure what I can do at that prompt, but myby nunit - uBoot
bodhi Wrote: ------------------------------------------------------- > Please try the new kwboot with 2017.07 uboot. I did try the new kwboot on the RPi with the 2017.07 image (as mentioned above), and the behavior was the same. The image seemed to be pushed completely but then it hangs and the only thing I can do is cancel out of kwboot and power cycle the NSA. So what does that tell usby nunit - uBoot
bodhi Wrote: ------------------------------------------------------- > Here is the u-boot image that I built to kill > watchdog: > uboot.2013.10-bodhi-1-uart.nsa325.test.4.kwb. > > Please try kwboot this image instead of the > 2017.07 image. Thanks for the quick turnaround. I first tried on my RPi with the new kwboot, and was only able to get 21% before the 30s watchdby nunit - uBoot
bodhi Wrote: ------------------------------------------------------- > So yours and Flecks situation might be recoverable > with a different kwboot. > > Let me see I can rebuild another kwboot version > from mainline. Thanks a bunch for your help with this bodhi!by nunit - uBoot
bodhi Wrote: ------------------------------------------------------- > At this point, the watchdog has not been disabled. > The BootROM might have temporarily stops the > watchdog while the image is being loaded. But > until after something has permanently disbaled it > (new u-boot does that first thing), the watchdog > could still kicks in. So even if you start a > uby nunit - uBoot
bodhi Wrote: ------------------------------------------------------- > That’s the HW watchdog kicks in. I’ve solved > this problem long ago. > > Let me find the right binary. Some background on my particular unit: I used it for a years with only the stock firmware, then lent it to a friend for a few months, and when I got it back, it exhibited these symptoms. I doubt tby nunit - uBoot
I have an NSA325v1 that exhibits the exact same symptoms (power and hd2 LEDs always lit, reboots itself every 30s, etc.). After much googling and reading the various posts here, I have a working serial connections via an RPi v1 as well as a cp2102 USB-TTL converter. With both connections, I also get the same behavior where kwboot hangs after it finishes sending the uboot image: root@raspberrby nunit - uBoot