Okay I managed to get everything working too. I had to do the following steps:
1. reset eMMC sudo /opt/scripts/tools/developers/update_bootloader.sh 2. flash new image provided above 3. After that the model from /opt/scripts/tools/version.sh was wrong for me. I'm using a BBBW but model field had just regular beaglebone black in it. This prevent wifi (via connman) from working. I followed another post about this (https://groups.google.com/forum/#!topic/beagleboard/_ydry5HYVNQ) which suggested to reset eeprom: GND TP1 then run as root: dd if=/opt/scripts/device/bone/bbbw-eeprom.dump of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom reboot. Everything works fine now! Thanks Robert and Hugh On Saturday, May 25, 2019 at 2:37:07 PM UTC-7, Hugh Frater wrote: > > Robert, is it ok to use this image in production or should I use the > current stretch IOT image and flash the eMMC to overwrite this old > bootloader? > > On Saturday, 25 May 2019 20:55:58 UTC+1, RobertCNelson wrote: >> >> > This is what I think is relevant from my uBoot console: >> > >> > U-Boot SPL 2017.03-00002-gd12b1519b4 (Mar 14 2017 - 10:28:26) >> > Trying to boot from MMC2 >> > U-Boot 2017.03-00002-gd12b1519b4 (Mar 14 2017 - 10:28:26 -0500), Build: >> jenkins- >> > github_Bootloader-Builder-532 >> >> There you go!! Would you please give me a dd copy of the first 100Mb >> of the eMMC partition.. Such that i can use it to update the >> version.sh script, to detect this bad version... >> >> 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/1d518f39-61eb-4847-9f90-1ff28261a6fc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
