MKIMAGE arch/arm64/boot/dts/rockchip/overlay/rockchip-fixup.scr
/bin/sh: 1: mkimage: not found
scripts/Makefile.lib:343: recipe for target ‘arch/arm64/boot/dts/rockchip/overlay/rockchip-fixup.scr’ failed
make[3]: *** [arch/arm64/boot/dts/rockchip/overlay/rockchip-fixup.scr] Error 127
scripts/Makefile.build:484: recipe for target ‘arch/arm64/boot/dts/rockchip/overlay’ failed
make[2]: *** [arch/arm64/boot/dts/rockchip/overlay] Error 2
scripts/Makefile.build:484: recipe for target ‘arch/arm64/boot/dts/rockchip’ failed
make[1]: *** [arch/arm64/boot/dts/rockchip] Error 2
arch/arm64/Makefile:127: recipe for target ‘dtbs’ failed
make: *** [dtbs] Error 2
make kernel error
which tool did you use to compile?
Hi, I am following the steps in the bsp docs. I found slightly different ones here:
https://docs.radxa.com/en/rockpi/rockpis/low-level-dev/kernel
In my case, I issue the command for rock-pi-s:
./bsp linux stable rock-pi-s --no-config -r 99
I see no errors. Everything seems to complete as expect and I see many deb files. As per the instructions, I then install just:
sudo dpkg -i linux-headers-6.1.68-99-stable_6.1.68-99_arm64.deb
sudo dpkg -i linux-image-6.1.68-99-stable_6.1.68-99_arm64.deb
This seems to complete as expected, but then I reboot and I get nothing at all. No bootup and no flashing blue LED.
Any idea what am I doing wrong? I need to make a custom kernel to include HIDRAW module.
Any logs outputed from the serial port? Please send here so that I can analyze.
Thank you for your reply. I’ll check the serial console and advise the output. Cheers,
Please see the serial console output. It seems to just freeze at “Starting kernel …”
console_log.zip (2.1 KB)
Hi, do you have any feedback on this? I’m in the same situation again now. I’ve updated bsp and still have the same issue.
-
What’s the behavior of ROCK PI S’ user led ? ROCK PI S uses the mainline kernel, and the kernel serial port output is not enabled by default.
-
For HIDRAW module, you need add it to stable/kconfig.conf.
The LED stays solid, not flashing like when it normally boots.
Can you clarify the location of kconfig.conf? Is this preferred over “make menuconfig” in linux source?
if you use “make menuconfig” to generate the .config, you need use the flag “–no-prepare-source” or “–dirty”, otherwise the bsp will over write the .config, for detailed parameter information, you can run . /bsp to get.
And you can also add it to bsp/stable/kconfig.conf, then run the cmd “./bsp linux stable rock-pi-s -r 99”, then check the .src/linux/.config, you can find the CONFIG_HIDRAW driver is enabled.
Ok, so the bsp/stable/kconfig.conf file doesn’t exist yet. So it needs to be created?
I will answer my own question. Yes, I created this and it merged into .config.
Hi @Nasca, I was able to build a valid .deb header and image using the kconfig.conf method, so all good there.
One thing though, the image deb took a painful amount of time to install as it got stuck on “Updating overlays…” for hours. It only worked after I created a very large temporary swap space. Is there a way to streamline this?
Some packages are in the form of dkms, which are compiled during installation.