by shogunx » Sat Nov 22, 2014 4:12 pm
GreyTery,
Finally got a chance to implement the workaround you pointed me to on the network reset issue. I get the same results as you... the nodes just boot now. Terrific! I also discovered something interesting. I inadvertantly transposed two characters on one node, leaving the board in a non-bootable state. It would boot the kernel, but hang. I pulled the network cable, booted again, thereby giving no fpga image, dtb, or kernel to the board. With that method, it would go into an endless loop of searching for network, but never dropped me to a u-boot shell. Given that it was essentially bricked anyway, I set the appropriate values in /etc/fw_env.config, and ran a fwsetenv despite the CRC check error warning. This indeed overwrote the factory u-boot paramaters at 0x4E0000, and upon reboot, the device dropped to a u-boot prompt again. I manually rebuilt the environment variables with setenv, referencing a working nodes configuration, and now it boots as normal. This bring another issue though... why won't fw_setenv and fw_printenv work correctly, despite the correct values in /etc/fw_env.config? Is there a bug in the CRC check as well?
Cheers
Scott