Asynchronous SError Interrupt | RPI5 Boot Issue

General Discussions
, ,
1

Hi all,

First apologies as I’m quite new to embedded Linux, Yocto, and this forum - let me know if this isn’t the most suitable place for this question.

For the last several days I’ve been banging my head against a wall trying to create an image for the raspi5. This led me to finding this https://hub.mender.io/t/raspberry-pi-5/6689 discussion/guide which I’ve followed, but am still unable to boot the pi.

I’ve plugged in a UART debug tool to view the serial which shows the kernel being loaded before exiting with --[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]—

There’s also:

[    1.386105] SError Interrupt on CPU2, code 0x00000000be000011 -- SError

[    1.386117] pc : bcm2712_pull_config_set+0x68/0xe8
[    1.386127] lr : bcm2712_pull_config_set+0x4c/0xe8
[    1.386131] sp : ffffc00080043aa0
[    1.386132] x29: ffffc00080043aa0 x28: ffffd00085434008 x27: ffffd000852e0118
[    1.386136] x26: ffffd000852279d0 x25: ffff800016cb0680 x24: 0000000000000000
[    1.386140] x23: 0000000000000018 x22: ffff800016c8e540 x21: 0000000000000122
[    1.386143] x20: ffff800016c8e480 x19: 0000000000000000 x18: ffffffffffffffff
[    1.386146] x17: 0000000000000000 x16: 0000000000000000 x15: ffffc00080043800
[    1.386149] x14: ffff800016cb068a x13: ffff800016cb0688 x12: 3030306330356437
[    1.386152] x11: 0000000000000040 x10: ffff8000168f5760 x9 : ffffd0008477c8d4
[    1.386155] x8 : ffff80001806cb90 x7 : 0000000000000000 x6 : 0000000000000000
[    1.386158] x5 : ffff80001806cb68 x4 : 0000000000000024 x3 : 0000000000000018
[    1.386161] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[    1.386164] Kernel panic - not syncing: Asynchronous SError Interrupt

I believe this is possibly due to a warning I get during build (see below). I’ve tried putting KERNEL_DEVICETREE = “broadcom/bcm2712-rpi-5-b.dtb” to get rid of the error but that doesn’t seem to work either.

Any help on this would be massively appreciated, please also let me know if there’s any useful information I’ve missed.

Warning message during boot:

WARNING: u-boot-1_2024.04-r0 do_provide_mender_defines: Found more than one dtb specified in KERNEL_DEVICETREE (          broadcom/bcm2712-rpi-5-b.dtb           overlays/overlay_map.dtb     overlays/at86rf233.dtbo     overlays/disable-bt.dtbo     overlays/disable-wifi.dtbo     overlays/dwc2.dtbo     overlays/gpio-ir.dtbo     overlays/gpio-ir-tx.dtbo     overlays/gpio-key.dtbo     overlays/gpio-poweroff.dtbo     overlays/gpio-shutdown.dtbo     overlays/hifiberry-amp.dtbo     overlays/hifiberry-amp100.dtbo     overlays/hifiberry-amp3.dtbo     overlays/hifiberry-amp4pro.dtbo     overlays/hifiberry-dac.dtbo     overlays/hifiberry-dacplus.dtbo     overlays/hifiberry-dacplusadc.dtbo     overlays/hifiberry-dacplusadcpro.dtbo     overlays/hifiberry-dacplusdsp.dtbo     overlays/hifiberry-dacplushd.dtbo     overlays/hifiberry-digi-pro.dtbo     overlays/hifiberry-digi.dtbo     overlays/justboom-both.dtbo     overlays/justboom-dac.dtbo     overlays/justboom-digi.dtbo     overlays/i2c-gpio.dtbo     overlays/i2c-rtc.dtbo     overlays/imx219.dtbo     overlays/imx477.dtbo     overlays/imx708.dtbo     overlays/iqaudio-dac.dtbo     overlays/iqaudio-dacplus.dtbo     overlays/mcp2515-can0.dtbo     overlays/mcp2515-can1.dtbo     overlays/mcp3008.dtbo     overlays/miniuart-bt.dtbo     overlays/pitft22.dtbo     overlays/pitft28-capacitive.dtbo     overlays/pitft28-resistive.dtbo     overlays/pitft35-resistive.dtbo     overlays/pps-gpio.dtbo     overlays/rpi-ft5406.dtbo     overlays/rpi-poe.dtbo     overlays/vc4-fkms-v3d.dtbo     overlays/vc4-fkms-v3d-pi4.dtbo     overlays/vc4-kms-v3d.dtbo     overlays/vc4-kms-v3d-pi4.dtbo     overlays/vc4-kms-v3d-pi5.dtbo     overlays/vc4-kms-dsi-7inch.dtbo     overlays/w1-gpio.dtbo     overlays/w1-gpio-pullup.dtbo     overlays/wm8960-soundcard.dtbo          ). Only one should be specified. Choosing the last one: overlays/overlay_map.dtb. Set KERNEL_DEVICETREE to the desired dtb file to silence this warning.
2

It’s worth noting I’ve made sure the SD still works with the original raspberry pi OS, so pretty sure it’s not a hardware issue.

3

