Deployment Tool v2026.1 and below / Nexus: Why does Multi-Boot Dynamic/Static image switching fail when SEDC is enabled?

Deployment Tool v2026.1 and below / Nexus: Why does Multi-Boot Dynamic/Static image switching fail when SEDC is enabled?

Description:

When generating Multi-Boot MCS files with Soft Error Detection and Correction (SEDC) enabled, device fail to boot or jump to the designated next boot address in Dynamic/Static mode.


Solution:
Due to an issue in Radiant Deployment Tool v2026.1 and below, enabling SEDC caused an incorrect frame offset calculation during MCS file generation. This prevented the correct Next Boot Address from being written into the bitstream header / jump table, leading to fallback boot or boot timeout errors.


Resolution / Workaround:

  1. Software Update: Upgrade to Lattice Radiant version 26.1.1.
  2. Workaround for earlier versions: If using an unpatched Radiant version, disable SEDC in the bitstream generation settings when packaging the Multi-Boot MCS file, or manually verify frame alignment without SEDC enabled.