Welcome! Log In Create A New Profile

Advanced

U-Boot for Zyxel NSA-325v2 kwboot didn't help

Posted by kofec 
U-Boot for Zyxel NSA-325v2 kwboot didn't help
November 29, 2019 10:18AM
Hi,
There is no stock uboot or doesn't start. I don't know history of this hardware.
Is it hardware issue or I can try something else:
/kwboot-tool# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p 
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]


I have second nsa325v2 and it is working fine. Does it mean that this is hardware issue ? Is there any thing else I can try ?



Edited 1 time(s). Last edit at 11/29/2019 10:33AM by kofec.
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
November 29, 2019 05:10PM
kofec,

> Does it mean that this is hardware issue ? Is
> there any thing else I can try ?

Unfortunately, it might be hardware problem. Some NSA325 (very few) has this behavior that it is just stuck at this point.

If you let it boot without kwboot and just run serial console, then what is the behavior?


=====

You could try to run a newer version of kwboot to see if it helps showing more info.

Quote
https://forum.doozan.com/read.php?3,12381
To download ARM kwboot binary for UART booting at Dropbox

kwboot-2016.05.tar
md5:
76977c5a61544a5707dfa17ae832a3ad
sha256:
25ee4fa8a94372d2d398cac4704e9ee3ca87585c29e72e18323209b7f163209d

kwboot (this is an older version)
md5:
0efd011bdb244436e432a8de33e639a1

If you've already tried the above versions and it did not help, you can run the current kwboot in your Debian rootfs. It is likely a newer version than the one I uploaded above.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
November 29, 2019 06:34PM
> If you let it boot without kwboot and just run serial console, then what is the behavior?

Nothing. Even single character

> kwboot-2016.05.tar

After unpack:
./kwboot
bash: ./kwboot: cannot execute binary file: Exec format error
I used both version of kwboot (from your website and provided with system) and the same result(first post).

Current behavior is power led (blue) turn on fir 31 seconds turn off for 1 second and again turn on for 31 seconds and again again ...



Edited 1 time(s). Last edit at 11/29/2019 06:35PM by kofec.
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
November 29, 2019 10:00PM
kofec,

> Current behavior is power led (blue) turn on fir
> 31 seconds turn off for 1 second and again turn on
> for 31 seconds and again again ...

That's actually a bit of a good clue! this box has a HW watchdog that kicks in every 30 seconds. If it were silent than I would say only installing JTAG would be able to unbrick it.

Is this behavior the same whether you boot with stock u-boot, and boot with kwboot? In my u-boot build, which you loaded with kwboot, the watchdog is killed right away upon starting, so it would be really strange if watchdog is still alive.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
November 30, 2019 04:17AM
You are right. We I load your uboot the Power LED is not blinking after 30 seconds. Also fan is control (RPM is changing). On ethernet I don't see any packet (wireshark) but the physical link is up.
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
November 30, 2019 05:54PM
kofec,

It think it is likely a bad RAM chip.

The fact that the watchdog was killed during kwboot, told me that the BootROM has done all the necessary preparation to run u-boot. And then u-boot image loading was successful, so it about or starting to run u-boot image, but u-boot crashed too early for us to see the u-boot banner.

If you don't want to have to install JTAG and consider this is a brick for now, then put this box on the shelves until I have time to figure out how to verify this is a HW problem (I can't promise if or when I can do it).

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
December 02, 2019 03:13AM
Thanks a lot for you help. I also suspect RAM module but I was surprised that u-boot image loading was successful - As I understand it was loaded to RAM. If we tried all known simple methods to recover this device I going to sell it - I will describe all our findings. Maybe someone needs the case or have tools and knowledge to replace RAM module. So thanks again for you help.
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
December 02, 2019 04:05AM
kofec,

> Thanks a lot for you help. I also suspect RAM
> module but I was surprised that u-boot image
> loading was successful - As I understand it was
> loaded to RAM.