Hi @LindaLinda2005,

Thanks for reaching out. This is not a kind of misbehavior which I have yet seen. Can you provide a little more log so maybe there can be something understood from the context?

Greetz,
Josef

1 Like
4

Thanks for the quick reply.

I’ve been working on it a bit more this morning and have found this forum post which seems to cover the same error I’m seeing.

It looks like once I’ve flashed the SD with the created .sdimg I’m missing the file ‘bcm2712d0.dtbo’, and manually copying this from a working Rpi5 OS to the /boot/overlays directory on the SD resolves my issue allowing me to boot successfully.

What is confusing me still though is why I’m missing this file (and potentially others?) from my image.

Steps I’ve done to get the error:

Full kernel log:

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x414fd0b1]
[    0.000000] Linux version 6.6.22-v8-16k (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 13.3.0, G4
[    0.000000] KASLR enabled
[    0.000000] random: crng init done
[    0.000000] Machine model: Raspberry Pi 5 Model B Rev 1.0
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000002000000, size 320 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x0000000002000000..0x0000000015ffffff (327680 KiB) map reusable lia
[    0.000000] OF: reserved mem: 0x0000000000000000..0x000000000007ffff (512 KiB) nomap non-reusable0
[    0.000000] OF: reserved mem: 0x000000003fd16ae0..0x000000003fd16b17 (0 KiB) nomap non-reusable n0
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000000000-0x000000007fffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x000000000007ffff]
[    0.000000]   node   0: [mem 0x0000000000080000-0x000000003fbfffff]
[    0.000000]   node   0: [mem 0x0000000040000000-0x000000007fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
[    0.000000] On node 0, zone DMA: 256 pages in unavailable ranges
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.2
[    0.000000] percpu: Embedded 14 pages/cpu s184936 r8192 d36248 u229376
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] CPU features: detected: Virtualization Host Extensions
[    0.000000] CPU features: detected: Hardware dirty bit management
[    0.000000] CPU features: detected: Spectre-v4
[    0.000000] CPU features: detected: Spectre-BHB
[    0.000000] CPU features: kernel page table isolation forced ON by KASLR
[    0.000000] CPU features: detected: Kernel page table isolation (KPTI)
[    0.000000] alternatives: applying boot alternatives
[    0.000000] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_0
[    0.000000] Dentry cache hash table entries: 262144 (order: 7, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 6, 1048576 bytes, linear)
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 130304
[    0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[    0.000000] Memory: 1722928K/2093056K available (14400K kernel code, 2272K rwdata, 4720K rodata, )
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 46619 entries in 46 pages
[    0.000000] ftrace: allocated 46 pages with 4 groups
[    0.000000] trace event string verifier disabled
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000]  Rude variant of Tasks RCU enabled.
[    0.000000]  Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] Root IRQ handler: gic_handle_irq
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_ids
[    0.000000] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
[    0.000166] Console: colour dummy device 80x25
[    0.000181] Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 Bog)
[    0.000186] pid_max: default: 32768 minimum: 301
[    0.000209] LSM: initializing lsm=capability,integrity
[    0.000267] Mount-cache hash table entries: 4096 (order: 1, 32768 bytes, linear)
[    0.000276] Mountpoint-cache hash table entries: 4096 (order: 1, 32768 bytes, linear)
[    0.000644] cgroup: Disabling memory control group subsystem
[    0.001070] RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1.
[    0.001095] RCU Tasks Rude: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1.
[    0.001116] RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1.
[    0.001174] rcu: Hierarchical SRCU implementation.
[    0.001175] rcu:     Max phase no-delay instances is 1000.
[    0.001746] EFI services will not be available.
[    0.001803] smp: Bringing up secondary CPUs ...
[    0.001957] Detected PIPT I-cache on CPU1
[    0.001996] CPU1: Booted secondary processor 0x0000000100 [0x414fd0b1]
[    0.002172] Detected PIPT I-cache on CPU2
[    0.002206] CPU2: Booted secondary processor 0x0000000200 [0x414fd0b1]
[    0.002366] Detected PIPT I-cache on CPU3
[    0.002397] CPU3: Booted secondary processor 0x0000000300 [0x414fd0b1]
[    0.002425] smp: Brought up 1 node, 4 CPUs
[    0.002428] SMP: Total of 4 processors activated.
[    0.002430] CPU features: detected: 32-bit EL0 Support
[    0.002432] CPU features: detected: Data cache clean to the PoU not required for I/D coherence
[    0.002434] CPU features: detected: Common not Private translations
[    0.002435] CPU features: detected: CRC32 instructions
[    0.002438] CPU features: detected: RCpc load-acquire (LDAPR)
[    0.002439] CPU features: detected: LSE atomic instructions
[    0.002440] CPU features: detected: Privileged Access Never
[    0.002442] CPU features: detected: RAS Extension Support
[    0.002444] CPU features: detected: Speculative Store Bypassing Safe (SSBS)
[    0.002478] CPU: All CPU(s) started at EL2
[    0.002479] alternatives: applying system-wide alternatives
[    0.004292] devtmpfs: initialized
[    0.007042] Enabled cp15_barrier support
[    0.007048] Enabled setend support
[    0.007143] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 764504178s
[    0.007149] futex hash table entries: 1024 (order: 2, 65536 bytes, linear)
[    0.007950] pinctrl core: initialized pinctrl subsystem
[    0.008118] DMI not present or invalid.
[    0.008296] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.008900] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
[    0.008949] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.008998] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.009015] audit: initializing netlink subsys (disabled)
[    0.009072] audit: type=2000 audit(0.008:1): state=initialized audit_enabled=0 res=1
[    0.009187] thermal_sys: Registered thermal governor 'step_wise'
[    0.009198] cpuidle: using governor menu
[    0.009256] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.009287] ASID allocator initialised with 32768 entries
[    0.009605] Serial: AMBA PL011 UART driver
[    0.010534] bcm2835-mbox 107c013880.mailbox: mailbox enabled
[    0.010878] 107d001000.serial: ttyAMA10 at MMIO 0x107d001000 (irq = 15, base_baud = 0) is a PL0112
[    0.010889] printk: console [ttyAMA10] enabled
[    0.732730] raspberrypi-firmware soc:firmware: Attached to firmware from 2024-06-05T15:41:49, vard
[    0.746781] raspberrypi-firmware soc:firmware: Firmware hash is 6fe0b09100000000000000000000000000
[    0.762493] Modules: 2G module region forced by RANDOMIZE_MODULE_REGION_FULL
[    0.769571] Modules: 0 pages in range for non-PLT usage
[    0.769572] Modules: 129304 pages in range for PLT usage
[    0.779379] bcm2835-dma 1000010000.dma: DMA legacy API manager, dmachans=0x1
[    0.792326] iommu: Default domain type: Translated
[    0.797244] iommu: DMA domain TLB invalidation policy: strict mode
[    0.803546] SCSI subsystem initialized
[    0.807336] usbcore: registered new interface driver usbfs
[    0.812854] usbcore: registered new interface driver hub
[    0.818192] usbcore: registered new device driver usb
[    0.823348] pps_core: LinuxPPS API ver. 1 registered
[    0.828328] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.>
[    0.837500] PTP clock support registered
[    0.841479] Advanced Linux Sound Architecture Driver Initialized.
[    0.847808] vgaarb: loaded
[    0.850613] clocksource: Switched to clocksource arch_sys_counter
[    1.067626] VFS: Disk quotas dquot_6.6.0
[    1.071579] VFS: Dquot-cache hash table entries: 2048 (order 0, 16384 bytes)
[    1.078681] FS-Cache: Loaded
[    1.081595] CacheFiles: Loaded
[    1.086181] NET: Registered PF_INET protocol family
[    1.091146] IP idents hash table entries: 32768 (order: 4, 262144 bytes, linear)
[    1.099306] tcp_listen_portaddr_hash hash table entries: 1024 (order: 0, 16384 bytes, linear)
[    1.107878] Table-perturb hash table entries: 65536 (order: 4, 262144 bytes, linear)
[    1.115653] TCP established hash table entries: 16384 (order: 3, 131072 bytes, linear)
[    1.123668] TCP bind hash table entries: 16384 (order: 5, 524288 bytes, linear)
[    1.131370] TCP: Hash tables configured (established 16384 bind 16384)
[    1.138015] MPTCP token hash table entries: 2048 (order: 1, 49152 bytes, linear)
[    1.145461] UDP hash table entries: 1024 (order: 1, 32768 bytes, linear)
[    1.152213] UDP-Lite hash table entries: 1024 (order: 1, 32768 bytes, linear)
[    1.159443] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    1.165248] RPC: Registered named UNIX socket transport module.
[    1.171190] RPC: Registered udp transport module.
[    1.175921] RPC: Registered tcp transport module.
[    1.180675] RPC: Registered tcp-with-tls transport module.
[    1.186179] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.192648] PCI: CLS 0 bytes, default 64
[    1.196730] kvm [1]: IPA Size Limit: 40 bits
[    1.201034] kvm [1]: GICV region size/alignment is unsafe, using trapping (reduced performance)
[    1.209791] kvm [1]: vgic interrupt IRQ9
[    1.213737] kvm [1]: VHE mode initialized successfully
[    1.219267] Initialise system trusted keyrings
[    1.223775] workingset: timestamp_bits=46 max_order=17 bucket_order=0
[    1.230251] zbud: loaded
[    1.232942] NFS: Registering the id_resolver key type
[    1.238016] Key type id_resolver registered
[    1.242210] Key type id_legacy registered
[    1.246232] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.252957] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.260413] F2FS not supported on PAGE_SIZE(16384) != 4096
[    1.265963] Key type asymmetric registered
[    1.270072] Asymmetric key parser 'x509' registered
[    1.274976] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    1.282436] io scheduler mq-deadline registered
[    1.286981] io scheduler kyber registered
[    1.291007] io scheduler bfq registered
[    1.295043] irq_brcmstb_l2: registered L2 intc (/soc/interrupt-controller@7c502000, parent irq: 2)
[    1.304193] irq_brcmstb_l2: registered L2 intc (/soc/intc@7d503000, parent irq: 27)
[    1.311932] irq_brcmstb_l2: registered L2 intc (/soc/intc@7d508380, parent irq: 28)
[    1.319671] irq_brcmstb_l2: registered L2 intc (/soc/intc@7d508400, parent irq: 29)
[    1.327410] irq_brcmstb_l2: registered L2 intc (/soc/interrupt-controller@7d510600, parent irq: 3)
[    1.336541] irq_brcmstb_l2: registered L2 intc (/soc/intc@7d517b00, parent irq: 31)
[    1.379936] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    1.386466] SError Interrupt on CPU0, code 0x00000000be000011 -- SError
[    1.386470] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.22-v8-16k #1
[    1.386474] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)
[    1.386475] pstate: 804000c9 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    1.386478] pc : bcm2712_pull_config_set+0x68/0xe8
[    1.386488] lr : bcm2712_pull_config_set+0x4c/0xe8
[    1.386492] sp : ffffc00080043aa0
[    1.386493] x29: ffffc00080043aa0 x28: ffffd00085434008 x27: ffffd000852e0118
[    1.386497] x26: ffffd000852279d0 x25: ffff800016b1ad80 x24: 0000000000000000
[    1.386501] x23: 0000000000000018 x22: ffff8000169ab340 x21: 0000000000000122
[    1.386504] x20: ffff8000169ab280 x19: 0000000000000000 x18: ffffffffffffffff
[    1.386507] x17: 0000000000000000 x16: 0000000000000000 x15: ffffc00080043800
[    1.386510] x14: ffff800016b1ad8a x13: ffff800016b1ad88 x12: 3030306330356437
[    1.386513] x11: 0000000000000040 x10: ffff80001674e360 x9 : ffffd0008477c8d4
[    1.386516] x8 : ffff80001805d268 x7 : 0000000000000000 x6 : 0000000000000000
[    1.386519] x5 : ffff80001805d240 x4 : 0000000000000024 x3 : 0000000000000018
[    1.386521] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[    1.386525] Kernel panic - not syncing: Asynchronous SError Interrupt
[    1.386527] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.22-v8-16k #1
[    1.386529] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)
[    1.386530] Call trace:
[    1.386532]  dump_backtrace+0x9c/0x100
[    1.386536]  show_stack+0x20/0x38
[    1.386539]  dump_stack_lvl+0x48/0x60
[    1.386543]  dump_stack+0x18/0x28
[    1.386545]  panic+0x328/0x390
[    1.386551]  nmi_panic+0x94/0xa0
[    1.386555]  arm64_serror_panic+0x78/0x90
[    1.386558]  arm64_is_fatal_ras_serror+0x44/0xc0
[    1.386561]  do_serror+0x64/0x80
[    1.386563]  el1h_64_error_handler+0x30/0x48
[    1.386567]  el1h_64_error+0x64/0x68
[    1.386570]  bcm2712_pull_config_set+0x68/0xe8
[    1.386574]  bcm2712_pinconf_set+0x6c/0xe0
[    1.386576]  pinconf_apply_setting+0xa0/0x128
[    1.386581]  pinctrl_commit_state+0xe8/0x220
[    1.386584]  pinctrl_select_state+0x24/0x40
[    1.386588]  pinctrl_bind_pins+0x150/0x168
[    1.386592]  really_probe+0x5c/0x2c0
[    1.386595]  __driver_probe_device+0x80/0x140
[    1.386597]  driver_probe_device+0x44/0x170
[    1.386599]  __driver_attach+0x98/0x1b0
[    1.386602]  bus_for_each_dev+0x84/0xf0
[    1.386607]  driver_attach+0x2c/0x40
[    1.386609]  bus_add_driver+0xf0/0x208
[    1.386611]  driver_register+0x64/0x138
[    1.386613]  __platform_driver_register+0x30/0x48
[    1.386616]  brcmuart_init+0x44/0x88
[    1.386619]  do_one_initcall+0x60/0x2c0
[    1.386622]  kernel_init_freeable+0x1ec/0x3d8
[    1.386626]  kernel_init+0x2c/0x1f8
[    1.386630]  ret_from_fork+0x10/0x20
[    1.386634] SMP: stopping secondary CPUs
[    1.386639] Kernel Offset: 0x100004000000 from 0xffffc00080000000
[    1.386640] PHYS_OFFSET: 0x0
[    1.386641] CPU features: 0x0,00000001,70028143,0000720b
[    1.386643] Memory Limit: none
[    1.659907] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7.1 | VT102 | Offline | ttyACM0
5

