For future reference by others, I think instead of "if=/opt/scripts/device/bone/bbgw-eeprom.dump"
it should have been stated as: "if=/opt/scripts/device/bone/bbbw-eeprom.dump" since I have a BeagleBone Black Wireless (but it is manufactured by GHI as you said). I first updated using the first file, and my device type was shows as BeagleBone Green Wireless. The WiFi would not work (using connmanctl for setup). I then flashed using the second file, and my device displayed as BeagleBone Black Wireless, and I was then successful in setting up WiFi connectivity. On Monday, December 16, 2019 at 2:27:17 PM UTC-8, RobertCNelson wrote: > > On Mon, Dec 16, 2019 at 3:58 PM ags <alfred....@gmail.com <javascript:>> > wrote: > > > > My next question was going to be "what should the EEPROM ID be... or > what form should it take"? > > An even better, answer, look on side of the board, there is a bar code > with the coded: BWA5***** that's what the device tester was supposed > to write to the eeprom. ;) > > > This (non-functioning) BBBW was purchased in Dec 2018 (just now putting > it into service). I have another BBBW purchased in Feb 2017 that worked > out-of-box (almost... it had a different issue with the "out-of-box > configuration" that you also helped me with) and it shows: > > > > eeprom:[A335BNLTBWA51650BBWG0378] > > > > model:[TI_AM335x_BeagleBone_Black_Wireless] > > > > > > So does a "correct" BBB Wireless EEPROM ID follow the A335BNLT BWA51*** > BBWG0***] format, with the first wildcard digits some form of version of > the wireless chip and the second wildcard digits the board or SoC rev? > (spaces mine to separate the different fields) > > The first Wild card, is the year in 2 digits and the week in 2 digits. > The last wildcard is incremental units of that week.. > > BWA5 = BeagleBone Black Wireless > > BBWG = BeagleBone Black Wireless, Manufactured by GHI > > > > > Finally, was my expectation/understanding incorrect that using > /boot/uEnv.txt to override the EEPROM setting and force loading the > wireless dtb would also work, without changing the EEPROM? (My thinking was > to try that first, then if it worked it would validate the idea the the > EEPROM was bad and then reflash the EEPROM). > > Well, you did have this old version of u-boot installed to the eMMC: > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2016.11-rc3-00002-g73df7f]:[location: dd MBR] > > So the overide probably just didn't work.. > > 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1a93972a-7f2c-492e-a95a-e0c367d3dbcc%40googlegroups.com.