Right. However, when u-boot starts, there will be more memory relocation and heap space allocated,..... So I'm guessing that when the crash occurred.

> If we tried all known simple
> methods to recover this device I going to sell it
> - I will describe all our findings. Maybe someone
> needs the case or have tools and knowledge to
> replace RAM module. So thanks again for you help.

I did rebuild a Pogo V4 u-boot with DEBUG to run a test to see if we can see some more info. But it did not print out much (in fact there is only one extra line) before the version banner. So it is not a good sign that we can see a whole lot with the rebuild of NSA325. But until that is confirmed with the NSA325 image, there is still some slim hope.

The complicate method is to install a JTAG header and then run OpenOCD like in this thread:
https://forum.doozan.com/read.php?3,21789

At the moment we don't have the configuration file for NSA325 to run JTAG. So that would make the JTAG solution even more time consuming.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
December 04, 2019 11:11PM
kofec,

Here is the NSA325 u-boot rebuilt with full DEBUG on. Hope it will tell more about what's going on. Please try kwboot with this version.

-bodhi
===========================
Forum Wiki
bodhi's corner
Attachments:
open | download - uboot.2017.07-tld-1.nsa325.debug.mtd0.kwb (640 KB)
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
December 05, 2019 12:40AM
Thanks, I will try today when back home
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
December 05, 2019 12:16PM
It is strange but still nothing:

nsa325/kwboot-tool# ./kwboot -t -B 115200 /dev/ttyUSB0 -b ../uboot.2017.07-tld-1.nsa325.debug.mtd0.kwb -p
Sending boot message. Please reboot the target...-
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  2 % [......................................................................]
  4 % [......................................................................]
............
 97 % [......................................................................]
 98 % [......................................................................]
 99 % [..........]
[Type Ctrl-\ + c to quit]

Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
December 05, 2019 06:03PM
kofec,

As I've suspected, the crash/hang might have occured too early.

In the normal case, there at least one debug print statement that should output an initcall() before the banner.

So basically, I don't see we can try any more simple methods to figure out.

More investigation will be complicated (i.e. add debug printf, using JTAG).

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
May 18, 2020 01:53AM
is there any picture where to find the JTAG pin on NSA325 v1 or v2?
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
May 18, 2020 02:53AM
buec65,

> is there any picture where to find the JTAG pin on
> NSA325 v1 or v2?

I do have a NSA325 board with JTAG header installed. I believe this board UART port is damaged, and asked my friend to install a JTAG header to so I can revive it in the future.

But I did not have enough time to revisit this project.

The Kirkwood JTAG port should be the same in these boxes. It is a standard JTAG port.

So see the Popo E02 thread for the pinouts:

https://forum.doozan.com/read.php?3,21789

I have to dig it out of my shelf if you need to see the pic of this JTAG header on the board.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 05/18/2020 02:55AM by bodhi.
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 10, 2020 01:31AM
UART of my NSA325 didn´t show a massage, but i think it is because of broken firmware.

RaspberryPi B+ is available - i will try to rescue NSA325
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 10, 2020 04:52AM
buec65 Wrote:
-------------------------------------------------------
> UART of my NSA325 didn´t show a massage, but i
> think it is because of broken firmware.
>
> RaspberryPi B+ is available - i will try to rescue
> NSA325

Cool! I think between Joerg, you, and I, we should be able to figure out the procedure for JTAG on this box.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 20, 2020 07:44AM
started first broken NSA325 (v2) using kwboot on a raspberry pi +

