On Fri, Jul 21, 2017 at 10:01 AM, Jeff Andich <[email protected]> wrote: > Hi, > > Yesterday, for some reason, when I fetched the 2017.01 u-boot, it no longer > runs on my 572xEVM/??BB-X15?? Nothing prints out on console and no lights > blink around the SD Card. However, when I re-dd'ed MLO and u-boot.img to > the SD Card fetched 2 months ago, using the same instructions for building > the 2017.01 u-boot from, > https://eewiki.net/display/linuxonarm/BeagleBoard-X15, it runs again. That > SPL reports the CPU as DRA752-GP, ES2.0, and the Board as AM572x EVM Rev A3.
i have that board in a box at home now, i really need to power it on and test it.. > > I noticed that the version of the u-boot patch file, > 0001-beagle_x15-uEnv.txt-bootz-n-fixes.patch fetched yesterday was different > than the same filename I ended up fetching about 2 months ago (and applying > to 2017.01 u-boot) after doing a diff on the patch files. > > Both times, I BELIEVE I got the patch from here: > https://rcn-ee.com/repos/git/u-boot-patches/ti-2017.01/0001-beagle_x15-uEnv.txt-bootz-n-fixes.patch > > > Did the patch file change? My diff shows some changes with the addition of > BB-X15 revc. If the patch file changed, is ti typical for the file name not > to change as well (e.g. 0002-beagle....) ? > > What do I need to do to make my target work again with the latest patch? Yes the patch changes. Normally with u-boot that doesn't matter, as a new rcX build is every few weeks. However the git tree for the x15 is also changing: http://git.ti.com/gitweb/?p=ti-u-boot/ti-u-boot.git;a=shortlog;h=refs/heads/ti-u-boot-2017.01 Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYjaBfL9Zm2txioDSLbsy9KkotoHRJAoahGWezA8o72Hyw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
