Re: [beagleboard] Working links to blank-EEPROM flasher image?

[William Hermans]

Or wait, I guess I was comparing the white's eeprom to the blacks eeprom,
so they look the same. Yeah, writing a white eeprom to a black eeprom would
be bad haha :/

On Mon, Apr 18, 2016 at 3:12 PM, William Hermans  wrote:

> Thanks Gerald, and Robert. So yeah it does look different, however . . . I
> can not think of a reason why a beagleboard.org eeprom would fail on an
> element14 board. I mean they both have exactly the same hardware as far as
> device tree goes, yeah ?
>
> I mean, in the long run, I'm not sure this is really an important
> question, but is something I think is good to know. Also I was expecting
> something more complex for an eeprom "string", but heh, serves me right for
> "thinking" ;)
>
> On Mon, Apr 18, 2016 at 3:06 PM, Robert Nelson 
> wrote:
>
>>
>>
>> On Mon, Apr 18, 2016 at 5:03 PM, William Hermans 
>> wrote:
>>
>>>
 *Oh they are there, too... But since the 'blank' eeprom flasher's
 overwrite the board eeprom, the oem's need to contact me directly.. and i
 can point them directly to the image and tweak they need to do..*

 *With all the clones today, the days of just "BeagleBone Black" 100%
 clone blank eeprom are over. ;)*

 *Regards,*
>>>
>>> Yeah, I read the instructions above. So I'm curious though. Is the
>>> eeprom any different between say circuitco, and element14 BBB's ? I suppose
>>> I could dump, and diff ( if i was sure I knew how to dump correctly ).
>>>
>>
>> Here is the full list:
>>
>> https://github.com/beagleboard/image-builder/blob/master/readme.md
>>
>> 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/CAOCHtYgcRgYTzugWHz7%3DSvrVKP2q7ObD7y_0Poz%2Bk2AsykAf8Q%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/CALHSORrswb3PeAcUmMuS23gcz4%3DayCbDcsB_DerEFC36NwQShQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[William Hermans]

Thanks Gerald, and Robert. So yeah it does look different, however . . . I
can not think of a reason why a beagleboard.org eeprom would fail on an
element14 board. I mean they both have exactly the same hardware as far as
device tree goes, yeah ?

I mean, in the long run, I'm not sure this is really an important question,
but is something I think is good to know. Also I was expecting something
more complex for an eeprom "string", but heh, serves me right for
"thinking" ;)

On Mon, Apr 18, 2016 at 3:06 PM, Robert Nelson 
wrote:

>
>
> On Mon, Apr 18, 2016 at 5:03 PM, William Hermans 
> wrote:
>
>>
>>> *Oh they are there, too... But since the 'blank' eeprom flasher's
>>> overwrite the board eeprom, the oem's need to contact me directly.. and i
>>> can point them directly to the image and tweak they need to do..*
>>>
>>> *With all the clones today, the days of just "BeagleBone Black" 100%
>>> clone blank eeprom are over. ;)*
>>>
>>> *Regards,*
>>
>> Yeah, I read the instructions above. So I'm curious though. Is the eeprom
>> any different between say circuitco, and element14 BBB's ? I suppose I
>> could dump, and diff ( if i was sure I knew how to dump correctly ).
>>
>
> Here is the full list:
>
> https://github.com/beagleboard/image-builder/blob/master/readme.md
>
> 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/CAOCHtYgcRgYTzugWHz7%3DSvrVKP2q7ObD7y_0Poz%2Bk2AsykAf8Q%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALHSORpUikn-djDJxw09mM%3DuZ%3DFGc2fqcjww9zZ6EjaMjwxGog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[Gerald Coley]

It should not be. But, then again.

Gerald


On Mon, Apr 18, 2016 at 5:03 PM, William Hermans  wrote:

>
>> *Oh they are there, too... But since the 'blank' eeprom flasher's
>> overwrite the board eeprom, the oem's need to contact me directly.. and i
>> can point them directly to the image and tweak they need to do..*
>>
>> *With all the clones today, the days of just "BeagleBone Black" 100%
>> clone blank eeprom are over. ;)*
>>
>> *Regards,*
>
> Yeah, I read the instructions above. So I'm curious though. Is the eeprom
> any different between say circuitco, and element14 BBB's ? I suppose I
> could dump, and diff ( if i was sure I knew how to dump correctly ).
>
> On Mon, Apr 18, 2016 at 1:16 PM, Robert Nelson 
> wrote:
>
>>
>>
>> On Mon, Apr 18, 2016 at 3:04 PM, William Hermans 
>> wrote:
>>
>>> Robert, so which is the blank eeprom flasher ?
>>>
>>
>> Oh they are there, too... But since the 'blank' eeprom flasher's
>> overwrite the board eeprom, the oem's need to contact me directly.. and i
>> can point them directly to the image and tweak they need to do..
>>
>> With all the clones today, the days of just "BeagleBone Black" 100% clone
>> blank eeprom are over. ;)
>>
>> 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/CAOCHtYizQDRCRp7Su85EPj2_30z5Hs99CGjbx%3Dp2cM60QP7FPw%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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/CALHSORqTKJzJLYi-7KMXqKZ46dRxZsyafXTB68g8p3tiAYc9CA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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/CAHK_S%2BfRPx7sV6px7EnuQT30SVe0R7vgv1Ou5aUERd-TZqcxZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Mon, Apr 18, 2016 at 5:03 PM, William Hermans  wrote:

>
>> *Oh they are there, too... But since the 'blank' eeprom flasher's
>> overwrite the board eeprom, the oem's need to contact me directly.. and i
>> can point them directly to the image and tweak they need to do..*
>>
>> *With all the clones today, the days of just "BeagleBone Black" 100%
>> clone blank eeprom are over. ;)*
>>
>> *Regards,*
>
> Yeah, I read the instructions above. So I'm curious though. Is the eeprom
> any different between say circuitco, and element14 BBB's ? I suppose I
> could dump, and diff ( if i was sure I knew how to dump correctly ).
>

Here is the full list:

https://github.com/beagleboard/image-builder/blob/master/readme.md

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/CAOCHtYgcRgYTzugWHz7%3DSvrVKP2q7ObD7y_0Poz%2Bk2AsykAf8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[William Hermans]

>
>
> *Oh they are there, too... But since the 'blank' eeprom flasher's
> overwrite the board eeprom, the oem's need to contact me directly.. and i
> can point them directly to the image and tweak they need to do..*
>
> *With all the clones today, the days of just "BeagleBone Black" 100% clone
> blank eeprom are over. ;)*
>
> *Regards,*

Yeah, I read the instructions above. So I'm curious though. Is the eeprom
any different between say circuitco, and element14 BBB's ? I suppose I
could dump, and diff ( if i was sure I knew how to dump correctly ).

On Mon, Apr 18, 2016 at 1:16 PM, Robert Nelson 
wrote:

>
>
> On Mon, Apr 18, 2016 at 3:04 PM, William Hermans 
> wrote:
>
>> Robert, so which is the blank eeprom flasher ?
>>
>
> Oh they are there, too... But since the 'blank' eeprom flasher's overwrite
> the board eeprom, the oem's need to contact me directly.. and i can point
> them directly to the image and tweak they need to do..
>
> With all the clones today, the days of just "BeagleBone Black" 100% clone
> blank eeprom are over. ;)
>
> 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/CAOCHtYizQDRCRp7Su85EPj2_30z5Hs99CGjbx%3Dp2cM60QP7FPw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALHSORqTKJzJLYi-7KMXqKZ46dRxZsyafXTB68g8p3tiAYc9CA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Mon, Apr 18, 2016 at 3:04 PM, William Hermans  wrote:

> Robert, so which is the blank eeprom flasher ?
>

Oh they are there, too... But since the 'blank' eeprom flasher's overwrite
the board eeprom, the oem's need to contact me directly.. and i can point
them directly to the image and tweak they need to do..

With all the clones today, the days of just "BeagleBone Black" 100% clone
blank eeprom are over. ;)

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/CAOCHtYizQDRCRp7Su85EPj2_30z5Hs99CGjbx%3Dp2cM60QP7FPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[William Hermans]

Robert, so which is the blank eeprom flasher ?

On Mon, Apr 18, 2016 at 12:05 PM, Robert Nelson 
wrote:

