Changes between Version 14 and Version 15 of Yocto/Building


Ignore:
Timestamp:
05/08/2019 09:24:50 PM (6 years ago)
Author:
Ryan Erbstoesser
Comment:

update section for ubi size in building

Legend:

Unmodified
Added
Removed
Modified

  • Yocto/Building

    v14 v15  
    224224 * By default, images, kernels, etc are found in {{{tmp/deploy/images/ventana}}}.
    225225
    226 7. Grab .ubi file which contains both kernel and root filesystem and program it to the board with instructions below:
     2267. Use the .ubi file which contains both kernel and root filesystem and program it to the board with instructions in the section [#installing Installing Yocto UBI Files]:
     227 * Which ubi size to use, normal or large, has to do with the flash geometry size (see [wiki:/linux/ubi/#flashgeometry here] to determine your flash geometry) 
    227228{{{#!bash
    228229tmp/deploy/images/ventana/gateworks-image-multimedia-ventana_normal.ubi
    … …  
    231232
    232233Notes:
    233  * to download any updates and rebuild, repeat the above starting with step 3
    234  * to re-activate a new shell repeat the above starting with step 4 (you can only have 1 shell activated at a time - you need to activate a new shell if you have exited a previously activated shell)
    235  * to clean a specific recipe use {{{bitbake -f -c clean <recipe>}}}. Note that to represent the kernel you can use the virtual recipe name 'virtual/kernel'
     234 * To download any updates and rebuild, repeat the above starting with step 3
     235 * To re-activate a new shell repeat the above starting with step 4 (you can only have 1 shell activated at a time - you need to activate a new shell if you have exited a previously activated shell)
     236 * To clean a specific recipe use {{{bitbake -f -c clean <recipe>}}}. Note that to represent the kernel you can use the virtual recipe name 'virtual/kernel'
    236237  - Note: After cleaning a recipe, rebuild with the {{{--no-setscene}}} command line argument to bitbake, e.g. bitbake --no-setscene <recipe>
    237  * to clean all built items (but not remove downloaded sources or the sstate-cache) you can {{{rm -rf tmp}}}.
    238  * to clean everything and start over you can remove the entire build directory and repeat the above starting with step 4 (this will remove all downloaded sources as well)
     238 * To clean all built items (but not remove downloaded sources or the sstate-cache) you can {{{rm -rf tmp}}}.
     239 * To clean everything and start over you can remove the entire build directory and repeat the above starting with step 4 (this will remove all downloaded sources as well)
    239240
    240241Useful References:
    … …  
    377378
    378379= Installing Firmware =
    379 
     380[=#installing]
    380381== NAND FLASH ==
    381382There are 2 options:
    … …  
    383384 2. JTAG Programmer (more steps and slower, requires no network)- Link [wiki:jtag_instructions#CreatingjtagableimagesforVentana here]
    384385
    385 Boards with a NAND FLASH large enough to accommodate your image (Ventana boards have a 256MB NAND flash by default which is large enough for fsl-image-multimedia) can have the UBI filesystem created by the build process placed on them. A ubi image will be built in tmp/deploy/images directory alongside the kernel and filesystem tarballs. The ubi image will end with _normal.ubi which is suitable for standard NAND flash sizes on Ventana boards. If you have a Ventana with a 1GB or larger NAND device, you need to build for the 'large' NAND flash layout which you can do by changing the UBI_CONFIG variable in {{{sources/meta-gateworks/conf/machine/ventana.conf}}} from 'normal' to 'large' which will result in a ubi image ending with {{{_large.ubi}}}.
     386Boards with a NAND FLASH large enough to accommodate your image (Ventana boards have a 256MB NAND flash by default which is large enough for fsl-image-multimedia) can have the UBI filesystem created by the build process placed on them. A ubi image will be built in tmp/deploy/images directory alongside the kernel and filesystem tarballs.
     387
     388 * Which ubi size to use, normal or large, has to do with the flash geometry size (see [wiki:/linux/ubi/#flashgeometry here] to determine your flash geometry) 
     389
     390 * To build for the 'large' NAND flash layout can be done by changing the UBI_CONFIG variable in {{{sources/meta-gateworks/conf/machine/ventana.conf}}} from 'normal' to 'large' which will result in a ubi image ending with {{{_large.ubi}}}.
    386391
    387392To install firmware to a Ventana board using Serial/ENET, do the following: