From: <[email protected]> Reply-To: <[email protected]> Date: Friday, February 21, 2014 at 10:51 PM To: <[email protected]> Subject: [beagleboard] Re: Latest image Angstrom Distribution BBB 2GB eMMC 2013-09-04 reports as Angstrom v2012.12?
> Hi Bruce :) I am having the same issue. > Do you have a solution? > Regards Andrew If you want the latest Angstrom, you need to checkout the following branch: git checkout angstrom-v2013.12-yocto1.5 If you change the branch, be sure to delete or rename the complete build folder. You will also have to redo the config: MACHINE=beaglebone ./oebb.sh config beaglebone MACHINE=beaglebone ./oebb.sh update Refresh you environment: . ./environment-angstrom-v2013.12 Note, that line has a dot, space and then ./environment-angstrom-v2013.12 After that, you can now build V2013.12. Regards, John > > > On Sunday, January 19, 2014 9:56:14 AM UTC+11, [email protected] wrote: >> Hi, >> >> I installed the latest image Angstrom Distribution (BeagleBone Black - 2GB >> eMMC) 2013-09-04 from >> https://s3.amazonaws.com/angstrom/demo/beaglebone/BBB-eMMC-flasher-2013.09.04 >> .img.xz and installed it on my shinny new BBB, I waited for the 4 LEDs to go >> solid then I removed the SD card and booted it. When I SSH in, it reports >> the version as: >> ro...@beaglebone <javascript:> :~# cat /etc/angstrom-version >> Angstrom v2012.12 (Core edition) >> Built from branch: angstrom-staging-yocto1.3 >> Revision: 2ac8ed60f1c4152577f334b223b9203f57ed1722 >> Target system: arm-angstrom-linux-gnueabi >> >> As well, when I do opkg update/opkg upgrade, it seems to be pulling packages >> from V2012.12 feed rather than V2013.12 feed. >> >> Is this expected? Did I make a mistake somewhere? Did the new image really >> get burned to eMMC? >> >> Thanks, >> Bruce > > > On Sunday, January 19, 2014 9:56:14 AM UTC+11, [email protected] wrote: >> Hi, >> >> I installed the latest image Angstrom Distribution (BeagleBone Black - 2GB >> eMMC) 2013-09-04 from >> https://s3.amazonaws.com/angstrom/demo/beaglebone/BBB-eMMC-flasher-2013.09.04 >> .img.xz and installed it on my shinny new BBB, I waited for the 4 LEDs to go >> solid then I removed the SD card and booted it. When I SSH in, it reports >> the version as: >> ro...@beaglebone <javascript:> :~# cat /etc/angstrom-version >> Angstrom v2012.12 (Core edition) >> Built from branch: angstrom-staging-yocto1.3 >> Revision: 2ac8ed60f1c4152577f334b223b9203f57ed1722 >> Target system: arm-angstrom-linux-gnueabi >> >> As well, when I do opkg update/opkg upgrade, it seems to be pulling packages >> from V2012.12 feed rather than V2013.12 feed. >> >> Is this expected? Did I make a mistake somewhere? Did the new image really >> get burned to eMMC? >> >> Thanks, >> Bruce > > -- > 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