>
>
> On Mon, Apr 18, 2016 at 1:46 PM, Phil Mills  wrote:
>
>> Thanks!  Turns out my manufacturing folks were having some PEBKAC errors
>> anyway, but thanks for pointing me to the new host.
>> Is there any substantive difference between the USB Flasher images from
>> various points in the Testing directory tree?
>>
>
> Oh, just weekly snapshots...  The latest the better...
>
> We are getting close to cutting a new jessie/v4.1.x/lxqt release for
> seeed..
>
> 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/CAOCHtYimSNrwEhW%2B1ZgaUFSUmrO2T7M7RXP_6u8G7KDakF9-Pg%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALHSORooba5SU7aYPG3%3DuO-_0%2BwHzD-x37%3DP_FZQMMypL%3DTAig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Mon, Apr 18, 2016 at 1:46 PM, Phil Mills  wrote:

> Thanks!  Turns out my manufacturing folks were having some PEBKAC errors
> anyway, but thanks for pointing me to the new host.
> Is there any substantive difference between the USB Flasher images from
> various points in the Testing directory tree?
>

Oh, just weekly snapshots...  The latest the better...

We are getting close to cutting a new jessie/v4.1.x/lxqt release for seeed..

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/CAOCHtYimSNrwEhW%2B1ZgaUFSUmrO2T7M7RXP_6u8G7KDakF9-Pg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[Phil Mills]

Thanks!  Turns out my manufacturing folks were having some PEBKAC errors
anyway, but thanks for pointing me to the new host.
Is there any substantive difference between the USB Flasher images from
various points in the Testing directory tree?

On Mon, Apr 18, 2016 at 8:59 AM Robert Nelson 
wrote:

> On Mon, Apr 18, 2016 at 9:51 AM, Phil Mills  wrote:
>
>> Robert,
>>
>> It's been a while on this, but can you re-post the flasher img.xz
>> someplace (bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
>> 
>> )?
>>
>> I see you've taken it down from your website and my backup copy no longer
>> validates correctly.  Since this is actually a pretty valuable tool, is
>> there a way that it could be posted up permanantly on one of the Beaglebone
>> websites or GitHub pages?
>>
>
> Hi Phil,
>
> I have an archive site now hosted at dreamhost: (taking full advantage of
> their "unlimited" space...)
>
> https://rcn-ee.online/rootfs/bb.org/
>
> to relieve "disk space" pressure on my linode host (rcn-ee.net)..
>
> 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/CAOCPF%2BtpYKMpvEuvrf7VBaKMOSXEThtjG%2B3bwzj06YT-Xn8ZjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[Phil Mills]

Robert,

It's been a while on this, but can you re-post the flasher img.xz someplace 
(bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz 

)?

I see you've taken it down from your website and my backup copy no longer 
validates correctly.  Since this is actually a pretty valuable tool, is 
there a way that it could be posted up permanantly on one of the Beaglebone 
websites or GitHub pages?

-phil

On Tuesday, September 8, 2015 at 3:30:18 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills  > wrote: 
> > I have inherited responsibility for a bunch of 3rd-party direct clones 
> of a 
> > Beaglebone Black C5 (only known change is in silkscreening). 
> > 
> > Since none of these have any contents written to the onboard EEPROM, 
> they 
> > fail to boot with "C" written to the serial console with no uSD 
> card, 
> > and 
> > 
> >> 
> >> U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06) 
> >> Incorrect magic number (0x) in EEPROM 
> >> Could not get board ID. 
> >> Incorrect magic number (0x) in EEPROM 
> >> Could not get board ID. 
> >> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the 
> >> board ### 
> > 
> > 
> > ...written to the console when I try to boot it from a uSD cards with a 
> > stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need to 
> get 
> > some good contents into the EEPROM. 
> > 
> > 
> > I've been trying to hunt down instructions for how to access the U-Boot 
> > prompt to manually write the EEPROM via the i2c bus, but haven't hit any 
> > luck there. 
> > 
> > 
> > Robert Nelson's posted links in the past to what he's described as the 
> > "factory images for flashing boards with blank EEPROMs", but those links 
> (to 
> > rcn-ee.org) are stale/dead or behind apparently access-controlled 
> folders on 
> > his server. 
> > 
> > 
> > 
> > Could anyone provide a good set of instructions for getting access to a 
> > uBoot prompt from a stock flasher image OR provide current links to the 
> > blank-EEPROM manufacturing images (or equivalents) that RCN's 
> referenced? 
>
> So the "blank-flasher" (did everything by default) went away.  Instead 
> we now have a "usbflasher".. 
>
> Step 1: (microSD) 
>
>
> http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.bmap
>  
>
> http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.img.xz
>  
>
> (bmaptools 3.2) 
> sudo bmaptools copy --bmap *.bmap *.img.xz /dev/sdX 
>
> Step 2: (usb drive) 
> Format it as fat32, 2 or 3 files "custom: job.txt" and the image files.. 
>
> For example: 
>
> to flash: 2015-03-01 
>
> First download the base image: 
>
>
> http://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
>  
>
> Then the "eeprom" 
>
>
> https://raw.githubusercontent.com/RobertCNelson/boot-scripts/master/device/bone/bbb-eeprom.dump
>  
>
> finally crate the "job.txt" file 
>
> abi=aaa 
> conf_eeprom_file=bbb-eeprom.dump 
> conf_eeprom_compare=335 
> conf_image=bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz 
> conf_resize=enable 
> conf_partition1_startmb=1 
> conf_partition1_fstype=0xE 
> conf_partition1_endmb=96 
> conf_partition2_fstype=0x83 
> conf_root_partition=2 
>
> Step 3: (flashing) 
>
> Insert "microSD" with usbflasher image bmap'ed to it.. 
> Insert "usb flash drive" with 
> bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz, bbb-eeprom.dump 
> & job.txt all in the base directory 
> GND TP4 (write protect on eeprom) 
> Power board 
>
> Serial Log the first one to make sure it correctly flashes.. 
>
> 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/819ae9e3-b827-4227-9291-4009016cd450%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Mon, Apr 18, 2016 at 9:51 AM, Phil Mills  wrote:

> Robert,
>
> It's been a while on this, but can you re-post the flasher img.xz
> someplace (bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
> 
> )?
>
> I see you've taken it down from your website and my backup copy no longer
> validates correctly.  Since this is actually a pretty valuable tool, is
> there a way that it could be posted up permanantly on one of the Beaglebone
> websites or GitHub pages?
>

Hi Phil,

I have an archive site now hosted at dreamhost: (taking full advantage of
their "unlimited" space...)

https://rcn-ee.online/rootfs/bb.org/

to relieve "disk space" pressure on my linode host (rcn-ee.net)..

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/CAOCHtYhwpb34bm%2BNfFrQY2Q5hy6AVhXjZpOpDtWjj%3DapkkkgyQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

[William Hermans]

Sound like you have it under control then. Glad you got it working. A
couple of side notes . . .

I use Debian Wheezy i386 ( 32bit ) for all my dev machines for the
beaglebone. Have had great success with all. Virtual machine, or real.
However, I do not use X at all. Just a basic command line interface.

Also I did not think through what I was saying about sshfs . . . with
sshfs, you mount a remote file system, so technically, you *could* mount
the home directory in your virtual machine, and run tools like dd, bmap, or
whatever on the file - remotely. It might be a little slower, but it should
work.

Good luck Phil !

On Wed, Sep 9, 2015 at 1:04 PM, Phil Mills  wrote:

