On Thu, Apr 6, 2017 at 3:47 PM, Robert LaMoreaux <roblamoreaux...@gmail.com> wrote: > Robert, > > I broke down and got another BBBL which I will use mobile, while I use the > original for development and testing while tethered to USB. > I'll check the signals with a scope on the original as I get time in case it > is something like the oscillator. > > I did notice that the broken one has the WIFI light come on then go off at > reset and the new one it does not come on > > One question I had. With the new SDCARD image, the eMMC flashing > instructions say to uncomment the line in /boot/uEnv.txt > > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh > > I noticed in the /opt/scripts/tools/eMMC directory that there is a file > called init-eMMC-flasher-v3-bbbl.sh stuff that appears to be for updating > the eMMC on the BBBL. SSo my question is for updating the BBBL should I make > that line read: > > cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3-bbbl.sh
For end users with production boards, both those scripts do the exact same thing. For boards HOT off the assembly line, the "bbbl.sh" variant is used to help first program the correct "BBBL" eeprom into the board eeprom. 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/CAOCHtYinPwqK7%2B%3DSMi3OJUXw-cZQbmADFcj%3Ddp8FEixrZg_%2BWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
