otamaker: Include eeprom-ab in the payload list

eeprom-ab support needs rpi-connect-ota 1.3.14 or later.

Signed-off-by: Phil Elwell <phil@raspberrypi.com>

Author: pelwell

otamaker/README.md

@@ -81,6 +81,7 @@ The artefact header is meant to provide a high-level view of the contents - what
 
 The following payload types are recognised:
 * `image-sparse` - a _sparse image_ of a complete partition, which contains all the data sectors in full but with holes and chunks of fixed values represented efficiently. The name of the payload must match the name of a partition - `boot` and `system` for the `trixie-minbase-ab` images from `rpi-image-gen`. These payloads are written directly to the indicated partition as they are downloaded - this saves time and means you don't need large amounts of temporary storage to host it.
+* `eeprom-ab` - a Pi 5 A/B EEPROM update (requires that an AB-compatible EEPROM image is already installed, that the image includes `rpi-connect-ota` 1.3.14 or later and the `rpieepromab` package, and that `config.txt` includes `dtoverlay=nospi10`).
 * `script` - a program to execute on the remote device. As the name suggests, this is expected to be a script of some description, but it doesn't have to be.
 * `tmpfile` - some other file to be copied to the device for the duration of the update. These are intended to be used by scripts, which they must appear before in the list of payloads in order to be accessible.