https://elinux.org/api.php?action=feedcontributions&user=Jayneil&feedformat=atomeLinux.org - User contributions [en]2024-03-19T07:17:54ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=Minnowboard:MAX&diff=322400Minnowboard:MAX2014-04-11T21:54:00Z<p>Jayneil: Created the MinnowBoard MAX landing page</p>
<hr />
<div>[[File:MinnowBoard_MAX-Top-Angled.jpg|700px|MinnowBoard MAX|center]] [[File:Minnowboard.org.png|center|800px]]<br />
__NOTOC__</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:MinnowBoard&diff=322358Minnowboard:MinnowBoard2014-04-10T23:06:19Z<p>Jayneil: </p>
<hr />
<div>[[File:Minnowboard.org.png|center]]<br />
<br />
__NOTOC__<br />
= Introduction =<br />
<br />
http://www.minnowboard.org is a community dedicated to the support of Open Hardware utilizing Intel® processors. This web site will serve as a starting point for the MinnowBoard community.<br />
<br />
The MinnowBoard is an Intel® Atom™ processor based board which introduces Intel® Architecture to the small and low cost embedded market for the developer and maker community. It has exceptional performance, flexibility, openness and standards<br />
<br />
= Boards =<br />
<br />
<br />
<br />
{| border="1" style="background:transparent;"<br />
| style="width:180%; align:left;vertical-align:top; border:1px solid #aaa; padding-left:5px;"|<br />
=MinnowBoard MAX=<br />
[[File:MinnowBoard_MAX-Top-Angled.jpg|510px|MinnowBoard MAX|center]]<br />
| style="width:180%; vertical-align:top; border:1px solid #aaa; padding-left:5px;"|<br />
=[http://elinux.org/Minnowboard:Minnow_Original MinnowBoard]=<br />
[[File:MinnowRevA-Angled2.jpg|470px|link=Minnowboard:Minnow_Original]]<br />
<br />
|}<br />
<br />
=Community=<br />
*IRC: Freenode network, Channel: #minnowboard<br />
*[http://lists.elinux.org/pipermail/elinux-minnowboard/ Mailing List archives]<br />
<br />
<br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:MinnowBoard&diff=322352Minnowboard:MinnowBoard2014-04-10T23:04:46Z<p>Jayneil: /* Community */</p>
<hr />
<div>[[File:Minnowboard.org.png|center]]<br />
<br />
__NOTOC__<br />
= Introduction =<br />
<br />
http://www.minnowboard.org is a community dedicated to the support of Open Hardware utilizing Intel® processors. This web site will serve as a starting point for the MinnowBoard community.<br />
<br />
The MinnowBoard is an Intel® Atom™ processor based board which introduces Intel® Architecture to the small and low cost embedded market for the developer and maker community. It has exceptional performance, flexibility, openness and standards<br />
<br />
= Boards =<br />
<br />
Click on the appropriate board to be redirected to its page:<br />
<br />
{| border="1" style="background:transparent;"<br />
| style="width:180%; align:left;vertical-align:top; border:1px solid #aaa; padding-left:5px;"|<br />
=MinnowBoard MAX=<br />
[[File:MinnowBoard_MAX-Top-Angled.jpg|510px|MinnowBoard MAX|center]]<br />
| style="width:180%; vertical-align:top; border:1px solid #aaa; padding-left:5px;"|<br />
=[http://elinux.org/Minnowboard:Minnow_Original MinnowBoard]=<br />
[[File:MinnowRevA-Angled2.jpg|470px|link=Minnowboard:Minnow_Original]]<br />
<br />
|}<br />
<br />
=Community=<br />
*IRC: Freenode network, Channel: #minnowboard<br />
*[http://lists.elinux.org/pipermail/elinux-minnowboard/ Mailing List archives]<br />
<br />
<br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:MinnowBoard&diff=322346Minnowboard:MinnowBoard2014-04-10T23:02:46Z<p>Jayneil: /* Boards */</p>
<hr />
<div>[[File:Minnowboard.org.png|center]]<br />
<br />
__NOTOC__<br />
= Introduction =<br />
<br />
http://www.minnowboard.org is a community dedicated to the support of Open Hardware utilizing Intel® processors. This web site will serve as a starting point for the MinnowBoard community.<br />
<br />
The MinnowBoard is an Intel® Atom™ processor based board which introduces Intel® Architecture to the small and low cost embedded market for the developer and maker community. It has exceptional performance, flexibility, openness and standards<br />
<br />
= Boards =<br />
<br />
Click on the appropriate board to be redirected to its page:<br />
<br />
{| border="1" style="background:transparent;"<br />
| style="width:180%; align:left;vertical-align:top; border:1px solid #aaa; padding-left:5px;"|<br />
=MinnowBoard MAX=<br />
[[File:MinnowBoard_MAX-Top-Angled.jpg|510px|MinnowBoard MAX|center]]<br />
| style="width:180%; vertical-align:top; border:1px solid #aaa; padding-left:5px;"|<br />
=[http://elinux.org/Minnowboard:Minnow_Original MinnowBoard]=<br />
[[File:MinnowRevA-Angled2.jpg|470px|link=Minnowboard:Minnow_Original]]<br />
<br />
|}<br />
<br />
=Community=<br />
Feel free to join the Minnowboard community on IRC.<br />
* Freenode network, Channel: #minnowboard<br />
<br />
<br />
<br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:Minnow_Original&diff=322340Minnowboard:Minnow Original2014-04-10T21:22:25Z<p>Jayneil: Resized the Minnowboard.org logo to 800px</p>
<hr />
<div><br />
<br />
<br />
[[File:MinnowRevA-Angled2.jpg|500px|center]] [[File:Minnowboard.org.png|center|800px]]<br />
__NOTOC__<br />
<br />
<br />
<br />
<br />
<br />
{| border="1" style="background:transparent;"<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
=== Documentation ===<br />
----<br />
*Beginner friendly instructions/documentation available from [http://elinux.org/Minnowboard:Basics here]<br />
*Have you developed a project with MinnowBoard you'd like to share? Please do so here on our [[Minnowboard:Projects|Community Projects]] page.<br />
*Interested in documentation? Please read the article [http://elinux.org/How_to_Contribute_MinnowBoard_Documentation "How to contribute to MinnowBoard Documentation] to quickly help you get started.<br />
* [http://elinux.org/Minnowboard:Building_Angstrom_Linux_for_the_MinnowBoard Building Angstrom Linux for the MinnowBoard]<br />
* [http://elinux.org/Minnowboard:Debian_Bare_Minimum_Bootstrapping Installing Debian on your MinnowBoard]<br />
* [http://files.minnowboard.org/pdfs/Installing%20Windows%20on%20the%20MinnowBoard.pdf Installing Windows 8.1 on the MinnowBoard] (PDF, 800kB)<br />
*Accessory boards for the MinnowBoard are called Lure Boards. There are several types and sizes of these boards available. The specifications and reference board information is available on the [[MinnowBoard:Lures_Specifications|Lures Specifications]] wiki page.<br />
<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
<br />
=== Design Files ===<br />
----<br />
Below you can download the MinnowBoard design files:<br />
<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_Schematics_002-003195_REVA_CCR.pdf Schematics – PDF (877 kb)]<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_BRD.zip Allegro board design file], can be viewed in the free [http://www.cadence.com/products/pcb/Pages/downloads.aspx Allegro Physical Viewer] program (4.1 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_ORCAD_002-003195_REVA_CCR.DSN ORCAD design file] – readable in ORCAD v16 or newer (13.6 MB)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_CAD_RevA_CDC2FAB.zip Generic .CAD file] (1.6 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_MFG.zip Manufacturing files] – including Gerber data, drill data, DXF and PDF drawing files, component X-Y list, and IPC netlist extract (3.0 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_ASSY_and_FAB_PDFs.zip Assembly and fabrication documents] – PDF (194 kb, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_BOM_002-003195_REVA_CCR_BOM.XLSX BOM] – Bill of Materials (28 kb)<br />
<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
<br />
=== Resources ===<br />
----<br />
* [http://www.minnowboard.org MinnowBoard Project Page]<br />
* [http://www.intel.com/content/www/us/en/intelligent-systems/queens-bay/embedded-intel-atom-e6xx-series-with-intel-platform-controller-hub-eg20t.html Intel Atom E6xx Pages]<br />
* [http://uefidk.intel.com/content/minnowboard-uefi-firmware MinnowBoard UEFI Open Development Community]<br />
* [[Minnowboard:Minnow_Accessories|MinnowBoard Accessory List]]<br />
* [[Minnowboard:Expansion_Interfaces|MinnowBoard Expansion Interface Descriptions]]<br />
* [[Minnowboard:SPI_Boot_flash|MinnowBoard SPI Serial Flash Memory Programming]]<br />
* [[Minnowboard:FAQ|MinnowBoard FAQ]]<br />
* [[Minnowboard:Hardware_Revisions|MinnowBoard Hardware Revisions]]<br />
* [[Minnowboard:Jumpers_and_Headers|Jumpers and Headers on the MinnowBoard]]<br />
|}<br />
<br />
<br />
<br><br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:MinnowBoard&diff=322334Minnowboard:MinnowBoard2014-04-10T20:58:50Z<p>Jayneil: /* Boards */</p>
<hr />
<div>[[File:Minnowboard.org.png|center]]<br />
<br />
__NOTOC__<br />
= Introduction =<br />
<br />
http://www.minnowboard.org is a community dedicated to the support of Open Hardware utilizing Intel® processors. This web site will serve as a starting point for the MinnowBoard community.<br />
<br />
The MinnowBoard is an Intel® Atom™ processor based board which introduces Intel® Architecture to the small and low cost embedded market for the developer and maker community. It has exceptional performance, flexibility, openness and standards<br />
<br />
= Boards =<br />
[[File:MinnowBoard_MAX-Top-Angled.jpg|550px|MinnowBoard MAX]]<br />
[[File:MinnowRevA-Angled2.jpg|440px|link=Minnowboard:Minnow_Original]]<br />
<br />
=Community=<br />
Feel free to join the Minnowboard community on IRC.<br />
* Freenode network, Channel: #minnowboard<br />
<br />
<br />
<br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:MinnowBoard&diff=322328Minnowboard:MinnowBoard2014-04-10T20:58:17Z<p>Jayneil: Clean design</p>
<hr />
<div>[[File:Minnowboard.org.png|center]]<br />
<br />
__NOTOC__<br />
= Introduction =<br />
<br />
http://www.minnowboard.org is a community dedicated to the support of Open Hardware utilizing Intel® processors. This web site will serve as a starting point for the MinnowBoard community.<br />
<br />
The MinnowBoard is an Intel® Atom™ processor based board which introduces Intel® Architecture to the small and low cost embedded market for the developer and maker community. It has exceptional performance, flexibility, openness and standards<br />
<br />
= Boards =<br />
[[File:MinnowBoard_MAX-Top-Angled.jpg|550px|MinnowBoard MAX|link=Minnowboard:Minnow_Original]]<br />
[[File:MinnowRevA-Angled2.jpg|440px]]<br />
<br />
=Community=<br />
Feel free to join the Minnowboard community on IRC.<br />
* Freenode network, Channel: #minnowboard<br />
<br />
<br />
<br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]</div>Jayneilhttps://elinux.org/index.php?title=File:MinnowBoard_MAX-Top-Angled.jpg&diff=322322File:MinnowBoard MAX-Top-Angled.jpg2014-04-10T20:47:02Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:MinnowBoard&diff=322316Minnowboard:MinnowBoard2014-04-10T19:59:16Z<p>Jayneil: Removed the minnowboard template at the bottom</p>
<hr />
<div>[[File:Minnowboard.org.png|center]]<br />
<br />
__NOTOC__<br />
= Introduction =<br />
<br />
http://www.minnowboard.org is a community dedicated to the support of Open Hardware utilizing Intel® processors. This web site will serve as a starting point for the MinnowBoard community.<br />
<br />
The MinnowBoard is an Intel® Atom™ processor based board which introduces Intel® Architecture to the small and low cost embedded market for the developer and maker community. It has exceptional performance, flexibility, openness and standards<br />
<br />
=Documentation=<br />
<br />
==Getting Started==<br />
Excited to explore the MinnowBoard? Beginner friendly instructions/documentation available from [http://elinux.org/Minnowboard:Basics here]<br />
<br />
==Community==<br />
Feel free to join the Minnowboard community on IRC.<br />
* Freenode network, Channel: #minnowboard<br />
<br />
==MinnowBoard Projects==<br />
<br />
Have you developed a project with MinnowBoard you'd like to share? Please do so here:<br />
<br />
[[Minnowboard:Projects|Community Projects]]<br />
<br />
==OS Support==<br />
We'd love to have documents written on the following topics:<br />
<br />
* [http://elinux.org/Minnowboard:Building_Angstrom_Linux_for_the_MinnowBoard Building Angstrom Linux for the MinnowBoard]<br />
* Building Poky Linux for the Minnowboard<br />
* [http://elinux.org/Minnowboard:Debian_Bare_Minimum_Bootstrapping Installing Debian on your MinnowBoard]<br />
* [http://files.minnowboard.org/pdfs/Installing%20Windows%20on%20the%20MinnowBoard.pdf Installing Windows 8.1 on the MinnowBoard] (PDF, 800kB)<br />
<br />
==Contribute to Documentation==<br />
Please read the article [http://elinux.org/How_to_Contribute_MinnowBoard_Documentation "How to contribute to MinnowBoard Documentation] to quickly help you get started.<br />
<br />
= Accessory Boards =<br />
<br />
Accessory boards for the MinnowBoard are called Lure Boards. There are several types and sizes of these boards available. The specifcations and reference board information is available on the [[MinnowBoard:Lures_Specifications|Lures Specifications]] wiki page.<br />
<br />
=Design Files=<br />
Below you can download the MinnowBoard design files:<br />
<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_Schematics_002-003195_REVA_CCR.pdf Schematics – PDF (877 kb)]<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_BRD.zip Allegro board design file], can be viewed in the free [http://www.cadence.com/products/pcb/Pages/downloads.aspx Allegro Physical Viewer] program (4.1 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_ORCAD_002-003195_REVA_CCR.DSN ORCAD design file] – readable in ORCAD v16 or newer (13.6 MB)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_CAD_RevA_CDC2FAB.zip Generic .CAD file] (1.6 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_MFG.zip Manufacturing files] – including Gerber data, drill data, DXF and PDF drawing files, component X-Y list, and IPC netlist extract (3.0 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_ASSY_and_FAB_PDFs.zip Assembly and fabrication documents] – PDF (194 kb, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_BOM_002-003195_REVA_CCR_BOM.XLSX BOM] – Bill of Materials (28 kb)<br />
<br />
= Resources =<br />
<br />
* [http://www.minnowboard.org MinnowBoard Project Page]<br />
* [http://www.intel.com/content/www/us/en/intelligent-systems/queens-bay/embedded-intel-atom-e6xx-series-with-intel-platform-controller-hub-eg20t.html Intel Atom E6xx Pages]<br />
* [http://uefidk.intel.com/content/minnowboard-uefi-firmware MinnowBoard UEFI Open Development Community]<br />
* [[Minnowboard:Minnow_Accessories|MinnowBoard Accessory List]]<br />
* [[Minnowboard:Expansion_Interfaces|MinnowBoard Expansion Interface Descriptions]]<br />
* [[Minnowboard:SPI_Boot_flash|MinnowBoard SPI Serial Flash Memory Programming]]<br />
* [[Minnowboard:FAQ|MinnowBoard FAQ]]<br />
* [[Minnowboard:Hardware_Revisions|MinnowBoard Hardware Revisions]]<br />
* [[Minnowboard:Jumpers_and_Headers|Jumpers and Headers on the MinnowBoard]]<br />
<br><br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:Minnow_Original&diff=322310Minnowboard:Minnow Original2014-04-10T19:56:51Z<p>Jayneil: Tabular columns</p>
<hr />
<div><br />
<br />
<br />
[[File:MinnowRevA-Angled2.jpg|500px|center]] [[File:Minnowboard.org.png|center]]<br />
__NOTOC__<br />
<br />
<br />
<br />
<br />
<br />
{| border="1" style="background:transparent;"<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
=== Documentation ===<br />
----<br />
*Beginner friendly instructions/documentation available from [http://elinux.org/Minnowboard:Basics here]<br />
*Have you developed a project with MinnowBoard you'd like to share? Please do so here on our [[Minnowboard:Projects|Community Projects]] page.<br />
*Interested in documentation? Please read the article [http://elinux.org/How_to_Contribute_MinnowBoard_Documentation "How to contribute to MinnowBoard Documentation] to quickly help you get started.<br />
* [http://elinux.org/Minnowboard:Building_Angstrom_Linux_for_the_MinnowBoard Building Angstrom Linux for the MinnowBoard]<br />
* [http://elinux.org/Minnowboard:Debian_Bare_Minimum_Bootstrapping Installing Debian on your MinnowBoard]<br />
* [http://files.minnowboard.org/pdfs/Installing%20Windows%20on%20the%20MinnowBoard.pdf Installing Windows 8.1 on the MinnowBoard] (PDF, 800kB)<br />
*Accessory boards for the MinnowBoard are called Lure Boards. There are several types and sizes of these boards available. The specifications and reference board information is available on the [[MinnowBoard:Lures_Specifications|Lures Specifications]] wiki page.<br />
<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
<br />
=== Design Files ===<br />
----<br />
Below you can download the MinnowBoard design files:<br />
<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_Schematics_002-003195_REVA_CCR.pdf Schematics – PDF (877 kb)]<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_BRD.zip Allegro board design file], can be viewed in the free [http://www.cadence.com/products/pcb/Pages/downloads.aspx Allegro Physical Viewer] program (4.1 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_ORCAD_002-003195_REVA_CCR.DSN ORCAD design file] – readable in ORCAD v16 or newer (13.6 MB)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_CAD_RevA_CDC2FAB.zip Generic .CAD file] (1.6 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_MFG.zip Manufacturing files] – including Gerber data, drill data, DXF and PDF drawing files, component X-Y list, and IPC netlist extract (3.0 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_ASSY_and_FAB_PDFs.zip Assembly and fabrication documents] – PDF (194 kb, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_BOM_002-003195_REVA_CCR_BOM.XLSX BOM] – Bill of Materials (28 kb)<br />
<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
<br />
=== Resources ===<br />
----<br />
* [http://www.minnowboard.org MinnowBoard Project Page]<br />
* [http://www.intel.com/content/www/us/en/intelligent-systems/queens-bay/embedded-intel-atom-e6xx-series-with-intel-platform-controller-hub-eg20t.html Intel Atom E6xx Pages]<br />
* [http://uefidk.intel.com/content/minnowboard-uefi-firmware MinnowBoard UEFI Open Development Community]<br />
* [[Minnowboard:Minnow_Accessories|MinnowBoard Accessory List]]<br />
* [[Minnowboard:Expansion_Interfaces|MinnowBoard Expansion Interface Descriptions]]<br />
* [[Minnowboard:SPI_Boot_flash|MinnowBoard SPI Serial Flash Memory Programming]]<br />
* [[Minnowboard:FAQ|MinnowBoard FAQ]]<br />
* [[Minnowboard:Hardware_Revisions|MinnowBoard Hardware Revisions]]<br />
* [[Minnowboard:Jumpers_and_Headers|Jumpers and Headers on the MinnowBoard]]<br />
|}<br />
<br />
<br />
<br><br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:Minnow_Original&diff=322304Minnowboard:Minnow Original2014-04-10T19:26:00Z<p>Jayneil: </p>
<hr />
<div><br />
<br />
<br />
[[File:MinnowRevA-Angled2.jpg|500px|center]] [[File:Minnowboard.org.png|center]]<br />
__NOTOC__<br />
<br />
<br />
<br />
<br />
<br />
{| border="1" style="background:transparent;"<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
=== [[Buying RPi|Buying Guide]] ===<br />
----<br />
Where can I get one and for how much?<br />
<br />
* Base price is $25 for the model A and $35 for the model B Raspberry Pi. This price excludes local taxes and shipping.<br />
<br />
* The Raspberry Pi's official worldwide distribution partners are [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components]<br />
* Detailed information and other resellers can be found on the [[RPi Buying | Buying Guide]] page.<br />
<br />
* You can find out which peripherals and such are tested to work with the Pi in the [[RPi_VerifiedPeripherals | Verified Peripherals]] section<br />
<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
<br />
=== [[RPi Hardware Basic Setup|Basic Setup]] ===<br />
----<br />
First little Raspberry Pi Steps...<br />
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.<br />
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.<br />
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]<br />
* If you are not using a HDMI monitor you may need to set up the correct video mode by editing the [[RPiconfig]] text file on the SD-card.<br />
* Note: On the Debian OS after you log in you need to type '''startx''' at the prompt to get a graphic desktop.<br />
* Particularly after first boot its important to do a clean shutdown with the command '''sudo halt'''<br />
<br />
* '''Having problems? Try the [[R-Pi_Troubleshooting | Troubleshooting]] page.'''<br />
<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
<br />
=== Resources ===<br />
----<br />
* [http://www.minnowboard.org MinnowBoard Project Page]<br />
* [http://www.intel.com/content/www/us/en/intelligent-systems/queens-bay/embedded-intel-atom-e6xx-series-with-intel-platform-controller-hub-eg20t.html Intel Atom E6xx Pages]<br />
* [http://uefidk.intel.com/content/minnowboard-uefi-firmware MinnowBoard UEFI Open Development Community]<br />
* [[Minnowboard:Minnow_Accessories|MinnowBoard Accessory List]]<br />
* [[Minnowboard:Expansion_Interfaces|MinnowBoard Expansion Interface Descriptions]]<br />
* [[Minnowboard:SPI_Boot_flash|MinnowBoard SPI Serial Flash Memory Programming]]<br />
* [[Minnowboard:FAQ|MinnowBoard FAQ]]<br />
* [[Minnowboard:Hardware_Revisions|MinnowBoard Hardware Revisions]]<br />
* [[Minnowboard:Jumpers_and_Headers|Jumpers and Headers on the MinnowBoard]]<br />
|}<br />
<br />
==Getting Started==<br />
Excited to explore the MinnowBoard? Beginner friendly instructions/documentation available from [http://elinux.org/Minnowboard:Basics here]<br />
<br />
==MinnowBoard Projects==<br />
<br />
Have you developed a project with MinnowBoard you'd like to share? Please do so here:<br />
<br />
[[Minnowboard:Projects|Community Projects]]<br />
<br />
==OS Support==<br />
We'd love to have documents written on the following topics:<br />
<br />
* [http://elinux.org/Minnowboard:Building_Angstrom_Linux_for_the_MinnowBoard Building Angstrom Linux for the MinnowBoard]<br />
* Building Poky Linux for the Minnowboard<br />
* [http://elinux.org/Minnowboard:Debian_Bare_Minimum_Bootstrapping Installing Debian on your MinnowBoard]<br />
* [http://files.minnowboard.org/pdfs/Installing%20Windows%20on%20the%20MinnowBoard.pdf Installing Windows 8.1 on the MinnowBoard] (PDF, 800kB)<br />
<br />
==Contribute to Documentation==<br />
Please read the article [http://elinux.org/How_to_Contribute_MinnowBoard_Documentation "How to contribute to MinnowBoard Documentation] to quickly help you get started.<br />
<br />
= Accessory Boards =<br />
<br />
Accessory boards for the MinnowBoard are called Lure Boards. There are several types and sizes of these boards available. The specifcations and reference board information is available on the [[MinnowBoard:Lures_Specifications|Lures Specifications]] wiki page.<br />
<br />
=Design Files=<br />
Below you can download the MinnowBoard design files:<br />
<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_Schematics_002-003195_REVA_CCR.pdf Schematics – PDF (877 kb)]<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_BRD.zip Allegro board design file], can be viewed in the free [http://www.cadence.com/products/pcb/Pages/downloads.aspx Allegro Physical Viewer] program (4.1 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_ORCAD_002-003195_REVA_CCR.DSN ORCAD design file] – readable in ORCAD v16 or newer (13.6 MB)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_CAD_RevA_CDC2FAB.zip Generic .CAD file] (1.6 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_MFG.zip Manufacturing files] – including Gerber data, drill data, DXF and PDF drawing files, component X-Y list, and IPC netlist extract (3.0 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_ASSY_and_FAB_PDFs.zip Assembly and fabrication documents] – PDF (194 kb, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_BOM_002-003195_REVA_CCR_BOM.XLSX BOM] – Bill of Materials (28 kb)<br />
<br />
<br />
<br><br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]<br />
{{Template:MinnowBoard}}</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:Minnow_Original&diff=322298Minnowboard:Minnow Original2014-04-10T19:21:21Z<p>Jayneil: </p>
<hr />
<div><br />
<br />
<br />
[[File:MinnowRevA-Angled2.jpg|500px|center]] [[File:Minnowboard.org.png|center]]<br />
__NOTOC__<br />
<br />
<br />
<br />
<br />
=Documentation=<br />
<br />
{| border="1" style="background:transparent;"<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
=== [[Buying RPi|Buying Guide]] ===<br />
----<br />
Where can I get one and for how much?<br />
<br />
* Base price is $25 for the model A and $35 for the model B Raspberry Pi. This price excludes local taxes and shipping.<br />
<br />
* The Raspberry Pi's official worldwide distribution partners are [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components]<br />
* Detailed information and other resellers can be found on the [[RPi Buying | Buying Guide]] page.<br />
<br />
* You can find out which peripherals and such are tested to work with the Pi in the [[RPi_VerifiedPeripherals | Verified Peripherals]] section<br />
<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
<br />
=== [[RPi Hardware Basic Setup|Basic Setup]] ===<br />
----<br />
First little Raspberry Pi Steps...<br />
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.<br />
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.<br />
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]<br />
* If you are not using a HDMI monitor you may need to set up the correct video mode by editing the [[RPiconfig]] text file on the SD-card.<br />
* Note: On the Debian OS after you log in you need to type '''startx''' at the prompt to get a graphic desktop.<br />
* Particularly after first boot its important to do a clean shutdown with the command '''sudo halt'''<br />
<br />
* '''Having problems? Try the [[R-Pi_Troubleshooting | Troubleshooting]] page.'''<br />
<br />
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |<br />
<br />
=== [[RPi Beginners|Beginners Guide]] ===<br />
----<br />
You've just got your new Raspberry Pi device - what now?<br />
* [[RPi Beginners|Beginners Guide]]<br />
<br />
* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.<br />
<br />
* Read a small book for the Raspberry Pi Beginner [http://bitkistl.blogspot.co.at/2013/01/raspberry-pi-e-book.html]<br />
<br />
* Get started with some basic projects and tutorials:<br />
**[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials]<br /><br />
**[http://www.pibeginners.com Raspberry Pi IV Beginners]<br /><br />
**[http://www.youtube.com/playlist?list=PLgyU3jNA6VjS3ij6ZXbb2x4GdEP3bAWzO My First Raspberry Pi Game]<br />
**[http://files.nathanbookham.com/raspberry-pi Guides, tutorials, tools and distribution downloads]<br />
<br />
*[[RPi Tutorial Easy GPIO Hardware & Software|Easy GPIO Hardware & Software]] - in-progress at the moment<br />
<br />
* Take a look through the [[#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.<br />
<br />
* Pick up a copy of [http://www.pi-supply.com/product/raspberry-pi-handbook/ the Raspberry Pi Handbook] to get you started on some fantastic projects<br />
* Get started with Linux: [http://raspberrywebserver.com/linux-basics/ Linux Basics]<br />
|}<br />
<br />
==Getting Started==<br />
Excited to explore the MinnowBoard? Beginner friendly instructions/documentation available from [http://elinux.org/Minnowboard:Basics here]<br />
<br />
==MinnowBoard Projects==<br />
<br />
Have you developed a project with MinnowBoard you'd like to share? Please do so here:<br />
<br />
[[Minnowboard:Projects|Community Projects]]<br />
<br />
==OS Support==<br />
We'd love to have documents written on the following topics:<br />
<br />
* [http://elinux.org/Minnowboard:Building_Angstrom_Linux_for_the_MinnowBoard Building Angstrom Linux for the MinnowBoard]<br />
* Building Poky Linux for the Minnowboard<br />
* [http://elinux.org/Minnowboard:Debian_Bare_Minimum_Bootstrapping Installing Debian on your MinnowBoard]<br />
* [http://files.minnowboard.org/pdfs/Installing%20Windows%20on%20the%20MinnowBoard.pdf Installing Windows 8.1 on the MinnowBoard] (PDF, 800kB)<br />
<br />
==Contribute to Documentation==<br />
Please read the article [http://elinux.org/How_to_Contribute_MinnowBoard_Documentation "How to contribute to MinnowBoard Documentation] to quickly help you get started.<br />
<br />
= Accessory Boards =<br />
<br />
Accessory boards for the MinnowBoard are called Lure Boards. There are several types and sizes of these boards available. The specifcations and reference board information is available on the [[MinnowBoard:Lures_Specifications|Lures Specifications]] wiki page.<br />
<br />
=Design Files=<br />
Below you can download the MinnowBoard design files:<br />
<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_Schematics_002-003195_REVA_CCR.pdf Schematics – PDF (877 kb)]<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_BRD.zip Allegro board design file], can be viewed in the free [http://www.cadence.com/products/pcb/Pages/downloads.aspx Allegro Physical Viewer] program (4.1 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_ORCAD_002-003195_REVA_CCR.DSN ORCAD design file] – readable in ORCAD v16 or newer (13.6 MB)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_CAD_RevA_CDC2FAB.zip Generic .CAD file] (1.6 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_MFG.zip Manufacturing files] – including Gerber data, drill data, DXF and PDF drawing files, component X-Y list, and IPC netlist extract (3.0 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_ASSY_and_FAB_PDFs.zip Assembly and fabrication documents] – PDF (194 kb, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_BOM_002-003195_REVA_CCR_BOM.XLSX BOM] – Bill of Materials (28 kb)<br />
<br />
= Resources =<br />
<br />
* [http://www.minnowboard.org MinnowBoard Project Page]<br />
* [http://www.intel.com/content/www/us/en/intelligent-systems/queens-bay/embedded-intel-atom-e6xx-series-with-intel-platform-controller-hub-eg20t.html Intel Atom E6xx Pages]<br />
* [http://uefidk.intel.com/content/minnowboard-uefi-firmware MinnowBoard UEFI Open Development Community]<br />
* [[Minnowboard:Minnow_Accessories|MinnowBoard Accessory List]]<br />
* [[Minnowboard:Expansion_Interfaces|MinnowBoard Expansion Interface Descriptions]]<br />
* [[Minnowboard:SPI_Boot_flash|MinnowBoard SPI Serial Flash Memory Programming]]<br />
* [[Minnowboard:FAQ|MinnowBoard FAQ]]<br />
* [[Minnowboard:Hardware_Revisions|MinnowBoard Hardware Revisions]]<br />
* [[Minnowboard:Jumpers_and_Headers|Jumpers and Headers on the MinnowBoard]]<br />
<br><br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]<br />
{{Template:MinnowBoard}}</div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:Minnow_Original&diff=322286Minnowboard:Minnow Original2014-04-10T19:10:48Z<p>Jayneil: Changed default board image</p>
<hr />
<div><br />
<br />
[[File:MinnowRevA-Angled2.jpg|600px|center]]<br />
<br />
__NOTOC__<br />
<br />
<br />
<br />
<br />
<br />
=Documentation=<br />
<br />
==Getting Started==<br />
Excited to explore the MinnowBoard? Beginner friendly instructions/documentation available from [http://elinux.org/Minnowboard:Basics here]<br />
<br />
==MinnowBoard Projects==<br />
<br />
Have you developed a project with MinnowBoard you'd like to share? Please do so here:<br />
<br />
[[Minnowboard:Projects|Community Projects]]<br />
<br />
==OS Support==<br />
We'd love to have documents written on the following topics:<br />
<br />
* [http://elinux.org/Minnowboard:Building_Angstrom_Linux_for_the_MinnowBoard Building Angstrom Linux for the MinnowBoard]<br />
* Building Poky Linux for the Minnowboard<br />
* [http://elinux.org/Minnowboard:Debian_Bare_Minimum_Bootstrapping Installing Debian on your MinnowBoard]<br />
* [http://files.minnowboard.org/pdfs/Installing%20Windows%20on%20the%20MinnowBoard.pdf Installing Windows 8.1 on the MinnowBoard] (PDF, 800kB)<br />
<br />
==Contribute to Documentation==<br />
Please read the article [http://elinux.org/How_to_Contribute_MinnowBoard_Documentation "How to contribute to MinnowBoard Documentation] to quickly help you get started.<br />
<br />
= Accessory Boards =<br />
<br />
Accessory boards for the MinnowBoard are called Lure Boards. There are several types and sizes of these boards available. The specifcations and reference board information is available on the [[MinnowBoard:Lures_Specifications|Lures Specifications]] wiki page.<br />
<br />
=Design Files=<br />
Below you can download the MinnowBoard design files:<br />
<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_Schematics_002-003195_REVA_CCR.pdf Schematics – PDF (877 kb)]<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_BRD.zip Allegro board design file], can be viewed in the free [http://www.cadence.com/products/pcb/Pages/downloads.aspx Allegro Physical Viewer] program (4.1 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_ORCAD_002-003195_REVA_CCR.DSN ORCAD design file] – readable in ORCAD v16 or newer (13.6 MB)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_CAD_RevA_CDC2FAB.zip Generic .CAD file] (1.6 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_MFG.zip Manufacturing files] – including Gerber data, drill data, DXF and PDF drawing files, component X-Y list, and IPC netlist extract (3.0 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_ASSY_and_FAB_PDFs.zip Assembly and fabrication documents] – PDF (194 kb, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_BOM_002-003195_REVA_CCR_BOM.XLSX BOM] – Bill of Materials (28 kb)<br />
<br />
= Resources =<br />
<br />
* [http://www.minnowboard.org MinnowBoard Project Page]<br />
* [http://www.intel.com/content/www/us/en/intelligent-systems/queens-bay/embedded-intel-atom-e6xx-series-with-intel-platform-controller-hub-eg20t.html Intel Atom E6xx Pages]<br />
* [http://uefidk.intel.com/content/minnowboard-uefi-firmware MinnowBoard UEFI Open Development Community]<br />
* [[Minnowboard:Minnow_Accessories|MinnowBoard Accessory List]]<br />
* [[Minnowboard:Expansion_Interfaces|MinnowBoard Expansion Interface Descriptions]]<br />
* [[Minnowboard:SPI_Boot_flash|MinnowBoard SPI Serial Flash Memory Programming]]<br />
* [[Minnowboard:FAQ|MinnowBoard FAQ]]<br />
* [[Minnowboard:Hardware_Revisions|MinnowBoard Hardware Revisions]]<br />
* [[Minnowboard:Jumpers_and_Headers|Jumpers and Headers on the MinnowBoard]]<br />
<br><br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]<br />
{{Template:MinnowBoard}}</div>Jayneilhttps://elinux.org/index.php?title=File:MinnowRevA-Angled2.jpg&diff=322280File:MinnowRevA-Angled2.jpg2014-04-10T19:08:53Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Minnowboard:Minnow_Original&diff=322274Minnowboard:Minnow Original2014-04-10T19:06:55Z<p>Jayneil: Separate original minnow page</p>
<hr />
<div>[[File:MB-RevA-Angled.png|800px|center]]<br />
<br />
__NOTOC__<br />
<br />
<br />
<br />
<br />
<br />
=Documentation=<br />
<br />
==Getting Started==<br />
Excited to explore the MinnowBoard? Beginner friendly instructions/documentation available from [http://elinux.org/Minnowboard:Basics here]<br />
<br />
==MinnowBoard Projects==<br />
<br />
Have you developed a project with MinnowBoard you'd like to share? Please do so here:<br />
<br />
[[Minnowboard:Projects|Community Projects]]<br />
<br />
==OS Support==<br />
We'd love to have documents written on the following topics:<br />
<br />
* [http://elinux.org/Minnowboard:Building_Angstrom_Linux_for_the_MinnowBoard Building Angstrom Linux for the MinnowBoard]<br />
* Building Poky Linux for the Minnowboard<br />
* [http://elinux.org/Minnowboard:Debian_Bare_Minimum_Bootstrapping Installing Debian on your MinnowBoard]<br />
* [http://files.minnowboard.org/pdfs/Installing%20Windows%20on%20the%20MinnowBoard.pdf Installing Windows 8.1 on the MinnowBoard] (PDF, 800kB)<br />
<br />
==Contribute to Documentation==<br />
Please read the article [http://elinux.org/How_to_Contribute_MinnowBoard_Documentation "How to contribute to MinnowBoard Documentation] to quickly help you get started.<br />
<br />
= Accessory Boards =<br />
<br />
Accessory boards for the MinnowBoard are called Lure Boards. There are several types and sizes of these boards available. The specifcations and reference board information is available on the [[MinnowBoard:Lures_Specifications|Lures Specifications]] wiki page.<br />
<br />
=Design Files=<br />
Below you can download the MinnowBoard design files:<br />
<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_Schematics_002-003195_REVA_CCR.pdf Schematics – PDF (877 kb)]<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_BRD.zip Allegro board design file], can be viewed in the free [http://www.cadence.com/products/pcb/Pages/downloads.aspx Allegro Physical Viewer] program (4.1 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_ORCAD_002-003195_REVA_CCR.DSN ORCAD design file] – readable in ORCAD v16 or newer (13.6 MB)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_CAD_RevA_CDC2FAB.zip Generic .CAD file] (1.6 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_MFG.zip Manufacturing files] – including Gerber data, drill data, DXF and PDF drawing files, component X-Y list, and IPC netlist extract (3.0 MB, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_RevA_ASSY_and_FAB_PDFs.zip Assembly and fabrication documents] – PDF (194 kb, ZIP compressed)<br />
* [http://files.minnowboard.org/hw-design/MinnowBoard_BOM_002-003195_REVA_CCR_BOM.XLSX BOM] – Bill of Materials (28 kb)<br />
<br />
= Resources =<br />
<br />
* [http://www.minnowboard.org MinnowBoard Project Page]<br />
* [http://www.intel.com/content/www/us/en/intelligent-systems/queens-bay/embedded-intel-atom-e6xx-series-with-intel-platform-controller-hub-eg20t.html Intel Atom E6xx Pages]<br />
* [http://uefidk.intel.com/content/minnowboard-uefi-firmware MinnowBoard UEFI Open Development Community]<br />
* [[Minnowboard:Minnow_Accessories|MinnowBoard Accessory List]]<br />
* [[Minnowboard:Expansion_Interfaces|MinnowBoard Expansion Interface Descriptions]]<br />
* [[Minnowboard:SPI_Boot_flash|MinnowBoard SPI Serial Flash Memory Programming]]<br />
* [[Minnowboard:FAQ|MinnowBoard FAQ]]<br />
* [[Minnowboard:Hardware_Revisions|MinnowBoard Hardware Revisions]]<br />
* [[Minnowboard:Jumpers_and_Headers|Jumpers and Headers on the MinnowBoard]]<br />
<br><br />
[[Category: MinnowBoard]]<br />
[[Category: MinnowBoard Expansion Boards]]<br />
[[Category: CircuitCo]]<br />
{{Template:MinnowBoard}}</div>Jayneilhttps://elinux.org/index.php?title=File:MB-RevA-Angled.png&diff=322268File:MB-RevA-Angled.png2014-04-10T19:02:03Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=File:Minnow_board.JPG&diff=322262File:Minnow board.JPG2014-04-10T18:56:23Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=BeagleBoard/GSoC/Ideas-2016&diff=318248BeagleBoard/GSoC/Ideas-20162014-03-04T21:56:55Z<p>Jayneil: </p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category: BeagleBoard]]<br />
[[Category: GSoC]]<br />
<br />
__TOC__<br />
<br />
=Welcome!=<br />
BeagleBoard.org hopes to be accepted as a mentoring organization in the [[BeagleBoard/GSoC|Google Summer of Code]] for 2014! Below, we've collected project ideas for the GSoC-2014.<br />
<br />
==Background==<br />
BeagleBoard.org is a volunteer organization that seeks to advance the state of open-source software on [http://en.wikipedia.org/wiki/Open-source_hardware open-source hardware] platforms capable of running high-level languages and operating systems (primarily Linux) in embedded environments. Born from taking mobile phone processors and putting them on low-cost boards to build affordable desktop computers, BeagleBoard.org has evolved to focus on the needs of the "maker" community with greater focus on the I/O needed for controlling motors and reading sensors to build things like robots, 3d printers, flying drones, in-car computer systems and much more. Past BeagleBoard.org GSoC projects included [[BeagleBoard/GSoC/2010_Projects/C6Run|an RPC framework for heterogeneous processor communication]], [[BeagleBoard/GSoC/2010_Projects/USBSniffer|a transparent USB packet sniffer]], [[BeagleBoard/GSoC/2010_Projects/XBMC|ARM optimizations for XBMC]], [[BeagleBoard/GSoC/2010_Projects/FFTW|ARM optimizations for FFTs]], [[BeagleBoard/GSoC/2010_Projects/Pulse_Width_Modulation|make-shift pulse-width-modulation]] and [[BeagleBoard/GSoC/2010_Projects/OpenCV|RPC optimizations for OpenCV]]. BeagleBoard.org has benefited from sponsorship from Texas Instruments, [[CircuitCo]], Digi-Key and others, but avoids any dependence on that sponsorship for sustaining the effort. The project has evolved over the past few years with over 100,000 boards in circulation with developers worldwide and strong roots in the Linaro, Yocto Project, Angstrom Distribution and Linux communities---and support for running most major Linux distributions including Ubuntu, Android, Fedora, Debian, ArchLinux, Gentoo, Buildroot and many more.<br />
<br />
BeagleBoard was inspiration for Raspberry Pi[http://www.linuxuser.co.uk/features/raspberry-pi-interview-eban-upton-reveals-all] and is available for only $45 through over 30 distributors world-wide (and is even available at Microcenter and Radio Shack in the USA), but is more than a throw-away computer. It is an instance of true open hardware, exposing users to the broader world of electronics, demystifying computers and fostering an environment of clones that have changed the industry for good.<br />
<br />
Students will be expected to demonstrate an understanding of cross-compiling before being accepted, but support for demonstration is available through the IRC channel that typically has approximately 150 online chatters logged on at any time, most with sufficient experience to explain the process.<br />
<br />
'''''<span style="color:red">Every accepted student will be sent a BeagleBone Black before the first week of coding for testing their project.</span>'''''<br />
<br />
Additional hardware will be provided depending on need and value.<br />
<br />
For more information, check out http://beagleboard.org and http://beagleboard.org/brief.<br />
<br />
==Students looking for ideas==<br />
Student proposals can encompass projects inspired from the following list of ideas or can include personal project ideas. Previous Google Summer of Code projects show that the key to success is being passionate about your project, so propose something that is extremely interesting to you, even if it is not on this list. We will be glad to help students develop ideas into projects via [http://webchat.freenode.net/?channels=beagle the BeagleBoard IRC] or [http://groups.google.com/group/beagleboard the BeagleBoard mailing list]. There are many potential project ideas and we will match students to projects based on their interests and help scope the proposals to something that can be completed in the Summer of Code timeframe.<br />
<br />
There are more than 300 existing projects listed at http://beagleboard.org/project. If you are interested in any of the projects listed on the BeagleBoard.org projects page, contact the project members to see if there are any aspects of their projects that can be enhanced to create a GSoC project. There are also several ideas on the[[ECE497_Project_Ideas|ECE497 class project idea list]]. You can also check out [[BeagleBoard/GSoC/Ideas-2013|last year's idea page]].<br />
<br />
==Mentors wondering where to help==<br />
Please start by registering your ideas for student projects below by following the template provided with the existing ideas. Furthermore, scroll down to the bottom and give everyone a bit of information about your expertise and availability by adding yourself to the table. Jason will make final approvals for mentor assignments based on if we first get accepted as a mentoring organization and best matching mentor skill sets with student project ideas deemed valuable to the community.<br />
<br />
You will also need to register on [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Melange] and request to be a mentor for BeagleBoard.org.<br />
<br />
==General requirements==<br />
All projects have the following basic requirements:<br />
# Once accepted, the project must be registered on http://beagleboard.org/project.<br />
# All newly generated materials must be released under an [http://www.opensource.org/licenses open source license].<br />
# Individual students shall retain copyright on their works.<br />
# Source code generated during the project must be released on github.com (to be cloned to github.com/beagleboard on successful completion).<br />
# The registration on http://beagleboard.org/project must include an RSS feed with project announcements and updates at every milestone. Sources for the RSS feed should be blogger.com, wordpress.com, or some other established blog-hosting service with known reliability.<br />
# To help you to break your project down into manageable chunks and also to help the project's mentors to better support your efforts, weekly project status reports should be e-mailed to the project's mentors and the organization administrator (Jason Kridner). Each status report should outline:<br />
## what was accomplished that week, <br />
## any issues that prevented that week's goals from being completed and<br />
## your goals for the next week.<br />
# Students will provide two recorded audio/video presentations uploaded to youtube or vimeo (screencasts are appropriate), one near the beginning of the project summarizing their project goals and another in the wrap-up phase to summarize their accomplishments. Examples can be found on http://beagleboard.org/gsoc.<br />
# Students will demonstrate their ability to cross-compile and utilize version control software by creating a "Hello World" application and generating a pull request to https://github.com/jadonk/gsoc-application/tree/master/ExampleEntryJasonKridner. For assistance, please visit http://beagleboard.org/chat or utilize the beagleboard-gsoc Google Group. The "Hello World" application must print your name and the date out in an ARM Linux environment. Freely available emulators may be used to test your application or you can ask anyone on the chat or mailing list to help you test.<br />
# All projects will produce reusable software components and will not be "what–I-built-over-my-summer-vacation" projects. Including a hardware component is welcome, but the project *deliverable* will be software that may be utilized by a wide audience of the BeagleBoard.org community.<br />
<br />
=Ideas=<br />
There are several areas needing contributions:<br><br />
'''Kernel''': Improving the state of the Linux kernel including improved ARM/OMAP/Sitara platform support, simplifying the development of add-on hardware for embedded systems and exchanging hardware connectivity information with userspace.<br><br />
'''Secondary processor support (RPC/gcc/etc.)''': Enabling usage of DSPs, PRUs, FPGAs, Cortex-M3s, Arduinos, MSP430 launchpads and other attached processing platforms.<br><br />
'''Scripting libraries and web interfaces''': Improving the Bonescript JavaScript library, web-based interface libraries, examples or alternatives in other languages.<br><br />
'''Frameworks for open-hardware projects''': Consolidating support for simplified home manufacturing (CNC, 3D printers, laser cutters, pick-and-place machines, etc.), drones/bots (ROS, IMU, video streaming, etc.) or other common tasks.<br><br />
'''Optimizations to existing userspace applications/libraries''': Optimizations to applications and libraries like XBMC to make them run better on resource constrained environments or to take advantage of more specialized processing elements.<br><br />
<br />
==BeaglePilot==<br />
Porting ArduPilot to BeagleBone Black. Some of the tasks include:<br />
<br><br />
<br />
* PRU drivers (PWM and PPM)<br />
* SPI drivers for cape sensors<br />
* RC Input (PPM)<br />
* Power handling<br />
* Analog sensing<br />
* Flight tests<br />
<br />
''Goal:'' ArduPilot/APM is a open source autopilot system supporting multi-copters, traditional helicopters, fixed wing aircraft and rovers. The community decided to switch to the BeagleBone Black as their main target thereby the goal of this project will be to support this step, code and test everything to make the BeagleBone the next "platform for aerial devices".<br><br />
''Existing Project:'' [http://ardupilot.com ArduPilot Website], [https://github.com/diydrones/ardupilot Source Code], [https://github.com/BeaglePilot BeaglePilot on GitHub] <br><br />
''Hardware Skills:'' Interfacing sensors, PPM, PRUSS, some experience RC planes/multicopters<br><br />
''Software Skills:'' C, C++, Python, Assembly<br><br />
''Possible Mentors:'' Andrew Tridgell, Kevin Hester, Lorenz Meier <br><br />
''Workload:'' Considering the experience these first months at BeaglePilot we estimate that there's room for 3 students on this project. <br><br />
<br />
==Upstreaming Beagleboard.org Kernel Patches==<br />
The BeagleBone currently relies on a number of out-of-tree kernel patches in order to boot. These patches are maintained by Koen Kooi (CircuitCo) and come from many sources, including TI employees and various mailing lists. Getting more of these patches upstream would make it easier to boot a BeagleBone and also make use of a BeagleBone easier for users and kernel developers who need to track upstream kernel changes, or who otherwise need to be closer to the bleeding edge of Linux kernel development. The current patch set is [https://github.com/beagleboard/kernel/tree/3.8 maintained at github] and contains scripts to easily patch an upstream kernel. The scripts in this repository are used to build the BeagleBoard.org kernels which ship with the Angstrom SD card images.<br />
<br><br />
<br />
''Goal:'' Push as many patches as possible to [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git Linus's mainline kernel tree] via the appropriate [http://git.kernel.org/cgit/ staging kernels] for the subsystems involved.<br><br />
''Existing Project:'' [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git The Mainline Linux Kernel], [http://github.com/beagleboard/kernel/tree/3.8 patches needing to be pushed]<br><br />
''Hardware Skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals.<br><br />
''Software Skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation and testing.<br><br />
''Possible mentors:'' Matt Porter, Matt Ranostay, Koen Kooi, Alan Ott<br><br />
<br />
==Generic Device Tree Creator==<br />
Device Tree usage can be a steep learning curve for many. Despite N tutorials for it. Kernel version and naming convention changes cause issues.<br />
So how about a tool to create the DT file for the Beaglebone Black. <br />
Select the required options. Need this gpio for pru. Need this adc for tsc. Need this pin.<br />
And it generated DT bindings for you.<br />
<br />
Ideally it should effectively expand for other embedded development kits. If you load a Beaglebone Black Rev C file. The DT bindings for that are generated.<br />
If you load a Beaglebone White Rev A file, DT bindings for that are generated etc..<br />
Similarly, kernel version changes should be easy to incorporate as well.<br />
<br />
Getting the whole thing as part of GSoC can get too much unless you are really skilled. So a basic structure should be the aim initially. <br />
Suggestions for the base platform running the tool are welcome. e.g. A webapp/bonescript can be used. Python perhaps.<br />
<br />
''Goal:'' Get a basic device tree creator for BBB (and possibly BBW) working with a structure to allow different board types<br><br />
''Existing Project:'' https://github.com/jluebbe/tools is a small bit of a starting point. <br><br />
''Hardware Skills:'' Should be able to understand the capes <br><br />
''Software Skills:'' Cross-compile the Linux kernel and testing the DT.<br><br />
''Possible mentors:'' Jason Kridner<br><br />
<br />
<br />
==IIO debugging tools==<br />
Quick background: IIO is the new way of doing sensors but being a newer interface, it lacks tools<br />
for debugging. This project is to produce sometools to debug drivers.<br />
There are several ways this project can happen:<br><br />
1. We can implement userland tools that read IIO data similar to the evtest tool. <br><br />
2. We can implement a event handler for the IIO driver. This way existing tools and code can be used. There was references from another mailing list (probally LKML) talking about this.<br><br />
<br />
''Goal:'' Userspace application similar to evtest that captures debug events and instrumented IIO driver code to produce those events.<br><br />
''Existing Project:'' [http://github.com/beagleboard/kernel/tree/3.8 patched kernel with IIO driver]<br><br />
''Hardware Skills:'' None.<br><br />
''Software Skills:''C coding (1), (2) requires kernel coding<br><br />
''Possible mentors:'' Hunyue Yau<br><br />
<br />
==node-webkit based cross-platform getting-started app==<br />
Newbies often have a difficult time following directions that could be replaced by an application. The steps to download and install an application is something that even newbies can typically manage. This avoid issues like having bad browsers or not having typical development tools like 'ssh'. This is a common problem across all embedded Linux platforms and node-webkit provides a good solution for making it cross-platform.<br />
<br />
''Features'':<br />
* Provide instructions for getting up-and-running with the board based (incorporate the Getting Started Guide)<br />
* Automatically discover boards on the LAN using mDNS and predetermined IP addresses<br />
* Act as a browser to interact with the board, including performing SSH and SCP<br />
* Discover the latest SD card images from multiple distributions<br />
* Bootload the board with a USB-mass-storage-class application<br />
* Program SD cards through the board or a USB adapter<br />
* Program on-board eMMC<br />
<br />
''Goal:'' Provide a downloadable application for Linux, Windows and Mac that enables unexperienced users to get going enough to start learning about using Linux and the embedded I/O.<br><br />
''Existing Project:'' [http://github.com/jadonk/beaglebone-getting-started/tree/node-webkit-app Incomplete node webkit app for the BeagleBone Getting Started guide]<br><br />
''Hardware Skills:'' N/A<br><br />
''Software Skills:'' Able to write software in JavaScript and work with node.js modules<br><br />
''Possible mentors:'' Jason Kridner<br><br />
<br />
==OpenEmbedded support for npm packages for node.js==<br />
Using npm for packages works well for grabbing most recent versions of things, but it doesn't work well to make sure you are getting tested versions built for your platform, it doesn't integrate with the native package manager, it is a huge security hole and it generally is a mess for distributions. OpenEmbedded provides a great vehicle for creating distributions that can professionally support deploying node.js packages rather than relying on a tool that is really only geared for prototyping.<br />
<br />
* Create a bitbake 'npm' class<br />
* Cross-build native code using node-waf, node-gyp and nw-gyp<br />
* Create dependencies using package.json<br />
<br />
''Goal:'' Bitbake 'npm' class and recipes for tools like 'node-serialport', 'express', 'socket.io' and more.<br><br />
''Existing Project:'' http://www.openembedded.org/wiki/BitBake, https://npmjs.org/<br><br />
''Hardware Skills:'' N/A<br><br />
''Software Skills:'' Familiarity with C++, JavaScript and Python. Basic understanding of build systems.<br><br />
''Possible mentors:'' Jason Kridner<br><br />
<br />
==BoneScript web pages with live-running examples and documentation==<br />
{{#ev:youtube|VP0DOheLxQA||right|5 JavaScript Tricks for BeagleBone}}<br />
The BoneScript JavaScript library enables hardware control from web pages using socket.io for remote procedure calls. This provides an excellent environment for teaching how to wire-up sensors and controls and rapidly prototype user interfaces. Numerous examples exist on the web, but consolidation and testing are required to make them usable by novices. Examples include interfacing with potentiometers, light sensors, temperature sensors, motors and LED arrays then visualizing/controlling with Twitter, Facebook, jQuery, Spacebrew and dweet,io.<br />
<br />
''Goal:'' About 25 web pages with executable script that demonstrate how to connect up sensor and actuator hardware integrated into the bone101 repository and shared on http://beagleboard.org/Support/BoneScript<br><br />
''Existing Projects:'' [http://makezine.com/2014/01/14/5-easy-javascript-tricks-you-can-teach-your-beaglebone/ 5 easy tricks presentation], http://beagleboard.org/Support/BoneScript, https://github.com/jadonk/bone101, [https://github.com/jadonk/beaglebone-getting-started/blob/add-bone101/Docs/demo_bmp085.html BMP085 Bonescript example], [http://elinux.org/Category:ECE497 ECE497 examples]<br><br />
''Hardware Skills:'' Basic knowledge of digital circuits.<br><br />
''Software Skills:'' JavaScript and some familiarity with Linux<br><br />
''Possible mentors:'' Jason Kridner<br><br />
<br />
==Integrate support libraries into Angstrom==<br />
Many BeagleBone and embedded Linux support libraries in various programming languages exist as projects that aren't included in the distro shipped with BeagleBoard and BeagleBone. These need bitbake recipes added to meta-beagleboard such that they can be easily downloaded and incorporated into the shipping distro.<br />
<br />
* Python PyBBIO<br />
* Ruby beaglebone-ruby<br />
* Perl bonelib<br />
<br />
''Goal:'' PyBBIO, beaglebone-ruby and bonelib included in the distro shipping with BeagleBone<br><br />
''Existing Project:'' [https://github.com/alexanderhiam/PyBBIO PyBBIO], [https://github.com/ryanfaerman/beaglebone-ruby beaglebone-ruby], [http://sourceforge.net/p/bonelib/wiki/Home/ bonelib]<br><br />
''Hardware Skills:'' Able to wire up simple hardware, like LEDs<br><br />
''Software Skills:'' Familiarity with Python, Ruby, Perl, embedded Linux and build systems.<br><br />
''Possible mentors:'' Jason Kridner<br><br />
<br />
==SYSFS entries for IIO and PWM==<br />
IIO and PWM provide mechanisms for sampling touch screens, performing general purpose A/D conversions to read sensors, generating voltage levels and driving motors. The Linux kernel SYSFS mechanism provides a simplified mechanism for userspace applications to set parameters and read/write data values.<br />
<br />
''Goal:'' Push patches to Linux mainline providing SYSFS entries for IIO and PWM useful for building a demo robot<br><br />
''Existing project:'' http://github.com/beagleboard/kernel<br><br />
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br><br />
''Software skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation<br><br />
''Possible mentors:'' Laine Walker-Avina<br><br />
<br />
==Using BeagleBone PRUs to control CNC and 3D printer stepper motor Drivers==<br />
This project is to write code for the PRU (realtime processors on the AM335x used in the Beagle Bone) so that it can generate multiple step and direction outputs based on a queue of commands in real time. This needs to be done in real time so the acceleration and coordination of multiple stepper motors can be controlled and coordinated. A step/dir signal is commonly used in a lot of stepper motor drivers. While it is possible to generate stepper phase information from the PRU, it is also undesireable from a testing stand point. An example of a reason for doing this is controlling the X/Y directions of the head of a 3D printer so that it can generate precise curves. While similar code has been done, it is not done in a real time fashion so it is difficult to add coordination between motors and/or maintain a known acceleration.<p><br />
<br />
The result of this code should be something interfaceable to a control system like the non realtime portions of the Linux CNC project (formerly the EMC project). But as a demo, this same code should also demonstrate a node.js functionality such as a "G-code" interpreter. This node.js portion can be considered a second project due to the different skill sets required and ideally this project would be split between two GSoC students. One project would be working mostly on PRU assembly with integration into the Linux kernel. The other project would be working mostly on userspace JavaScript in node.js and C++ code for anything needing optimization or low-level kernel access. Mentors would heavily assist on defining the right interfaces between the two programming environments.<br />
<br />
''Goal'': create code to use the AM335x PRUs to generate multiple step and direction outputs for reprap and CNC applications<br><br />
''Existing projects'': [http://github.com/beagleboard/am335x_pru_package Pru Documentation], [https://www.kernel.org/doc/htmldocs/uio-howto.html UIO Driver documentation]<br><br />
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br><br />
''Software skills:'' Assembly and C coding. Node.js for g-code interpretation<br><br />
''Possible mentors:'' Tom King, Jason Kridner, Hunyue Yau, Laine Walker-Avina<br><br />
<br />
==PRU upstreaming==<br />
Remove HWMOD dependency requirement for PRU along with adding device tree bindings so it can be upstreamed into Linus's tree.<br />
<br />
''Goal'': Push patches to Linux mainline providing support for the AM335x PRU<br><br />
''Existing project'': https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/<br><br />
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br><br />
''Software skills:'' Able to write software in C, understand existing patches with PRU support, create patches to the Linux kernel and perform cross-compilation<br><br />
''Possible mentors:'' Start with Jason Kridner and Matt Porter, but we'll get some others involved<br><br />
<br />
==PRU firmware loader==<br />
Allow "firmware" which are really binary PRU applications to be loaded directly on PRU cores and executed using the request_firmware() functionality of the Linux Kernel. This should also be Cape Manager to load PRU cape specific applications.<br />
<br />
Ideal workflow:<br />
<br />
* Cape detected that uses the PRU<br />
** Setup pinmux <br />
* Find the respective firmware file for PRU core (or both cores) /lib/firmware/cape_A020_pru0.bin<br />
* Load onto PRU and begin execution.<br />
<br />
''Goal'': Push patches to Linux mainline providing support to loading firmware on PRU cores and executing<br><br />
''Existing project'': https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/<br><br />
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br><br />
''Software skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation<br><br />
''Possible mentors:'' Matt Ranostay, Matt Porter<br><br />
<br />
==Virtual machine for PRU==<br />
Based on Chris Roger's BotSpeak work to provide a virtual machine for typical Arduino functions that can be accessed from LabView, build a virtual machine to enable PRU programming from Bonescript. The virtual machine is a simple interpreter that loops over the commands to perform such as delay, pinMode, analogRead, analogWrite, digitalRead and digitalWrite functions.<br />
<br />
A basic design is elaborated upon at http://github.com/jadonk/pruduino<br />
<br />
''Goal'': Implement a BotSpeak interpreter that off-loads hard real-time tasks from Bonescript onto the PRU and include that in the BoneScript project<br><br />
''Existing projects'': [http://github.com/jadonk/pruduino PRUDUINO], http://github.com/beagleboard/am335x_pru_package, http://github.com/jadonk/bonescript, [https://sites.google.com/site/botspeak/the-language Chris' language definition]<br><br />
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br><br />
''Software skills:'' Able to write software in JavaScript and assembly<br><br />
''Possible mentors:'' Chris Rogers, Jason Kridner, Tom King<br><br />
<br />
==Android-based remote display==<br />
Use your Android phone as a remote display and control unit for you BeagleBone. Display your applications UI on the phone screen and use your phone's touchscreen to control your application on the Beaglebone.<br />
<br />
Since all Android devices are required to support ADK (Accessory Development Kit) mode, a BeagleBone acting as a USB host can talk to an Android phone over USB. An Android application would provide the "remote" screen for the Beaglebone, much like an USB based external display on a PC. At the same time button presses and touchscreen events can be relayed to the Beaglebone as it if had a local keyboard connected<br />
<br />
Many applications are possible, from a simple shell to aid developing and debugging to a remote X server that hosts GUI apps. <br />
<br />
If ADK mode can also be achieved in u-boot, it could help to setup and debug the bootloader even before the Linux kernel starts.<br />
<br />
Further, a part of the Android devices' filesystem could me made accessible to mount on the Beaglebone<br />
<br />
''Goal:'' Implement a remote display and keyboard for the Beaglebone running on an Android phone or tablet<br><br />
''Existing Project:'' https://github.com/SpecLad/libusb-android, [https://code.google.com/p/rowboat/wiki/AccessoryDevKit BeagleBone implementation of Android Accessory Development Toolkit]<br><br />
''Hardware Skills:'' Some knowledge of USB<br><br />
''Software Skills:'' Java, C and familiarity with Android<br><br />
''Possible mentors:'' Vladimir Pantelic, Jason Kridner and others<br><br />
<br />
<br />
==Cross platform USB boot==<br />
Boot (and flash) your BeagleBone (Black) from a Windows, Mac or Linux computer without using a microSD card.<br />
<br />
Extend [https://github.com/ungureanuvladvictor/BeagleDroid last year's GSoC project] to boot from an Android device to support Windows, Mac and Linux hosts.<br />
<br />
''Goal:'' Download a Linux image from the web and boot a BeagleBone using it over USB<br><br />
''Existing Project:'' https://github.com/ungureanuvladvictor/BeagleDroid, https://github.com/ungureanuvladvictor/BBBlfs<br><br />
''Hardware Skills:'' Some knowledge of USB<br><br />
''Software Skills:'' C and familiarity with Mac, Linux and Windows<br><br />
''Possible mentors:'' Vladimir Pantelic, Jason Kridner<br><br />
<br />
==Android under Angstrom==<br />
Some people want to play Angry Birds or run other Android apps on their BeagleBoard/BeagleBone. Of course, you could use the Rowboat Android project as-is, but then you'd have to give up all of their typical Linux/X11 applications available in Angstrom. This project would use an Android-enabled kernel and a combination of both Angstrom and Android file systems. The input and display methods required for Android would need to be adjusted to run in on a virtual terminal and chroot/chvt would be used to invoke the various user space windows.<br />
<br />
This has essentially been done once as part of [https://www.alwaysinnovating.com/beagleboard/ Always Innovating's Super-Jumbo] demo running Ubuntu, Angstrom, ChromeOS and Android simultaneously. The fundamental challenge is getting it reproducible and integrated into the OpenEmbedded build system for Angstrom and then starting to minimize the wasted file space by sharing libraries. Eventually, even making Android applications run in a window is desired.<br />
<br />
''Goal'': Run Android applications under Angstrom and toggle back-and-forth using CTRL-ALT-Fn key presses.<br><br />
''Existing projects'': http://arowboat.org, http://www.angstrom-distribution.org<br><br />
''Hardware skills:'' Minimal<br><br />
''Software skills:'' Able to write software in C and Java, experience with X11 and Android<br><br />
''Possible mentors:'' Hunyue Yau, Vladimir Pantelic<br><br />
<br />
==Library of Arduino-compatible functions for StarterWare==<br />
This would be an implementation of Arduino utilizing the BeagleBone Black and the StarterWare O/S independent library for accessing the hardware. Without having to access the hardware through an operating system, developers will be able to fine-tune the system to achieve optimal resource management of the CPU, peripherals and memory.<br />
The project would also include basic documentation and generation of code samples for various functionality of the library, such as SPI,Serial,Ethernet for starters. This would make the project thorough and ready for use by various developers in the community.<br />
<br />
''Goal:'' Utilize the Energia fork of Arduino to push support for BeagleBone and BeagleBone Black<br><br />
''Existing Project:'' [https://github.com/energia/Energia Energia], [http://processors.wiki.ti.com/index.php/StarterWare StarterWare]<br><br />
''Hardware Skills:'' Yes<br><br />
''Software Skills:'' C/C++<br><br />
''Possible mentors:'' Jason Kridner (others can be referred if there are interested students)<br />
<br />
==Documentation for BeagleBone and BeagleBone Black==<br />
'''We need to avoid documentation projects for GSoC. Please turn this into a coding project. Providing code examples might be sufficient, but code needs to be the output. The documentation can be a side-effect.'''<br />
Produce HOWTOs and code samples for use of I/O on BeagleBone to be placed in the neutral elinux.org BeagleBone community pages.<br />
<br />
''Goal:'' The Beagleboard.org community has lacked a canonical source of high quality documentation on how to use peripherals found on AM335x. Peripheral use to be documented will include UARTs, I2C, SPI, PWM, ADC, USB Host/Gadget as well as advanced topics such as software development and optimization for the M3 and PRU coprocessors.<br><br />
''Existing Project:'' [http://www.elinux.org/BeagleBone_Community elinux.org BeagleBone Community Page]<br><br />
''Hardware Skills:'' Yes<br><br />
''Software Skills:'' C<br><br />
''Possible mentors:'' Hunyue Yau and Matt Porter (others welcome to volunteer)<br />
<br />
==PyBBIO library development==<br />
PyBBIO is a Python library that aims to provide Arduino-style API for hardware IO support on the Beaglebone and BeagleBone Black. It is meant to make hardware development fast and easy with Python.<br />
<br />
''Goal:'' Moving portions to C extensions to speed up PyBBIO, as well as adding further peripheral support and internal libraries. Preliminary ideas list here: [https://github.com/alexanderhiam/PyBBIO/wiki/GSoC-2014-ideas]<br/><br />
''Existing Project:'' [https://github.com/alexanderhiam/PyBBIO PyBBIO]<br/><br />
''Hardware Skills:'' Yes<br/><br />
''Software Skills:'' Python, C, familiar with Python C extensions<br/><br />
''Possible mentors:'' Alexander Hiam<br />
<br />
==Previous ideas==<br />
* [[BeagleBoard/GSoC/Ideas-2013]]<br />
* [[BeagleBoard/GSoC/Ideas-2012]]<br />
<br />
=Mentors=<br />
{| border="1"<br />
! Name<br />
! IRC nickname<br />
! Native language<br />
! Other languages<br />
! Timezone<br />
! Software help<br />
! Hardware help<br />
! Focus projects<br />
|-<br />
| Jason Kridner<br />
| jkridner<br />
| English<br />
| -<br />
| US Eastern<br />
| JavaScript, C, u-boot<br />
| wiring, timing diagrams, basic debug<br />
| BoneScript development<br />
|-<br />
| Vladimir Pantelic<br />
| av500<br />
| German<br />
| English, Serbian<br />
| CET<br />
| Experienced on most areas of Embedded Linux, Multimedia<br />
| Schematic Review + Design<br />
| Embedded Linux, Linux Multimedia, Android<br />
|-<br />
| Matt Ranostay<br />
| mranostay<br />
| English (U.S. Midwestern Dialect)<br />
| None<br />
| US Pacific Time<br />
| Experienced on most areas of Embedded Linux or Systems<br />
| Schematic Review + Design<br />
| ARM/AM335x Kernel Development<br />
|-<br />
| Philip Balister<br />
| Crofton<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
| Russ Dill<br />
| Russ<br />
| English<br />
| None<br />
| US Pacific Time<br />
| Experienced on most areas of Embedded Linux or Systems<br />
| Schematic Review + Design<br />
| ARM/AM335x Kernel Development<br />
|-<br />
| Matt Porter<br />
| mdp<br />
| English (U.S. Midwestern Dialect)<br />
| None<br />
| US Eastern<br />
| Embedded Linux Firmware/Kernel and system level design. Designing Linux drivers to make the best use of existing infrastructure.<br />
| Schematic Review + Design<br />
| ARM/AM335x/OMAP/PRU U-Boot and Kernel/Driver Development<br />
|-<br />
| Koen Kooi<br />
| koen<br />
| Dutch<br />
| English<br />
| CET<br />
| Experienced on most areas of Embedded Linux, buildsystems<br />
| -<br />
| -<br />
|-<br />
| Tom King<br />
| ka6sox<br />
| English<br />
| None<br />
| US Pacific Time<br />
| Experienced on most areas of Embedded Linux or Systems<br />
| Schematic Review + Design, Board Layout<br />
| ARM/AM335x Kernel Development<br />
|-<br />
| Laine Walker-Avina<br />
| Ceriand<br />
| English<br />
| -<br />
| US Pacific<br />
| C, Assembly, Buildroot, Reprap<br />
| USB protocol & logic analyzers, Various JTAG probes, 3d printer<br />
| OpenOCD, bootloaders, Linux kernel, Reprap firmware<br />
|-<br />
| Alan Ott<br />
| alan_o<br />
| American English (Central Florida Dialect)<br />
| American English (Midwestern Dialect)<br />
| US Eastern (EDT)<br />
| Linux Kernel, Firmware<br />
| Breadboard wire-jamming<br />
| 802.15.4 Wireless, USB<br />
|-<br />
| Hunyue Yau<br />
| ds2<br />
| English<br />
| -<br />
| US Pacific<br />
| Android, C, Linux, scripting<br />
| Yes<br />
| -<br />
|-<br />
| Tom Rini<br />
| Tartarus<br />
| English<br />
| -<br />
| US Eastern<br />
| C, u-boot, OpenEmbedded<br />
| -<br />
| U-Boot or OpenEmbedded development<br />
|-<br />
| Luis Gustavo Lira<br />
| lglira<br />
| Spanish<br />
| English<br />
| GMT/UTC -5<br />
| Embedded Linux, C, Android<br />
| Design, Debug, Wiring<br />
| Projects on the BeagleBone<br />
|-<br />
| Derek Molloy<br />
| molloyd<br />
| -<br />
| -<br />
| GMT (London)<br />
| C++, Java, Embedded C/C++<br />
| Digital Circuits, Interfacing to Sensors<br />
| Beaglebone Applications, Linux Multimedia, Embedded Linux<br />
|-<br />
| Steven Frank Barrett<br />
| steveb<br />
| English<br />
| -<br />
| US Mountain<br />
| C<br />
| microcontrollers, BeagleBone<br />
| -<br />
|-<br />
| Frans Meulenbroeks<br />
| eFfeM<br />
| Dutch<br />
| English<br />
| CET<br />
| Linux (including drivers), U-Boot, C, Documentation; Coding Style, QA<br />
| device interfacing (for drivers), review FPGA code<br />
| -<br />
|-<br />
| Pantelis Antoniou<br />
| panto<br />
| Greek<br />
| English<br />
| GMT+2<br />
| Linux Kernel, S/W Architecture <br />
| -<br />
| Embedded Linux architecture fixes<br />
|-<br />
| Andrew Tridgell<br />
| tridge<br />
| English<br />
| <br />
| GMT+11<br />
| Linux Kernel, C, C++, python <br />
| -<br />
| ArduPilot<br />
|-<br />
| Kevin Hester<br />
| kevinh /kevinh_<br />
| English<br />
| <br />
| GMT-8<br />
| Linux embedded, C, C++<br />
| -<br />
| Drone software developer<br />
|-<br />
| Lorenz Meier<br />
| LorenzMeier<br />
| English<br />
| <br />
| GMT+1<br />
| mobile localization, 3D reconstruction on smartphones and micro air vehicles<br />
| -<br />
| <br />
|-<br />
| Alexander Hiam<br />
| alexanderhiam<br />
| English<br />
| -<br />
| US Eastern<br />
| Python, C, Linux Kernel<br />
| Prototyping, design, layout, debugging<br />
| PyBBIO<br />
|}<br />
[[BeagleBoard/GSoC/Ideas-2012#Mentors|Previous mentors]]</div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=312074Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-13T22:12:12Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx <br />
<br />
''Note:- '''DO NOT''' install a distro-packaged version of bitbake. The metadata included in various yocto layers only works with a particular version of bitbake. Angstrom and Yocto will ensure the correct version is included when you check out the code.''<br />
<br />
<br />
[[File:Angstroms8.png|1026px]]<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
[[File:Angstroms7.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
When it comes to building the Angstrom image you have lots of options and recipes to choose from, each resulting in a different configuration and packages. The typical command would be:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake <IMAGE NAME><br />
<br />
Few examples of the types of Image you can build are ''systemd-image'' (minimalistic and perfect for embedded developers) or the ''systemd-gnome-image'' (With gnome2 desktop environment)<br />
<br />
Let us finally build the image now:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-gnome-image<br />
<br />
[[File:Angstroms9.png|1026px]]<br />
<br />
<br />
'''Step-8:'''<br />
<br />
In my case the resulting image was located in ''/setup-scripts/deploy/eglibc/images/minnow''<br />
<br />
[[File:Angstroms10.png|1026px]]<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms10.png&diff=312068File:Angstroms10.png2014-01-13T22:11:51Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms8.png&diff=312062File:Angstroms8.png2014-01-13T22:06:31Z<p>Jayneil: Jayneil uploaded a new version of &quot;File:Angstroms8.png&quot;</p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=312056Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-13T20:25:14Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx <br />
<br />
''Note:- '''DO NOT''' install a distro-packaged version of bitbake. The metadata included in various yocto layers only works with a particular version of bitbake. Angstrom and Yocto will ensure the correct version is included when you check out the code.''<br />
<br />
<br />
[[File:Angstroms8.png|1026px]]<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
[[File:Angstroms7.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
When it comes to building the Angstrom image you have lots of options and recipes to choose from, each resulting in a different configuration and packages. The typical command would be:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake <IMAGE NAME><br />
<br />
Few examples of the types of Image you can build are ''systemd-image'' (minimalistic and perfect for embedded developers) or the ''systemd-gnome-image'' (With gnome2 desktop environment)<br />
<br />
Let us finally build the image now:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-gnome-image<br />
<br />
[[File:Angstroms9.png|1026px]]<br />
<br />
<br />
'''Step-8:'''<br />
<br />
In my case the resulting image was located in ''/setup-scripts/deploy/eglibc/images/minnow''<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=312050Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-13T20:20:24Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx <br />
<br />
''Note:- '''DO NOT''' install a distro-packaged version of bitbake. The metadata included in various yocto layers only works with a particular version of bitbake. Angstrom and Yocto will ensure the correct version is included when you check out the code.''<br />
<br />
<br />
[[File:Angstroms8.png|1026px]]<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
[[File:Angstroms7.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
When it comes to building the Angstrom image you have lots of options and recipes to choose from, each resulting in a different configuration and packages. The typical command would be:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake <IMAGE NAME><br />
<br />
Few examples of the types of Image you can build are ''systemd-image'' (minimalistic and perfect for embedded developers) or the ''systemd-gnome-image'' (With gnome2 desktop environment)<br />
<br />
Let us finally build the image now:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-gnome-image<br />
<br />
[[File:Angstroms9.png|1026px]]<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=312044Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-13T20:19:46Z<p>Jayneil: Removed installing Bitbake from pre requisites</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx <br />
<br />
''Note:- '''DO NOT''' install a distro-packaged version of bitbake. The metadata included in various yocto layers only works with a particular version of bitbake. Angstrom and Yocto will ensure the correct version is included when you check out the code.''<br />
<br />
<br />
[[File:Angstroms8.png|1026px]]<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
[[File:Angstroms7.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
When it comes to building the Angstrom image you have lots of options and recipes to choose from, each resulting in a different configuration and packages. The typical command would be:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake <IMAGE NAME><br />
<br />
Few examples of the types of Image you can build are ''systemd-image'' (minimalistic and perfect for embedded developers) or the ''systemd-gnome-image'' (With gnome2 desktop environment)<br />
<br />
Let us finally build the image now:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-gnome-image<br />
<br />
[[File:Angstroms9.png|1026px]]<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=312038Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-13T20:16:01Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx <br />
<br />
[[File:Angstroms8.png|1026px]]<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
[[File:Angstroms7.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
When it comes to building the Angstrom image you have lots of options and recipes to choose from, each resulting in a different configuration and packages. The typical command would be:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake <IMAGE NAME><br />
<br />
Few examples of the types of Image you can build are ''systemd-image'' (minimalistic and perfect for embedded developers) or the ''systemd-gnome-image'' (With gnome2 desktop environment)<br />
<br />
Let us finally build the image now:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-gnome-image<br />
<br />
[[File:Angstroms9.png|1026px]]<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311432Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:48:21Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
[[File:Angstroms8.png|1026px]]<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
[[File:Angstroms7.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
When it comes to building the Angstrom image you have lots of options and recipes to choose from, each resulting in a different configuration and packages. The typical command would be:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake <IMAGE NAME><br />
<br />
Few examples of the types of Image you can build are ''systemd-image'' (minimalistic and perfect for embedded developers) or the ''systemd-gnome-image'' (With gnome2 desktop environment)<br />
<br />
Let us finally build the image now:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-gnome-image<br />
<br />
[[File:Angstroms9.png|1026px]]<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms9.png&diff=311426File:Angstroms9.png2014-01-08T00:47:24Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms8.png&diff=311420File:Angstroms8.png2014-01-08T00:40:28Z<p>Jayneil: Jayneil uploaded a new version of &quot;File:Angstroms8.png&quot;</p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311414Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:38:13Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
[[File:Angstroms8.png|1026px]]<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
[[File:Angstroms7.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms8.png&diff=311408File:Angstroms8.png2014-01-08T00:37:43Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311402Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:36:52Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
[[File:Angstroms7.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms7.png&diff=311396File:Angstroms7.png2014-01-08T00:36:22Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311390Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:35:18Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
[[File:Angstroms6.png|1026px]]<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms6.png&diff=311384File:Angstroms6.png2014-01-08T00:34:49Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311378Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:33:13Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
[[File:Angstroms5.png|1026px]]<br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms5.png&diff=311372File:Angstroms5.png2014-01-08T00:31:10Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms4.png&diff=311366File:Angstroms4.png2014-01-08T00:30:09Z<p>Jayneil: Jayneil uploaded a new version of &quot;File:Angstroms4.png&quot;</p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311360Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:27:58Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
[[File:Angstroms4.png|1026px]]<br />
<br />
<br />
'''Step-7:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms4.png&diff=311354File:Angstroms4.png2014-01-08T00:27:05Z<p>Jayneil: Jayneil uploaded a new version of &quot;File:Angstroms4.png&quot;</p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms4.png&diff=311348File:Angstroms4.png2014-01-08T00:23:46Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311342Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:23:10Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
Now type the command below to switch to a stable branch of your choice:<br />
<br />
git checkout -b <stable branch name><br />
<br />
The command in our case becomes <br />
<br />
git checkout -b remotes/origin/angstrom-v2013.06-yocto1.4<br />
<br />
[[File:Angstroms3.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
<br />
'''Step-7:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms3.png&diff=311336File:Angstroms3.png2014-01-08T00:18:57Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311330Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:18:07Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
By default the git branch you will be working with will be ''master'' . Since the '''master''' continuously undergoing changes and bug fixes it can sometimes lead to unsuccessful build generation. So, it is better to switch to a stable branch. To see which branch you are currently working with type the commands below:<br />
<br />
cd setup-scripts/<br />
git branch -a<br />
<br />
[[File:Angstroms2.png|1026px]]<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
<br />
'''Step-7:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-8:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms2.png&diff=311324File:Angstroms2.png2014-01-08T00:11:36Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311318Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:11:12Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-7:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311312Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:11:00Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
<br />
'''Step-4:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
<br />
'''Step-5:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
<br />
'''Step-6:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
<br />
'''Step-7:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311306Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-08T00:10:11Z<p>Jayneil: /* Procedure */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
[[File:Angstroms1.png|1026px]]<br />
<br />
'''Step-4:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
'''Step-5:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
'''Step-6:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
'''Step-7:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=File:Angstroms1.png&diff=311300File:Angstroms1.png2014-01-08T00:08:52Z<p>Jayneil: </p>
<hr />
<div></div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311294Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-07T23:34:41Z<p>Jayneil: /* Writing the Angstrom Image to an external storage device */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
'''Step-4:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
'''Step-5:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
'''Step-6:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
'''Step-7:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
*[http://elinux.org/Installing_Angstrom_on_a_Hard_Disk Installing Angstrom on a Hard Disk] <br />
<br />
*[http://elinux.org/Minnowboard:Preparing_microSD_Card Installing Angstrom on a microSD card]<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneilhttps://elinux.org/index.php?title=Dummies_Guide_to_Building_Angstrom_Linux_for_MinnnowBoard&diff=311288Dummies Guide to Building Angstrom Linux for MinnnowBoard2014-01-07T23:32:39Z<p>Jayneil: /* Writing the Angstrom Image to an external storage device */</p>
<hr />
<div>{{Template:Minnowboard_home}}<br />
<br />
[[File:Angstrom_os_logo.png|center]]<br />
<br />
=Summary=<br />
This guide explains building the Embedded Linux distribution - [http://www.angstrom-distribution.org/ Angstrom] from source in a beginner friendly manner. <br />
<br />
==Important Notes==<br />
1. These instructions have been documented using Ubuntu 12.04 LTS as the reference operating system. It is advised that you also have the same setup. <br />
<br />
2. Please make sure that you have at least 18GB of free space available as the source code can take up a lot of space.<br />
<br />
3. It took 8 hours to build a systemd-image on a dual core I7 machine with 8GB RAM and only two(out of the possible 4) threads used.<br />
<br />
=Procedure=<br />
<br />
'''Step-1:'''<br />
<br />
Install the pre-requisites by typing the command below in the terminal:<br />
<br />
sudo apt-get install gawk wget git diffstat unzip build-essential chrpath libsdl1.2-dev xterm unzip texinfo \<br />
git texi2html subversion ncurses-dev sed cvs coreutils docbook-utils python-pysqlite2 help2man make \<br />
gcc g++ desktop-file-utils chrpath dosfstools kpartx bitbake<br />
<br />
'''Step-2:'''<br />
<br />
Change the default shell in Ubuntu from dash to bash typing the command below in the terminal::<br />
<br />
sudo dpkg-reconfigure bash<br />
<br />
'''Step-3:'''<br />
<br />
The next step is to download the [https://github.com/Angstrom-distribution/setup-scripts Angstrom setup scripts] which will help us prepare a development environment for building the Angstrom image. Type the following command in your terminal:<br />
<br />
git clone git://github.com/Angstrom-distribution/setup-scripts.git<br />
<br />
'''Step-4:'''<br />
<br />
Make the necessary changes to the local.conf file as shown below. This file can be found in ~/setup-scripts/conf/local.conf . <br />
<br />
# Add this to the bottom:<br />
MACHINE ?= "minnow"<br />
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" <br />
NOISO = "1"<br />
<br />
'''Explanation:'''<br />
* LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" : This is required to prevent the resulting image from <br />
including anything that might violate the license terms of the packages used to implement the video acceleration feature, <br />
such as gst-ffmpeg and ffmpeg.<br />
* NOISO = "1" : Due to a bug in ISO generation when building for EFI-only machines, it is necessary to include this line in <br />
your local.conf:<br />
<br />
'''Step-5:'''<br />
<br />
Setup the necessary environment for MinnowBoard by typing the command below in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh config minnow<br />
<br />
'''Step-6:'''<br />
<br />
Build the image by typing the following command in the terminal:<br />
<br />
MACHINE=minnow ./oebb.sh bitbake systemd-image<br />
<br />
'''Step-7:'''<br />
<br />
The resulting image will be located in ~/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/deploy/images/minnow/<br />
<br />
=Writing the Angstrom Image to an external storage device=<br />
<br />
Now that we have successfully built an Angstrom image from source, the next step is to write the image to an external storage device(microSD card, HDD etc.) and test it on the MinnowBoard. Depending on which type of storage device you are planning to write the image to, please select an appropriate link from below:<br />
<br />
=Troubleshooting=<br />
<br />
==Starting Over==<br />
<br />
==Deleting past images to free up space==<br />
<br />
[[Category: MinnowBoard]]</div>Jayneil