> Win32Imager definitely works better for my setup (and resulted in a
> bootable SD card).  I'm happy leaving the VM out of this part of the
> process - detection and mounting of USB devices that get transferred to it
> from the host is INCREDIBLY hit-or-miss on this VM.
>
> First pass at running with a card processed by Win32Imager resulted in
> failure (but I neglected to save out the logs).  It booted (yay) and looked
> like it had gotten just to where it wanted to begin writing from the image
> on the USB stick and failed there with a kernel panic.
>
> After that, I tried booting off of a flasher image uSD card, but
> apparently the EEPROM had not been successfully written prior to the
> failure.
>
> Re-built my USB stick and tried again, and it /looks/ like it's going
> better:
>
>- Serial monitor  shows an fsck failure , but it continued ("error 2
>(no such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1")
>- Serial monitor stopped on "B" with the USR LED's cycling back and
>forth in a "hey, world, I'm copying your image!" way that I like to see.
>
> LED's eventually settled at "all on", so I've powered down, pulled the uSD
> cards, put power back in and it /looks/ like it's running from the LEDs, but
> * No output on the serial console
>
> After one more hard power cycle (failed to respond to power button) the
> USB network adapter showed up in Windows (still no console output?) and I
> can SSH into the board.
>
> I think that's got me running - now to verify it on a few more boards in
> my pile.
>
>
> Much thanks, Robert.
>
>
> On Wednesday, September 9, 2015 at 11:59:03 AM UTC-6, RobertCNelson wrote:
>
>> On Wed, Sep 9, 2015 at 12:52 PM, Phil Mills  wrote:
>> > Robert,
>> >
>> > I'm not having success - the serial monitor continues to display
>> "C" as
>> > soon as it's powered up, so that seems to indicate that it's not
>> finding
>> > anything bootable on that SD card with the blank flasher image.
>>
>> Yeah... "VirtualBox"
>>
>> Just use 'win32imager" on the base *.img.xz with Windows 7...
>>
>> All the vm's are crap when it comes to writing to a microSD card..
>>
>> >
>> > My setup: 64-bit Debian Jessie (as VirtualBox VM on a Win7 host);
>> > 2GB uSD card, freshly formatted & overwritten in a uSD->USB converter
>> > (Virtualbox won't pass the built-in card reader on my laptop into the
>> VMs)
>> > 16GB uSD card, freshly formatted in a uSD->SD converter
>> > Installed bmaptool ver3.2 via apt-get
>> > Brought 2GB card over to VM
>> >
>> > mounted as /dev/sdd1; did "umount /dev/sdd1" to allow bmaptool to open
>> w/
>> > exclusive access
>> > Ran bmaptool as described above - no errors indicated.
>> > Ejected uSD from VM image, host.
>> >
>> > Inserted 16GB uSD into Win7 system,
>> >
>> > copied 2015-03-01 debian 7.8 image
>> > copied eeprom dump
>> > created new job.txt file with contents as described above (UNIX line
>> > endings)
>> > ejected uSD from Win7
>> >
>> > 2GB uSD into reader on BBB
>> > 16GB uSD into USB adapter, then to USB on BBB
>> > Serial cable connected
>> > TP4 grounded to P8-1
>> > Power applied via mini-USB cable
>> > ""
>> >
>> > Suggestions or troubleshooting steps?
>> > I have erased/re-formatted/reloaded the cards 2x with same results.
>>
>> 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.
>

-- 
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] Working links to blank-EEPROM flasher image?

[Phil Mills]

Win32Imager definitely works better for my setup (and resulted in a 
bootable SD card).  I'm happy leaving the VM out of this part of the 
process - detection and mounting of USB devices that get transferred to it 
from the host is INCREDIBLY hit-or-miss on this VM.

First pass at running with a card processed by Win32Imager resulted in 
failure (but I neglected to save out the logs).  It booted (yay) and looked 
like it had gotten just to where it wanted to begin writing from the image 
on the USB stick and failed there with a kernel panic.

After that, I tried booting off of a flasher image uSD card, but apparently 
the EEPROM had not been successfully written prior to the failure.

Re-built my USB stick and tried again, and it /looks/ like it's going 
better:

   - Serial monitor  shows an fsck failure , but it continued ("error 2 (no 
   such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1")
   - Serial monitor stopped on "B" with the USR LED's cycling back and 
   forth in a "hey, world, I'm copying your image!" way that I like to see.

LED's eventually settled at "all on", so I've powered down, pulled the uSD 
cards, put power back in and it /looks/ like it's running from the LEDs, but
* No output on the serial console

After one more hard power cycle (failed to respond to power button) the USB 
network adapter showed up in Windows (still no console output?) and I can 
SSH into the board.

I think that's got me running - now to verify it on a few more boards in my 
pile.


Much thanks, Robert.


On Wednesday, September 9, 2015 at 11:59:03 AM UTC-6, RobertCNelson wrote:
>
> On Wed, Sep 9, 2015 at 12:52 PM, Phil Mills  > wrote: 
> > Robert, 
> > 
> > I'm not having success - the serial monitor continues to display "C" 
> as 
> > soon as it's powered up, so that seems to indicate that it's not finding 
> > anything bootable on that SD card with the blank flasher image. 
>
> Yeah... "VirtualBox" 
>
> Just use 'win32imager" on the base *.img.xz with Windows 7... 
>
> All the vm's are crap when it comes to writing to a microSD card.. 
>
> > 
> > My setup: 64-bit Debian Jessie (as VirtualBox VM on a Win7 host); 
> > 2GB uSD card, freshly formatted & overwritten in a uSD->USB converter 
> > (Virtualbox won't pass the built-in card reader on my laptop into the 
> VMs) 
> > 16GB uSD card, freshly formatted in a uSD->SD converter 
> > Installed bmaptool ver3.2 via apt-get 
> > Brought 2GB card over to VM 
> > 
> > mounted as /dev/sdd1; did "umount /dev/sdd1" to allow bmaptool to open 
> w/ 
> > exclusive access 
> > Ran bmaptool as described above - no errors indicated. 
> > Ejected uSD from VM image, host. 
> > 
> > Inserted 16GB uSD into Win7 system, 
> > 
> > copied 2015-03-01 debian 7.8 image 
> > copied eeprom dump 
> > created new job.txt file with contents as described above (UNIX line 
> > endings) 
> > ejected uSD from Win7 
> > 
> > 2GB uSD into reader on BBB 
> > 16GB uSD into USB adapter, then to USB on BBB 
> > Serial cable connected 
> > TP4 grounded to P8-1 
> > Power applied via mini-USB cable 
> > "" 
> > 
> > Suggestions or troubleshooting steps? 
> > I have erased/re-formatted/reloaded the cards 2x with same results. 
>
> 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] Working links to blank-EEPROM flasher image?

[William Hermans]

Ah, but I keep forgetting . . . I can do this personally because I boot NFS
root . . . with tons of additional space left. So unles you're able to get
NFS root working, or use a USB thumb( USB host on the BBB ) drive this
won't work.

On Wed, Sep 9, 2015 at 12:45 PM, William Hermans  wrote:

> Also, for the record Win32imager is garbage, and is one reason why I
> recommend setting up either a real machine, or virtual machine with Linux (
> preferably Debian ) when developing for the beaglebone black.
>
> There is also another options Phil. You can use the beaglebone to write
> the image for you. It's kind of convoluted, but you can build the image on
> your virtual machine, then use sshfs or some other method to transfer the
> file to the beaglebone. This is of course assuming you're able to boot from
> eMMC.
>
> On Wed, Sep 9, 2015 at 12:40 PM, William Hermans 
> wrote:
>
>> So short version. . .
>>
>> Virtualbox main screen -> click settings.
>> subsection "USB" -> click it.
>> On the USB filter section - Far right - Click the second from the top
>> icon that looks like a pen with a plus sign on it.
>>
>> From here, a fly out will popup listing the USB devices virtualbox sees.
>> If your card reader is like most, and is USB based, it should be listed
>> here. Granted, it may be listed as "unknown device" in which case you'll
>> have to experiment and find out which device it is. I would highly
>> recommend disconnecting all other USB storage devices when doing this. To
>> avoid complications related to finding your actual card reader.
>>
>> Once enabling a USB filter on a specific device, click OK, and restart /
>> start your virtual machine. Test / check until you've found the right
>> device.
>>
>>
>> On Wed, Sep 9, 2015 at 12:26 PM, William Hermans 
>> wrote:
>>
>>> Guys . .  it's not the boot bit, and it's not the virtual machine. I use
>>> virtualbox _all_the_time_ and have no such issues.
>>>
>>> @Phil
>>>
>>> What sdcard reader does your laptop have in it ? Name brand, and type.
>>> Chances are pretty good that you're just unaware of how to setup such
>>> devices in the virtualbox config. However, it's not garunteed. Some( a very
>>> few ) devices refuse to work no matter what you do. But I've yet to
>>> personally run into one that won't. Out of the last 3 laptops I've owned
>>> over the last 8 or so years . . .
>>>
>>> Anyhow if i can get the above information from you, I can probably help
>>> you out in setting it up correctly.
>>>
>>> On Wed, Sep 9, 2015 at 11:04 AM, Robert Nelson 
>>> wrote:
>>>
 On Wed, Sep 9, 2015 at 1:01 PM, Graham  wrote:
 > Did you set the "boot" bit on the uSD card?
 > --- Graham

 'boot' bit is set in the raw *.img

 If the vm skipped setting that one bit, who knows what else it
 skipped.. :)

 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.

