Ah, I missed that the hard coded address in the last line also was also a fdtaddr occurrence that I still needed to fix. However, it still didn't work afterwards, so I got rid of the variables I had set up and replaced them all with the new hard coded addresses. That did the trick - phew!
Thanks again for your help! On Wednesday, October 8, 2014 12:25:30 PM UTC+2, Sebastian H wrote: > > I changed the addresses, but the BBB still won't boot up. Now it's in a > bootloop - At first the heartbeat lights up for half a second before all 4 > leds light up. Then the leds go dark and it repeats itself. > Here's my revised uEnv.txt: > http://pastebin.com/E6QnFSU0 > > Did I make a mistake or is there still anything missing? > > I wonder if perhaps the hard coded address in the last line might be the > culprit? > > Thanks, > Sebastian > > On Wednesday, October 8, 2014 3:22:00 AM UTC+2, RobertCNelson wrote: >> >> On Tue, Oct 7, 2014 at 7:52 PM, Sebastian H <[email protected]> wrote: >> > After updating to the kernel 3.14.19-ti-r27 I can't boot my BBB >> anymore. >> > User leds light up all 4 and then I mostly just see the heatbeat led >> and not >> > much other activity and I can't SSH into it. I don't have a serial >> cable so >> > I don't have access to any more details than that. >> > >> > Searching the net, I came across this thread where someone had a >> similar >> > issue: >> > >> https://groups.google.com/forum/embed/?place=forum/beagleboard&showsearch=true&showpopout=true&showtabs=true&hideforumtitle=true&parenturl=http%3A%2F%2Fbeagleboard.org%2FCommunity%2FForums#!searchin/beagleboard/Image$20Name$3A$20$20$203.14.19/beagleboard/rkiFSA1cXvU/mua-2y7zg8IJ >> >> > >> > Could this be an issue with my uEnv.txt file as well? >> > Since I set up the Debian on the eMMC back in September 2013, I haven't >> > reflashed the system and only updated it via apt-get. Any way to update >> the >> > file without having to reflash the eMMC so I don't have to reinstall >> the >> > system? >> > >> > Here's what's in my uEnv.txt >> > http://pastebin.com/aVWXYtWH >> > >> > If I roll back to a backup with the 3.8.13 kernel, is there anything I >> > should before running the kernel update to avoid this issue? >> >> conf_loadaddr="0x82000000" >> conf_fdtaddr="0x88000000" >> conf_initrdaddr="0x88080000" >> >> Change your load addrees's it's overlapping with the kernel.. >> >> Regards, >> >> -- >> Robert Nelson >> http://www.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]. For more options, visit https://groups.google.com/d/optout.
