c17af3fd47
On the multi-MTD layout (default) the 'data' UBI volume is never created and thus not mounted by the system. This is because with this layout, the creation of the UBI volume is done by the 'update' command, but nobody updates this partition cause DEY doesn't generate an image for it. We want the 'data' UBI volume to be created so that the CC6UL can connect to the regular Remote Manager URI and store the certificate in it. As long as a UBI volume is created, Linux will mount it, so this commit erases the partition and creates the UBI volume. The same goes for the 'update' partition. The installer was relying on the recovery mechanism to wipe this partition, but this is not longer required with UBI. As long as the installer erases the partition and creates the volume, Linux will be able to mount it, so the boot in recovery mode has been removed from the script. Note: the formatting is only done for multi-MTD layout; the ubivolscript creates all volumes for single-MTD layout. Signed-off-by: Hector Palacios <hector.palacios@digi.com> |
||
|---|---|---|
| .. | ||
| alsa-state | ||
| ath-prop-tools | ||
| digi-sc-firmware | ||
| firmware-atheros | ||
| firmware-murata-infineon | ||
| firmware-murata-nxp | ||
| firmware-qualcomm | ||
| formfactor | ||
| libubootenv | ||
| trustfence-cst | ||
| trustfence-stm-signtools | ||
| u-boot | ||
| usbutils | ||