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 cby 1oldmike - uBoot
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)by 1oldmike - uBoot
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.0by 1oldmike - uBoot
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 –by 1oldmike - uBoot