| Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende ÜberarbeitungLetzte ÜberarbeitungBeide Seiten der Revision |
| software:linux:images:start [2023-05-10 15:22] – Urs Graf | software:linux:images:start [2023-07-07 15:23] – Urs Graf |
|---|
| ===== Downloading ===== | ===== Downloading ===== |
| |
| ==== x86 & Beaglebone Blue ==== | The images that are currently available for the [[ ..:yocto:bblue ]], [[ ..:yocto:cb20 ]] and [[ ..:yocto:x86-rt ]] can be downloaded from the {{https://gitlab.ost.ch/tech/inf/public/yocto/meta-ost/-/packages | meta-ost Gitlab package registry}}. |
| |
| The images that are currently available for the [[ ..:yocto:bblue ]] and [[ ..:yocto:x86-rt ]] can be downloaded from the {{https://gitlab.ost.ch/tech/inf/public/yocto/meta-ost/-/packages | meta-ost Gitlab package registry}}. | Please note, that these images are built for development, see [[software:linux:yocto:meta-ost#ost-distro_vs_ost-devel_-_Development_vs_Production_Images|Development vs Production]]. For production images you have to built it with a full yocto installation, see [[software:linux:yocto:setup|Setup and Building]] or use the eSDK, see [[software:linux:yocto:sdks|SDK's]]. |
| | |
| Please note, that these images are built for development, see [[software:linux:yocto:meta-ost#ost-distro_vs_ost-devel_-_Development_vs_Production_Images|Development vs Production]]. For production images you have to built it with a full yocto installation, see [[software:linux:yocto:setup|Setup and Building]] or use the eSDK, see [[software:linux:yocto:sdk:start|SDK's]]. | |
| |
| | ---- |
| | DELETEME |
| ==== Toradex ==== | ==== Toradex ==== |
| |
| https://wiki.bu.ost.ch/infoportal/_media/software/linux/images/image_list.json | https://wiki.bu.ost.ch/infoportal/_media/software/linux/images/image_list.json |
| </code> | </code> |
| | ---- |
| |
| | ===== Extracting ===== |
| === Flashing a .wic image === | The images for [[ ..:yocto:bblue ]] and [[ ..:yocto:x86-rt ]] are provided in ''gzipped'' and need to be decompressed using ''gunzip'' before use: |
| Linux script example for ''.wic'' image flashing onto an external storage device, e.g. an external SD card (<color #ed1c24>Beware: ''sdb'' has to be replaced with the correct device (use ''lsblk'' command to discover the correct device)!</color>): \\ | |
| <code> | <code> |
| #!/bin/sh | gunzip ost-image-*.wic.gz |
| umount /dev/sdb* | </code> Note that ''gunzip'' will remove the original ''.wic.gz'' file and only the ''.wic'' file will be available after. ''gzip'' and ''gunzip'' should come preinstalled on most distributions, otherwise search for the ''gzip'' package in your distro's repositories. |
| wipefs -a /dev/sdb | |
| dd if=ost-ros-image-melodic-bblue.wic of=/dev/sdb bs=1M status=progress | |
| eject /dev/sdb | |
| </code> | |
| ===== Extracting the archives ===== | |
| |
| ==== Gitlab Images ==== | Images for [[ ..:yocto:cb20 ]] are provided as *Tezi*.tar file. You have to unpack it before it is recognized by the easy installer. |
| The images are provided in ''gzipped'' and need to be decompressed using ''gunzip'' before use: | |
| <code> | <code> |
| gunzip ost-image-*.wic.gz | tar -xvf *Tezi*.tar |
| </code> | </code> |
| |
| Note that ''gunzip'' will remove the original ''.wic.gz'' file and only the ''.wic'' file will be available after. ''gzip'' and ''gunzip'' should come preinstalled on most distributions, otherwise search for the ''gzip'' package in your distro's repositories. | |
| |
| The SDK can be downloaded directly from Gitlab and do not need to be extracted any further. | ===== Flashing onto a SD Card or USB Stick ==== |
| | Linux script example for ''.wic'' image flashing onto an external storage device, e.g. an external SD card. <color #ed1c24>Beware: ''sdb'' has to be replaced with the correct device. Use ''lsblk'' command to discover the correct device!</color>. ''sdX'' where ''X'' is a small letter starting from ''a'' usually represents a SATA or USB drive, names starting with ''nvme'' represent NVME SSDs and SD cards usually start with ''mmcblk''. |
| | These names represent the device as found in ''/dev'', so ''sda'' is found under ''/dev/sda''. ''lsblk'' uses a tree to show devices and their partitions. For example ''sda1'' is the first partition on ''sda'' and ''nvme1n1p1'' is the first partition of ''nvme1n1''. |
| |
| ==== Legacy Images / SDK ==== | **WARNING: Writing the image to the USB Stick will erase all content! Make absolutely sure you have identified the correct device! dd will not hesitate to override your OS drive if you tell it to do!** |
| |
| Images and SDKs in the ''tar.xz'' format can be extracted using the 'tar' command. | |
| <code> | <code> |
| tar -vxJf <filename> | #!/bin/sh |
| | umount /dev/sdb* |
| | wipefs -a /dev/sdb |
| | dd if=ost-ros-image-melodic-bblue.wic of=/dev/sdb bs=1M status=progress |
| | eject /dev/sdb |
| </code> | </code> |
| | |
| |
| ===== Using the Images ===== | ===== Using the Images ===== |
| | generic x86 | [[ ..:yocto:x86-rt ]] | | | generic x86 | [[ ..:yocto:x86-rt ]] | |
| |
| ===== Creating Custom Images ===== | ==== Configuring the Network ==== |
| | |
| Custom Images can be built by folliwing the [[ ..:yocto/getting_started_cpp | getting started guide ]] up to and including "Building an Image". | |
| | |
| ==== Creating Archives ==== | |
| | |
| This step is optional and only needed if the images need to be in the same format as the images provided on the [[ .:downloads ]] page | |
| | |
| The following command can be used to create ''tar.xz'' archives like provided above: | |
| | |
| <code> | |
| tar -C <path to target> -cvhJf ntb-dev-image-2020.02.21.tar.xz <target file/folder> | |
| </code> | |
| | |
| For example: | |
| <code> | |
| tar -C tmp/deploy/images/ -cvhJf ntb-dev-image-2020.02.21.tar.xz bblue | |
| </code> | |
| |
| ''ntb-dev-image-1.0-rc0.tar.xz'' now contains a directory called bblue (since bblue was a folder originally) and all its content. | See [[software:linux:linux_os:network|General Network Settings]] for help to setup necessary network connections. |
| If one was to use ''tar -C tmp/deploy -cJf ntb-dev-image-2020.02.21.tar.xz images/bblue'', the archive would contain an ''images'' folder with ''bblue'' inside it. | |
