The official way to trigger and execute image-based OTA update is by putting the payload under /ota and corresponding ota_tool under a specified ${WORKDIR}.
However, does it support that we can put these files in an external storage, such as SD card or M.2 drive, and still complete to update the BSP flashed in emmc?
Or it would be suggested to clear the disk space first by following the guide here then do the update with internal drive?
The case is that my target device doesn’t have enough disk space for ordinary OTA process and I’m looking for a workaround.
I think /ota is necessary to be located under root directory to update current roorfs, but you could put other update tools in ${WORKDIR} on external storage.
Or you could refer to the guide to optimize the disk space first.
If /ota is necessary to be located under root directory, does that mean I no matter what have to clear out at least a certain amount of space for storing decompressed “ota_payload”? i.e. a spare space bigger than the size of ota_payload.tar.gz?