>>>
>>>
>>
>

-- 
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] Working links to blank-EEPROM flasher image?

[William Hermans]

Also, for the record Win32imager is garbage, and is one reason why I
recommend setting up either a real machine, or virtual machine with Linux (
preferably Debian ) when developing for the beaglebone black.

There is also another options Phil. You can use the beaglebone to write the
image for you. It's kind of convoluted, but you can build the image on your
virtual machine, then use sshfs or some other method to transfer the file
to the beaglebone. This is of course assuming you're able to boot from eMMC.

On Wed, Sep 9, 2015 at 12:40 PM, William Hermans  wrote:

> So short version. . .
>
> Virtualbox main screen -> click settings.
> subsection "USB" -> click it.
> On the USB filter section - Far right - Click the second from the top icon
> that looks like a pen with a plus sign on it.
>
> From here, a fly out will popup listing the USB devices virtualbox sees.
> If your card reader is like most, and is USB based, it should be listed
> here. Granted, it may be listed as "unknown device" in which case you'll
> have to experiment and find out which device it is. I would highly
> recommend disconnecting all other USB storage devices when doing this. To
> avoid complications related to finding your actual card reader.
>
> Once enabling a USB filter on a specific device, click OK, and restart /
> start your virtual machine. Test / check until you've found the right
> device.
>
>
> On Wed, Sep 9, 2015 at 12:26 PM, William Hermans 
> wrote:
>
>> Guys . .  it's not the boot bit, and it's not the virtual machine. I use
>> virtualbox _all_the_time_ and have no such issues.
>>
>> @Phil
>>
>> What sdcard reader does your laptop have in it ? Name brand, and type.
>> Chances are pretty good that you're just unaware of how to setup such
>> devices in the virtualbox config. However, it's not garunteed. Some( a very
>> few ) devices refuse to work no matter what you do. But I've yet to
>> personally run into one that won't. Out of the last 3 laptops I've owned
>> over the last 8 or so years . . .
>>
>> Anyhow if i can get the above information from you, I can probably help
>> you out in setting it up correctly.
>>
>> On Wed, Sep 9, 2015 at 11:04 AM, Robert Nelson 
>> wrote:
>>
>>> On Wed, Sep 9, 2015 at 1:01 PM, Graham  wrote:
>>> > Did you set the "boot" bit on the uSD card?
>>> > --- Graham
>>>
>>> 'boot' bit is set in the raw *.img
>>>
>>> If the vm skipped setting that one bit, who knows what else it skipped..
>>> :)
>>>
>>> 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.
>>>
>>
>>
>

-- 
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] Working links to blank-EEPROM flasher image?

[William Hermans]

So short version. . .

Virtualbox main screen -> click settings.
subsection "USB" -> click it.
On the USB filter section - Far right - Click the second from the top icon
that looks like a pen with a plus sign on it.

>From here, a fly out will popup listing the USB devices virtualbox sees. If
your card reader is like most, and is USB based, it should be listed here.
Granted, it may be listed as "unknown device" in which case you'll have to
experiment and find out which device it is. I would highly recommend
disconnecting all other USB storage devices when doing this. To avoid
complications related to finding your actual card reader.

Once enabling a USB filter on a specific device, click OK, and restart /
start your virtual machine. Test / check until you've found the right
device.


On Wed, Sep 9, 2015 at 12:26 PM, William Hermans  wrote:

> Guys . .  it's not the boot bit, and it's not the virtual machine. I use
> virtualbox _all_the_time_ and have no such issues.
>
> @Phil
>
> What sdcard reader does your laptop have in it ? Name brand, and type.
> Chances are pretty good that you're just unaware of how to setup such
> devices in the virtualbox config. However, it's not garunteed. Some( a very
> few ) devices refuse to work no matter what you do. But I've yet to
> personally run into one that won't. Out of the last 3 laptops I've owned
> over the last 8 or so years . . .
>
> Anyhow if i can get the above information from you, I can probably help
> you out in setting it up correctly.
>
> On Wed, Sep 9, 2015 at 11:04 AM, Robert Nelson 
> wrote:
>
>> On Wed, Sep 9, 2015 at 1:01 PM, Graham  wrote:
>> > Did you set the "boot" bit on the uSD card?
>> > --- Graham
>>
>> 'boot' bit is set in the raw *.img
>>
>> If the vm skipped setting that one bit, who knows what else it skipped..
>> :)
>>
>> 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.
>>
>
>

-- 
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] Working links to blank-EEPROM flasher image?

[William Hermans]

Guys . .  it's not the boot bit, and it's not the virtual machine. I use
virtualbox _all_the_time_ and have no such issues.

@Phil

What sdcard reader does your laptop have in it ? Name brand, and type.
Chances are pretty good that you're just unaware of how to setup such
devices in the virtualbox config. However, it's not garunteed. Some( a very
few ) devices refuse to work no matter what you do. But I've yet to
personally run into one that won't. Out of the last 3 laptops I've owned
over the last 8 or so years . . .

Anyhow if i can get the above information from you, I can probably help you
out in setting it up correctly.

On Wed, Sep 9, 2015 at 11:04 AM, Robert Nelson 
wrote:

> On Wed, Sep 9, 2015 at 1:01 PM, Graham  wrote:
> > Did you set the "boot" bit on the uSD card?
> > --- Graham
>
> 'boot' bit is set in the raw *.img
>
> If the vm skipped setting that one bit, who knows what else it skipped.. :)
>
> 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.
>

-- 
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] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Wed, Sep 9, 2015 at 1:01 PM, Graham  wrote:
> Did you set the "boot" bit on the uSD card?
> --- Graham

'boot' bit is set in the raw *.img

If the vm skipped setting that one bit, who knows what else it skipped.. :)

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] Working links to blank-EEPROM flasher image?

[Graham]

Did you set the "boot" bit on the uSD card?
--- Graham

==

On Wednesday, September 9, 2015 at 12:52:31 PM UTC-5, Phil Mills wrote:
>
> Robert,
>
> I'm not having success - the serial monitor continues to display "C" 
> as soon as it's powered up, so that seems to indicate that it's not finding 
> anything bootable on that SD card with the blank flasher image.
>
>
>1. My setup: 64-bit Debian Jessie (as VirtualBox VM on a Win7 host);  
>2GB uSD card, freshly formatted & overwritten in a uSD->USB converter 
>(Virtualbox won't pass the built-in card reader on my laptop into the VMs)
>16GB uSD card, freshly formatted in a uSD->SD converter
>2. Installed bmaptool ver3.2 via apt-get
>3. Brought 2GB card over to VM
>   1. mounted as /dev/sdd1; did "umount /dev/sdd1" to allow bmaptool 
>   to open w/ exclusive access
>   2. Ran bmaptool as described above - no errors indicated.
>   3. Ejected uSD from VM image, host.
>4. Inserted 16GB uSD into Win7 system, 
>   1. copied 2015-03-01 debian 7.8 image
>   2. copied eeprom dump
>   3. created new job.txt file with contents as described above (UNIX 
>   line endings)
>   4. ejected uSD from Win7
>5. 2GB uSD into reader on BBB
>6. 16GB uSD into USB adapter, then to USB on BBB
>7. Serial cable connected
>8. TP4 grounded to P8-1
>9. Power applied via mini-USB cable
>10. ""
>
> Suggestions or troubleshooting steps?
> I have erased/re-formatted/reloaded the cards 2x with same results.
>
> -phil
>
> On Tuesday, September 8, 2015 at 3:45:03 PM UTC-6, RobertCNelson wrote:
>>
>> On Tue, Sep 8, 2015 at 4:38 PM, Phil Mills  wrote: 
>> > Robert, 
>> > 
>> > Thanks for the prompt (and detailed!) reply.  That's exactly the 
>> information 
>> > I'm trying to find. 
>> > 
>> > ...now I just have to convince our IT staff / McAffee to white-list 
>> your web 
>> > server (if it ain't one thing, it's another) so I can get those files. 
>>
>> make sure to use the https version too.. "https://rcn-ee.com/";  missed 
>> the s in my copy/paste... 
>>
>> > 
>> > This may be useful information to add to a wiki somewhere - I can't be 
>> the 
>> > only person with blank (or inadvertently borked) BBB EEPROMs running 
>> around. 
>>
>> It only sets the initial "code" A335BNLT, just enough to assume to be a 
>> bbb.. 
>>
>> But i don't want it make it too easy.. it's really for 
>> CircuitCo/cm's/cloner's/etc to use.. ;) 
>>
>> and if you are making a "98%" clone that's going to be sold into the 
>> general population, we really want you to contact beagleboard.org and 
>> we have empty bits for you to use for identification.. (the 
>> beaglebone-green is the most recent example..) 
>>
>> 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] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Wed, Sep 9, 2015 at 12:52 PM, Phil Mills  wrote:
> Robert,
>
> I'm not having success - the serial monitor continues to display "C" as
> soon as it's powered up, so that seems to indicate that it's not finding
> anything bootable on that SD card with the blank flasher image.

