If anybody else is following the tftp boot approach then they will also need to exercise that patch, identified by . I use the same patch text file when automatically building the bootscript for each board so it's just as well it worked for me first time - otherwise I'd have 4 bricks!! You've proved that it's a messy, tricky, dangerous patch - but it is necessary for tftp load.
Hopefully, there are enough CAVEATs and WARNINGs in the posts and wiki guide to keep the Lawyers off my back!
It's not clear why the gigabit interface change was made to the U-Boot source in the first place. From some of Fred's posts, I understand that the U-Boot probably needs to be re-built and re-issued - in part because it's not compatible with the Vivado rebuild of the FPGA (??). Hopefully, the bug(?) will be fixed.
As for /etc/fw_env.config, fw_setenv, etc., Whoa! You're too many pages ahead of me again. But it's very useful to know that there's a way to get at a partially bricked board from the UART console. Briefly searching around forums this morning, it looks like if you get a bad CRC error, then U-Boot somehow ends up using the default, built-in variables. (But don't take my word for that).
Cheers,Statistics: Posted by greytery — Sun Nov 23, 2014 11:33 am
]]>