Public bug reported: [Impact]
xlnx-image-update is currently available in resolute but not properly delivered via the noble archive path we need. For noble images, functionality is currently provided via Ubuntu Xilinx main/default image composition, which is not ideal for lifecycle management. Publishing xlnx-image-update in noble archive enables supported package- based delivery and remote upgrade of Xilinx boot firmware on deployed devices. [Test Plan] 1. Build the noble source package from ubuntu/noble-devel. 2. Install the package on TW lab Xilinx target device(s). 3. Verify command behavior with: - no arguments (expect usage/error output and non-zero exit) - invalid path argument (expect clean failure) - valid boot image path argument (expected update flow starts/completes) 4. Reboot and verify the expected image/boot result on target hardware. 5. Confirm no regressions in the normal boot/update workflow. [Where problems could occur] - Incorrect write/update to QSPI alternate image could affect next boot behavior. - Mitigation: - Scope is limited to devices explicitly using this utility. - Package introduces no daemon/service. - Hardware validation performed in TW lab on target devices before release. [Other Info] - Development repo: https://code.launchpad.net/~limerick-team/ubuntu/+source/xlnx-image-update/+git/xlnx-image-update - User MP (fork -> limerick-team): TBD - Build logs/artifacts: TBD - Test logs from TW lab: TBD - Follow-up MP (limerick-team -> ubuntu archive): TBD ** Affects: xlnx-image-update (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2145545 Title: [SRU] [Noble] Backport xlnx-image-update to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xlnx-image-update/+bug/2145545/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
