Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
Hi Robert, I am attempting this process again but now am getting: /opt/scripts/tools# ./beaglebone-black-eMMC-flasher.sh Error: script halting, system unrecognized... How do I fix this? On Thursday, September 10, 2015 at 1:33:00 PM UTC-7, Matt Maher Peterson wrote: > > Thanks that worked very well. > > Owe you a beer! > > Kind Regards. > > On Thursday, September 10, 2015 at 11:15:40 AM UTC-7, RobertCNelson wrote: >> >> On Thu, Sep 10, 2015 at 12:58 PM, Matt Maher Peterson >>wrote: >> > Sorry I should have been more clear. >> > >> > So on a known good beaglebone that I have my custom debian installed on >> how >> > do I make a copy of this on uSD card such that I flash another BBB with >> a >> > different emmc chip. >> > >> > Is the workflow like this: >> > 1. Boot up known good Kingston BBB with custom image. >> > 2. Insert a uSD card => 4GB >> > 3. execute /opt/scripts/tools/ >> git pull >> > 4. execute /opt/scripts/tools/eMMC# >> > ./beaglebone-black-make-microSD-flasher-from-eMMC.sh >> > 5. Insert this card into a new BBB that needs to be flashed? >> > >> > Am I understanding this properly? >> >> Correct ;) >> >> 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
On Tue, Oct 6, 2015 at 3:36 PM, Matt Maher Petersonwrote: > Hi Robert, > > I am attempting this process again but now am getting: > > /opt/scripts/tools# ./beaglebone-black-eMMC-flasher.sh > Error: script halting, system unrecognized... > > How do I fix this? that one is eol... look at the previous emails.. 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
Not sure I am following are you saying run a different script? Sorry I am noob... I tried the init-eMMC-flasher.sh and get the same result. On Tuesday, October 6, 2015 at 1:43:46 PM UTC-7, RobertCNelson wrote: > > On Tue, Oct 6, 2015 at 3:36 PM, Matt Maher Peterson >wrote: > > Hi Robert, > > > > I am attempting this process again but now am getting: > > > > /opt/scripts/tools# ./beaglebone-black-eMMC-flasher.sh > > Error: script halting, system unrecognized... > > > > How do I fix this? > > that one is eol... > > look at the previous emails.. > > 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
Ok I see now. Use the script that is /opt/scripts/tools/emmc. One more question. The reason I was trying this tool again is that my custom debian image stopped auto connecting to my computer via usb. I am running Ubuntu on my desktop and the little network icon just seams to be cycling thru trying to establish a connection. It never seams to quite get there. Any ideas? On Tuesday, October 6, 2015 at 2:06:55 PM UTC-7, RobertCNelson wrote: > > On Tue, Oct 6, 2015 at 4:02 PM, Matt Maher Peterson >wrote: > > Not sure I am following are you saying run a different script? > > > > Sorry I am noob... > > > > I tried the init-eMMC-flasher.sh and get the same result. > > We went over this a month ago... look in the "eMMC" directory above.. > > and read the readme.md (git pull) to get the latest.. > > 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
On Tue, Oct 6, 2015 at 4:02 PM, Matt Maher Petersonwrote: > Not sure I am following are you saying run a different script? > > Sorry I am noob... > > I tried the init-eMMC-flasher.sh and get the same result. We went over this a month ago... look in the "eMMC" directory above.. and read the readme.md (git pull) to get the latest.. 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
Hi, I have a debian image I built with custom device tree and code that I have created. I have copied and flashed this onto new beaglebones using this tool: http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents This worked great untill a recent shipment of BBB REV C from element 14. I can see a difference a between the two boards where the emmc chips are different the 'old rev c' has a kingston chip whereas the 'new rev c' has a different one with a number 4LA18 JWA06 and M with a circle. When I use the tool mentioned above I get the proper led sequence tell me the emmc is being flashed (blinking once a second, then goes solid when finished). On these new board the LED sequence starts off right but goes solids very quickly and seemingly no image has been copied? What am I missing here?? Cheers, Matt -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
On Thu, Sep 10, 2015 at 11:41 AM, Matt Maher Petersonwrote: > Hi, > > I have a debian image I built with custom device tree and code that I have > created. I have copied and flashed this onto new beaglebones using this > tool: > > http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents > > This worked great untill a recent shipment of BBB REV C from element 14. I > can see a difference a between the two boards where the emmc chips are > different the 'old rev c' has a kingston chip whereas the 'new rev c' has a > different one with a number 4LA18 JWA06 and M with a circle. > > When I use the tool mentioned above I get the proper led sequence tell me > the emmc is being flashed (blinking once a second, then goes solid when > finished). On these new board the LED sequence starts off right but goes > solids very quickly and seemingly no image has been copied? > > What am I missing here?? Nand/eMMC vary in size, the current eMMC's being used range in sizes: #Micron 3744MB (bbb): 3925868544 bytes -> 3925.86 Megabyte #Kingston 3688MB (bbb): 3867148288 bytes -> 3867.15 Megabyte #Kingston 3648MB (bbb): 3825205248 bytes -> 3825.21 Megabyte dd based image tools can't handle this. Use the rsync "flashers"... 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
rsync flashers? could you provide more info or link? Thanks On Thursday, September 10, 2015 at 9:46:05 AM UTC-7, RobertCNelson wrote: > > On Thu, Sep 10, 2015 at 11:41 AM, Matt Maher Peterson >wrote: > > Hi, > > > > I have a debian image I built with custom device tree and code that I > have > > created. I have copied and flashed this onto new beaglebones using this > > tool: > > > > http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents > > > > This worked great untill a recent shipment of BBB REV C from element 14. > I > > can see a difference a between the two boards where the emmc chips are > > different the 'old rev c' has a kingston chip whereas the 'new rev c' > has a > > different one with a number 4LA18 JWA06 and M with a circle. > > > > When I use the tool mentioned above I get the proper led sequence tell > me > > the emmc is being flashed (blinking once a second, then goes solid when > > finished). On these new board the LED sequence starts off right but > goes > > solids very quickly and seemingly no image has been copied? > > > > What am I missing here?? > > Nand/eMMC vary in size, the current eMMC's being used range in sizes: > > #Micron 3744MB (bbb): 3925868544 bytes -> 3925.86 Megabyte > #Kingston 3688MB (bbb): 3867148288 bytes -> 3867.15 Megabyte > #Kingston 3648MB (bbb): 3825205248 bytes -> 3825.21 Megabyte > > dd based image tools can't handle this. Use the rsync "flashers"... > > 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
Sorry I should have been more clear. So on a known good beaglebone that I have my custom debian installed on how do I make a copy of this on uSD card such that I flash another BBB with a different emmc chip. Is the workflow like this: 1. Boot up known good Kingston BBB with custom image. 2. Insert a uSD card => 4GB 3. execute /opt/scripts/tools/eMMC# ./beaglebone-black-make-microSD-flasher-from-eMMC.sh 4. Insert this card into a new BBB that needs to be flashed? Am I understanding this properly? On Thursday, September 10, 2015 at 10:46:25 AM UTC-7, RobertCNelson wrote: > > On Thu, Sep 10, 2015 at 11:58 AM, Matt Maher Peterson >wrote: > > rsync flashers? could you provide more info or link? > > For this flasher image: > > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29 > > This rsync based script is what runs behind the scenes.. > > > https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh > > > 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
Thanks that worked very well. Owe you a beer! Kind Regards. On Thursday, September 10, 2015 at 11:15:40 AM UTC-7, RobertCNelson wrote: > > On Thu, Sep 10, 2015 at 12:58 PM, Matt Maher Peterson >wrote: > > Sorry I should have been more clear. > > > > So on a known good beaglebone that I have my custom debian installed on > how > > do I make a copy of this on uSD card such that I flash another BBB with > a > > different emmc chip. > > > > Is the workflow like this: > > 1. Boot up known good Kingston BBB with custom image. > > 2. Insert a uSD card => 4GB > > 3. execute /opt/scripts/tools/ > git pull > > 4. execute /opt/scripts/tools/eMMC# > > ./beaglebone-black-make-microSD-flasher-from-eMMC.sh > > 5. Insert this card into a new BBB that needs to be flashed? > > > > Am I understanding this properly? > > Correct ;) > > 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
On Thu, Sep 10, 2015 at 11:58 AM, Matt Maher Petersonwrote: > rsync flashers? could you provide more info or link? For this flasher image: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29 This rsync based script is what runs behind the scenes.. https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?
On Thu, Sep 10, 2015 at 12:58 PM, Matt Maher Petersonwrote: > Sorry I should have been more clear. > > So on a known good beaglebone that I have my custom debian installed on how > do I make a copy of this on uSD card such that I flash another BBB with a > different emmc chip. > > Is the workflow like this: > 1. Boot up known good Kingston BBB with custom image. > 2. Insert a uSD card => 4GB > 3. execute /opt/scripts/tools/ git pull > 4. execute /opt/scripts/tools/eMMC# > ./beaglebone-black-make-microSD-flasher-from-eMMC.sh > 5. Insert this card into a new BBB that needs to be flashed? > > Am I understanding this properly? Correct ;) 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. For more options, visit https://groups.google.com/d/optout.