# Asynchronous SError Interrupt | RPI5 Boot Issue

**URL:** <https://hub.mender.io/t/asynchronous-serror-interrupt-rpi5-boot-issue/7275>\
**Category:** General Discussions\
**Tags:** yocto, raspberry-pi-5, scarthgap\
**Created:** [October 27, 2024, 5:51pm UTC](https://hub.mender.io/t/asynchronous-serror-interrupt-rpi5-boot-issue/7275 "2024-10-27T17:51:44Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![LindaLinda2005](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/lindalinda2005/32/2336_2.png) [@LindaLinda2005](https://hub.mender.io/u/LindaLinda2005)\
**Post date:** [October 30, 2024, 2:21pm UTC](https://hub.mender.io/t/asynchronous-serror-interrupt-rpi5-boot-issue/7275/12 "2024-10-30T14:21:34Z")

</div>

Hey @TheYoctoJester,

I’ve loaded your image onto my SD and it fails to boot with the same error as before. But! I think I’ve finally figured out why.

I have the Rpi5 2G ram board, which according to [this](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#flagship-series) documentation, uses the BCM2712 **D0** chip. Whereas the 4G & 8G ram options use the BCM2712 **C1** (which I think is also just referred to as BCM2712).

I don’t know what chip the 1G version runs, as I can’t find documentation for it existing. However, if you have the 4G, 8G, or the 1G also doesn’t use the BCM2712 **D0** chip, that might explain why doing the same things as each other doesn’t work.

I wonder if copying the bcm2712d0.dtbo into your overlays folder would actually cause the issue on your board instead.

Either way, going forward what would you suggest I do?

As a temporary solution I added this to my local.conf via a .yml file which seems to have worked:

```auto
RPI_KERNEL_DEVICETREE_OVERLAYS:append = " overlays/bcm2712d0.dtbo"

```

---

_[View the full topic](https://hub.mender.io/t/asynchronous-serror-interrupt-rpi5-boot-issue/7275)._