Jayofelony

The actual message of the crash found ``` [ 2433.353690] brcmfmac: brcmf_sdio_bus_sleep Enter: request WAKE currently WAKE [ 2433.353701] brcmfmac: brcmf_sdio_clkctl Enter [ 2433.353712] brcmfmac: brcmf_sdio_bus_sleep new state WAKE [...

I trust you experts in this know what you are talking about, I don't even know if it's a nexmon bug or something that my software is doing wrong. Heck,...

Kernel 6.6.20+rpt-rpi-v8 and 6.6.20+rpt-rpi-2712 have been released when you run `apt-get dist-upgrade`.

Can you make it add the bcm2712-rpi-5.dtb to it as well when you build an image for pi 4? The bcm2710 is also there when you build the 2711 (pi4/400).

When i build a pi 4 image there is no pi5 dtb there, it boots fine on 02 and 4, but not on the 5 Kernel 6.2.y

Open an issue on my GitHub if you will, with logs, config.toml and commands used.

Also opened an issue with the original repo of seemoo-lab. Since this happens on both builds with either repo. https://github.com/seemoo-lab/nexmon/issues/595

``` qemu_binary_source_path = "/usr/libexec/qemu-binfmt/arm-binfmt-P" qemu_binary_destination_path = "/usr/libexec/qemu-binfmt/arm-binfmt-P" ``` This worked for me.

Well it seems to link to the `/lib/firmware/brcm/brcmfmac43436-sdio.bin` file. Which has been patched with nexmon.   So in theory it should work, as the RPi using the 43436b0 chipset...

``` pi@raspberrypi:~ $ sudo dmesg | grep brcmf [ 10.585321] brcmfmac: F1 signature read @0x18000000=0x1542a9a6 [ 10.600550] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430b0-sdio for chip BCM43430/2 [ 10.603142] usbcore: registered new interface...