Thanks a lot for your help. Everything seems to work awesomely now - turns out it was just my bad partitioning. FWIW: even following the instructions I still have to unplug / replug the TX pin, otherwise kwboot is stuck on "Sending debug message. Please reboot the target...".by rkachowski - Debian
so amazon came through and provided a uart - usb connection, and eventually I managed to get the serial console working. what i've found is that when all the leds turn on dim and wait there, the TX connector needs to be removed and immediately reattached to continue the boot process. from there i can interrupt the autoboot and get into the console. *** Booting kernel from kernel 1 @0x0by rkachowski - Debian
sorry about the paste bin, I was just concerned about noise in the thread. I've retried the commands as above with no success. I'll also find a new usb drive to see if that works, but the next step will be a serial console setup. (it turns out I have an ftdi TTL 232r v5 cable lying around, is this suitable? I considered it before but I'm not sure about the voltages / which pinsby rkachowski - Debian
So I've run the setenv commands, put the usb into the front port, synced and restarted. Unfortunately the nas booted up again into the stock os, the fw_printenv output after reboot is available here https://pastebin.com/EbLuwbRy One small note is that the busybox install doesn't have `shutdown`, only `reboot` and `poweroff`. The fact that @kekeke has it running gives me hope though!by rkachowski - Debian
sure, the env is ~ # fw_printenv CASset=max CONTRY_TYPE=FF FEATURE_BIT=00 MALLOC_len=5 MODEL_ID=B303 MPmode=SMP PRODUCT_NAME=STG-328 VENDOR_NAME=MitraStar Technology Corp. autoload=no baudrate=115200 boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:2m(u-boot),2m(env),2m(by rkachowski - Debian
Hey, Thanks for getting back to me. I have firmware V5.20 which came installed with the device. I don't have a serial terminal - I was hoping to follow your usb instructions - but I'll ask around and see if i can acquire one. The output is below, the disk is /dev/sdb and it automounts to some /e-data/ dir ~ # mount /proc on /proc type proc (rw) /sys on /sys type sysfs (rw)by rkachowski - Debian
I'm trying this with the ZyXEL nas326 (method B - usb installation without serial) and encountering similar errors as were mentioned here before by @nastynas, notably * the firmware is reset every time it reboots - ssh access is disabled until initial account setup + configuration * occasionally locks up on boot (unresponsive, all leds deactivated) The dmesg boot is here - https://pasby rkachowski - Debian