... wait a few days. I'm about to write it down - but there are still a few issues. Get a serial cable in the meantime! ;-)by JoniDaBoni - uBoot
Hi bodhi, I'm now stuck a 8.2e - in the saved envs, there are no mtdparts - and the ethaddr looks interesting ...? bootargs= bootcmd= bootdelay=2 baudrate=115200 arch=sandbox cpu=sandbox board=sandbox board_name=sandbox stdin=serial,cros-ec-keyb,usbkbd stdout=serial,vidconsole stderr=serial,vidconsole ethaddr=00:00:11:22:33:44 eth1addr=00:00:11:22:33:45 eth3addr=00:00:1by JoniDaBoni - Debian
Thank you for the confirmation ... worked as expected. So I continue with step 8 ?!by JoniDaBoni - Debian
Hi bodhi, worked like a charm. I am now in the middle of the uboot flash procedure. But the result of step 6 is not as expected: root@debian:/# flash_erase /dev/mtd0 0 4 Erasing 128 Kibyte @ 7f563f5c00000064 -- 4 % complete What should I do???by JoniDaBoni - Debian
Hi bodhi, (as I started with the article on Nas central (a while ago ...), I have used saveenv / resetenv beforehand ... not not recently.) Given my rather unproductive and unsuccessful experiences with stock OS (I was not able to get anywhere with the instructions form the u-boot thread with the Marvell prompt in stock), I would choose option #2 - but I think you'd be better at estimaby JoniDaBoni - Debian
OK, so, if I interrupt the kwboot countdown, I fall back to the teminal prompt; if I let the countdown go through to the prompt of the kwboot u-boot, OR if I let the box boot and interrupt the u-boot countdown of the stock u-boot, it gives me the same result on printev (see below). Maybe I have a too mechanical perspective on this, but I don't understand where the envs (that are apparentby JoniDaBoni - Debian
Hi Bodhi, that worked and I was able to login to debian. I made the first modifications (generating the SSH keys, apt-get update etc.). By then I realized that I would not have the time to flash the new uboot and I quit debian. But the next time I tried to kwboot, I only got the following message (I cut the stuff above the loading): 97 % [.................................................by JoniDaBoni - Debian
Hi, me again - small update: the best I can get with the kwboot is 0% [++xmodem: Bad message ... and on the other terminal window (screen), I can see that the box goes in some sort of limbo with a lot of weird characters ... ;-)by JoniDaBoni - Debian
Hi Bodhi, thank you for your quick and kind reply. > > 2: UART booting: > > Didn't work for me - I always get the message > > "xmodem: Bad message" ...? (But I'm almost > willing > > to go ahead like this and risk it ...) > > Now when you got "xmodem: Bad message', it is > actually not bad. It means the NSA325 Booby JoniDaBoni - Debian
Hi Bodhi, like Hans Peter (Zyxel NSA325 Newbie question), I have a NSA325 that I'd like to use with Debian (stock OS is too old/limited, the hardware too good to just throw it away). I have a fair basic knowledge of linux, but like Hans Peter, I feel like I'm missing sometimes a bit of information here and there and/or I'm not capable of tying the relevant parts together. So theby JoniDaBoni - Debian