citruz
Nanopi M4V2 support
Describe the issue you are experiencing
I am trying to get a HAOS image working for the Nanopi M4V2. So far none of the images boot (even the RockPro64). I am using the program disks (gnome-disk-utility & UDisks) or the dd command to flash the images but only DietPi and ArmBian images worked.
What operating system image do you use?
rockpi-4a
What version of Home Assistant Operating System is installed?
none
Did you upgrade the Operating System.
No
Steps to reproduce the issue
Burn the RockPi image to the SD card an boo the Nanopi M4V2 without the emmc module
Anything in the Supervisor logs that might be useful for us?
no
Anything in the Host logs that might be useful for us?
no
System information
No response
Additional information
No response
The M4V2 is not yet supported upstream in neither u-boot nor the Linux kernel, just the regular M4. Do you know if that would work instead?
It will work as the only difference between the regular M4 and the M4V2 is the ram amount (2GB vs 4GB) and chip. Friendlyelec said: "The only difference between the NanoPi M4 and NanoPi M4V2 is the RAM chip model. The NanoPi M4 uses and LPDDR3 RAM chip and the NanoPi M4V2 uses an LPDDR4 RAM chip....."
Let me know if this works: https://github.com/citruz/haos-rockpi/releases/tag/11.2%2B20231209
Thank you Citruz! Unfortunately I copied to the sd-card using the xzcat & dd commands and doesn't' boot. I power on the NanoPi and no green light and nothing come to the screen. I tryed in the sd-card and in the emmc but so far no luck. Only DietPi and ArmBian works. And https://sd-card-images.johang.se/boards/nanopi_m4.html if I have ArmBian in the emmc.
When you tried booting from sd card, did you have another image in the emmc? If yes, it would be a good idea to fully wipe the emmc before trying to boot from sd so that it is forced to use the bootloader from the sd. The only feasible option to debug this is with serial output so that we can see what is going wrong. Do you have a USB-serial adapter? Using a different kind of memory (ddr3 vs ddr4) sounds like a pretty good reason why the M4 image wouldn't work on an M4V2. I saw some patches being sent around for the M4V2 which could be worth a try but without the ability to debug over serial it's not ideal.
I don't have the USB-serial and I removed the emmc before power on the NanoPi with the sd. Could be that the memory make the different but both sbc have the same link to download the official images from FriendlyElec. Thanks for your help I will keep playing and if I success I will let you know.
In that case serial logs are the only way to go forward. These adapters are cheap ;)