Can't Modify U-Boot Environment Variables on Updated Firmware

Jump to: navigation, search

Yes. One thing that wasn't clear to me was where to actually get those files. I've been using the ones that are found in ~/tmp/deploy/images/h3ulcb/ after building yocto. Assuming that's the correct path, I'm going to try rebuilding yocto in case I messed something up in that process.

One possible indication of what the issue is: I looked through the Renesas Device Manual to find a solution and found that in the section on booting the addresses the board boots from are slightly different from those on the e-linux wiki (looking at page 238 in particular). I'm a machine learning guy by trade and my architecture knowledge is rather scant comparatively so maybe this is nothing/not what I thought it means.

23:10, 18 July 2017

Yes, /tmp/deploy/images/h3ulcb is correct path. Please refer to the No13 of

All updating methods are described below. Could you try again?

If "u-boot" still doesn't start up please attach the log when flashing the firmware.

03:03, 21 July 2017

Rebuilding the whole thing from scratch worked. Something must have gone wrong in the initial build because the .dtb file sizes between the two builds were off by a few hundred bytes.

22:38, 22 July 2017