Bodhi, Digging a little deeper into this; using the "Arch envs," I changed the loadaddr (load address used in U-Boot command load) variable to 0x800000 and attempted to run the kernel ... success. I'm not sure where I have gone wrong using/setting up uboot.2016.05-tld-1.environment; however, I am more than a little embarrassed for jumping the gun assuming the issue was the lby jazzoo - uBoot
Bodi, Not the case at all. I did, in fact, follow the instructions after reading and rereading them several times including step 8.) Flashing default u-boot envs image: (sub section B.) using the uboot.2016.05-tld-1.environment you kindly provided. Including making changes to match the GoFlex Home and enabling NC console support. The box is working and I am grateful for your knowleby jazzoo - uBoot
I followed your "installation" instructions for both the new U-boot and Kernel on a "stock" Goflex Home. All went great and the box booted fine. Pressing my luck, I tried repeating the same installation using the same installation files and repeating the same instructions on a GFH I'd installed Arch on some years ago. U-Boot works, however the U-Boot environment variby jazzoo - uBoot