Yeah... "VirtualBox"

Just use 'win32imager" on the base *.img.xz with Windows 7...

All the vm's are crap when it comes to writing to a microSD card..

>
> My setup: 64-bit Debian Jessie (as VirtualBox VM on a Win7 host);
> 2GB uSD card, freshly formatted & overwritten in a uSD->USB converter
> (Virtualbox won't pass the built-in card reader on my laptop into the VMs)
> 16GB uSD card, freshly formatted in a uSD->SD converter
> Installed bmaptool ver3.2 via apt-get
> Brought 2GB card over to VM
>
> mounted as /dev/sdd1; did "umount /dev/sdd1" to allow bmaptool to open w/
> exclusive access
> Ran bmaptool as described above - no errors indicated.
> Ejected uSD from VM image, host.
>
> Inserted 16GB uSD into Win7 system,
>
> copied 2015-03-01 debian 7.8 image
> copied eeprom dump
> created new job.txt file with contents as described above (UNIX line
> endings)
> ejected uSD from Win7
>
> 2GB uSD into reader on BBB
> 16GB uSD into USB adapter, then to USB on BBB
> Serial cable connected
> TP4 grounded to P8-1
> Power applied via mini-USB cable
> ""
>
> Suggestions or troubleshooting steps?
> I have erased/re-formatted/reloaded the cards 2x with same results.

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] Working links to blank-EEPROM flasher image?

[Phil Mills]

Robert,

I'm not having success - the serial monitor continues to display "C" as 
soon as it's powered up, so that seems to indicate that it's not finding 
anything bootable on that SD card with the blank flasher image.


   1. My setup: 64-bit Debian Jessie (as VirtualBox VM on a Win7 host);  
   2GB uSD card, freshly formatted & overwritten in a uSD->USB converter 
   (Virtualbox won't pass the built-in card reader on my laptop into the VMs)
   16GB uSD card, freshly formatted in a uSD->SD converter
   2. Installed bmaptool ver3.2 via apt-get
   3. Brought 2GB card over to VM
  1. mounted as /dev/sdd1; did "umount /dev/sdd1" to allow bmaptool to 
  open w/ exclusive access
  2. Ran bmaptool as described above - no errors indicated.
  3. Ejected uSD from VM image, host.
   4. Inserted 16GB uSD into Win7 system, 
  1. copied 2015-03-01 debian 7.8 image
  2. copied eeprom dump
  3. created new job.txt file with contents as described above (UNIX 
  line endings)
  4. ejected uSD from Win7
   5. 2GB uSD into reader on BBB
   6. 16GB uSD into USB adapter, then to USB on BBB
   7. Serial cable connected
   8. TP4 grounded to P8-1
   9. Power applied via mini-USB cable
   10. ""

Suggestions or troubleshooting steps?
I have erased/re-formatted/reloaded the cards 2x with same results.

-phil

On Tuesday, September 8, 2015 at 3:45:03 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Sep 8, 2015 at 4:38 PM, Phil Mills  > wrote: 
> > Robert, 
> > 
> > Thanks for the prompt (and detailed!) reply.  That's exactly the 
> information 
> > I'm trying to find. 
> > 
> > ...now I just have to convince our IT staff / McAffee to white-list your 
> web 
> > server (if it ain't one thing, it's another) so I can get those files. 
>
> make sure to use the https version too.. "https://rcn-ee.com/";  missed 
> the s in my copy/paste... 
>
> > 
> > This may be useful information to add to a wiki somewhere - I can't be 
> the 
> > only person with blank (or inadvertently borked) BBB EEPROMs running 
> around. 
>
> It only sets the initial "code" A335BNLT, just enough to assume to be a 
> bbb.. 
>
> But i don't want it make it too easy.. it's really for 
> CircuitCo/cm's/cloner's/etc to use.. ;) 
>
> and if you are making a "98%" clone that's going to be sold into the 
> general population, we really want you to contact beagleboard.org and 
> we have empty bits for you to use for identification.. (the 
> beaglebone-green is the most recent example..) 
>
> 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] Working links to blank-EEPROM flasher image?

[William Hermans]

>
> *Well Intel owns McAfee, rcn-ee.com  only provides ARM
> stuff, and i once*
> * told an Intel recruiter x86 was boring..*
>
> * Not surprised. ;)*


That's pretty funny. Probably since it's true. heh

But when will Intel realize that x86 is boring I wonder ?

On Tue, Sep 8, 2015 at 3:53 PM, Robert Nelson 
wrote:

> On Tue, Sep 8, 2015 at 5:18 PM, Phil Mills  wrote:
> > We're not doing retail distribution, but I'll remind our product manager
> to
> > check in w/ BeagleBoard.org to make sure we're not stepping on toes.
> >
> > As long as I can get it to boot / flash (thank you again!), the scripts
> to
> > get it serialized & date-stamped as part of our configuration sequence
> won't
> > be any trouble at all.
> >
> > While I'm asking questions: is there a good reference script / utility to
> > create an image file (.img.xz format) from an existing BBB ?
>
> https://github.com/beagleboard/image-builder
>
> 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.
>

-- 
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] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Tue, Sep 8, 2015 at 5:18 PM, Phil Mills  wrote:
> We're not doing retail distribution, but I'll remind our product manager to
> check in w/ BeagleBoard.org to make sure we're not stepping on toes.
>
> As long as I can get it to boot / flash (thank you again!), the scripts to
> get it serialized & date-stamped as part of our configuration sequence won't
> be any trouble at all.
>
> While I'm asking questions: is there a good reference script / utility to
> create an image file (.img.xz format) from an existing BBB ?

https://github.com/beagleboard/image-builder

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] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Tue, Sep 8, 2015 at 5:20 PM, Phil Mills  wrote:
> Silly, ain't it.
>
> From the McAfee naughty-naughty screen:
> URL Categories: Malicious Sites, Personal Pages, Technical/Business Forums,
> Malicious Downloads
> Reputation: High Risk (127)

Well Intel owns McAfee, rcn-ee.com only provides ARM stuff, and i once
told an Intel recruiter x86 was boring..

Not surprised. ;)

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] Working links to blank-EEPROM flasher image?

[Phil Mills]

Silly, ain't it.

>From the McAfee naughty-naughty screen:
*URL Categories:* Malicious Sites, Personal Pages, Technical/Business 
Forums, Malicious Downloads 
*Reputation:* High Risk (127)

-phil

On Tuesday, September 8, 2015 at 4:08:44 PM UTC-6, Rick M wrote:
>
>
> > On Sep 8, 2015, at 14:38 , Phil Mills > 
> wrote: 
> > 
> > ...now I just have to convince our IT staff / McAffee to white-list your 
> web server (if it ain't one thing, it's another) so I can get those files. 
>
> Ugh, where do you work that you have such restrictions on servers? 
>
>
> -- 
> Rick Mann 
> rm...@latencyzero.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] Working links to blank-EEPROM flasher image?

[Phil Mills]

We're not doing retail distribution, but I'll remind our product manager to 
check in w/ BeagleBoard.org to make sure we're not stepping on toes. 

As long as I can get it to boot / flash (thank you again!), the scripts to 
get it serialized & date-stamped as part of our configuration sequence 
won't be any trouble at all.