pi@raspberrypi:~ $ kwboot -p -t -b uboot.2017.07.kwb -B 115200 /dev/ttyUSB0
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  8 % [......................................................................]
 10 % [......................................................................]
 11 % [......................................................................]
 13 % [......................................................................]
 15 % [......................................................................]
 17 % [......................................................................]
 18 % [......................................................................]
 20 % [......................................................................]
 22 % [......................................................................]
 23 % [......................................................................]
 25 % [......................................................................]
 27 % [......................................................................]
 29 % [......................................................................]
 30 % [......................................................................]
 32 % [......................................................................]
 34 % [......................................................................]
 35 % [......................................................................]
 37 % [......................................................................]
 39 % [......................................................................]
 41 % [......................................................................]
 42 % [......................................................................]
 44 % [......................................................................]
 46 % [......................................................................]
 47 % [......................................................................]
 49 % [......................................................................]
 51 % [......................................................................]
 53 % [......................................................................]
 54 % [......................................................................]
 56 % [......................................................................]
 58 % [......................................................................]
 59 % [......................................................................]
 61 % [......................................................................]
 63 % [......................................................................]
 64 % [......................................................................]
 66 % [......................................................................]
 68 % [......................................................................]
 70 % [......................................................................]
 71 % [......................................................................]
 73 % [......................................................................]
 75 % [......................................................................]
 76 % [......................................................................]
 78 % [......................................................................]
 80 % [......................................................................]
 82 % [......................................................................]
 83 % [......................................................................]
 85 % [......................................................................]
 87 % [......................................................................]
 88 % [......................................................................]
 90 % [......................................................................]
 92 % [......................................................................]
 94 % [......................................................................]
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]


U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0


NSA325> printenv
arcNumber=4495
baudrate=115200
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
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; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm$load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
console=console=ttyS0,115200
device=0:1
devices=usb ide
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-nsa325.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtddevname=key_store
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x100000(uboot),0x80000(stock_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
nand_erasesize=20000
nand_oobsize=40
nand_writesize=800
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 3115/131068 bytes
NSA325>


NSA325> usb start
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 5
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 4
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 3
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 2
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 1
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 0
1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
NSA325> usb stop
stopping USB..
EHCI failed to shut down host controller.
NSA325> usb start
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 5
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 4
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 3
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 2
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 1
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 0
1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
NSA325>

NSA325> ide reset

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: WDC WD5000LPCX-60VHAT0 Firm: 01.01A01 Ser#:  WD-WX41AC5RYN2Y
            Type: Hard Disk
            Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
** First descriptor is NOT a primary desc on 0:1 **
NSA325> ide reset

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: ST980411ASG  Firm: DE17 Ser#: 5TF0DHEA
            Type: Hard Disk
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
** First descriptor is NOT a primary desc on 0:1 **
NSA325>

USB and SATA did not work for me

pi@raspberrypi:~ $ sudo openocd -f pogo.cfg
Open On-Chip Debugger 0.10.0+dev-01281-gf0909fe9-dirty (2020-06-12-12:02)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
Warn : use 'feroceon.cpu' as target identifier, not '0'
pogo_load_uboot
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : BCM2835 GPIO JTAG/SWD bitbang driver
Info : JTAG and SWD modes enabled
Info : clock speed 2030 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9 (Marvell Semiconductors), part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Info : starting gdb server for feroceon.cpu on 3333
Info : Listening on port 3333 for gdb connections

> nand list
#0: NAND 128MiB 3.3V 8-bit (unknown) pagesize: 2048, buswidth: 8,
blocksize: 131072, blocks: 1024

>
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 20, 2020 04:07PM
buec65,

> started first broken NSA325 (v2) using kwboot on a
> raspberry pi +
>

> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03
> -0700)
> ZyXEL NSA325 2-Bay Power Media Server

Then there is no need for JTAG.

> NSA325> usb start
> starting USB...
> USB0: USB EHCI 1.00
> scanning bus 0 for devices... EHCI timed out on TD
> - token=0x80008c80

The USB drive has a problem, probably a brand that u-boot does not like. What brand is this? If it is not Sandisk or Transcend, get one of these 2 brands of flash drive if you could.

> Reset IDE: Bus 0: OK Bus 1: not available
> Device 0: Model: WDC WD5000LPCX-60VHAT0 Firm:
> 01.01A01 Ser#: WD-WX41AC5RYN2Y
> Type: Hard Disk
> Capacity: 131071.9 MB = 127.9 GB
> (268435455 x 512)
> ** First descriptor is NOT a primary desc on 0:1
> **

