I’m trying to display a 3.5 TFT LCD on rpi3 (Raspberry Pi 3 Model B v1.2 – Raspberry Pi 2015) built with buildroot+busybox, but sources like this repo from lcdwiki uses debian-based distro tooling for the setup since Raspbian/Raspberry OS is the most used. I am also using chroot and qemu-user-static (ARM) to inspect the filesystem, edit files and run programs. I borrowed the rpi3 for this and neither I nor the owner have the buildroot configuration source. Can someone point me to what is normally done in these cases?

I’ve tried to edit some config files. Maybe the /dev management option “Dynamic using devmpfs+mdev” from the buildroot manual could work?

I’ve tried to understand the boot process order for this case using busybox init instead of a debian-based with systemd and this was my conclusion:

• 1. pcb power (ARM11 is disabled )
• 2. -> SoC GPU loads first-stage bootloader bootcode.bin into cache L2 and exec
• 3. -> bootcode.bin initializes SDRAM and loads the second-stage bootloader start.elf to the external RAM and exec
• 4. -> start.elf configures hardware based on config.txt, loads kernel image into kernel.img, read kernel command line arguments from cmdline.txt
• 5. -> inits Linux, calling busybox init
• 6. -> reads /etc/inittab, which reads the /etc/mdev.conf
• 7. -> starts /etc/init.d/rcS“