I'm off work today so I can't say exactly what versions I was using, but I recall following the instructions verbatim and everything worked perfectly.
I suppose if your modifications to the u-boot source were bad enough, you could cause boot to fail. If I recall correctly, I started by allowing the blank eeprom case to follow the black boot path. That seemed easiest to get started and I think it just added an OR to an if statement. Figuring out what's happening without a serial debug port is feeling around blind. If you're not getting paid for it, it's not so bad, but it wastes a lot of time. No way could I do that at work. Good luck. On Thu, Aug 13, 2020, 1:07 PM Joshua Park <[email protected]> wrote: > Were you using u-boot version 2018.03rc1 when you made it work? That is > the only thing that I had to change when following pocket beagle image > tutorial <https://www.digikey.com/eewiki/display/linuxonarm/PocketBeagle> > since the 0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch > provided in the blank board ID method is written for that version. In case > I made a mistake somewhere I will go back and try again. > > On Thursday, August 13, 2020 at 12:31:48 PM UTC-4 [email protected] wrote: > >> It should work on an original pocket beagle. Like I told Sam Park in a >> separate thread, you basically must have a serial debug adapter connected >> to the device to debug u-boot issues. >> >> I can say that I have followed rcn's instructions for building and >> installing u-boot and followed octavo's directions for modifying a board >> with a blank eeprom, and things worked perfectly, for me. >> >> Good luck! >> >> On Thu, Aug 13, 2020, 11:12 AM Joshua Park <[email protected]> wrote: >> >>> >>> Hi all, >>> >>> I'm currently working on a project involving a custom SBC based off the >>> Pocket Beagle. I'm in the process of building a image for it and I am >>> trying to utilize a blank board ID mentioned here: >>> https://octavosystems.com/app_notes/osd335x-eeprom-during-boot/. >>> However upon testing, I found out that the image for some reason does not >>> boot on the original Pocket Beagle. Why is this the case? As far as I know, >>> utilizing a blank board ID is not the recommended way to boot however I >>> don't see why it shouldn't boot with the original Pocket Beagle. Thanks. >>> >>> -- >>> 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/1715f20d-48b4-4a31-b330-b950ccad2059n%40googlegroups.com >>> <https://groups.google.com/d/msgid/beagleboard/1715f20d-48b4-4a31-b330-b950ccad2059n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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/4eeffa58-5a80-429a-a9e0-bf32f1800182n%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/4eeffa58-5a80-429a-a9e0-bf32f1800182n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAGS%2B2h_gVnEMV6BUcMjxvx3u82UFQVfkXu7a7hc44i2nc_yp2g%40mail.gmail.com.
