diff --git a/content/guides/image_building.md b/content/guides/image_building.md
index 3de4239e1ce6d8ef5bc239546d16611a45d95b51..770d3841942e25bdc058e9e73bf6de6a98e48f91 100644
--- a/content/guides/image_building.md
+++ b/content/guides/image_building.md
@@ -71,7 +71,7 @@ It is important to consider which version of Apertis is going to be used. At
 any given time, Apertis has an old and new stable release and a version being
 actively developed. As this guide is acting as a demonstration and as there'll
 be no product release the latest Apertis stable
-[release]( {{< ref "release.md" >}} ) will be used, v2023 at time of writing.
+[release]( {{< ref "release.md" >}} ) will be used, v2024 at time of writing.
 
 {{% notice tip %}}
 To make best use of the release support of the Apertis project, developers are
@@ -131,13 +131,36 @@ machine of the target architecture.
 
 The process for setting up a devroot is documented in
 [Development containers using devroot-enter]( {{< ref "tooling.md#development-containers-using-devroot-enter" >}} ).
- Download the latest v2023 ARM 64-bit devroot, install it and spawn a devroot
-container.
+Download the latest v2024 ARM 64-bit devroot, install it and spawn a devroot
+container using the `devroot_enter`. This command will automatically bind the
+user's home directory, but we will need to find it manually:
+
+```
+$ devroot-enter ${DEVROOT_PATH}
+...
+user@devroot:/tmp$ cd ${HOMEDIR}
+user@devroot:/home/user$
+```
+
+We will install
+[`git-buildpackage`](https://manpages.debian.org/bookworm/git-buildpackage/git-buildpackage.1.en.html)
+which is a useful tool to help with building debian packages and setup the name and email used by Git:
+
+```
+user@devroot:/home/user$ sudo apt update
+...
+user@devroot:/home/user$ sudo apt install git-buildpackage
+...
+user@devroot:/home/user$ git config --global user.name "External Developer"
+user@devroot:/home/user$ git config --global user.email "external@example.org"
+user@devroot:/home/user$ export DEBEMAIL="External Developer <external@example.org>"
+
+```
 
 # Building Arm Trusted Firmware
 
 Looking at the
-[documentation for building U-Boot for the Allwinner Arm SoCs](https://gitlab.apertis.org/pkg/u-boot/-/blob/apertis/v2023/doc/board/allwinner/sunxi.rst),
+[documentation for building U-Boot for the Allwinner Arm SoCs](https://gitlab.apertis.org/pkg/u-boot/-/blob/apertis/v2024/doc/board/allwinner/sunxi.rst),
 we can see that Arm Trusted Firmware (ATF) is a dependency for building U-Boot, so
 we'll start with that.
 
@@ -146,18 +169,18 @@ The Apertis project already has a
 we can clone that repsoitory locally:
 
 ```
-$ git clone https://gitlab.apertis.org/pkg/arm-trusted-firmware.git
-$ cd arm-trusted-firmware
+user@devroot:/home/user$ git clone https://gitlab.apertis.org/pkg/arm-trusted-firmware.git
+user@devroot:/home/user$ cd arm-trusted-firmware
 ```
 
 In order to make it a little easier to track changes made here and updates made
 by the Apertis project to ATF over time (allowing easier updating in the
 future) we will create a branch under a distinct project name. For example if
-we use "orange" as our project name, we will create an `orange/v2023` branch
-from the `apertis/v2023` branch:
+we use "orange" as our project name, we will create an `orange/v2024` branch
+from the `apertis/v2024` branch:
 
 ```
-$ git checkout -b orange/v2023 apertis/v2023
+user@devroot:/home/user/arm-trusted-firmware$ git checkout -b orange/v2024 origin/apertis/v2024
 ```
 
 {{% notice note %}}
@@ -168,39 +191,39 @@ creating our customised "downstream" packages.
 Looking at the
 [hardware documentation](http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-2.html)
 we can see that the device has the Allwinner H616 CPU. The
-[U-Boot documentation](https://gitlab.apertis.org/pkg/u-boot/-/blob/apertis/v2023/doc/board/allwinner/sunxi.rst)
+[U-Boot documentation](https://gitlab.apertis.org/pkg/u-boot/-/blob/apertis/v2024/doc/board/allwinner/sunxi.rst)
 helpfully tells us for this SoC we need to build ATF for the `sun50i_h616`
 platform.
-[Looking in `debian/rules`](https://gitlab.apertis.org/pkg/arm-trusted-firmware/-/blob/apertis/v2023/debian/rules)
+[Looking in `debian/rules`](https://gitlab.apertis.org/pkg/arm-trusted-firmware/-/blob/apertis/v2024/debian/rules)
 we find a list of platforms that the package is built for, so we add `sun50i_h616` to this:
 
 ```diff
 --- a/debian/rules
 +++ b/debian/rules
-@@ -14,7 +14,7 @@
+@@ -14,7 +14,7 @@ else
  VERBOSE=1
  endif
  
--platforms := g12a gxbb sun50i_a64 sun50i_h6 rk3328 rk3399 rpi3 rpi4 imx8mn k3
-+platforms := g12a gxbb sun50i_a64 sun50i_h6 sun50i_h616 rk3328 rk3399 rpi3 rpi4 imx8mn k3
- platforms_nodebug := imx8mq
+-platforms := g12a gxbb sun50i_a64 sun50i_h6 rcar rk3328 rk3399 rpi3 rpi4 imx8mn imx8mm k3
++platforms := g12a gxbb sun50i_a64 sun50i_h6 sun50i_h616 rcar rk3328 rk3399 rpi3 rpi4 imx8mn imx8mm k3
+ # Disable building of imx8mq, as it is not well supported upstream.
+ #platforms_nodebug := imx8mq
  
- # By default, iMX8MN uses UART2 console. However, other boards supported
 ```
 
 Commit this change:
 
 ```
-$ git commit -s -m "Add sun50i_h616 to build platforms" debian/rules
+user@devroot:/home/user/arm-trusted-firmware$ git commit -s -m "Add sun50i_h616 to build platforms" debian/rules
 ```
 
 We should also create a changelog entry for a new release and commit it:
 
 ``` 
-$ gbp dch --git-author --ignore-branch -l orange -R
-$ DEBIAN_PACKAGE=$(dpkg-parsechangelog -S Source)
-$ DEBIAN_VERSION=$(dpkg-parsechangelog -S Version)
-$ git commit -s -m "Release ${DEBIAN_PACKAGE} version ${DEBIAN_VERSION}" debian/changelog
+user@devroot:/home/user/arm-trusted-firmware$ gbp dch --git-author --ignore-branch -l orange -R
+user@devroot:/home/user/arm-trusted-firmware$ DEBIAN_PACKAGE=$(dpkg-parsechangelog -S Source)
+user@devroot:/home/user/arm-trusted-firmware$ DEBIAN_VERSION=$(dpkg-parsechangelog -S Version)
+user@devroot:/home/user/arm-trusted-firmware$ git commit -s -m "Release ${DEBIAN_PACKAGE} version ${DEBIAN_VERSION}" debian/changelog
 ```
 
 {{% notice info %}}
@@ -209,36 +232,19 @@ suffix for a local "downstream" revision of the Apertis package. See our
 documentation on [versioning]( {{< ref "versioning.md" >}} ) for more details.
 {{% /notice %}}
 
-We will now build it locally, using the devroot that we setup earlier. First
-enter the devroot and find the source tree, the `devroot_enter` command will
-automatically bind the user's home directory:
-
-```
-$ devroot-enter ${DEVROOT_PATH}
-...
-user@devroot:/tmp$ cd ${ATF_SOURCE_PATH}
-user@devroot:/home/user/arm-trusted-firmware$ 
-```
-
-In order to build ATF successfully, we need to install it's build dependencies.
-We will also install
-[`git-buildpackage`](https://manpages.debian.org/bookworm/git-buildpackage/git-buildpackage.1.en.html)
-which is a useful tool to help with building debian packages:
+We will now build it locally using the devroot.  In order to build ATF
+successfully, we need to install it's build dependencies:
 
 ```
-user@devroot:/home/user/arm-trusted-firmware$ sudo apt update
-...
 user@devroot:/home/user/arm-trusted-firmware$ sudo apt build-dep arm-trusted-firmware
 ...
-user@devroot:/home/user/arm-trusted-firmware$ sudo apt install git-buildpackage
-...
 user@devroot:/home/user/arm-trusted-firmware$ 
 ```
 
 We can then use `git-buildpackage` to build ATF:
 
 ```
-user@devroot:/home/user/arm-trusted-firmware$ gbp buildpackage --git-ignore-branch -a arm64 -B -d -uc -us
+user@devroot:/home/user/arm-trusted-firmware$ gbp buildpackage --git-ignore-branch iB -d -uc -us
 ```
 
 In order for the U-Boot build to use the binaries in the package of ATF that
@@ -247,10 +253,11 @@ was just built, we must install the new package in the devroot:
 ```
 user@devroot:/home/user/arm-trusted-firmware$ cd ..
 user@devroot:/home/user$ sudo dpkg -i arm-trusted-firmware_*_arm64.deb 
-(Reading database ... 31313 files and directories currently installed.)
- Preparing to unpack arm-trusted-firmware_2.7.0+dfsg-2+apertis3orange1_arm64.deb ...
-Unpacking arm-trusted-firmware (2.7.0+dfsg-2+apertis3orange1) over (2.7.0+dfsg-2+apertis3bv2023preb1) ...
-Setting up arm-trusted-firmware (2.7.0+dfsg-2+apertis3orange1) ...
+Selecting previously unselected package arm-trusted-firmware.
+(Reading database ... 30207 files and directories currently installed.)
+Preparing to unpack arm-trusted-firmware_2.10.0+dfsg-1+apertis2orange1_arm64.deb ...
+Unpacking arm-trusted-firmware (2.10.0+dfsg-1+apertis2orange1) ...
+Setting up arm-trusted-firmware (2.10.0+dfsg-1+apertis2orange1) ...
 user@devroot:/home/user$
 ```
 
@@ -267,9 +274,9 @@ user@devroot:/home/user$
 Now that we have the required ATF binaries we can modify U-Boot to build for our board. Start by cloning the [Apertis U-Boot repository](https://gitlab.apertis.org/pkg/u-boot) (as we did with ATF) and creating a downstream project branch:
 
 ```
-$ git clone https://gitlab.apertis.org/pkg/u-boot.git
-$ cd u-boot
-$ git checkout -b orange/v2023 apertis/v2023
+user@devroot:/home/user$ git clone https://gitlab.apertis.org/pkg/u-boot.git
+user@devroot:/home/user$ cd u-boot
+user@devroot:/home/user/u-boot$ git checkout -b orange/v2024 origin/apertis/v2024
 ```
 
 Like with ATF, we need to update the package configuration to build for the Orange Pi Zero2. The U-Boot package builds for a lot of different boards already, with the configuration for these split out from `debian/rules` into `debian/targets/mk`. To add the Pi Zero, we add the following entries to this file:
@@ -277,9 +284,9 @@ Like with ATF, we need to update the package configuration to build for the Oran
 ```diff
 --- a/debian/targets.mk
 +++ b/debian/targets.mk
-@@ -263,6 +263,11 @@
+@@ -265,6 +265,11 @@ ifeq (${DEB_HOST_ARCH},arm64)
      spl/sunxi-spl.bin u-boot-nodtb.bin u-boot-sunxi-with-spl.fit.itb \
-     u-boot.bin uboot.elf
+     u-boot.bin uboot.elf u-boot-sunxi-with-spl.bin
  
 +  # External Developer <external.developer@collabora.com>
 +  u-boot-sunxi_platforms += orangepi_zero2
@@ -289,17 +296,16 @@ Like with ATF, we need to update the package configuration to build for the Oran
    # Frederic Danis <frederic.danis@collabora.com>
    u-boot-sunxi_platforms += orangepi_zero_plus2
    orangepi_zero_plus2_assigns := BL31=/usr/lib/arm-trusted-firmware/sun50i_a64/bl31.bin
-
 ```
 
 Commit this change, create a changelog entry for a new release and commit that too:
 
 ``` 
-$ git commit -s -m "Add Orange Pi Zero2 to built platforms" debian/targets.mk
-$ gbp dch --git-author --ignore-branch -l orange -R
-$ DEBIAN_PACKAGE=$(dpkg-parsechangelog -S Source)
-$ DEBIAN_VERSION=$(dpkg-parsechangelog -S Version)
-$ git commit -s -m "Release ${DEBIAN_PACKAGE} version ${DEBIAN_VERSION}" debian/changelog
+user@devroot:/home/user/u-boot$ git commit -s -m "Add Orange Pi Zero2 to built platforms" debian/targets.mk
+user@devroot:/home/user/u-boot$ gbp dch --git-author --ignore-branch -l orange -R
+user@devroot:/home/user/u-boot$ DEBIAN_PACKAGE=$(dpkg-parsechangelog -S Source)
+user@devroot:/home/user/u-boot$ DEBIAN_VERSION=$(dpkg-parsechangelog -S Version)
+user@devroot:/home/user/u-boot$ git commit -s -m "Release ${DEBIAN_PACKAGE} version ${DEBIAN_VERSION}" debian/changelog
 ```
 
 As with building ATF we need to ensure that all required dependencies are
@@ -316,16 +322,16 @@ buildpackage`. Here we limit building to just the target we are interested in:
 
 ```
 user@devroot:/home/user/u-boot$ export DEB_BUILD_PROFILES=pkg.uboot.platform.orangepi_zero2
-user@devroot:/home/user/u-boot$ gbp buildpackage --git-ignore-branch -a arm64 -B -d -uc -us
-...
+user@devroot:/home/user/u-boot$ gbp buildpackage --git-ignore-branch -B -d -uc -us
 ```
 
 This generates a bunch of U-Boot binary packages in the parent directory,
 including one for `sunxi` based devices such as the Orange Pi Zero2:
 
 ```
-user@devroot:/home/user/u-boot$ ls ../u-boot-sunxi*.deb
-../u-boot-sunxi_2023.01+dfsg-1+apertis6orange1_arm64.deb
+user@devroot:/home/user/u-boot$ cd ..
+user@devroot:/home/user$ ls u-boot-sunxi*.deb
+u-boot-sunxi_2024.01+dfsg-1+apertis2orange1_arm64.deb
 ```
 
 # Checking kernel
@@ -336,22 +342,23 @@ Zero2:
 
 ```
 user@devroot:/home/user$ apt download "linux-image-*-arm64"
-Get:1 https://repositories.apertis.org/apertis v2023/target arm64 linux-image-6.1.0-7-arm64 arm64 6.1.20-1+apertis4~v2023bv2023.0db1 [60.3 MB]
-Fetched 60.3 MB in 13s (4580 kB/s)
-user@devroot:/home/user$ dpkg -X linux-image-*.deb linux-deb
+Get:1 https://repositories.apertis.org/apertis v2024/target arm64 linux-image-6.6.13-arm64 arm64 6.6.13-1+apertis2bv2024.0db1 [82.5 MB]
+Get:2 https://repositories.apertis.org/apertis v2024-updates/target arm64 linux-image-6.6.0-2-arm64 arm64 6.6.1-0+apertis2bv2024.0bb1 [61.0 MB]
+Fetched 144 MB in 49s (2934 kB/s)
+user@devroot:/home/user$ dpkg -X linux-image-6.6.13-arm64_6.6.13-1+apertis2bv2024.0db1_arm64.deb linux-deb
 ./
 ./boot/
 ...
 ./usr/share/lintian/overrides/
-./usr/share/lintian/overrides/linux-image-6.1.0-7-arm64
-user@devroot:/home/user$ ls linux-deb/boot/dtbs/6.1.0-7-arm64/allwinner/*zero2*
-linux-deb/boot/dtbs/6.1.0-7-arm64/allwinner/sun50i-h616-orangepi-zero2.dtb
+./usr/share/lintian/overrides/linux-image-6.6.13-arm64
+user@devroot:/home/user$ ls linux-deb/boot/dtbs/*-arm64/allwinner/*zero2*
+linux-deb/boot/dtbs/6.6.13-arm64/allwinner/sun50i-h616-orangepi-zero2.dtb
 ```
 
 A quick look at the config used to build it also suggests it's been built with support for the H616, so we'll assume for now that the Apertis kernel is ready to boot on the OrangePi Zero2:
 
 ```
-user@devroot:/home/user$ grep H616 linux-deb/boot/config-6.1.0-7-arm64 
+user@devroot:/home/user$ grep H616 linux-deb/boot/config-*-arm64
 CONFIG_PINCTRL_SUN50I_H616=y
 CONFIG_PINCTRL_SUN50I_H616_R=y
 CONFIG_SUN50I_H616_CCU=y
@@ -375,26 +382,32 @@ hardware-specific support libraries) which tends to be a common artifact used
 between boards with the same architecture, this is then enhanced for a specific
 device or use case by a [HWpack]( {{< ref "hwpack-requirements.md#hwpack" >}} ).
 
-Clone the `apertis-image-recipes` repository as with previous repositories and
+{{% notice note %}}
+It is best to build these images from the appropriate `image-builder` docker
+container, as documented in the `apertis-image-recipes`
+[README.md](https://gitlab.apertis.org/infrastructure/apertis-image-recipes#building-in-docker).
+This needs to be run in the SDK or another Linux environment where docker is
+available. Here we will assume use of the SDK.
+{{% /notice %}}
+
+Clone the `apertis-image-recipes` repository into a runing SDK instance and
 create a downstream project branch:
 
 ```
-$ git clone https://gitlab.apertis.org/infrastructure/apertis-image-recipes.git
-$ cd apertis-image-recipes
-$ git checkout -b orange/v2023 apertis/v2023
+user@sdk:~$ git clone https://gitlab.apertis.org/infrastructure/apertis-image-recipes.git
+...
+user@sdk:~$ cd apertis-image-recipes
+user@sdk:~/apertis-image-recipes$ git checkout -b orange/v2024 origin/apertis/v2024
 ```
 
 ## Building an OSpack
 
 As previously mentioned, the aim is to build a `fixedfunction` image, to do
 this we start by building the appropriate OSpack (`ospack-fixedfunction.yaml`).
-It is best to build these images from the appropriate `image-builder` docker
-container, as documented in the `apertis-image-recipes`
-[README.md](https://gitlab.apertis.org/infrastructure/apertis-image-recipes#building-in-docker).
 
 ```
-$ RELEASE=v2023
-$ docker run \
+user@sdk:~/apertis-image-recipes$ RELEASE=v2024
+user@sdk:~/apertis-image-recipes$ docker run \
   -i -t --rm \
   -w /recipes \
   -v $(pwd):/recipes \
@@ -570,8 +583,7 @@ We can now build the final image, again using the appropriate `image-builder`
 docker container:
 
 ```
-$ RELEASE=v2023
-$ docker run \
+user@sdk:~/apertis-image-recipes$ docker run \
   -i -t --rm \
   -w /recipes \
   -v $(pwd):/recipes \
@@ -596,10 +608,10 @@ The image writing process is quite simple as the Debos scripts have already
 generated the image with the required partitions and firmware installed as
 required so that the image can just be written to the beginning of the SD card:
 
-    $ sudo bmaptool copy apertis-v2023-fixedfunction-arm64-orangepi_zero2.img.gz $sdcard
+    $ sudo bmaptool copy apertis-v2024-fixedfunction-arm64-orangepi_zero2.img.gz $SDCARD
 
 {{% notice warning %}}
-Make sure to set `$sdcard` to the device file of the SD card.
+Make sure to set `SDCARD` to the device file of the SD card.
 {{% /notice %}}
 
 Insert the SD card into the board, [attach the serial
@@ -607,13 +619,13 @@ console](https://linux-sunxi.org/Xunlong_Orange_Pi_Zero2#Serial_port) cable and
 power supply and boot:
 
 ```
-U-Boot SPL 2023.01+dfsg-1+apertis6orange1 (Jun 12 2023 - 17:51:06 +0000)
+U-Boot SPL 2024.01+dfsg-1+apertis2orange1-00002-g5a39a00d9-dirty (Feb 23 2024 - 20:05:46 +0000)
 DRAM: 1024 MiB
 Trying to boot from MMC1
-NOTICE:  BL31: v2.7(debug):apertis/2.7.0+dfsg-2+apertis3-2-g6830268
-NOTICE:  BL31: Built : 16:00:31, Jun 13 2023
+NOTICE:  BL31: v2.10.0	(debug):apertis/2.10.0+dfsg-1+apertis2-2-gcb99379-dirty
+NOTICE:  BL31: Built : 18:18:20, Feb 23 2024
 NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
-NOTICE:  BL31: Found U-Boot DTB at 0x4a0923e8, model: OrangePi Zero2
+NOTICE:  BL31: Found U-Boot DTB at 0x4a0b3458, model: OrangePi Zero2
 INFO:    ARM GICv2 driver initialized
 INFO:    Configuring SPC Controller
 INFO:    PMIC: Probing AXP305 on RSB
@@ -625,8 +637,8 @@ INFO:    PMIC: dcdcd voltage: 1.500V
 INFO:    PMIC: dcdce voltage: 3.300V
 INFO:    BL31: Platform setup done
 INFO:    BL31: Initializing runtime services
-INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
-INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
+INFO:    BL31: cortex_a53: CPU workaround for erratum 855873 was applied
+INFO:    BL31: cortex_a53: CPU workaround for erratum 1530924 was applied
 INFO:    PSCI: Suspend is unavailable
 INFO:    BL31: Preparing for EL3 exit to normal world
 INFO:    Entry point address = 0x4a000000
@@ -634,43 +646,53 @@ INFO:    SPSR = 0x3c9
 INFO:    Changed devicetree.
 
 
-U-Boot 2023.01+dfsg-1+apertis6orange1 (Jun 12 2023 - 17:51:06 +0000) Allwinner Technology
+U-Boot 2024.01+dfsg-1+apertis2orange1-00002-g5a39a00d9-dirty (Feb 23 2024 - 20:05:46 +0000) Allwinner Technology
 
 CPU:   Allwinner H616 (SUN50I)
 Model: OrangePi Zero2
 DRAM:  1 GiB
-Core:  48 devices, 18 uclasses, devicetree: separate
+Core:  54 devices, 22 uclasses, devicetree: separate
 WDT:   Not starting watchdog@30090a0
 MMC:   mmc@4020000: 0
 Loading Environment from FAT... Unable to use mmc 0:1...
 In:    serial@5000000
 Out:   serial@5000000
 Err:   serial@5000000
-Net:   eth0: ethernet@5020000
+Allwinner mUSB OTG (Peripheral)
+Net:   eth0: ethernet@5020000using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
+MAC de:ad:be:ef:00:01
+HOST MAC de:ad:be:ef:00:00
+RNDIS ready
+, eth1: usb_ether
+starting USB...
+Bus usb@5200000: USB EHCI 1.00
+Bus usb@5200400: USB OHCI 1.0
+scanning bus usb@5200000 for devices... 1 USB Device(s) found
+scanning bus usb@5200400 for devices... 1 USB Device(s) found
+       scanning usb for storage devices... 0 Storage Device(s) found
 Hit any key to stop autoboot:  0 
 switch to partitions #0, OK
 mmc0 is current device
 Scanning mmc 0:1...
 Found /extlinux/extlinux.conf
 Retrieving file: /extlinux/extlinux.conf
-U-Boot menu
-1:	Apertis v2023 6.1.0-0.deb11.13-arm64
-2:	Apertis v2023 6.1.0-0.deb11.13-arm64 (rescue target)
-Enter choice: 1:	Apertis v2023 6.1.0-0.deb11.13-arm64
-Retrieving file: /initrd.img-6.1.0-0.deb11.13-arm64
-Retrieving file: /vmlinuz-6.1.0-0.deb11.13-arm64
-append: root=UUID=208a5921-308d-4b07-b953-ef916f2f6da9 rootwait rw quiet splash plymouth.ignore-serial-consoles fsck.mode=auto fsck.repair=yes
-Retrieving file: /dtbs/6.1.0-0.deb11.13-arm64/allwinner/sun50i-h616-orangepi-zero2.dtb
-Moving Image from 0x40080000 to 0x40200000, end=42120000
+1:	Apertis v2024 6.6.13-arm64
+Retrieving file: /vmlinuz-6.6.13-arm64
+Retrieving file: /initrd.img-6.6.13-arm64
+append: root=UUID=17f9cad5-d684-4509-931c-d260268cbe06 rootwait rw quiet splash plymouth.ignore-serial-consoles fsck.mode=auto fsck.repair=yes
+Retrieving file: /dtbs/6.6.13-arm64/allwinner/sun50i-h616-orangepi-zero2.dtb
+Moving Image from 0x40080000 to 0x40200000, end=424d0000
 ## Flattened Device Tree blob at 4fa00000
    Booting using the fdt blob at 0x4fa00000
 Working FDT set to 4fa00000
-   Loading Ramdisk to 48054000, end 49fff45c ... OK
-   Loading Device Tree to 000000004804d000, end 00000000480530d0 ... OK
-Working FDT set to 4804d000
+   Loading Ramdisk to 483f4000, end 49ffff51 ... OK
+   Loading Device Tree to 00000000483ed000, end 00000000483f3bfb ... OK
+Working FDT set to 483ed000
 
 Starting kernel ...
 
-Apertis v2023 apertis ttyS0
+...
+
+Apertis v2024 apertis ttyS0
 apertis login: 
 ```