This HDD needs to be reformatted. Use fdisk to wipe it first. And then create a brand new partition.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 21, 2020 10:31AM
bodhi,

formated disk using minitool partition wizard
primary partition ext2 active

NSA325> ide reset

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: ST980411ASG  Firm: DE17 Ser#: 5TF0DHEA
            Type: Hard Disk
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
** First descriptor is NOT a primary desc on 0:1 **


NSA325> nand bad

Device 0 bad blocks:
  00000000

 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]


U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:48:40 -0700)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
NSA325>

is there a possibility loading uboot over serial to ram an flash to nand?
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 21, 2020 04:28PM
buec65,


> is there a possibility loading uboot over serial
> to ram an flash to nand?

It is not NAND problem. The CRC error was simply that you did not flash the env image to NAND during installation. However, the u-boot internal envs are used if that happened. So there is no need to flash envs to NAND until after you have logged into Debian.

In fact, you could run the box with this CRC error, unless you want to set u-boot envs in Debian.

So I would recommend you use fdisk to wipe the HDD and recreate the rootfs. Don't use any other tool in this case.

If there is still problem after that, then you should use dd to wipe it, and then use fdisk to create partition again.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 21, 2020 11:11PM
Bodhi,

all my USB flash drives work with other NSA325 only this unit does not accept them.
Without kwboot only hd02 and power led.

I don't know how get this back working.

Maybe there is a way in opnocd
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 22, 2020 01:29AM
buec65,

> all my USB flash drives work with other NSA325
> only this unit does not accept them.
> Without kwboot only hd02 and power led.

- Create a new rootfs on a USB drive thumb drive. Preferably a Sandisk thumb drive.
- Boot with kwboot and plug in the USB drive.
- Do

usb reset

When u-boot can initialize the USB drive successfuly, boot into Debian. And then install u-boot image and its envs image.

There is no difference between serial console and JTAG, as far as booting a u-boot image in memory after it was loaded.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 28, 2020 05:22AM
 kwboot -p -t -b uboot.2017.07.kwb -o 5 -B 115200 /dev/ttyUSB0Sending boot message. Please reboot the target...\
Sending boot image...
...
 99 % [....................................]
[Type Ctrl-\ + c to quit]


U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0 [PRIME]
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: empty MTD device detected
ubi0: attached mtd1 (name "mtd=2", size 126 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1014, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 990, total reserved PEBs: 24, PEBs reserved for bad PEB handling: 20
Read 0 bytes from volume kernel to 800000
Volume kernel not found!
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
NSA325> help

NSA325> ide reset

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: ST980411ASG  Firm: DE17 Ser#: 5TF0DHEA
            Type: Hard Disk
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
** First descriptor is NOT a primary desc on 0:1 **
NSA325>

SATA disk formated at raspberry pi fat, ext2, ext3 always same output

SanDisk USB Ultra did not recognize

NSA325> usb reset
resetting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 5
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 4
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 3
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 2
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 1
EHCI timed out on TD - token=0x80008c80
EHCI fail timeout STS_ASS reset
unable to get device descriptor (error=-1) retry: 0
1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
NSA325>

NSA325> usb info
1: Hub,  USB Revision 2.0
 - u-boot EHCI Host Controller
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

NSA325>


NSA325> nand info

Device 0: nand0, sector size 128 KiB
  Page size       2048 b
  OOB size          64 b
  Erase size    131072 b
  subpagesize      512 b
  options     0x40001014
  bbt options 0x00000000
NSA325> bdinfo
arch_number = 0x0000118F
boot_params = 0x00000100
DRAM bank   = 0x00000000
-> start    = 0x00000000
-> size     = 0x20000000
eth0name    = egiga0
ethaddr     = 5C:F4:AB:DE:F1:66
current eth = egiga0
ip_addr     = 192.168.10.172
baudrate    = 115200 bps
TLB addr    = 0x1FFF0000
relocaddr   = 0x1FF2F000
reloc off   = 0x1F92F000
irq_sp      = 0x1FB0EEF0
sp start    = 0x1FB0EEE0
NSA325> printenv
FEATURE_BIT=00
MODEL_ID=AA03
PRODUCT_NAME=NSA-325
arcNumber=4495
baudrate=115200
bootcmd=ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000
bootdelay=3
console=console=ttyS0,115200
enaDCPref=yes
enaICPref=yes
ethact=egiga0
ethaddr=5C:F4:AB:DE:F1:66
ethmtu=1500
ethprime=egiga0
image_multi=yes
ipaddr=192.168.10.172
mainlineLinux=yes
mtddevname=uboot
mtddevnum=0
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x0c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi)
nandEcc=1bit
nand_erasesize=20000
nand_oobsize=40
nand_writesize=800
netmask=255.255.255.0
partition=nand0,0
pcieTune=no
pcieTune1=no
sata_dma_mode=yes
stderr=serial
stdin=serial
stdout=serial
usb0Mode=host

