[SRU] Update Machine Entries for AMD-Xilinx Kria Boards

[Talha Can Havadar]

[Impact]

Since the model names in the DTBs have been updated in AMD-Xilinx kernel, we need to update the machine entries in flash-kernel as well.

[Where problems could occur]

The patch adds support for the new model names of AMD-Xilinx Kria boards and also separates the boot script.

So problems can only occur on the following boards:

* Kria KR260
* Kria KV260
* Kria KD240

[Test Case]

* Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed)
* Update flash-kernel to the version in -proposed: sudo apt install -t jammy-proposed flash-kernel
* Run flash-kernel (if the upgrade didn't already): sudo flash-kernel
* Reboot: sudo reboot
* Ensure system boots successfully

[Regression Potential]

The only database entry adjusted is for those boards listed, and DEP-8 tests already cover the functionality of matching boards to database entries, including those using wildcards.

As part of this update, we will also separate the boot script of Kria boards from ZCU, so that we won't risk introducing a regression to other boards.

As the patch creates a new boot script for boards (listed above), booting should be re-tested against the potentially affected boards under the proposed package.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "noble-1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

[Launchpad Janitor (janitor)]

This bug was fixed in the package flash-kernel - 3.107ubuntu5

---------------
flash-kernel (3.107ubuntu5) noble; urgency=medium

  [ Juerg Haefliger ]
  * Remove raspi-nolpae kernel flavor from all Pi boards (LP: #2048864)
  * Add raspi-realtime kernel flavor to bcm2711 and bcm2712 based Pi boards
    (LP: #2051960)

  [ Talha Can Havadar ]
  * Update Xilinx board support (LP: #2054556)
    - Remove support claim for Xilinx ZCU111
    - Add new machine entries for KV260 and KR260 due to model string changes
    - Create separate bootscript for AMD-Xilinx Kria board family

 -- Dave Jones <email address hidden> Thu, 22 Feb 2024 15:29:21 +0000

[Dave Jones (waveform)]

Tweaked the SRU regression section a bit, otherwise looks good; sponsoring for jammy

[Łukasz Zemczak (sil2100)]

Hello Talha, or anyone else affected,

Accepted flash-kernel into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/flash-kernel/3.104ubuntu20 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

The upload per-se seems fine, so I accepted it as is. It worries me however the removal of support claim for Xilinx ZCU111. Of course that's just a no-op change, as it was only in the comment, but it just made me wonder of any possible ZCU111 users in jammy. But as long as the new uploads do not explicitly disable or break the functionality there, I'm good as-is.

[Talha Can Havadar (tchavadar)]

On KD240,

```
Generating u-boot image... done.
Taking backup of image.fit.
Installing new image.fit.
Generating boot script u-boot image... done.
Taking backup of boot.scr.uimg.
Installing new boot.scr.uimg.

ubuntu@kria:~$ apt policy flash-kernel
flash-kernel:
  Installed: 3.104ubuntu20
  Candidate: 3.104ubuntu20
  Version table:
 *** 3.104ubuntu20 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 Packages
        100 /var/lib/dpkg/status
     3.104ubuntu19 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
     3.104ubuntu17xlnx2 500
        500 http://oem.archive.canonical.com/updates jammy-limerick/public arm64 Packages
     3.104ubuntu9 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

FRU Inventory From File: /sys/devices/platform/axi/ff030000.i2c/i2c-1/1-0050/eeprom

  FRU Board Manufacturing Date/Time: 06/26/23 - 13:40:00
  FRU Board Manufacturer: XILINX
  FRU Board Product Name: SMK-K24-XCL2G
  FRU Board Serial Number: 51281B136M4F

```

And board also reboots fine after the update.

[Talha Can Havadar (tchavadar)]

On KV260,

```
flash-kernel: installing version 5.15.0-1025-xilinx-zynqmp
Couldn't find DTB on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image-5.15.0-1025-xilinx-zynqmp /lib/firmware/5.15.0-1025-xilinx-zynqmp/device-tree/
Generating u-boot image... done.
Taking backup of image.fit.
Installing new image.fit.
Generating boot script u-boot image... done.
Taking backup of boot.scr.uimg.
Installing new boot.scr.uimg.

ubuntu@kria:~$ apt policy flash-kernel
flash-kernel:
  Installed: 3.104ubuntu20
  Candidate: 3.104ubuntu20
  Version table:
 *** 3.104ubuntu20 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 Packages
        100 /var/lib/dpkg/status
     3.104ubuntu19 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
     3.104ubuntu17xlnx2 500
        500 http://oem.archive.canonical.com/updates jammy-limerick/public arm64 Packages
     3.104ubuntu9 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

som:
  board:
    date: 13878118
    fileid: '00'
    language: 0
    manufacturer: XILINX
    part: 5057-01
    pcieinfo:
      Device_ID: '0000'
      SubDevice_ID: '0000'
      SubVendor_ID: '0000'
      Vendor_ID: 10ee
    product: SMK-K26-XCL2G
```
And board also reboots fine after the update.

[Luca Corna (lucacorna)]

@Łukasz,

about your concern about ZCU111, we should have explained that we don't support ZCU111 and it never was: https://ubuntu.com/download/amd

[Vic Liu (zongminl)]

On KR260,
```
ubuntu@kria:~$ apt-cache policy flash-kernel
flash-kernel:
  Installed: 3.104ubuntu20
  Candidate: 3.104ubuntu20
  Version table:
 *** 3.104ubuntu20 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 Packages
        100 /var/lib/dpkg/status
     3.104ubuntu19 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
     3.104ubuntu17xlnx2 500
        500 http://oem.archive.canonical.com/updates jammy-limerick/public arm64 Packages
     3.104ubuntu9 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

Preparing to unpack .../flash-kernel_3.104ubuntu20_arm64.deb ...^M
Unpacking flash-kernel (3.104ubuntu20) over (3.104ubuntu19) ...^M
Setting up flash-kernel (3.104ubuntu20) ...^M
Installing new version of config file /etc/flash-kernel/bootscript/bootscr.zynqmp ...^M
flash-kernel: deferring update (trigger activated)^M
Processing triggers for man-db (2.10.2-1) ...^M
Processing triggers for initramfs-tools (0.140ubuntu13.4) ...^M
update-initramfs: Generating /boot/initrd.img-5.15.0-1025-xilinx-zynqmp^M
flash-kernel: installing version 5.15.0-1025-xilinx-zynqmp^M
Couldn't find DTB on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image-5.15.0-1025-xilinx-zynqmp /lib/firmware/5.15.0-1025-xilinx-zynqmp/device-tree/^M
Generating u-boot image... done.^M
Taking backup of image.fit.^M
Installing new image.fit.^M
Generating boot script u-boot image... done.^M
Taking backup of boot.scr.uimg.^M
Installing new boot.scr.uimg.^M
Processing triggers for flash-kernel (3.104ubuntu20) ...^M
flash-kernel: installing version 5.15.0-1025-xilinx-zynqmp^M
Couldn't find DTB on the following paths: /etc/flash-kernel/dtbs /usr/lib/linux-image-5.15.0-1025-xilinx-zynqmp /lib/firmware/5.15.0-1025-xilinx-zynqmp/device-tree/^M
Generating u-boot image... done.^M
Taking backup of image.fit.^M
Installing new image.fit.^M
Generating boot script u-boot image... done.^M
Taking backup of boot.scr.uimg.^M
Installing new boot.scr.uimg.^M

FRU Inventory From File: /sys/devices/platform/axi/ff030000.i2c/i2c-1/1-0050/eeprom

  FRU Board Manufacturing Date/Time: 10/07/21 - 17:38:00
  FRU Board Manufacturer: XILINX
  FRU Board Product Name: SMK-K26-XCL2G
  FRU Board Serial Number: 50571A119R10
```

The board reboots fine after the update

[Talha Can Havadar (tchavadar)]

As explained in the comments above new version of the flash-kernal is tested on platforms. I changed the tag to `verification-done-jammy`

[Launchpad Janitor (janitor)]

This bug was fixed in the package flash-kernel - 3.104ubuntu20

---------------
flash-kernel (3.104ubuntu20) jammy; urgency=medium

  [ Talha Can Havadar ]
  * Update Xilinx board support (LP: #2054556)
    - Remove support claim for Xilinx ZCU111
    - Add new machine entries for KV260 and KR260 due to model string changes
    - Create separate bootscript for AMD-Xilinx Kria board family

 -- Talha Can Havadar <email address hidden> Thu, 29 Feb 2024 15:32:06 +0000

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for flash-kernel has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.