@LindaLinda2005

That’s really weird. What’s the process you use to flash the SD card? Can you try something unopinionated, like dd to write the image?

Greetz,
Josef

1 Like
6

@TheYoctoJester

This is how I’ve been flashing the SD card so far:

$ sudo dd if=/home/user/mender-raspberrypi5/meta-mender-community/my-raspberrypi5/build/tmp/deploy/images/raspberrypi5/core-image-base-raspberrypi5-20241028122103.sdimg of=/dev/sda bs=1M && sudo sync

I’ve also just tried flashing the SD using the same image with rpi-imager and get the same issue.

7

@LindaLinda2005 that’s even more strange. I’ve also built the image for the Raspberry Pi 5 to cross check and it immediately worked.

Last idea I have to offer right now, can you try core-image-minimal? That’s the one I always go for.

Greetz,
Josef

1 Like
8

@TheYoctoJester Thanks again but trying that hasn’t worked unfortunately, the file is still missing from the boot partition.

These are the only files in the build images folder with 2712 in the name:

~/mender-raspberrypi5/meta-mender-community/my-raspberrypi5-2/build/tmp/deploy/images/raspberrypi5$ ls | grep 2712
bcm2712-rpi-5-b-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029143105.dtb
bcm2712-rpi-5-b.dtb
bcm2712-rpi-5-b-raspberrypi5.dtb

