slot

Target slot for the image: SLOT_PRIMARY or SLOT_SECONDARY.

By default images are run from the primary slot. An update will be written to the secondary slot and will be swapped to the primary slot after it is confirmed and reset.

If the device supports Direct XIP feature it is possible to run an app from a secondary slot. The image has to be compiled for this slot. A ZIP package in that case may contain both images. In that case only the one compiled for the available slot will be sent, there is no swapping and the image is run directly from the slot that it was sent to.

Note: If the value given to the constructor is greater than 1, it will be truncated to the reminder of division by 2. Some implementations number slots as (image * 2 + slot), i.e. slot 3 is secondary slot of image 1.