While I'm asking questions: is there a good reference script / utility to 
create an image file (.img.xz format) from an existing BBB ?  

-phil

On Tuesday, September 8, 2015 at 4:04:40 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Sep 8, 2015 at 4:59 PM, Phil Mills  > wrote: 
> > Gerald, 
> > 
> > Robert's given me a workable answer to my question already, so I'm set, 
> BUT 
> > it seems like a pretty heavy-weight option - totally suitable for 
> > manufacturing / mass-production  / other "blank slate" scenarios, but 
> very 
> > heavy for Joe User who's just accidentally typed "i2cset -y 1 -0x50" 
> > with a paperclip in the wrong spot and corrupted the EEPROM on his BBB 
> that 
> > he's spend the last month working on. 
> > 
> > 
> > 
> > Your "I2C writes is what we do" response seems to imply that you've got 
> a 
> > lighter-weight method to edit contents on the EEPROM than what RCN's 
> > described? 
> > 
> > If so, I'd really appreciate a description of how YOU get to an 
> unbootable 
> > BBB to a state where you can write to a blank/corrupted EEPROM. 
>
> CircuitCo actually has two stages. 
>
> First they run my "usbflasher" on all boards to set the initial eeprom.. 
>
> Next all boards go thru a "tester" which adds the unique serial number 
> in eeprom, along with a 100% functionality test.. 
>
> 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] Working links to blank-EEPROM flasher image?

[Rick Mann]

> On Sep 8, 2015, at 14:38 , Phil Mills  wrote:
> 
> ...now I just have to convince our IT staff / McAffee to white-list your web 
> server (if it ain't one thing, it's another) so I can get those files.

Ugh, where do you work that you have such restrictions on servers?


-- 
Rick Mann
rm...@latencyzero.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] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Tue, Sep 8, 2015 at 4:59 PM, Phil Mills  wrote:
> Gerald,
>
> Robert's given me a workable answer to my question already, so I'm set, BUT
> it seems like a pretty heavy-weight option - totally suitable for
> manufacturing / mass-production  / other "blank slate" scenarios, but very
> heavy for Joe User who's just accidentally typed "i2cset -y 1 -0x50"
> with a paperclip in the wrong spot and corrupted the EEPROM on his BBB that
> he's spend the last month working on.
>
>
>
> Your "I2C writes is what we do" response seems to imply that you've got a
> lighter-weight method to edit contents on the EEPROM than what RCN's
> described?
>
> If so, I'd really appreciate a description of how YOU get to an unbootable
> BBB to a state where you can write to a blank/corrupted EEPROM.

CircuitCo actually has two stages.

First they run my "usbflasher" on all boards to set the initial eeprom..

Next all boards go thru a "tester" which adds the unique serial number
in eeprom, along with a 100% functionality test..

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] Working links to blank-EEPROM flasher image?

[Phil Mills]

Gerald,

Robert's given me a workable answer to my question already, so I'm set, BUT 
it seems like a pretty heavy-weight option - totally suitable for 
manufacturing / mass-production  / other "blank slate" scenarios, but very 
heavy for Joe User who's just accidentally typed "i2cset -y 1 -0x50" 
with a paperclip in the wrong spot and corrupted the EEPROM on his BBB that 
he's spend the last month working on.



Your "I2C writes is what we do" response seems to imply that you've got a 
lighter-weight method to edit contents on the EEPROM than what RCN's 
described?

If so, I'd really appreciate a description of how YOU get to an unbootable 
BBB to a state where you can write to a blank/corrupted EEPROM.

-phil

On Tuesday, September 8, 2015 at 3:35:32 PM UTC-6, Gerald wrote:
>
> I2C writes is what we do.
>
> Gerald
>
>
> On Tue, Sep 8, 2015 at 4:32 PM, Phil Mills  > wrote:
>
>> Gerald,
>>
>> I've got the SRM and know the format of the data that needs to get 
>> written there - I'm just stuck on HOW to get it there:
>>
>> Could anyone provide* a good set of instructions for getting access to a 
>>> uBoot prompt* from a stock flasher image OR provide current* links to 
>>> the blank-EEPROM manufacturing images* (or equivalents) that RCN's 
>>> referenced?
>>>
>>
>> The two methods I've seen discussed on the forums are:
>> 1) Manually updating the EEPROM from i2c commands issued within uBoot
>> 2) Using a flasher image with a uBoot build that bypasses the 
>> magic-number-check and writes content to the EEPROM from a command-line 
>> script.
>>
>>
>>
>>
>> On Tuesday, September 8, 2015 at 3:19:29 PM UTC-6, Gerald wrote:
>>>
>>> Take a real BBB and copy the contents if you need to. EEPROM data varies 
>>> with serial number and revision data. But the EEPROM data is described in 
>>> the SRM, is still valid and is not stale or old. 
>>>
>>> Gerald
>>>
>>>
>>> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills  wrote:
>>>
 I have inherited responsibility for a bunch of 3rd-party direct clones 
 of a Beaglebone Black C5 (only known change is in silkscreening).

 Since none of these have any contents written to the onboard EEPROM, 
 they fail to boot with "C" written to the serial console with no uSD 
 card, and 
  

> U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)
> Incorrect magic number (0x) in EEPROM
> Could not get board ID.
> Incorrect magic number (0x) in EEPROM
> Could not get board ID.
> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the 
> board ###


 ...written to the console when I try to boot it from a uSD cards with a 
 stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need to 
 get some good contents into the EEPROM.


 I've been trying to hunt down instructions for how to access the U-Boot 
 prompt to manually write the EEPROM via the i2c bus, but haven't hit any 
 luck there.


 Robert Nelson's posted links in the past to what he's described as the 
 "factory images for flashing boards with blank EEPROMs", but those links 
 (to rcn-ee.org) are stale/dead or behind apparently access-controlled 
 folders on his server.



 Could anyone provide a good set of instructions for getting access to a 
 uBoot prompt from a stock flasher image OR provide current links to the 
 blank-EEPROM manufacturing images (or equivalents) that RCN's referenced?

 -- 
 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...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>> Gerald
>>>  
>>> ger...@beagleboard.org
>>> http://beagleboard.org/
>>>
>> -- 
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Gerald
>  
> ger...@beagleboard.org 
> http://beagleboard.org/
>

-- 
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] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Tue, Sep 8, 2015 at 4:38 PM, Phil Mills  wrote:
> Robert,
>
> Thanks for the prompt (and detailed!) reply.  That's exactly the information
> I'm trying to find.
>
> ...now I just have to convince our IT staff / McAffee to white-list your web
> server (if it ain't one thing, it's another) so I can get those files.

make sure to use the https version too.. "https://rcn-ee.com/";  missed
the s in my copy/paste...

>
> This may be useful information to add to a wiki somewhere - I can't be the
> only person with blank (or inadvertently borked) BBB EEPROMs running around.

It only sets the initial "code" A335BNLT, just enough to assume to be a bbb..

But i don't want it make it too easy.. it's really for
CircuitCo/cm's/cloner's/etc to use.. ;)

and if you are making a "98%" clone that's going to be sold into the
general population, we really want you to contact beagleboard.org and
we have empty bits for you to use for identification.. (the
beaglebone-green is the most recent example..)

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] Working links to blank-EEPROM flasher image?

[Gerald Coley]

Just make sure you ground the Write Protect pin on the EEPROM.

Gerald


On Tue, Sep 8, 2015 at 4:38 PM, Phil Mills  wrote:

> Robert,
>
> Thanks for the prompt (and detailed!) reply.  That's exactly the
> information I'm trying to find.
>
> ...now I just have to convince our IT staff / McAffee to white-list your
> web server (if it ain't one thing, it's another) so I can get those files.
>
> This may be useful information to add to a wiki somewhere - I can't be the
> only person with blank (or inadvertently borked) BBB EEPROMs running
> around.
>
> -phil
>
> On Tuesday, September 8, 2015 at 3:30:18 PM UTC-6, RobertCNelson wrote:
>
>> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills  wrote:
>> > I have inherited responsibility for a bunch of 3rd-party direct clones
>> of a
>> > Beaglebone Black C5 (only known change is in silkscreening).
>> >
>> > Since none of these have any contents written to the onboard EEPROM,
>> they
>> > fail to boot with "C" written to the serial console with no uSD
>> card,
>> > and
>> >
>> >>
>> >> U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)
>> >> Incorrect magic number (0x) in EEPROM
>> >> Could not get board ID.
>> >> Incorrect magic number (0x) in EEPROM
>> >> Could not get board ID.
>> >> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the
>> >> board ###
>> >
>> >
>> > ...written to the console when I try to boot it from a uSD cards with a
>> > stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need
>> to get
>> > some good contents into the EEPROM.
>> >
>> >
>> > I've been trying to hunt down instructions for how to access the U-Boot
>> > prompt to manually write the EEPROM via the i2c bus, but haven't hit
>> any
>> > luck there.
>> >
>> >
>> > Robert Nelson's posted links in the past to what he's described as the
>> > "factory images for flashing boards with blank EEPROMs", but those
>> links (to
>> > rcn-ee.org) are stale/dead or behind apparently access-controlled
>> folders on
>> > his server.
>> >
>> >
>> >
>> > Could anyone provide a good set of instructions for getting access to a
>> > uBoot prompt from a stock flasher image OR provide current links to the
>> > blank-EEPROM manufacturing images (or equivalents) that RCN's
>> referenced?
>>
>> So the "blank-flasher" (did everything by default) went away.  Instead
>> we now have a "usbflasher"..
>>
>> Step 1: (microSD)
>>
>>
>> http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.bmap
>>
>> http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.img.xz
>>
>> (bmaptools 3.2)
>> sudo bmaptools copy --bmap *.bmap *.img.xz /dev/sdX
>>
>> Step 2: (usb drive)
>> Format it as fat32, 2 or 3 files "custom: job.txt" and the image files..
>>
>> For example:
>>
>> to flash: 2015-03-01
>>
>> First download the base image:
>>
>>
>> http://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
>>
>> Then the "eeprom"
>>
>>
>> https://raw.githubusercontent.com/RobertCNelson/boot-scripts/master/device/bone/bbb-eeprom.dump
>>
>> finally crate the "job.txt" file
>>
>> abi=aaa
>> conf_eeprom_file=bbb-eeprom.dump
>> conf_eeprom_compare=335
>> conf_image=bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
>> conf_resize=enable
>> conf_partition1_startmb=1
>> conf_partition1_fstype=0xE
>> conf_partition1_endmb=96
>> conf_partition2_fstype=0x83
>> conf_root_partition=2
>>
>> Step 3: (flashing)
>>
>> Insert "microSD" with usbflasher image bmap'ed to it..
>> Insert "usb flash drive" with
>> bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz, bbb-eeprom.dump
>> & job.txt all in the base directory
>> GND TP4 (write protect on eeprom)
>> Power board
>>
>> Serial Log the first one to make sure it correctly flashes..
>>
>> 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.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
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] Working links to blank-EEPROM flasher image?

[Phil Mills]

Robert,

Thanks for the prompt (and detailed!) reply.  That's exactly the 
information I'm trying to find.

...now I just have to convince our IT staff / McAffee to white-list your 
web server (if it ain't one thing, it's another) so I can get those files.

This may be useful information to add to a wiki somewhere - I can't be the 
only person with blank (or inadvertently borked) BBB EEPROMs running 
around. 

-phil

On Tuesday, September 8, 2015 at 3:30:18 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills  > wrote: 
> > I have inherited responsibility for a bunch of 3rd-party direct clones 
> of a 
> > Beaglebone Black C5 (only known change is in silkscreening). 
> > 
> > Since none of these have any contents written to the onboard EEPROM, 
> they 
> > fail to boot with "C" written to the serial console with no uSD 
> card, 
> > and 
> > 
> >> 
> >> U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06) 
> >> Incorrect magic number (0x) in EEPROM 
> >> Could not get board ID. 
> >> Incorrect magic number (0x) in EEPROM 
> >> Could not get board ID. 
> >> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the 
> >> board ### 
> > 
> > 
> > ...written to the console when I try to boot it from a uSD cards with a 
> > stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need to 
> get 
> > some good contents into the EEPROM. 
> > 
> > 
> > I've been trying to hunt down instructions for how to access the U-Boot 
> > prompt to manually write the EEPROM via the i2c bus, but haven't hit any 
> > luck there. 
> > 
> > 
> > Robert Nelson's posted links in the past to what he's described as the 
> > "factory images for flashing boards with blank EEPROMs", but those links 
> (to 
> > rcn-ee.org) are stale/dead or behind apparently access-controlled 
> folders on 
> > his server. 
> > 
> > 
> > 
> > Could anyone provide a good set of instructions for getting access to a 
> > uBoot prompt from a stock flasher image OR provide current links to the 
> > blank-EEPROM manufacturing images (or equivalents) that RCN's 
> referenced? 
>
> So the "blank-flasher" (did everything by default) went away.  Instead 
> we now have a "usbflasher".. 
>
> Step 1: (microSD) 
>
>
> http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.bmap
>  
>
> http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.img.xz
>  
>
> (bmaptools 3.2) 
> sudo bmaptools copy --bmap *.bmap *.img.xz /dev/sdX 
>
> Step 2: (usb drive) 
> Format it as fat32, 2 or 3 files "custom: job.txt" and the image files.. 
>
> For example: 
>
> to flash: 2015-03-01 
>
> First download the base image: 
>
>
> http://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
>  
>
> Then the "eeprom" 
>
>
> https://raw.githubusercontent.com/RobertCNelson/boot-scripts/master/device/bone/bbb-eeprom.dump
>  
>
> finally crate the "job.txt" file 
>
> abi=aaa 
> conf_eeprom_file=bbb-eeprom.dump 
> conf_eeprom_compare=335 
> conf_image=bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz 
> conf_resize=enable 
> conf_partition1_startmb=1 
> conf_partition1_fstype=0xE 
> conf_partition1_endmb=96 
> conf_partition2_fstype=0x83 
> conf_root_partition=2 
>
> Step 3: (flashing) 
>
> Insert "microSD" with usbflasher image bmap'ed to it.. 
> Insert "usb flash drive" with 
> bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz, bbb-eeprom.dump 
> & job.txt all in the base directory 
> GND TP4 (write protect on eeprom) 
> Power board 
>
> Serial Log the first one to make sure it correctly flashes.. 
>
> 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] Working links to blank-EEPROM flasher image?

[Gerald Coley]

I2C writes is what we do.

Gerald


On Tue, Sep 8, 2015 at 4:32 PM, Phil Mills  wrote:

> Gerald,
>
> I've got the SRM and know the format of the data that needs to get written
> there - I'm just stuck on HOW to get it there:
>
> Could anyone provide* a good set of instructions for getting access to a
>> uBoot prompt* from a stock flasher image OR provide current* links to
>> the blank-EEPROM manufacturing images* (or equivalents) that RCN's
>> referenced?
>>
>
> The two methods I've seen discussed on the forums are:
> 1) Manually updating the EEPROM from i2c commands issued within uBoot
> 2) Using a flasher image with a uBoot build that bypasses the
> magic-number-check and writes content to the EEPROM from a command-line
> script.
>
>
>
>
> On Tuesday, September 8, 2015 at 3:19:29 PM UTC-6, Gerald wrote:
>>
>> Take a real BBB and copy the contents if you need to. EEPROM data varies
>> with serial number and revision data. But the EEPROM data is described in
>> the SRM, is still valid and is not stale or old.
>>
>> Gerald
>>
>>
>> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills  wrote:
>>
>>> I have inherited responsibility for a bunch of 3rd-party direct clones
>>> of a Beaglebone Black C5 (only known change is in silkscreening).
>>>
>>> Since none of these have any contents written to the onboard EEPROM,
>>> they fail to boot with "C" written to the serial console with no uSD
>>> card, and
>>>
>>>
 U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)
 Incorrect magic number (0x) in EEPROM
 Could not get board ID.
 Incorrect magic number (0x) in EEPROM
 Could not get board ID.
 Unknown board, cannot configure pinmux.### ERROR ### Please RESET the
 board ###
>>>
>>>
>>> ...written to the console when I try to boot it from a uSD cards with a
>>> stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need to
>>> get some good contents into the EEPROM.
>>>
>>>
>>> I've been trying to hunt down instructions for how to access the U-Boot
>>> prompt to manually write the EEPROM via the i2c bus, but haven't hit any
>>> luck there.
>>>
>>>
>>> Robert Nelson's posted links in the past to what he's described as the
>>> "factory images for flashing boards with blank EEPROMs", but those links
>>> (to rcn-ee.org) are stale/dead or behind apparently access-controlled
>>> folders on his server.
>>>
>>>
>>>
>>> Could anyone provide a good set of instructions for getting access to a
>>> uBoot prompt from a stock flasher image OR provide current links to the
>>> blank-EEPROM manufacturing images (or equivalents) that RCN's referenced?
>>>
>>> --
>>> 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...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Gerald
>>
>> ger...@beagleboard.org
>> http://beagleboard.org/
>>
> --
> 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.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
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] Working links to blank-EEPROM flasher image?

[Phil Mills]

Gerald,

I've got the SRM and know the format of the data that needs to get written 
there - I'm just stuck on HOW to get it there:

Could anyone provide* a good set of instructions for getting access to a 
> uBoot prompt* from a stock flasher image OR provide current* links to the 
> blank-EEPROM manufacturing images* (or equivalents) that RCN's referenced?
>

The two methods I've seen discussed on the forums are:
1) Manually updating the EEPROM from i2c commands issued within uBoot
2) Using a flasher image with a uBoot build that bypasses the 
magic-number-check and writes content to the EEPROM from a command-line 
script.




On Tuesday, September 8, 2015 at 3:19:29 PM UTC-6, Gerald wrote:
>
> Take a real BBB and copy the contents if you need to. EEPROM data varies 
> with serial number and revision data. But the EEPROM data is described in 
> the SRM, is still valid and is not stale or old. 
>
> Gerald
>
>
> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills  > wrote:
>
>> I have inherited responsibility for a bunch of 3rd-party direct clones of 
>> a Beaglebone Black C5 (only known change is in silkscreening).
>>
>> Since none of these have any contents written to the onboard EEPROM, they 
>> fail to boot with "C" written to the serial console with no uSD card, 
>> and 
>>  
>>
>>> U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)
>>> Incorrect magic number (0x) in EEPROM
>>> Could not get board ID.
>>> Incorrect magic number (0x) in EEPROM
>>> Could not get board ID.
>>> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the 
>>> board ###
>>
>>
>> ...written to the console when I try to boot it from a uSD cards with a 
>> stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need to 
>> get some good contents into the EEPROM.
>>
>>
>> I've been trying to hunt down instructions for how to access the U-Boot 
>> prompt to manually write the EEPROM via the i2c bus, but haven't hit any 
>> luck there.
>>
>>
>> Robert Nelson's posted links in the past to what he's described as the 
>> "factory images for flashing boards with blank EEPROMs", but those links 
>> (to rcn-ee.org) are stale/dead or behind apparently access-controlled 
>> folders on his server.
>>
>>
>>
>> Could anyone provide a good set of instructions for getting access to a 
>> uBoot prompt from a stock flasher image OR provide current links to the 
>> blank-EEPROM manufacturing images (or equivalents) that RCN's referenced?
>>
>> -- 
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Gerald
>  
> ger...@beagleboard.org 
> http://beagleboard.org/
>

-- 
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] Working links to blank-EEPROM flasher image?

[Robert Nelson]

On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills  wrote:
> I have inherited responsibility for a bunch of 3rd-party direct clones of a
> Beaglebone Black C5 (only known change is in silkscreening).
>
> Since none of these have any contents written to the onboard EEPROM, they
> fail to boot with "C" written to the serial console with no uSD card,
> and
>
>>
>> U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)
>> Incorrect magic number (0x) in EEPROM
>> Could not get board ID.
>> Incorrect magic number (0x) in EEPROM
>> Could not get board ID.
>> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the
>> board ###
>
>
> ...written to the console when I try to boot it from a uSD cards with a
> stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need to get
> some good contents into the EEPROM.
>
>
> I've been trying to hunt down instructions for how to access the U-Boot
> prompt to manually write the EEPROM via the i2c bus, but haven't hit any
> luck there.
>
>
> Robert Nelson's posted links in the past to what he's described as the
> "factory images for flashing boards with blank EEPROMs", but those links (to
> rcn-ee.org) are stale/dead or behind apparently access-controlled folders on
> his server.
>
>
>
> Could anyone provide a good set of instructions for getting access to a
> uBoot prompt from a stock flasher image OR provide current links to the
> blank-EEPROM manufacturing images (or equivalents) that RCN's referenced?

So the "blank-flasher" (did everything by default) went away.  Instead
we now have a "usbflasher"..

Step 1: (microSD)

http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.bmap
http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.img.xz

(bmaptools 3.2)
sudo bmaptools copy --bmap *.bmap *.img.xz /dev/sdX

Step 2: (usb drive)
Format it as fat32, 2 or 3 files "custom: job.txt" and the image files..

For example:

to flash: 2015-03-01

First download the base image:

http://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz

Then the "eeprom"

https://raw.githubusercontent.com/RobertCNelson/boot-scripts/master/device/bone/bbb-eeprom.dump

finally crate the "job.txt" file

abi=aaa
conf_eeprom_file=bbb-eeprom.dump
conf_eeprom_compare=335
conf_image=bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
conf_resize=enable
conf_partition1_startmb=1
conf_partition1_fstype=0xE
conf_partition1_endmb=96
conf_partition2_fstype=0x83
conf_root_partition=2

Step 3: (flashing)

Insert "microSD" with usbflasher image bmap'ed to it..
Insert "usb flash drive" with
bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz, bbb-eeprom.dump
& job.txt all in the base directory
GND TP4 (write protect on eeprom)
Power board

Serial Log the first one to make sure it correctly flashes..

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] Working links to blank-EEPROM flasher image?

[Gerald Coley]

Take a real BBB and copy the contents if you need to. EEPROM data varies
with serial number and revision data. But the EEPROM data is described in
the SRM, is still valid and is not stale or old.

Gerald


On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills  wrote:

> I have inherited responsibility for a bunch of 3rd-party direct clones of
> a Beaglebone Black C5 (only known change is in silkscreening).
>
> Since none of these have any contents written to the onboard EEPROM, they
> fail to boot with "C" written to the serial console with no uSD card,
> and
>
>
>> U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)
>> Incorrect magic number (0x) in EEPROM
>> Could not get board ID.
>> Incorrect magic number (0x) in EEPROM
>> Could not get board ID.
>> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the
>> board ###
>
>
> ...written to the console when I try to boot it from a uSD cards with a
> stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need to
> get some good contents into the EEPROM.
>
>
> I've been trying to hunt down instructions for how to access the U-Boot
> prompt to manually write the EEPROM via the i2c bus, but haven't hit any
> luck there.
>
>
> Robert Nelson's posted links in the past to what he's described as the
> "factory images for flashing boards with blank EEPROMs", but those links
> (to rcn-ee.org) are stale/dead or behind apparently access-controlled
> folders on his server.
>
>
>
> Could anyone provide a good set of instructions for getting access to a
> uBoot prompt from a stock flasher image OR provide current links to the
> blank-EEPROM manufacturing images (or equivalents) that RCN's referenced?
>
> --
> 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.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
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] Working links to blank-EEPROM flasher image?

[Phil Mills]

I have inherited responsibility for a bunch of 3rd-party direct clones of a 
Beaglebone Black C5 (only known change is in silkscreening).

Since none of these have any contents written to the onboard EEPROM, they 
fail to boot with "C" written to the serial console with no uSD card, 
and 
 

> U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)
> Incorrect magic number (0x) in EEPROM
> Could not get board ID.
> Incorrect magic number (0x) in EEPROM
> Could not get board ID.
> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the 
> board ###


...written to the console when I try to boot it from a uSD cards with a 
stock BBB image (the 2015-03-01 Debian 7.8 image).  So clearly I need to 
get some good contents into the EEPROM.


I've been trying to hunt down instructions for how to access the U-Boot 
prompt to manually write the EEPROM via the i2c bus, but haven't hit any 
luck there.


Robert Nelson's posted links in the past to what he's described as the 
"factory images for flashing boards with blank EEPROMs", but those links 
(to rcn-ee.org) are stale/dead or behind apparently access-controlled 
folders on his server.



Could anyone provide a good set of instructions for getting access to a 
uBoot prompt from a stock flasher image OR provide current links to the 
blank-EEPROM manufacturing images (or equivalents) that RCN's referenced?

-- 
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.