Operating system image installation methods: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 16: | Line 16: | ||
| block unsigned |
| block unsigned |
||
| .zd alone |
| .zd alone |
||
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key# |
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key#Disabling_the_security_system|disable-security]], [[Ok|interrupt boot]], then use the ''fs-update'' command |
||
| [[Release notes]] |
| [[Release notes]] |
||
|- |
|- |
||
| Line 26: | Line 26: | ||
| nand unsigned |
| nand unsigned |
||
| .img and .crc |
| .img and .crc |
||
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key# |
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key#Disabling_the_security_system|disable-security]], [[Ok|interrupt boot]], then use the ''copy-nand'' command |
||
| [[Release notes]] [[Clean-install_procedure#Development_builds|Clean Install Procedure]] [[Nandblaster_for_XO-1]] |
| [[Release notes]] [[Clean-install_procedure#Development_builds|Clean Install Procedure]] [[Nandblaster_for_XO-1]] |
||
|- |
|- |
||
| nand partitioned<br> |
| nand partitioned<br> |
||
| .dat and .img |
| .dat and .img |
||
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key# |
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key#Disabling_the_security_system|disable-security]], [[Ok|interrupt boot]], then use the ''update-nand'' command |
||
| Used by [[DebXO]]. Used by [[UBIFS_initial_experiments|UBIFS experiments]]. See also [[OFW_NAND_FLASH_Updater|Technical description]]. |
| Used by [[DebXO]]. Used by [[UBIFS_initial_experiments|UBIFS experiments]]. See also [[OFW_NAND_FLASH_Updater|Technical description]]. |
||
|} |
|} |
||
The signed installation methods are the same for XO-4, XO-1.75, XO-1.5 and XO-1. This was by design, since we do not wish to increase the training burden for the deployment teams |
The signed installation methods are the same for XO-4, XO-1.75, XO-1.5 and XO-1. This was by design, since we do not wish to increase the training burden for the deployment teams. |
||
A deployment will typically [[OSBuilder#Signing_preparation|sign their builds]] and [[Firmware_security#Adding_Deployment_Keys_to_Manufacturing_Data|inject deployment keys]] at manufacture or on site. |
|||
The unsigned installation methods depend on the type of internal storage. XO-1 has raw NAND Flash. XO-1.5, XO-1.75 and XO-4 have microSD or eMMC managed Flash. |
The unsigned installation methods depend on the type of internal storage. XO-1 has raw NAND Flash. XO-1.5, XO-1.75 and XO-4 have microSD or eMMC managed Flash. |
||
Latest revision as of 02:14, 1 January 2014
We use a few different methods to install operating system images.
| installation method | what files are required | how to install | references |
|---|---|---|---|
| block signed | .zd and fs.zip | hold down the four game pad buttons and then turn on the laptop | Release notes |
| block unsigned | .zd alone | check if security is enabled, if so obtain developer key and disable-security, interrupt boot, then use the fs-update command | Release notes |
| nand signed | .img and fs.zip | hold down the four game pad buttons and then turn on the laptop | Release notes Clean Install Procedure Nandblaster_for_XO-1 |
| nand unsigned | .img and .crc | check if security is enabled, if so obtain developer key and disable-security, interrupt boot, then use the copy-nand command | Release notes Clean Install Procedure Nandblaster_for_XO-1 |
| nand partitioned |
.dat and .img | check if security is enabled, if so obtain developer key and disable-security, interrupt boot, then use the update-nand command | Used by DebXO. Used by UBIFS experiments. See also Technical description. |
The signed installation methods are the same for XO-4, XO-1.75, XO-1.5 and XO-1. This was by design, since we do not wish to increase the training burden for the deployment teams.
A deployment will typically sign their builds and inject deployment keys at manufacture or on site.
The unsigned installation methods depend on the type of internal storage. XO-1 has raw NAND Flash. XO-1.5, XO-1.75 and XO-4 have microSD or eMMC managed Flash.
See also Firmware/Storage.