[Buildroot-users] Support for Raspberry Pi CM5 on CM 5 IO Board

[Henry Hoegelow]

Dear Buildroot community,

About two weeks ago, I sent a message to this mailing list regarding
support for the Raspberry Pi Compute Module 5 (CM5) and its IO board,
including a kernel panic I encountered when trying to boot a Buildroot-
generated image.

Unfortunately, I haven't received any replies so far, and I'm unsure if
my message was overlooked, if I used the wrong mailing list, or if
perhaps I’m missing something obvious that made the message seem
unworthy of a response.

I'd be very grateful for any feedback or pointers — even just a
confirmation that the CM5 is currently unsupported in Buildroot would
help me understand how to proceed. I'm also happy to contribute to
getting support added, but I would need some guidance on where to
start.

If there is a more appropriate place to ask this question, please let
me know.

Thanks again for your time,
Henry

> Hi, 
> 
> my name is Henry and I am currently working on a series of musical
> instruments, all based on a Raspberry Pi Compute Module 5 sitting on
> a
> Compute Module 5 IO board. So far I haven't been able to use
> Buildroot
> or Yocto to create a bootable image for this setup. 
> 
> The commands: 
> 
> make raspberrypi5_defconfig 
> make 
> 
> will create an image, but when I try to boot it I get a kernel panic
> (see below). I suspect that a special config is needed for the CM5,
> as
> there are specific configs for the CM4 IO board (raspberrypicm4io,
> raspberrypicm4io-64), while for the raspi5 there is only the
> raspberrypi5 config.
> 
> I have tried to find information on the internet and on the buildroot
> mailing lists, but it seems that the CM5 + CM5 IO board is not yet
> supported by either buildroot or yocto. Or maybe I am just missing
> something obvious?
> 
> I'd also like to offer my help in adding support for the board - I am
> happy to spend some time on it, but I'd definitely need some
> pointers.
> I already tried to add the bcm2712-rpi-cm5-cm5io.dtb (found in
> output/build/rpi-firmware-
> 5476720d52cf579dc1627715262b30ba1242525e/boot) to the image, it has
> made no difference.
> 
> Thanks a lot,
> Henry
> 
> Hardware name: Raspberry Pi Compute Module 5 Rev 1.0 (DT)
> Call trace:
> dump_backtrace+0x9c/0x100
> show_stack+0x20/0x38
> dump_stack_lvl+0x48/0x60
> dump_stack+0x18/0x28
> panic+0x324/0x388
> nmi_panic+0x94/0xa0
> arm64_serror_panic+0x78/0x98
> arm64_is_fatal_ras_serror+0x44/0xc0
> serror_interrupt+0x64/0x80
> el1h_64_error_handler+0x30/0x48
> el1h_64_error+0x64/0x68
> bcm2712_pull_config_set+0x64/0xe8
> bcm2712_pinconf_set+0x94/0xd8
> pinconf_apply_setting+0xa0/0x128
> pinctrl_commit_state+0xf0/0x228
> pinctrl_select_state+0x24/0x40
> pinctrl_bind_pins+0x150/0x168
> really_probe+0x5c/0x2d0
> __driver_probe_device+0xb8/0x140
> driver_probe_device+0x44/0x170
> __driver_attach+0x98/0xb8
> bus_for_each_dev+0xb4/0xf0
> bus_add_driver+0xf8/0x208
> driver_register+0x64/0x138
> __platform_driver_register+0x30/ 48 
> brcmuart_init+ 44 / 88 
> do_one_initcall + 60 / 2c8 
> kernel_init_freeable + 1f8 / 3eO 
> kernel_init + 30 / 210 
> ret_from_fork + 10 / 20 
> SMP: stopping secondary CPUs 
> Kernel Offset: Ox100400000 from Oxffffffc080000000 
> PHYS_OFFSET: OxO 
> CPU features: OxO,00000001,70028143,000072Ob 
> Memory Limit: none 
> 
> [ end Kernel panic - not syncing: Asynchronous SError Interrupt ]