Environment size: 745/131068 bytes
NSA325> mtdinfo
Unknown command 'mtdinfo' - try 'help'
NSA325> mtdparts

device nand0 <orion_nand>, # parts = 3
 #: name                size            offset          mask_flags
 0: uboot               0x000c0000      0x00000000      0
 1: uboot_env           0x00080000      0x000c0000      0
 2: ubi                 0x07ec0000      0x00140000      0

active partition: nand0,0 - (uboot) 0x000c0000 @ 0x00000000

defaults:
mtdids  : none
mtdparts: none
NSA325>
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 28, 2020 03:42PM
buec65,

I think you should flash u-boot to NAND in serial console to unbrick it first. Make it more convenient to trouble shoot the drives. I will post a few commands to do that.

In the mean time, you should also check your power supply to see if it has enough juice in accordance with the specs.This one has a barrel connector, so a lot of other power supply unit can be used with this box. Also if you have a multimeter, then it is easy to see.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
June 30, 2020 12:09PM
bodhi,

power supply tested with other nsa325v2 work ok - used 2 or 3 different power supplies already.

> I will post a few commands to do that.

i will be happy trying this.

take as many time you need to find the commands - i am not in a hurry

sorry for my bad english - left school in 1983
Re: U-Boot for Zyxel NSA-325v2 kwboot didn't help
July 04, 2020 07:10PM
buec65,

> sorry for my bad english - left school in 1983

:) not a problem for me. I understood you just fine.

Here is how we flash the image in serial console.

==================


Flashing NSA325 u-boot in serial console
04 Jul 2020




1. In serial console (either after you kwboot into the box successfully, or just a regular serial console is fine), prepare tftpboot server and this box IP addresses. Assuming your router is 192.168.0.1, you tftp server is 192.168.0.220, and you want the NSA325 to be 192.168.0.231.


setenv serverip 192.168.0.220
setenv ipaddr 192.168.0.231


And put the image uboot.2017.07-tld-1.nsa325.mtd0.kwb in the /tftproot folder where the tftp server is.

2. Load the image to see if it is loaded OK.

tftpboot 0x800000 uboot.2017.07-tld-1.nsa325.mtd0.kwb
If it was loaded successfully, proceed to the next step.

3. Erase the 1st MB on mtd0

nand erase 0x0 0x100000

4. Flash this 512K u-boot image to 0x0 (here we load the image again to make sure it is clean).

tftpboot 0x800000 /uboot.2017.07-tld-1.nsa325.mtd0.kwb
nand write 0x800000 0x0 0x80000

5. Reset the box at serial console prompt

reset

6. Upon reboot successfully, interrupt serial console and

printenv

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 07/04/2020 07:14PM by bodhi.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: