From:  Brandon I <brandon.ir...@gmail.com>
Reply-To:  <beagleboard@googlegroups.com>
Date:  Friday, February 28, 2014 at 4:34 PM
To:  <beagleboard@googlegroups.com>
Cc:  <jhgo...@gmail.com>
Subject:  Re: [beagleboard] How are the production BBB images built?

>> > Maybe we can become free from SD cards in the near future for BBB
>> development.
> 
> Doesn't uboot support network boot already?
Hi Brandon,

I use u-boot on my BBB to tftp zImage from my desktop and then mount rootfs
via NFS on my desktop. Is that what you want?

Regards,
John
> 
> 
> On Thursday, February 27, 2014 11:29:23 PM UTC-8, jhg...@gmail.com wrote:
>> Robert,
>> 
>> Have you resolved any of these mysteries in the mean time?
>> 
>> I got into this by trying to "bitbake" a simpler image, such as
>> console-image, since I need no graphics or fancy webserver with node.js foo.
>> So far I have failed to boot from the SD card with anything which has been
>> made by the oebb.sh script or bitbake build system. Even Derek's 2-year-old
>> instructions 
>> <http://derekmolloy.ie/building-angstrom-for-beaglebone-from-source/>  seem
>> not to work for "console-image".
>> 
>> After I succeed at booting the BBB with my own custom image, I plan on
>> updating u-boot to allow "fastboot", an feature more commonly supported by
>> Android which allows one to boot or flash over USB, ethernet, etc. Maybe we
>> can become free from SD cards in the near future for BBB development.
>> 
>> Cheers,
>> Joe
>> 
>> On Friday, July 12, 2013 8:30:29 AM UTC-4, Robert P. J. Day wrote:
>>> On Fri, 12 Jul 2013, Chris Morgan wrote:
>>> 
>>>> > On Friday, July 12, 2013, Koen Kooi wrote:
>>>> > 
>>>> >       Op 12 jul. 2013, om 13:46 heeft Robert P. J. Day
>>>> <rpj...@crashcourse.ca> het
>>>> >       volgende geschreven:
>>>> > 
>>>>> >       > On Fri, 12 Jul 2013, Koen Kooi wrote:
>>>>> >       > 
>>>>>> >       >> It's all in the SRM, but for people too lazy to read that:
>>>>>> >       >> 
>>>>>> >       >> ï¿1Ž2 ï¿1Ž2 ï¿1Ž2Read
>>>>>> http://www.angstrom-distribution.org/building-angstrom and follow the
>>>> >       steps outlined there.
>>>>> >       > 
>>>>> >       > ï¿1Ž2gaaaaaah ... i am not interested in the general philosophy 
>>>>> > of
how to 
>>>>> >       > build angstrom, that's *not* the question on the table. the
question 
>>>>> >       > is, which *particular* configuration of angstrom is the one that
>>>>> >       > matches what is currently shipping on the BBB?
>>>> > 
>>>> >       The one I linked above. There is only one configuration of angstrom
>>>> per release and
>>>> >       the above matches the release that ships with the bones.
>>>> > 
>>>> > 
>>>> > Hello. 
>>>> > 
>>>> > I followed those instructions and, although I had selected the yocto
>>>> > 2013 release, I ended up with the component files in the deploy/
>>>> > directory but as rootfs and ubi files, not card images.
>>>> > 
>>>> > The information yesterday about the emmc-prepare.sh and other
>>>> > scripts has helped informationaly, I think I'll be able to build a
>>>> > sd card image today using those steps, but at this point it seems
>>>> > like a multi step process after following the angstrom build steps.
>>> 
>>>   actually, that's what i would have expected ... the primary purpose
>>> of OE/yocto is to build the fundamental images or objects, not so much
>>> to create the final bootable SD card image based on them, since some
>>> people might not want an SD card, they might be, say, trying to
>>> populate a TFTP or NFS server with those images.
>>> 
>>> rday 
>>> 
>>> -- 
>>> 
>>> ========================================================================
>>> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>>>                         http://crashcourse.ca
>>> 
>>> Twitter:                                       http://twitter.com/rpjday
>>> LinkedIn:                               http://ca.linkedin.com/in/rpjday
>>> ========================================================================
> -- 
> 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/groups/opt_out.


-- 
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/groups/opt_out.

Reply via email to