What calls/defines the list of overlay files to be included in the build? Is it possible it’s being missed out / overwritten by something else?

Edit: When you build the image, do you get the file added to the boot partition? If so, do you know what adds it?

9

@LindaLinda2005 I have set up a fresh build, it’s running at the moment. I’ll provide you with a list to compare and the resulting image tomorrow, so you can cross-check.

Another thought: do you have anything connected to the expansion header? Yesterday I saw a situation where that broke the boot process.

Greetz,
Josef

1 Like
10

Hi @LindaLinda2005,

So here’s how my build/tmp/deploy/image/raspberrypi5 directory looks after the generic raspberypi5.yml build from current scarthgap:

build/tmp/deploy/images/raspberrypi5
├── addonaa64.efi.stub
├── at86rf233-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> at86rf233.dtbo
├── at86rf233.dtbo
├── at86rf233-raspberrypi5.dtbo -> at86rf233.dtbo
├── bcm2712-rpi-5-b-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtb -> bcm2712-rpi-5-b.dtb
├── bcm2712-rpi-5-b.dtb
├── bcm2712-rpi-5-b-raspberrypi5.dtb -> bcm2712-rpi-5-b.dtb
├── bootfiles
│   ├── bootcode.bin
│   ├── cmdline.txt
│   ├── config.txt
│   ├── fixup4cd.dat
│   ├── fixup4.dat
│   ├── fixup4db.dat
│   ├── fixup4x.dat
│   ├── fixup_cd.dat
│   ├── fixup.dat
│   ├── fixup_db.dat
│   ├── fixup_x.dat
│   ├── rpi-bootfiles-20240319.stamp
│   ├── start4cd.elf
│   ├── start4db.elf
│   ├── start4.elf
│   ├── start4x.elf
│   ├── start_cd.elf
│   ├── start_db.elf
│   ├── start.elf
│   └── start_x.elf
├── boot.scr
├── core-image-minimal.env
├── core-image-minimal-raspberrypi5-20241030075103.bootimg
├── core-image-minimal-raspberrypi5-20241030075103.bootstrap-artifact
├── core-image-minimal-raspberrypi5-20241030075103.dataimg
├── core-image-minimal-raspberrypi5-20241030075103.ext3
├── core-image-minimal-raspberrypi5-20241030075103.ext4
├── core-image-minimal-raspberrypi5-20241030075103.manifest
├── core-image-minimal-raspberrypi5-20241030075103.mender
├── core-image-minimal-raspberrypi5-20241030075103.sdimg
├── core-image-minimal-raspberrypi5-20241030075103.sdimg.bmap
├── core-image-minimal-raspberrypi5-20241030075103.spdx.tar.zst
├── core-image-minimal-raspberrypi5-20241030075103.tar.bz2
├── core-image-minimal-raspberrypi5-20241030075103.testdata.json
├── core-image-minimal-raspberrypi5-20241030075103.wic.bmap
├── core-image-minimal-raspberrypi5-20241030075103.wic.bz2
├── core-image-minimal-raspberrypi5.bootimg -> core-image-minimal-raspberrypi5-20241030075103.bootimg
├── core-image-minimal-raspberrypi5.bootstrap-artifact -> core-image-minimal-raspberrypi5-20241030075103.bootstrap-artifact
├── core-image-minimal-raspberrypi5.dataimg -> core-image-minimal-raspberrypi5-20241030075103.dataimg
├── core-image-minimal-raspberrypi5.ext3 -> core-image-minimal-raspberrypi5-20241030075103.ext3
├── core-image-minimal-raspberrypi5.ext4 -> core-image-minimal-raspberrypi5-20241030075103.ext4
├── core-image-minimal-raspberrypi5.manifest -> core-image-minimal-raspberrypi5-20241030075103.manifest
├── core-image-minimal-raspberrypi5.mender -> core-image-minimal-raspberrypi5-20241030075103.mender
├── core-image-minimal-raspberrypi5.sdimg -> core-image-minimal-raspberrypi5-20241030075103.sdimg
├── core-image-minimal-raspberrypi5.sdimg.bmap -> core-image-minimal-raspberrypi5-20241030075103.sdimg.bmap
├── core-image-minimal-raspberrypi5.spdx.tar.zst -> core-image-minimal-raspberrypi5-20241030075103.spdx.tar.zst
├── core-image-minimal-raspberrypi5.tar.bz2 -> core-image-minimal-raspberrypi5-20241030075103.tar.bz2
├── core-image-minimal-raspberrypi5.testdata.json -> core-image-minimal-raspberrypi5-20241030075103.testdata.json
├── core-image-minimal-raspberrypi5.wic.bmap -> core-image-minimal-raspberrypi5-20241030075103.wic.bmap
├── core-image-minimal-raspberrypi5.wic.bz2 -> core-image-minimal-raspberrypi5-20241030075103.wic.bz2
├── disable-bt-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> disable-bt.dtbo
├── disable-bt.dtbo
├── disable-bt-raspberrypi5.dtbo -> disable-bt.dtbo
├── disable-wifi-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> disable-wifi.dtbo
├── disable-wifi.dtbo
├── disable-wifi-raspberrypi5.dtbo -> disable-wifi.dtbo
├── dwc2-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> dwc2.dtbo
├── dwc2.dtbo
├── dwc2-raspberrypi5.dtbo -> dwc2.dtbo
├── fw_env.config -> fw_env.config-raspberrypi5-2024.04-r0
├── fw_env.config.default
├── fw_env.config-raspberrypi5 -> fw_env.config-raspberrypi5-2024.04-r0
├── fw_env.config-raspberrypi5-2024.04-r0
├── gpio-ir-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> gpio-ir.dtbo
├── gpio-ir.dtbo
├── gpio-ir-raspberrypi5.dtbo -> gpio-ir.dtbo
├── gpio-ir-tx-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> gpio-ir-tx.dtbo
├── gpio-ir-tx.dtbo
├── gpio-ir-tx-raspberrypi5.dtbo -> gpio-ir-tx.dtbo
├── gpio-key-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> gpio-key.dtbo
├── gpio-key.dtbo
├── gpio-key-raspberrypi5.dtbo -> gpio-key.dtbo
├── gpio-poweroff-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> gpio-poweroff.dtbo
├── gpio-poweroff.dtbo
├── gpio-poweroff-raspberrypi5.dtbo -> gpio-poweroff.dtbo
├── gpio-shutdown-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> gpio-shutdown.dtbo
├── gpio-shutdown.dtbo
├── gpio-shutdown-raspberrypi5.dtbo -> gpio-shutdown.dtbo
├── hifiberry-amp100-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-amp100.dtbo
├── hifiberry-amp100.dtbo
├── hifiberry-amp100-raspberrypi5.dtbo -> hifiberry-amp100.dtbo
├── hifiberry-amp-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-amp.dtbo
├── hifiberry-amp3-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-amp3.dtbo
├── hifiberry-amp3.dtbo
├── hifiberry-amp3-raspberrypi5.dtbo -> hifiberry-amp3.dtbo
├── hifiberry-amp4pro-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-amp4pro.dtbo
├── hifiberry-amp4pro.dtbo
├── hifiberry-amp4pro-raspberrypi5.dtbo -> hifiberry-amp4pro.dtbo
├── hifiberry-amp.dtbo
├── hifiberry-amp-raspberrypi5.dtbo -> hifiberry-amp.dtbo
├── hifiberry-dac-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-dac.dtbo
├── hifiberry-dac.dtbo
├── hifiberry-dacplus-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-dacplus.dtbo
├── hifiberry-dacplusadc-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-dacplusadc.dtbo
├── hifiberry-dacplusadc.dtbo
├── hifiberry-dacplusadcpro-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-dacplusadcpro.dtbo
├── hifiberry-dacplusadcpro.dtbo
├── hifiberry-dacplusadcpro-raspberrypi5.dtbo -> hifiberry-dacplusadcpro.dtbo
├── hifiberry-dacplusadc-raspberrypi5.dtbo -> hifiberry-dacplusadc.dtbo
├── hifiberry-dacplusdsp-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-dacplusdsp.dtbo
├── hifiberry-dacplusdsp.dtbo
├── hifiberry-dacplusdsp-raspberrypi5.dtbo -> hifiberry-dacplusdsp.dtbo
├── hifiberry-dacplus.dtbo
├── hifiberry-dacplushd-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-dacplushd.dtbo
├── hifiberry-dacplushd.dtbo
├── hifiberry-dacplushd-raspberrypi5.dtbo -> hifiberry-dacplushd.dtbo
├── hifiberry-dacplus-raspberrypi5.dtbo -> hifiberry-dacplus.dtbo
├── hifiberry-dac-raspberrypi5.dtbo -> hifiberry-dac.dtbo
├── hifiberry-digi-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-digi.dtbo
├── hifiberry-digi.dtbo
├── hifiberry-digi-pro-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> hifiberry-digi-pro.dtbo
├── hifiberry-digi-pro.dtbo
├── hifiberry-digi-pro-raspberrypi5.dtbo -> hifiberry-digi-pro.dtbo
├── hifiberry-digi-raspberrypi5.dtbo -> hifiberry-digi.dtbo
├── i2c-gpio-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> i2c-gpio.dtbo
├── i2c-gpio.dtbo
├── i2c-gpio-raspberrypi5.dtbo -> i2c-gpio.dtbo
├── i2c-rtc-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> i2c-rtc.dtbo
├── i2c-rtc.dtbo
├── i2c-rtc-raspberrypi5.dtbo -> i2c-rtc.dtbo
├── Image -> Image-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.bin
├── Image-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.bin
├── Image-raspberrypi5.bin -> Image-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.bin
├── imx219-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> imx219.dtbo
├── imx219.dtbo
├── imx219-raspberrypi5.dtbo -> imx219.dtbo
├── imx477-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> imx477.dtbo
├── imx477.dtbo
├── imx477-raspberrypi5.dtbo -> imx477.dtbo
├── imx708-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> imx708.dtbo
├── imx708.dtbo
├── imx708-raspberrypi5.dtbo -> imx708.dtbo
├── iqaudio-dac-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> iqaudio-dac.dtbo
├── iqaudio-dac.dtbo
├── iqaudio-dacplus-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> iqaudio-dacplus.dtbo
├── iqaudio-dacplus.dtbo
├── iqaudio-dacplus-raspberrypi5.dtbo -> iqaudio-dacplus.dtbo
├── iqaudio-dac-raspberrypi5.dtbo -> iqaudio-dac.dtbo
├── justboom-both-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> justboom-both.dtbo
├── justboom-both.dtbo
├── justboom-both-raspberrypi5.dtbo -> justboom-both.dtbo
├── justboom-dac-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> justboom-dac.dtbo
├── justboom-dac.dtbo
├── justboom-dac-raspberrypi5.dtbo -> justboom-dac.dtbo
├── justboom-digi-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> justboom-digi.dtbo
├── justboom-digi.dtbo
├── justboom-digi-raspberrypi5.dtbo -> justboom-digi.dtbo
├── linuxaa64.efi.stub
├── mcp2515-can0-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> mcp2515-can0.dtbo
├── mcp2515-can0.dtbo
├── mcp2515-can0-raspberrypi5.dtbo -> mcp2515-can0.dtbo
├── mcp2515-can1-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> mcp2515-can1.dtbo
├── mcp2515-can1.dtbo
├── mcp2515-can1-raspberrypi5.dtbo -> mcp2515-can1.dtbo
├── mcp3008-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> mcp3008.dtbo
├── mcp3008.dtbo
├── mcp3008-raspberrypi5.dtbo -> mcp3008.dtbo
├── miniuart-bt-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> miniuart-bt.dtbo
├── miniuart-bt.dtbo
├── miniuart-bt-raspberrypi5.dtbo -> miniuart-bt.dtbo
├── modules-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.tgz
├── modules-raspberrypi5.tgz -> modules-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.tgz
├── overlay_map-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtb -> overlay_map.dtb
├── overlay_map.dtb
├── overlay_map-raspberrypi5.dtb -> overlay_map.dtb
├── pitft22-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> pitft22.dtbo
├── pitft22.dtbo
├── pitft22-raspberrypi5.dtbo -> pitft22.dtbo
├── pitft28-capacitive-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> pitft28-capacitive.dtbo
├── pitft28-capacitive.dtbo
├── pitft28-capacitive-raspberrypi5.dtbo -> pitft28-capacitive.dtbo
├── pitft28-resistive-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> pitft28-resistive.dtbo
├── pitft28-resistive.dtbo
├── pitft28-resistive-raspberrypi5.dtbo -> pitft28-resistive.dtbo
├── pitft35-resistive-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> pitft35-resistive.dtbo
├── pitft35-resistive.dtbo
├── pitft35-resistive-raspberrypi5.dtbo -> pitft35-resistive.dtbo
├── pps-gpio-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> pps-gpio.dtbo
├── pps-gpio.dtbo
├── pps-gpio-raspberrypi5.dtbo -> pps-gpio.dtbo
├── rpi-ft5406-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> rpi-ft5406.dtbo
├── rpi-ft5406.dtbo
├── rpi-ft5406-raspberrypi5.dtbo -> rpi-ft5406.dtbo
├── rpi-poe-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> rpi-poe.dtbo
├── rpi-poe.dtbo
├── rpi-poe-raspberrypi5.dtbo -> rpi-poe.dtbo
├── systemd-bootaa64.efi
├── u-boot.bin -> u-boot-raspberrypi5-2024.04-r0.bin
├── uboot.env
├── u-boot-initial-env -> u-boot-initial-env-raspberrypi5-2024.04-r0
├── u-boot-initial-env-raspberrypi5 -> u-boot-initial-env-raspberrypi5-2024.04-r0
├── u-boot-initial-env-raspberrypi5-2024.04-r0
├── u-boot-raspberrypi5-2024.04-r0.bin
├── u-boot-raspberrypi5.bin -> u-boot-raspberrypi5-2024.04-r0.bin
├── vc4-fkms-v3d-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> vc4-fkms-v3d.dtbo
├── vc4-fkms-v3d.dtbo
├── vc4-fkms-v3d-pi4-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> vc4-fkms-v3d-pi4.dtbo
├── vc4-fkms-v3d-pi4.dtbo
├── vc4-fkms-v3d-pi4-raspberrypi5.dtbo -> vc4-fkms-v3d-pi4.dtbo
├── vc4-fkms-v3d-raspberrypi5.dtbo -> vc4-fkms-v3d.dtbo
├── vc4-kms-dsi-7inch-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> vc4-kms-dsi-7inch.dtbo
├── vc4-kms-dsi-7inch.dtbo
├── vc4-kms-dsi-7inch-raspberrypi5.dtbo -> vc4-kms-dsi-7inch.dtbo
├── vc4-kms-v3d-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> vc4-kms-v3d.dtbo
├── vc4-kms-v3d.dtbo
├── vc4-kms-v3d-pi4-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> vc4-kms-v3d-pi4.dtbo
├── vc4-kms-v3d-pi4.dtbo
├── vc4-kms-v3d-pi4-raspberrypi5.dtbo -> vc4-kms-v3d-pi4.dtbo
├── vc4-kms-v3d-pi5-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> vc4-kms-v3d-pi5.dtbo
├── vc4-kms-v3d-pi5.dtbo
├── vc4-kms-v3d-pi5-raspberrypi5.dtbo -> vc4-kms-v3d-pi5.dtbo
├── vc4-kms-v3d-raspberrypi5.dtbo -> vc4-kms-v3d.dtbo
├── w1-gpio-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> w1-gpio.dtbo
├── w1-gpio.dtbo
├── w1-gpio-pullup-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> w1-gpio-pullup.dtbo
├── w1-gpio-pullup.dtbo
├── w1-gpio-pullup-raspberrypi5.dtbo -> w1-gpio-pullup.dtbo
├── w1-gpio-raspberrypi5.dtbo -> w1-gpio.dtbo
├── wm8960-soundcard-1-6.6.22+git0+6a24861d65_c04af98514-r0-raspberrypi5-20241029163023.dtbo -> wm8960-soundcard.dtbo
├── wm8960-soundcard.dtbo
└── wm8960-soundcard-raspberrypi5.dtbo -> wm8960-soundcard.dtbo

