# Using FIT Images as artifacts

**URL:** <https://hub.mender.io/t/using-fit-images-as-artifacts/1985>\
**Category:** General Discussions\
**Created:** [May 31, 2020, 11:03am UTC](https://hub.mender.io/t/using-fit-images-as-artifacts/1985 "2020-05-31T11:03:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![samlewis](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/samlewis/32/393_2.png) [@samlewis](https://hub.mender.io/u/samlewis)\
**Post date:** [June 1, 2020, 11:22pm UTC](https://hub.mender.io/t/using-fit-images-as-artifacts/1985/3 "2020-06-01T23:22:55Z")

</div>

I’ve think I’ve done essentially what you’re proposing (though on ARM) where my NOR storage contains:

Bootloader  
RootfsA - fitImage containing kernel, device tree and squashfs initramfs  
RootfsB - fitImage containing kernel, device tree and squashfs initramfs  
Data

It works well but there were some patches required to both the Mender client code and the Mender uboot code to facilitate loading fitImages and having a rootfs mounted in RAM. There’s some info in some of my previous posts: [Read only compressed rootfs in raw flash?](https://hub.mender.io/t/read-only-compressed-rootfs-in-raw-flash/950), [Updating when rootfs is in RAM?](https://hub.mender.io/t/updating-when-rootfs-is-in-ram/1127) and [Xilinx Zynq - change mender to have rootfs inside fit image](https://hub.mender.io/t/xilinx-zynq-change-mender-to-have-rootfs-inside-fit-image/1559/2).

As Drew said, it might be easier to use update modules but thought it was worth sharing in case it helps!

---

_[View the full topic](https://hub.mender.io/t/using-fit-images-as-artifacts/1985)._