Welcome! Log In Create A New Profile

Advanced

RN204 U-Boot boot issue

Posted by 1oldmike 
Forum List Message List New Topic
1oldmike
RN204 U-Boot boot issue
October 29, 2019 08:37PM
Preface, I am a newbie and am looking for some help with U-Boot. I have a little knowledge of programming. I know the ‘environment variables’ are just global constants that the program ‘U-Boot’ uses to process conditions. I have been reading on http://www.denx.de/ and a few other websites. One site https://www.linuxjournal.com/content/handy-u-boot-trick shows block diagram ‘x-loader – u-boot.bin – interruption – u-boot shell --or-- no interruption – execute bootcmd.
I have a Netgear NAS that does not boot correctly. I know the hardware is fine.
Here is the issue - with usb-serial attachment I am able to connect. If I interrupt the boot process and from the U-Boot command line and I type in ‘boot’, the unit comes up normally and I can access it. If I don’t interrupt the boot it goes into another state and I cannot access.
My question is what is U-Boot doing? What is it setting NAS up for? I have looked at some environment prints from a Buffalo NAS (which usually boots from the 1st harddrive) and compared it to my environment variables to see the differences. Not sure how U-Boot is handling things. I know U-Boot is basically bootstrap software to load up operating systems. If you need full environment printout I can supply.

U-Boot 2013.10-alpine_db-1.49 (Dec 21 2017 - 13:28:18)

Here is excerpts from my environment: 

bootcmd=run odmbootseq;
odmbootseq=run odmbootargs; run odmbootusb; run odmbootfirmware; failure;
odmbootargs=setenv bootargs pci=pcie_bus_perf console=ttyS0,115200 $reasonargs $bootargsextra ; printenv bootargs
reasonargs=reason=normal
bootargsextra=bdtype=rn204
odmbootusb=usb start;fatload usb 0 $loadaddr NTGR_USBBOOT_INFO.txt;if test $? -eq 0; then run odmbootbackusb;fi;
loadaddr=0x08000000
loadaddr_dt=0x07000000
loadaddr_fs=0x8800000
loadaddr_payload=0x08000004
loadaddr_rootfs_chk=0x07000000
nand_pt_addr_al_boot=0x0
nand_pt_addr_fs=0x01000000
nand_pt_addr_kernel=0x00400000
nand_pt_addr_kernel_1=0x00400000
nand_pt_addr_kernel_2=0x00a00000
nand_pt_desc_kernel_1=Test kernel A
nand_pt_desc_kernel_2=Test kernel B
nand_pt_size_al_boot=0x00100000
nand_pt_size_fs=0x3f000000
nand_pt_size_kernel=0x00c00000
odmbootbackusb=usb start;lcd_print "Loading..."; fatload usb 0 $loadaddr uImage-recovery;if test $? -eq 0; then fatload usb 0 $loadaddr_fs initrd-recovery.gz;if test $? -eq 0; then flash_contents_obj_read DT 0 $loadaddr_dt;run odmboot;else;lcd_print "Failed!";failure;fi;else;lcd_print "Failed!";failure;fi;
odmboot=lcd_print "Booting..."; gpio set 33;bootm $loadaddr $loadaddr_fs $loadaddr_dt;
test=echo this is a test!


This is from 'ALPINE_DB> fdt print'.
( Per Netgear for 'usb recovery' put usb drive in and press and hold the backup button and power on, and it 'should' load from the usb. Not sure if the backup button is 'gpio33'.) 

if_gpio33 {
	id = "if_gpio";
	arg = <0x00000021>;
};
button@3 {
	label = "Backup Button";
	linux,code = <0x00000085>;
	gpios = <0x00000009 0x00000000 0x00000001>;
};


If I do not interrupt boot process this is some of what comes on console: 

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!

Starting kernel ...


If I interrupt the boot process and type in boot at command line, this is what I get: 

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 ...


Also, I noticed in the environment these line: 

