ReadyNas rn204 won't start up

On futher checking. Via serial port connection. If I do not interupt boot it does this:

#1

Hit any key to stop autoboot: 0
bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
## Error: "odmbootusb" not defined

NAND read: device 0 offset 0x7000000, size 0x400000
4194304 bytes read: OK

NAND read: device 0 offset 0x7400000, size 0xb00000
11534336 bytes read: OK
## Booting kernel from Legacy Image at 08000000 ...
Image Name: Linux-3.10.20-al-2.5.2
Created: 2014-11-17 23:30:27 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2978744 Bytes = 2.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 08800000 ...
Image Name:
Created: 2015-01-12 8:29:10 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 10039368 Bytes = 9.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
** Using primary FDT on legacy kernel
## Flattened Device Tree blob at 01b25008
Booting using the fdt blob at 0x1b25008
Loading Kernel Image ... OK
Loading Ramdisk to 01190000, end 01b23048 ... OK
Using Device Tree in place at 01b25008, end 01b2c1b4
ft_board_setup_clock: unable to set /soc/arch-timer.clock-frequency!

If I interupt the boot process I get this:

#2

Hit any key to stop autoboot: 0  0
ALPINE_DB> printenv odmbootseq
odmbootseq=run odmbootargs; run odmbootusb; run odmbootfirmware; failure;
ALPINE_DB> run odmbootseq
bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
(Re)start USB...
USB0: Register 8000450 NbrPorts 8
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **

NAND read: device 0 offset 0x200000, size 0x600000
6291456 bytes read: OK

NAND read: device 0 offset 0x800000, size 0x400000
4194304 bytes read: OK
gpio: pin 33 (gpio 33) value is 1
## Booting kernel from Legacy Image at 08000000 ...
Image Name: Linux-4.4.184.alpine.1
Created: 2019-09-05 2:32:26 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3437376 Bytes = 3.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 08800000 ...
Image Name: initramfs
Created: 2019-09-18 3:20:11 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 3423536 Bytes = 3.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 07000000
Booting using the fdt blob at 0x7000000
Loading Kernel Image ... OK
reserving fdt memory region: addr=0 size=100000
Loading Ramdisk to 017df000, end 01b22d30 ... OK
Using Device Tree in place at 07000000, end 07008bd3

Starting kernel ...

So, if I do 'run odmbootseq' the RN204 comes up and seems normal. I can access it over the local network.

I have tried setting environment variable 'odmbootseq' removing 'run odmbootusb', saving environment and rebooting.

ALPINE_DB> printenv odmbootseq
odmbootseq=run odmbootargs; run odmbootusb; run odmbootfirmware; failure;

ALPINE_DB> printenv odmbootseq
odmbootseq=run odmbootargs; run odmbootfirmware; failure;

Still getting the first (#1) report. It would seem the 'odmbootfirmware' is booting from factory load(?) when boot is not interupted.

Confused, why if interrupting boot and issuing 'run odmbootseq' it works fine. Seem it is running that normally, just getting '## Error: "odmbootusb" not defined' when boot not interrupted, and dont get that when u-boot interrupted and manually 'run odmbootseq'. Doesn't seem to make sense.

Thanks in advance, any help would be appreciated.

Mike