1 directory, 228 files

Only additions which I injected through a local debug.yml:

header:
  version: 14

local_conf_header:
  tyj-debug: |
    EXTRA_IMAGE_FEATURES:append = " debug-tweaks ssh-server-dropbear "

I’m using a RPi5 1GB to test it, and it works nicely. At core-image-minimal-raspberrypi5.sdimg - Google Drive you should be able to download the image I used to check on your hardware.

Note for our future selves: the above link is valid as of 2024-10-30, but no guarantees are made for its persistence

Greetz,
Josef

1 Like
11

Thanks for this, I’ll have a look as soon as I’m able.

Regarding the expansion header, the only things I have connected to the board are the power supply & the UART debug tool. So I don’t think that’s the issue. Also, once I manually copy over the .dtbo file I can boot fine.

12

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 documentation, uses the BCM2712D0 chip. Whereas the 4G & 8G ram options use the BCM2712C1 (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 BCM2712D0 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:

RPI_KERNEL_DEVICETREE_OVERLAYS:append = " overlays/bcm2712d0.dtbo"
13

Hi @LindaLinda2005,

Great, that seems to be the breakthrough!

I have added the DTBO to my generic build, and it does not cause any problems on the 1GB variant, as the identifiers don’t match. So my proposal would be to unconditionally add it.

Can you verify that the extended raspberrypi5.yml in the new branch (GitHub - TheYoctoJester/meta-mender-community at scarthgap_rpi5_d0) works for you? Once I get your ack, I would like to merge it.

Thanks a lot for your persistence and contribution!

Greetz,
Josef

1 Like
14

Hey @TheYoctoJester,

I rebuilt with your modified file and it works perfectly. Though I was wondering if it would be better to have this change merged into ‘agherzan/meta-raspberrypi’, as this issue would affect all yocto builds for the rpi5 2Gb, and your mender port also seems to use this repository.

I’ve tested this (GitHub - LindaLinda2005/meta-raspberrypi at scarthgap) change on a plain yocto rpi5 build & it seems to work fine. Then I also checked to see if it would work with the mender port by changing the meta-mender-community/kas/include/raspberrypi.yml file to point to my repository & commit instead of the main, and again it seemed to work fine.

header:
  version: 14

repos:
  meta-raspberrypi:
    #url: https://github.com/agherzan/meta-raspberrypi.git
    #commit: 6df7e028a2b7b2d8cab0745dc0ed2eebc3742a17
    url: https://github.com/LindaLinda2005/meta-raspberrypi.git
    commit: ba3a8fb2c10910c5c7e9defcec1795f6bb585d91

Let me know your thoughts, I’ve not worked with git much before so don’t know what would be best/easiest.

Thank you for all your support with this too!

1 Like
15

Hi @LindaLinda2005,

Yes, you are absolutely right. This should be merged to meta-raspberrypi, to fix it for everybody using the 2GB version.

Before asking you, I actually have tested the behavior if it is set there too. So I’d now merge it to meta-mender-community for you to have a known good starting point right now which doesn’t involve personal repos.

Simultaneously, I encourage you to submit a PR to meta-raspberrypi. Once it is merged there, the addition in meta-mender-community can be removed again.

This is really a great example of how open source make things better for everybody.

Greetz,
Josef

1 Like
16

@TheYoctoJester Brilliant, I’ll mark this thread as solved now if your happy with that & will let you know when the pull request gets merged into the main meta-raspberrypi repository:)

Thanks again.

1 Like
17

@LindaLinda2005

perfect! For the record, merged as 559e5c157625429333079aa41b48b041219206ec to `meta-mender-community´.

Greetz,
Josef

1 Like