bootext4=lcd_print "Booting...";scsi init; ext4load scsi ${ext4dev}:${ext4part} $loadaddr ${ext4dir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr_dt $loadaddr;if test $? -ne 0; then run fail; exit; fi;fi;ext4load scsi ${ext4dev}:${ext4part} $loadaddr ${ext4dir}uImage;if test $? -ne 0; then run fail; exit; fi;fdt addr $loadaddr_dt;bootm $loadaddr - $fdtaddr;run fail; exit
bootnand=lcd_print "Booting...";nand set_partition_offset $nand_pt_addr_kernel;nand read $loadaddr $nand_pt_addr_kernel 4;setenvmem filesize $loadaddr;incenv filesize 4;nand read $loadaddr $nand_pt_addr_kernel $filesize;nand set_partition_offset $nand_pt_addr_al_boot;bootm $loadaddr_payload - $fdtaddr;lcd_print Failed!;failue;
bootnandmulti=run kernel_select;if test $kernel_selected -ne 0; then run bootnand; fi
boottftp=lcd_print "Booting...";tftpboot $loadaddr ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr_dt $loadaddr;if test $? -ne 0; then run fail; exit; fi;fi;tftpboot $loadaddr ${tftpdir}uImage;if test $? -ne 0; then run fail; exit; fi;fdt addr $loadaddr_dt;bootm $loadaddr - $fdtaddr;run fail; exit
bootupd=is_nand_boot; if test $? -eq 0; then run bootupdspi; else; run bootupdnand; fi
bootupdnand=lcd_print "Updating al-boot" "to NAND"; tftpboot $loadaddr_dt ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;tftpboot $loadaddr ${tftpdir}boot.img; if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_al_boot;nand erase.spread $nand_pt_addr_al_boot $filesize; nand write $loadaddr $nand_pt_addr_al_boot $filesize; nand erase.spread ${dt_location} 10000; nand write ${loadaddr_dt} ${dt_location} 10000; lcd_print "Done"
bootupdnandy=lcd_print "Updating al-boot" "to NAND"; echo >> Use YModem to upload the device tree binary...;loady $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;echo >> Use YModem to upload the boot image binary...;loady $loadaddr;if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_al_boot;nand erase.spread $nand_pt_addr_al_boot $filesize; nand write $loadaddr $nand_pt_addr_al_boot $filesize; nand erase.spread ${dt_location} 10000; nand write ${loadaddr_dt} ${dt_location} 10000;lcd_print "Done"
bootupdspi=lcd_print "Updating al-boot" "to SPI"; tftpboot $loadaddr_dt ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;setenv filesize_dt $filesize;tftpboot ${loadaddr} ${tftpdir}boot.img; if test $? -ne 0; then run fail; exit; fi;sf probe; sf erase 0 +${filesize}; sf write ${loadaddr} 0 ${filesize}; sf erase ${dt_location} +${filesize_dt}; sf write ${loadaddr_dt} ${dt_location} ${filesize_dt}; echo bootupd done;echo Notice: Changes in default environment variables will only take effect once the;echo environment variables are deleted from flash using the 'delenv' script;lcd_print "Done"
bootupdspiy=lcd_print "Updating al-boot" "to SPI"; echo >> Use YModem to upload the device tree binary...;loady $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;setenv filesize_dt $filesize;echo >> Use YModem to upload the boot image binary...;loady ${loadaddr};if test $? -ne 0; then run fail; exit; fi;sf probe; sf erase 0 +${filesize}; sf write ${loadaddr} 0 ${filesize}; sf erase ${dt_location} +${filesize_dt}; sf write ${loadaddr_dt} ${dt_location} ${filesize_dt};echo bootupd done;echo Notice: Changes in default environment variables will only take effect once the;echo environment variables are deleted from flash using the 'delenv' script;lcd_print "Done"
bootupdy=is_nand_boot; if test $? -eq 0; then run bootupdspiy;else; run bootupdnandy; fi
rootargshd=setenv rootargs root=${hdroot} rw
rootargsnand=setenv rootargs root=ubi0:root rootfstype=ubifs ubi.mtd=3
rootargsnfs=setenv rootargs root=/dev/nfs rw nfsroot=${serverip}:${nfsrootdir},tcp,nolock rw ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${board_name}:eth1:none
rootfsupd=lcd_print "Updating rootfs...";tftpboot $loadaddr_rootfs_chk ${tftpdir}rootfs.ubi.md5;if test $? -ne 0; then run fail; exit; fi;tftpboot $loadaddr ${tftpdir}rootfs.ubi;if test $? -ne 0; then run fail; exit; fi;md5sum -v $loadaddr $filesize *$loadaddr_rootfs_chk;if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_fs;nand erase.spread $nand_pt_addr_fs $nand_pt_size_fs;nand write $loadaddr $nand_pt_addr_fs $filesize;nand set_partition_offset $nand_pt_addr_al_boot;echo rootfsupd done;lcd_print "Done"


2nd question - how do the root and bootup and a few other statements come into play? What calls these variables?
3rd question – ‘odmbootseq=run odmbootargs; run odmbootusb; run odmbootfirmware; failure;’ what does ‘failure’ do in u-boot? I cannot find that in command listings, or anywhere on the web.

Thanks in advance.
Mike

=========
moderator edit: please use code tags to post logs and commands



Edited 1 time(s). Last edit at 10/29/2019 09:28PM by bodhi.
Reply Quote
bodhi
Re: RN204 U-Boot boot issue
October 29, 2019 09:59PM
Mike,

> If I do not interrupt boot process this is some of
> what comes on console:
>
Quote

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

The error said right there "odmbootusb" not defined. So it falls back and boot the kernel from NAND. 

bootcmd=run odmbootseq;
odmbootseq=run odmbootargs; run odmbootusb; run odmbootfirmware; failure;
odmbootusb=usb start;fatload usb 0 $loadaddr NTGR_USBBOOT_INFO.txt;if test $? -eq 0; then run odmbootbackusb;fi;

When you let it boot automatically, u-boot finds the definition of the bootcmd and execute it. It executed the envs in the script like macros. And somehow the odmbootusb was defined but not found.

Possible explanations:

This is a customed u-boot: 
U-Boot 2013.10-alpine_db-1.49 (Dec 21 2017 - 13:28:18)

So the bootcmd could have been redefined each time inside the code, it might do something extra you cannot see.

The fact that if you do a run expelicitly with "run odmbootseq", it woud work. Then it told me that the bootcmd is different from "bootcmd=run odmbootseq" when the box u-boot executed it.

You need to post the entire serial bootlog here so I can see the whole picture. Excerpted serial boot log is not good information, it is incomplete.

> 3rd question – ‘odmbootseq=run odmbootargs;
> run odmbootusb; run odmbootfirmware; failure;’
> what does ‘failure’ do in u-boot?

That failure command is a specific command that was added in this customed u-boot. There is no such command in u-boot mainline. So you need to have the GPL source for this box to know what it does.

Please post the entire serial bootlog of each case, and use code tags to make it readable.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
1oldmike
Re: RN204 U-Boot boot issue
October 30, 2019 09:05AM
Here is the entire serial boot -uninterrupted- 

Annapurna Labs
Board: Alpine Development Board
I2C:   ready
DRAM:  2 GiB
eeprom_per_device_init: no valid information found!
power_init_board: EEPROM per device information is not valid - using defaults!
Board config ID: Netgear NAS RN20x
dt_based_init: ETH params initialization failed!
ac_adapter_plug_in = 0
NAND:  128 MiB
  00:01.0     - 1c36:0001 - Network controller
  00:03.0     - 1c36:0001 - Network controller
  00:04.0     - 1c36:0011 - Cryptographic device
  00:05.0     - 1c36:0021 - Base system peripheral
  00:09.0     - 1c36:0031 - Mass storage controller
PCIE_0: Link up. Speed 5GT/s Width x1
  01:00.0     - 1b21:0612 - Mass storage controller
PCIE_1: Link up. Speed 5GT/s Width x1
  02:00.0     - 1b6f:7052 - Serial bus controller
In:    serial
Out:   serial
Err:   serial
Net:   , al_eth1 [PRIME], al_eth3
mn=00, hr=00, dt=01
Power On!
SERDES 2, p4, pma, reg[13][4:4] <= 0x00
SERDES 2, p4, pma, reg[15][2:0] <= 0x02
Found 4 Disks!
Delay 7s then power on another group of HDDs     7  6  5  4  3  2  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!

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 3.10.20-al-2.5.2 (dave.hu@dnis05) (gcc version 4.7.3 (Buildroot 2014.05-git-01051-gc6e87cd-dirty) ) #1 SMP Tue Nov 18 07:30:17 CST 2014
CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine: AnnapurnaLabs Alpine (Device Tree), model: NETGEAR ReadyNAS 20x
Memory policy: ECC disabled, Data cache writealloc
PERCPU: Embedded 9 pages/cpu @c2b3f000 s12992 r8192 d15680 u36864
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 522768
Kernel command line: pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 2048MB = 2048MB total
Memory: 2061100k/2061100k available, 36052k reserved, 1318912K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc079bf80   (7760 kB)
      .init : 0xc079c000 - 0xc07de2c0   ( 265 kB)
      .data : 0xc07e0000 - 0xc08347a8   ( 338 kB)
       .bss : 0xc08347a8 - 0xc089a550   ( 408 kB)
Hierarchical RCU implementation.
NR_IRQS:16 nr_irqs:16 16
sched_clock: 32 bits at 375MHz, resolution 2ns, wraps every 11453ms
Console: colour dummy device 80x30
Calibrating delay loop... 2793.47 BogoMIPS (lpj=13967360)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
/cpus/cpu@0 missing clock-frequency property
/cpus/cpu@1 missing clock-frequency property
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0xc059e8b0 - 0xc059e908
CPU1: Booted secondary processor
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
CPU2: failed to boot: -38
CPU3: failed to boot: -38
Brought up 2 CPUs
SMP: Total of 2 processors activated (5586.94 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
xor: measuring software checksum speed
   arm4regs  :  3088.000 MB/sec
   8regs     :  2440.000 MB/sec
   32regs    :  2300.000 MB/sec
xor: using function: arm4regs (3088.000 MB/sec)
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
Initializing System Fabric
Enabling IO Cache Coherency.
hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 8 bytes.
Serial: AMBA PL011 UART driver
bio: create slab <bio-0> at 0
raid6: int32x1    324 MB/s
raid6: int32x2    439 MB/s
raid6: int32x4    408 MB/s
raid6: int32x8    362 MB/s
raid6: using algorithm int32x2 (439 MB/s)
raid6: using intx1 recovery algorithm
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new interface driver ethub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Switching to clocksource arm,sp804
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 9804K (c1190000 - c1b23000)
hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available
al-pcie pcie-internal.2: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [mem 0xfe000000-0xfeffffff]
pci_bus 0000:00: root bus resource [bus 00]
pci_bus 0000:00: root bus resource [io  0x1000-0xffff]
pci 0000:00:01.0: PCI-E Max Payload Size set to  128/ 256 (was  128), Max Read Rq  128
pci 0000:00:03.0: PCI-E Max Payload Size set to  128/ 256 (was  128), Max Read Rq  128
pci 0000:00:04.0: PCI-E Max Payload Size set to  128/ 256 (was  128), Max Read Rq  128
pci 0000:00:05.0: PCI-E Max Payload Size set to  128/ 256 (was  128), Max Read Rq  128
pci 0000:00:09.0: PCI-E Max Payload Size set to  128/ 256 (was  128), Max Read Rq  128
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:01.0: BAR 0: assigned [mem 0xfe000000-0xfe01ffff 64bit]
pci 0000:00:03.0: BAR 0: assigned [mem 0xfe020000-0xfe03ffff 64bit]
pci 0000:00:04.0: BAR 0: assigned [mem 0xfe040000-0xfe05ffff 64bit]
pci 0000:00:04.0: BAR 7: assigned [mem 0xfe060000-0xfe07ffff 64bit]
pci 0000:00:05.0: BAR 0: assigned [mem 0xfe080000-0xfe09ffff 64bit]
pci 0000:00:05.0: BAR 7: assigned [mem 0xfe0a0000-0xfe0bffff 64bit]
pci 0000:00:01.0: BAR 4: assigned [mem 0xfe0c0000-0xfe0c3fff 64bit]
pci 0000:00:03.0: BAR 4: assigned [mem 0xfe0c4000-0xfe0c7fff 64bit]
pci 0000:00:09.0: BAR 5: assigned [mem 0xfe0c8000-0xfe0cbfff]
pci 0000:00:04.0: BAR 4: assigned [mem 0xfe0cc000-0xfe0cdfff 64bit]
pci 0000:00:05.0: BAR 4: assigned [mem 0xfe0ce000-0xfe0cffff 64bit]
pci 0000:00:01.0: BAR 2: assigned [mem 0xfe0d0000-0xfe0d0fff 64bit]
pci 0000:00:03.0: BAR 2: assigned [mem 0xfe0d1000-0xfe0d1fff 64bit]
PCIe 1: Link up. speed gen2 negotiated width 1
al-pcie fd800000.pcie-external0: link up: speed Gen 2 width x1
Configuring PCIE for IOCC
PCIE_1: snoop mode enable
al-pcie fd800000.pcie-external0: PCI host bridge to bus 0001:00
pci_bus 0001:00: root bus resource [io  0x10000-0x1ffff]
pci_bus 0001:00: root bus resource [mem 0xe0010000-0xe7ffffff]
pci_bus 0001:00: root bus resource [bus 00-ff]
pci 0001:00:00.0: PCI-E Max Payload Size set to  256/ 256 (was  256), Max Read Rq  256
PCI: bus0: Fast back to back transfers disabled
pci 0001:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0001:01:00.0: PCI-E Max Payload Size set to  256/ 512 (was  128), Max Read Rq  256
PCI: bus1: Fast back to back transfers disabled
pci 0001:00:00.0: BAR 14: assigned [mem 0xe0100000-0xe01fffff]
pci 0001:00:00.0: BAR 15: assigned [mem 0xe0200000-0xe02fffff pref]
pci 0001:00:00.0: BAR 0: assigned [mem 0xe0010000-0xe0010fff]
pci 0001:00:00.0: BAR 1: assigned [mem 0xe0011000-0xe0011fff pref]
pci 0001:00:00.0: BAR 13: assigned [io  0x10000-0x10fff]
pci 0001:01:00.0: BAR 6: assigned [mem 0xe0200000-0xe020ffff pref]
pci 0001:01:00.0: BAR 5: assigned [mem 0xe0100000-0xe01001ff]
pci 0001:01:00.0: BAR 4: assigned [io  0x10000-0x1001f]
pci 0001:01:00.0: BAR 0: assigned [io  0x10020-0x10027]
pci 0001:01:00.0: BAR 2: assigned [io  0x10028-0x1002f]
pci 0001:01:00.0: BAR 1: assigned [io  0x10030-0x10033]
pci 0001:01:00.0: BAR 3: assigned [io  0x10034-0x10037]
pci 0001:00:00.0: PCI bridge to [bus 01]
pci 0001:00:00.0:   bridge window [io  0x10000-0x10fff]
pci 0001:00:00.0:   bridge window [mem 0xe0100000-0xe01fffff]
pci 0001:00:00.0:   bridge window [mem 0xe0200000-0xe02fffff pref]
PCIe 2: Link up. speed gen2 negotiated width 1
al-pcie fd820000.pcie-external1: link up: speed Gen 2 width x1
Configuring PCIE for IOCC
PCIE_2: snoop mode enable
al-pcie fd820000.pcie-external1: PCI host bridge to bus 0002:00
pci_bus 0002:00: root bus resource [io  0x20000-0x2ffff]
pci_bus 0002:00: root bus resource [mem 0xe8010000-0xebffffff]
pci_bus 0002:00: root bus resource [bus 00-ff]
pci 0002:00:00.0: PCI-E Max Payload Size set to  256/ 256 (was  256), Max Read Rq  256
PCI: bus0: Fast back to back transfers disabled
pci 0002:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0002:01:00.0: PCI-E Max Payload Size set to  256/1024 (was  128), Max Read Rq  256
PCI: bus1: Fast back to back transfers disabled
PCI: enabling device 0002:01:00.0 (0140 -> 0142)
pci 0002:01:00.0: xHCI controller failing to respond
pci 0002:00:00.0: BAR 14: assigned [mem 0xe8100000-0xe81fffff]
pci 0002:00:00.0: BAR 0: assigned [mem 0xe8010000-0xe8010fff]
pci 0002:00:00.0: BAR 1: assigned [mem 0xe8011000-0xe8011fff pref]
pci 0002:01:00.0: BAR 0: assigned [mem 0xe8100000-0xe8107fff 64bit]
pci 0002:00:00.0: PCI bridge to [bus 01]
pci 0002:00:00.0:   bridge window [mem 0xe8100000-0xe81fffff]
bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
SGI XFS with security attributes, large block/inode numbers, no debug enabled
bio: create slab <bio-1> at 1
Btrfs loaded
msgmni has been set to 1468
alg: No test for stdrng (krng)
async_tx: api initialized (async)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
al_dma: Annapurna Labs DMA Driver 0.01
PCI: enabling device 0000:00:05.0 (0000 -> 0002)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
fd883000.uart0: ttyS0 at MMIO 0xfd883000 (irq = 49) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
PCI: enabling device 0000:00:09.0 (0000 -> 0002)
ahci 0000:00:09.0: use MSIX for ahci controller. vectors: 4
ahci 0000:00:09.0: controller can't do PMP, turning off CAP_PMP
ahci 0000:00:09.0: forcing PORTS_IMPL to 0xf
ahci 0000:00:09.0: AHCI 0001.0300 32 slots 4 ports 6 Gbps 0xf impl SATA mode
ahci 0000:00:09.0: flags: 64bit ncq sntf pm led clo only fbs pio slum part ccc apst 
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m16384@0xfe0c8000 port 0xfe0c8100 irq 132
ata2: SATA max UDMA/133 abar m16384@0xfe0c8000 port 0xfe0c8180 irq 133
ata3: SATA max UDMA/133 abar m16384@0xfe0c8000 port 0xfe0c8200 irq 134
ata4: SATA max UDMA/133 abar m16384@0xfe0c8000 port 0xfe0c8280 irq 135
ahci: probe of 0001:00:00.0 failed with error -22
PCI: enabling device 0001:01:00.0 (0140 -> 0143)
ahci: SSS flag set, parallel bus scan disabled
ahci 0001:01:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
ahci 0001:01:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs 
scsi4 : ahci
scsi5 : ahci
ata5: SATA max UDMA/133 abar m512@0xe0100000 port 0xe0100100 irq 136
ata6: SATA max UDMA/133 abar m512@0xe0100000 port 0xe0100180 irq 136
ahci: probe of 0002:00:00.0 failed with error -22
al_nand_probe: AnnapurnaLabs nand driver
ONFI param page 0 valid
ONFI flash detected
NAND device: Manufacturer ID: 0x01, Chip ID: 0xa1 (AMD/Spansion S34MS01G2), 128MiB, page size: 2048, OOB size: 64
Scanning device for bad blocks
9 ofpart partitions found on MTD device Alpine nand flash
Creating 9 MTD partitions on "Alpine nand flash":
0x000000000000-0x0000001c0000 : "u-boot"
0x0000001c0000-0x000000200000 : "u-boot-env"
0x000000200000-0x000000800000 : "uImage"
0x000000800000-0x000000c00000 : "minirootfs"
0x000000c00000-0x000007000000 : "ubifs"
0x000000080000-0x0000000a0000 : "dts"
0x000007000000-0x000008000000 : "factory-diag"
0x000000000000-0x0000001c0000 : "al_uboot"
0x000000000000-0x000008000000 : "flash"
al_eth_drv: AnnapurnaLabs unified 1GbE and 10GbE Ethernet Driver al_eth v0.2 (Feb 18, 2013)
al_eth 0000:00:01.0: Board info: phy exist Yes. phy addr 4. mdio freq 1000 Khz. SFP connected No. media 1
al_eth 0000:00:01.0 eth0: AnnapurnaLabs unified 1Gbe/10Gbe found at mem fe000000, mac addr a0:63:91:65:58:14
al_eth 0000:00:03.0: Board info: phy exist Yes. phy addr 5. mdio freq 1000 Khz. SFP connected No. media 1
al_eth 0000:00:03.0 eth1: AnnapurnaLabs unified 1Gbe/10Gbe found at mem fe020000, mac addr a0:63:91:65:58:15
etxhci_hcd-140409 0002:01:00.0: Etron xHCI Host Controller
etxhci_hcd-140409 0002:01:00.0: new USB bus registered, assigned bus number 1
ethub 1-0:1.0: USB hub found
ethub 1-0:1.0: 4 ports detected
etxhci_hcd-140409 0002:01:00.0: Etron xHCI Host Controller
etxhci_hcd-140409 0002:01:00.0: new USB bus registered, assigned bus number 2
ethub 2-0:1.0: USB hub found
ethub 2-0:1.0: 4 ports detected
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
rtc-ds1307 0-0068: rtc core: registered ds1337 as rtc0
rtc-ds1307 0-0068: 3 bytes nvram
i2c /dev entries driver
ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata4.00: ATA-8: WL2000GSA6472E, B7.Z2E.8, max UDMA/133
ata4.00: 3907029168 sectors, multi 0: LBA48 
ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata3.00: ATA-8: WL2000GSA6472E, 01.01KA2, max UDMA/133
ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
ata4.00: configured for UDMA/133
al_thermal_probe: Thermal Sensor Loaded at: 0xf218aa00.
ata5: SATA link down (SStatus 0 SControl 300)
sp805-wdt fd88c000.wdt0: registration successful
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
md: faulty personality registered for level -5
ata2.00: ATA-8: WL2000GSA6472E, 01.01KA2, max UDMA/133
ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com
ata3.00: configured for UDMA/133
ata2.00: configured for UDMA/133
al_mc_edac fb080000.mc: No ECC present, or ECC disabled
cpuidle: using governor ladder
cpuidle: using governor menu
ledtrig-cpu: registered to indicate activity on CPUs
al_crypto: Annapurna Labs Crypto Driver 0.01
ata1.00: ATA-8: WL2000GSA6472E, WD07, max UDMA/133
ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WL2000GSA6472E   WD07 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
scsi 1:0:0:0: Direct-Access     ATA      WL2000GSA6472E   01.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] Write Protect is off
scsi 2:0:0:0: Direct-Access     ATA      WL2000GSA6472E   01.0 PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
scsi 3:0:0:0: Direct-Access     ATA      WL2000GSA6472E   B7.Z PQ: 0 ANSI: 5
 sdb: sdb1 sdb2 sdb3
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 3:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
PCI: enabling device 0000:00:04.0 (0000 -> 0002)
 sdc: sdc1 sdc2 sdc3
sd 2:0:0:0: [sdc] Attached SCSI disk
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
 sdd: sdd1 sdd2 sdd3
sd 3:0:0:0: [sdd] Attached SCSI disk
pci 0000:00:04.1: PCI-E Max Payload Size set to  128/ 128 (was  128), Max Read Rq  128
PCI: enabling device 0000:00:04.1 (0400 -> 0402)
al_crypto 0000:00:04.1: al_crypto_pci_probe: Skipping alg/hash initialization, no allocated channels
al_crypto 0000:00:04.1: crc/csum algorithms registered in /proc/crypto
al_crypto 0000:00:04.0: algorithms registered in /proc/crypto
al_crypto 0000:00:04.0: hash algorithms registered in /proc/crypto
al_crypto 0000:00:04.0: al_crypto_pci_probe: Skipping crc initialization, no allocated channels
TCP: cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
Registering SWP/SWPB emulation handler
Key type encrypted registered
rtc-ds1307 0-0068: setting system clock to 2019-10-23 17:38:49 UTC (1571852329)
ata6: SATA link down (SStatus 0 SControl 300)
Freeing unused kernel memory: 264K (c079c000 - c07de000)

Starting Auto-Init-tools ...
Press ctrl+c to cancel the auto-init...(1s)
Starting logging: OK
[WARNNING] Not found partion!
env: can't execute 'get': No such file or directory
[WARNNING] No Mac address is defined, Use dconfigured MAC to RGMII mode:
efault Mac addreal_eth 0000:00:01.0 eth0: using MSI-X per Queue interrupt mode
ss!
env: can't execute 'add': Nlibphy: al mdio bus: probed
o such file or dal_eth 0000:00:01.0 eth0: phy[4]: device 8:04, driver Atheros 8035 ethernet
irectory
al_eth 0000:00:01.0 eth0: phy[4]:supported 2ef adv 2ef
configured MAC to RGMII mode:
al_eth 0000:00:03.0 eth1: using MSI-X per Queue interrupt mode
libphy: al mdio bus: probed
al_eth 0000:00:03.0 eth1: phy[5]: device 18:05, driver Atheros 8035 ethernet
al_eth 0000:00:03.0 eth1: phy[5]:supported 2ef adv 2ef
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
sh: write error: Device or resource busy
sh: write error: Device or resource busy
mount: mounting /dev/sda1 on /disks/sda1 failed: Invalid argument
mount: mounting /dev/sda2 on /disks/sda2 failed: Invalid argument
mount: mounting /dev/sda3 on /disks/sda3 failed: Invalid argument
mount: mounting /dev/sdb1 on /disks/sdb1 failed: Invalid argument
mount: mounting /dev/sdb2 on /disks/sdb2 failed: Invalid argument
mount: mounting /dev/sdb3 on /disks/sdb3 failed: Invalid argument
mount: mounting /dev/sdc1 on /disks/sdc1 failed: Invalid argument
mount: mounting /dev/sdc2 on /disks/sdc2 failed: Invalid argument
mount: mounting /dev/sdc3 on /disks/sdc3 failed: Invalid argument
mount: mounting /dev/sdd1 on /disks/sdd1 failed: Invalid argument
mount: mounting /dev/sdd2 on /disks/sdd2 failed: Invalid argument
mount: mounting /dev/sdd3 on /disks/sdd3 failed: Invalid argument
Initializing random number generator... done.
Starting system message bus: done
Starting SMB services: done
Starting NMB services: done


Welcome to NAS


Here is the entire boot -interrupted- with 'run odmbootseq' issued which should be the same as uninterrupted. 

Annapurna Labs
Board: Alpine Development Board
I2C:   ready
DRAM:  2 GiB
eeprom_per_device_init: no valid information found!
power_init_board: EEPROM per device information is not valid - using defaults!
Board config ID: Netgear NAS RN20x
dt_based_init: ETH params initialization failed!
ac_adapter_plug_in = 0
NAND:  128 MiB
  00:01.0     - 1c36:0001 - Network controller
  00:03.0     - 1c36:0001 - Network controller
  00:04.0     - 1c36:0011 - Cryptographic device
  00:05.0     - 1c36:0021 - Base system peripheral
  00:09.0     - 1c36:0031 - Mass storage controller
PCIE_0: Link up. Speed 5GT/s Width x1
  01:00.0     - 1b21:0612 - Mass storage controller
PCIE_1: Link up. Speed 5GT/s Width x1
  02:00.0     - 1b6f:7052 - Serial bus controller
In:    serial
Out:   serial
Err:   serial
Net:   , al_eth1 [PRIME], al_eth3
mn=00, hr=00, dt=01
Power On!
SERDES 2, p4, pma, reg[13][4:4] <= 0x00
SERDES 2, p4, pma, reg[15][2:0] <= 0x02
Found 4 Disks!
Delay 7s then power on another group of HDDs     7  6  5  4  3  2  1
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 ...


Starting the boot process...
Detected system type: RN204
Loading kernel modules...done
Boot mode: Normal
UBI device number 0, total 800 LEBs (101580800 bytes, 96.9 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
Bringing up network...eth0.done
Bringing up RAID arrays...done
e2fsck 1.42.13 (17-May-2015)
11655814_root: clean, 18349/1048576 files, 307165/1047552 blocks
Switching root to RAID device.


Welcome to ReadyNASOS 6.10.2!

[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Created slice System Slice.
[  OK  ] Reached target Slices.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket.
[  OK  ] Started ReadyNAS LCD splasher.
         Starting ReadyNASOS system prep...
         Starting Journal Service...
         Starting Create Static Device Nodes in /dev...
         Mounting POSIX Message Queue File System...
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started ReadyNASOS system prep.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Remount Root and Kernel File Systems.
         Starting Load/Save Random Seed...
         Starting Rebuild Hardware Database...
         Mounting Configuration File System...
         Mounting FUSE Control File System...
         Starting Apply Kernel Variables...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted Configuration File System.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Journal Service.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started udev Kernel Device Manager.
         Starting MD arrays...
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Rebuild Hardware Database.
[  OK  ] Found device /dev/md1.
         Activating swap md1...
[  OK  ] Activated swap md1.
[  OK  ] Found device /dev/disk/by-label/11655814:data.
[  OK  ] Started MD arrays.
[  OK  ] Reached target Swap.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /data...
         Starting udev Coldplug all Devices...
[  OK  ] Mounted /data.
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting LSB: Add to mtab the entry for /dev....
         Mounting Home Directory...
         Mounting Apps Directory...
[  OK  ] Mounted Apps Directory.
[  OK  ] Mounted Home Directory.
[  OK  ] Started LSB: Add to mtab the entry for /dev..
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started udev Coldplug all Devices.
         Starting udev Wait for Complete Device Initialization...
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[  OK  ] Started udev Wait for Complete Device Initialization.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started Log Truncate Timer.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Started Timer for ReadyNAS Update Service.
[  OK  ] Reached target Timers.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
[  OK  ] Started MD repair service.
[  OK  ] Started RAIDar discovery service.
         Starting Login Service...
[  OK  ] Started MD monitoring service.
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started DLNA/UPnP-AV media server.
[  OK  ] Started Reset I2C.
[  OK  ] Started Service for sickchill app.
[  OK  ] Started Service for sickrage app.
[  OK  ] Started WSD/LLMNR Discovery/Name Service Daemon.
[  OK  ] Started D-Bus System Message Bus.
         Starting Connection service...
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started Login Service.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Connection service.
[  OK  ] Reached target Network.
         Starting The Apache HTTP Server...
         Starting Samba NMB Daemon...
         Starting TVMosaic...
         Starting Netatalk AFP fileserver for Macintosh clients...
         Starting Plex Media Server...
         Starting Permit User Sessions...
[  OK  ] Started Netatalk AFP fileserver for Macintosh clients.
[  OK  ] Started Permit User Sessions.
         Starting Hostname Service...
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Hostname Service.
[  OK  ] Started Plex Media Server.
[  OK  ] Started TVMosaic.
[  OK  ] Started The Apache HTTP Server.
[  OK  ] Started Samba NMB Daemon.
         Starting Samba SMB Daemon...


ReadyNASOS 6.10.2 MyNas ttyS0

MyNas login: admin


Here is the entire printenv 

ALPINE_DB>  printenv
Manufacturer=NETGEAR
Product=ReadyNAS 204
SKUNum=RN204
SerialNum=4602535200479
Startup=Normal
UUID=33186880-1dd2-11b2-9d4a-22ad13f82a45
Version=V1.1 
arch=arm
autoload=n
baudrate=115200
board=alpine_db
board_name=alpine_db
boot_instance_active=0
boot_instance_non_active=1
bootargsextra=bdtype=rn204
bootargshd=run rootargshd; setenv bootargs $rootargs pci=pcie_bus_perf console=ttyS0,115200 $bootargsextra; printenv bootargs
bootargsnand=run rootargsnand; setenv bootargs $rootargs pci=pcie_bus_perf console=ttyS0,115200 $bootargsextra; printenv bootargs
bootargsnfs=run rootargsnfs; setenv bootargs $rootargs pci=pcie_bus_perf console=ttyS0,115200 $bootargsextra; printenv bootargs
bootcmd=run odmbootseq;
bootdelay=3
bootext4=lcd_print "Booting...";scsi init; ext4load scsi ${ext4dev}:${ext4part} $loadaddr ${ext4dir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr_dt $loadaddr;if test $? -ne 0; then run fail; exit; fi;fi;ext4load scsi ${ext4dev}:${ext4part} $loadaddr ${ext4dir}uImage;if test $? -ne 0; then run fail; exit; fi;fdt addr $loadaddr_dt;bootm $loadaddr - $fdtaddr;run fail; exit
bootnand=lcd_print "Booting...";nand set_partition_offset $nand_pt_addr_kernel;nand read $loadaddr $nand_pt_addr_kernel 4;setenvmem filesize $loadaddr;incenv filesize 4;nand read $loadaddr $nand_pt_addr_kernel $filesize;nand set_partition_offset $nand_pt_addr_al_boot;bootm $loadaddr_payload - $fdtaddr;lcd_print Failed!;failue;
bootnandmulti=run kernel_select;if test $kernel_selected -ne 0; then run bootnand; fi
boottftp=lcd_print "Booting...";tftpboot $loadaddr ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr_dt $loadaddr;if test $? -ne 0; then run fail; exit; fi;fi;tftpboot $loadaddr ${tftpdir}uImage;if test $? -ne 0; then run fail; exit; fi;fdt addr $loadaddr_dt;bootm $loadaddr - $fdtaddr;run fail; exit
bootupd=is_nand_boot; if test $? -eq 0; then run bootupdspi; else; run bootupdnand; fi
bootupdnand=lcd_print "Updating al-boot" "to NAND"; tftpboot $loadaddr_dt ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;tftpboot $loadaddr ${tftpdir}boot.img; if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_al_boot;nand erase.spread $nand_pt_addr_al_boot $filesize; nand write $loadaddr $nand_pt_addr_al_boot $filesize; nand erase.spread ${dt_location} 10000; nand write ${loadaddr_dt} ${dt_location} 10000; lcd_print "Done"
bootupdnandy=lcd_print "Updating al-boot" "to NAND"; echo >> Use YModem to upload the device tree binary...;loady $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;echo >> Use YModem to upload the boot image binary...;loady $loadaddr;if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_al_boot;nand erase.spread $nand_pt_addr_al_boot $filesize; nand write $loadaddr $nand_pt_addr_al_boot $filesize; nand erase.spread ${dt_location} 10000; nand write ${loadaddr_dt} ${dt_location} 10000;lcd_print "Done"
bootupdspi=lcd_print "Updating al-boot" "to SPI"; tftpboot $loadaddr_dt ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;setenv filesize_dt $filesize;tftpboot ${loadaddr} ${tftpdir}boot.img; if test $? -ne 0; then run fail; exit; fi;sf probe; sf erase 0 +${filesize}; sf write ${loadaddr} 0 ${filesize}; sf erase ${dt_location} +${filesize_dt}; sf write ${loadaddr_dt} ${dt_location} ${filesize_dt}; echo bootupd done;echo Notice: Changes in default environment variables will only take effect once the;echo environment variables are deleted from flash using the 'delenv' script;lcd_print "Done"
bootupdspiy=lcd_print "Updating al-boot" "to SPI"; echo >> Use YModem to upload the device tree binary...;loady $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;setenv filesize_dt $filesize;echo >> Use YModem to upload the boot image binary...;loady ${loadaddr};if test $? -ne 0; then run fail; exit; fi;sf probe; sf erase 0 +${filesize}; sf write ${loadaddr} 0 ${filesize}; sf erase ${dt_location} +${filesize_dt}; sf write ${loadaddr_dt} ${dt_location} ${filesize_dt};echo bootupd done;echo Notice: Changes in default environment variables will only take effect once the;echo environment variables are deleted from flash using the 'delenv' script;lcd_print "Done"
bootupdy=is_nand_boot; if test $? -eq 0; then run bootupdspiy;else; run bootupdnandy; fi
build_date=01/08/2016 
cpu=armv7
cvos_tags=0x01000000
cvos_tags_seed_a=0x01000004
cvos_tags_seed_b=0x01000008
cvos_tags_validate=mw.l ${cvos_tags} 0xcf05cf05
delenv=is_nand_boot; if test $? -eq 0; then run delenvspi; else; run delenvnand; fi
delenvnand=lcd_print "Deleting env..."; nand erase ${env_offset} 2000; if test -n ${env_offset_redund}; then nand erase ${env_offset_redund} 2000; fi;lcd_print "Done"
delenvspi=lcd_print "Deleting env..."; sf probe; sf erase ${env_offset} +2000;if test -n ${env_offset_redund}; then sf erase ${env_offset_redund} +2000;fi;lcd_print "Done"
dt_filename=dt.img
dt_is_from_toc=1
dt_location=80000
dtupd=is_nand_boot; if test $? -eq 0; then run dtupdspi; else; run dtupdnand; fi
dtupdnand=lcd_print "Updating DT" "to NAND"; tftpboot $loadaddr_dt ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;nand set_partition_offset $nand_pt_addr_al_boot;nand erase.spread ${dt_location} 10000; nand write ${loadaddr_dt} ${dt_location} 10000; lcd_print "Done"
dtupdnandy=lcd_print "Updating DT" "to NAND"; echo >> Use YModem to upload the device tree binary...;loady $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;nand set_partition_offset $nand_pt_addr_al_boot;nand erase.spread ${dt_location} 10000; nand write ${loadaddr_dt} ${dt_location} 10000; lcd_print "Done"
dtupdspi=lcd_print "Updating DT" "to SPI"; tftpboot $loadaddr_dt ${tftpdir}${dt_filename};if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;sf probe; sf erase ${dt_location} +${filesize}; sf write ${loadaddr_dt} ${dt_location} ${filesize};echo dtupd done;lcd_print "Done"
dtupdspiy=lcd_print "Updating DT" "to SPI"; echo >> Use YModem to upload the device tree binary...;loady $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;if test ${dt_is_from_toc} != 1; then; else flash_contents_obj_read_mem $loadaddr $loadaddr_dt;if test $? -ne 0; then run fail; exit; fi;fi;sf probe; sf erase ${dt_location} +${filesize}; sf write ${loadaddr_dt} ${dt_location} ${filesize}; echo dtupd done;lcd_print "Done"
dtupdy=is_nand_boot; if test $? -eq 0; then run dtupdspiy; else; run dtupdnandy; fi
eepromupd=confirm_msg "Perform EEPROM update? [y/n] ";if test $? -ne 0; then exit; fi;tftpboot ${tftpdir}eeprom.bin;if test $? -ne 0; then exit; fi;i2c probe ${pld_i2c_addr};if test $? -ne 0; then exit; fi;i2c write $fileaddr ${pld_i2c_addr} 0.2 $filesize;if test $? -ne 0; then exit;fi;echo eepromupd done
eepromupdy=confirm_msg "Perform EEPROM update? [y/n] ";if test $? -ne 0; then exit; fi;echo >> Use YModem to upload the EEPROM binary...;loady $loadaddr;if test $? -ne 0; then exit; fi;i2c probe ${pld_i2c_addr};if test $? -ne 0; then exit; fi;i2c write $loadaddr ${pld_i2c_addr} 0.2 $filesize;if test $? -ne 0; then exit;fi;echo eepromupdy done
env_offset=1c0000
env_offset_redund=1e0000
eth1addr=A0:63:91:65:58:14
eth3addr=A0:63:91:65:58:15
ethact=al_eth1
ethprime=al_eth1
ext4dev=0
ext4dir=boot/
ext4part=1
factory_diag=1
fail=echo Failed!; lcd_print "Failed!"
fdt_high=0xffffffff
fdtaddr=1b3a008
fwupd=tftpboot ${tftpdir}uboot_script_fw_update.bin;source ${loadaddr}
hdroot=/dev/sda1
hwsetting_rn202=serdes rx_params_set 2 0  00 07 00 00 08 00 08 07 10;serdes rx_params_set 2 1  00 07 00 00 08 00 08 07 10;serdes rx_params_set 2 2  00 07 00 00 08 00 08 07 10;serdes rx_params_set 2 3  00 07 00 00 08 00 08 07 10;serdes tx_params_set 2 0 1 27 6 0 0;serdes tx_params_set 2 1 1 27 6 0 0;mw.l 0xfc8f821c 0x04000000;mw.l 0xfc9f821c 0x04000000;
hwsetting_rn204=serdes rx_params_set 2 0  00 07 00 00 08 00 08 07 4;serdes rx_params_set 2 1  00 07 00 00 08 00 08 07 4;serdes rx_params_set 2 2  00 07 00 00 08 00 08 07 4;serdes rx_params_set 2 3  00 07 00 00 08 00 08 07 4;serdes wr 2 p4 pma 13 4 4 0;serdes wr 2 p4 pma 15 2 0 2;serdes tx_params_set 2 0 1 23 4 0 0;serdes tx_params_set 2 1 1 23 4 0 0;serdes tx_params_set 2 2 1 23 4 0 0;serdes tx_params_set 2 3 1 23 4 0 0;mw.l 0xfc9f821c 0x4000000;
kernel_rename_1=editenv nand_pt_desc_kernel_1;saveenv
kernel_rename_2=editenv nand_pt_desc_kernel_2;saveenv
kernel_select=setenv kernel_selected 0;setenv bootmenu_0 ${nand_pt_desc_kernel_1}=run kernel_select_1;setenv bootmenu_1 ${nand_pt_desc_kernel_2}=run kernel_select_2;bootmenu
kernel_select_1=setenv nand_pt_addr_kernel ${nand_pt_addr_kernel_1};setenv kernel_selected 1
kernel_select_2=setenv nand_pt_desc_kernel ${nand_pt_desc_kernel_2};setenv nand_pt_addr_kernel ${nand_pt_addr_kernel_2};setenv nand_pt_desc_kernel_2 ${nand_pt_desc_kernel_1};setenv nand_pt_addr_kernel_2 ${nand_pt_addr_kernel_1};setenv nand_pt_desc_kernel_1 ${nand_pt_desc_kernel};setenv nand_pt_addr_kernel_1 ${nand_pt_addr_kernel};saveenv;setenv kernel_selected 2
kernelupd=lcd_print "Updating kernel...";tftpboot $loadaddr_payload ${tftpdir}uImage;if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_kernel;mw.l $loadaddr $filesize;incenv filesize 4;nand erase.spread $nand_pt_addr_kernel $filesize;nand write $loadaddr $nand_pt_addr_kernel $filesize;nand set_partition_offset $nand_pt_addr_al_boot;echo kernelupd done;lcd_print "Done"
loadaddr=0x08000000
loadaddr_dt=0x07000000
loadaddr_fs=0x8800000
loadaddr_payload=0x08000004
loadaddr_rootfs_chk=0x07000000
nand_pt_addr_al_boot=0x0
nand_pt_addr_fs=0x01000000
nand_pt_addr_kernel=0x00400000
nand_pt_addr_kernel_1=0x00400000
nand_pt_addr_kernel_2=0x00a00000
nand_pt_desc_kernel_1=Test kernel A
nand_pt_desc_kernel_2=Test kernel B
nand_pt_size_al_boot=0x00100000
nand_pt_size_fs=0x3f000000
nand_pt_size_kernel=0x00c00000
nfsrootdir=/srv/root/
odmboot=lcd_print "Booting..."; gpio set 33;bootm $loadaddr $loadaddr_fs $loadaddr_dt;
odmbootargs=setenv bootargs pci=pcie_bus_perf console=ttyS0,115200 $reasonargs $bootargsextra ; printenv bootargs
odmbootbackusb=usb start;lcd_print "Loading..."; fatload usb 0 $loadaddr uImage-recovery;if test $? -eq 0; then fatload usb 0 $loadaddr_fs initrd-recovery.gz;if test $? -eq 0; then flash_contents_obj_read DT 0 $loadaddr_dt;run odmboot;else;lcd_print "Failed!";failure;fi;else;lcd_print "Failed!";failure;fi;
odmbootfirmware=lcd_print "Loading..."; nand read $loadaddr    0x200000 0x600000 ;flash_contents_obj_read DT 0 $loadaddr_dt;nand read $loadaddr_fs 0x800000 0x400000;run odmboot;
odmbootseq=run odmbootargs; run odmbootusb; run odmbootfirmware; failure;
odmbootusb=usb start;fatload usb 0 $loadaddr NTGR_USBBOOT_INFO.txt;if test $? -eq 0; then run odmbootbackusb;fi;
pld_i2c_addr=50
reasonargs=reason=normal
rootargshd=setenv rootargs root=${hdroot} rw
rootargsnand=setenv rootargs root=ubi0:root rootfstype=ubifs ubi.mtd=3
rootargsnfs=setenv rootargs root=/dev/nfs rw nfsroot=${serverip}:${nfsrootdir},tcp,nolock rw ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${board_name}:eth1:none
rootfsupd=lcd_print "Updating rootfs...";tftpboot $loadaddr_rootfs_chk ${tftpdir}rootfs.ubi.md5;if test $? -ne 0; then run fail; exit; fi;tftpboot $loadaddr ${tftpdir}rootfs.ubi;if test $? -ne 0; then run fail; exit; fi;md5sum -v $loadaddr $filesize *$loadaddr_rootfs_chk;if test $? -ne 0; then run fail; exit; fi;nand set_partition_offset $nand_pt_addr_fs;nand erase.spread $nand_pt_addr_fs $nand_pt_size_fs;nand write $loadaddr $nand_pt_addr_fs $filesize;nand set_partition_offset $nand_pt_addr_al_boot;echo rootfsupd done;lcd_print "Done"
skip_eth_halt=0
soc=alpine
test=echo this is a test!
vendor=annapurna-labs

Environment size: 12976/16379 bytes


I aggree 'failure' seems wrong, but I could not find it defined anywhere in the environmnet variables listing or maybe I missed.

Thank you for the very fast help. Much appreciate it.
Mike

===========

Moderator edit: please use code tags (formatted code) to post logs. That's the icon at the top (last one on the right) while you are editing the post (the left most icon is B, for bold text). Select the entire block of text and click the "formatted code" icon.



Edited 1 time(s). Last edit at 10/30/2019 10:30PM by bodhi.
Reply Quote
bodhi
Re: RN204 U-Boot boot issue
October 30, 2019 10:37PM
Quote

I aggree 'failure' seems wrong, but I could not find it defined anywhere in the environmnet variables listing or maybe I missed.

No it's not wrong by any means. As I said, this customed u-boot has this command patched in by Netgear. And it is not an enviroment variable.

At this point, as to not make thing worse, I would not further advise you to try something that potentially could mess it up (if it were my box, I would try something more adventurous).

The best next step is to find the GPL source for this box from Netgear. And then I can help looking at that source code to figure out why the bootcmd in NAND was not used,

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
1oldmike
Re: RN204 U-Boot boot issue
October 31, 2019 12:10AM
Got this from Netgear support site. https://kb.netgear.com/2649/NETGEAR-Open-Source-Code-for-Programmers-GPL

ReadyNAS OS 6 (ReadyNAS 202/204/212/214) 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.4.0, 6.4.1, 6.4.2, 6.5.0, 6.5.1, 6.5.2, 6.6.0, 6.7.0, 6.7.1, 6.7.2, 6.7.3, 6.7.4, 6.7.5, 6.8.0, 6.8.1, 6.9.0, 6.9.1, 6.9.2, 6.9.3, 6.9.4, 6.9.5, 6.10.0, 6.10.1, 6.10.2, 6.9.6 (Long term support version of V6.10.2)

Warnings:

Devices updated with 6.10.2 firmware should not be downgraded to firmware versions before 6.10.0.
ReadyNAS 102, 104, and 2120 systems must not be updated directly to 6.10.x from 6.3.x or older firmware. They must first be updated to either 6.2.5 or 6.3.5 then to 6.5.2 and then to 6.10.x.
ReadyNAS 202, 204, 212 and 212 systems must not be updated directly to 6.10.x from 6.3.x. They must first be updated to 6.3.5 then 6.5.2 and then to 6.10.x.

Currently have upgraded (by interrupting uboot the booting) to 6.10.2
Was at 6.4.2. Went to 6.5.2 then 6.10.2.

Was going to attach file but it is 1.8G.
Tried to break it up into 3 smaller zips (using 7-zip), all still over the 1000kb attachment limit.
Any way you might be able to download?

Was looking through it, there is a section on using mkimage to create the environment .bin file but I am not that good with compiling multiple files, so I could not make much sense of it.
As far as bootcmd not used, When I see, on failed boot, the error message it looked like to me, that it was running the bootcmd BUT due to the error, skips the rest of the line.
bootargs=pci=pcie_bus_perf console=ttyS0,115200 reason=normal bdtype=rn204
## Error: "odmbootusb" not defined

On U-Boot website there was this: (http://www.denx.de/wiki/publish/DULG/to-delete/UBootCmdGroupEnvironment.html)
TIP If a U-Boot variable contains several commands (separated by semicolon), and one of these commands fails when you "run" this variable, the remaining commands will be executed anyway.

TIP If you execute several variables with one call to run, any failing command will cause "run" to terminate, i. e. the remaining variables are not executed.

Per the first tip, if odmbootusb fails then it should run odmbootfirmware, but was think (I know mistake), maybe second tip is being applied.

Thanks again for all the help.
Mike
Reply Quote
bodhi
Re: RN204 U-Boot boot issue
October 31, 2019 02:02AM
Mike,

This is a non-destructive test (nothing change after you run it and then recycle power to the box). This test is to check if u-boot reset the bootcmd to some different internal value.

Power up, Interrup serial console, and 

setenv bootcmd 'echo running odmbootseq; run odmbootseq'
setenv odmbootseq 'echo running odmbootseq; run odmbootargs; run odmbootusb; run odmbootfirmware; failure'
setenv odmbootusb 'echo running odmbootusb; usb start;fatload usb 0 $loadaddr NTGR_USBBOOT_INFO.txt;if test $? -eq 0; then run odmbootbackusb;fi'
boot

And please post the serial console log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
bodhi
Re: RN204 U-Boot boot issue
November 01, 2019 05:49PM
Mike,

It will take a while to download with my slow internet.

If you already found u-boot source tree in the downloaded zip file, you can tar/zip it up and upload to Dropbox or somewhere.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
1oldmike
Re: RN204 U-Boot boot issue
November 03, 2019 09:54AM
I found issue.
I put and echo statement in the odmbootseq for testing.
It never showed up when boot NOT interrupted, and did when I interrupted and typed in 'boot' which runs 'bootcmd'.
Thought at first second u-boot was being used but when I looked at the hex load address it was the same for both.
So I figured it had to be something in the environment variables that was causing a different bootcmd to be run.
Also, noted that when boot not interrupted it loaded a 'compressed' version of linux, but when boot interrupted and 'boot' command issued, it loaded uncompressed linux.
Deleted 'FACTORY_DIAG=1' variable.
Now it boots up normally. Netgear has function to load back to factory settings. I think that previous owner was trying to do something and got it hosed that way. With that variable set, it was defaulting to a different load.
Thanks for all your time and help.
Mike
Reply Quote
bodhi
Re: RN204 U-Boot boot issue
November 03, 2019 04:43PM
Mike,

> It never showed up when boot NOT interrupted, and
> did when I interrupted and typed in 'boot' which
> runs 'bootcmd'.

That's what I've suspected. The bootcmd was reset by this u-boot to some internal value, and the bootcmd in NAND was ignored.

> Deleted 'FACTORY_DIAG=1' variable.

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
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: