neoxnitro Posted October 28, 2022 Posted October 28, 2022 Hi, My NanoPi M4 V2 Won't Boot via SD ... the emmc is not installed on the board The RED light is ON but the GREEN stay OFF I cannot reached to read correctly the data coming from the serial port debug (I tested with many bauderate, also with 1500000, same result ... a lot of weird characters) Tested Versions Won't boot: Armbian_22.08.1_Nanopim4v2_jammy_current_5.15.63.img.xz Armbian_22.08.1_Nanopim4v2_bullseye_current_5.15.63.img.xz Armbian_22.11.0-trunk_Nanopim4v2_sid_edge_6.0.3.img.xz Armbian_22.11.0-trunk_Nanopim4v2_kinetic_edge_6.0.3.img.xz Tested Version Boot properly: Armbian_21.02.1_Nanopim4v2_buster_current_5.10.12.img.xz I use a workbench power supply 5A ... with current limitation set to the max value I tested many SD card (all are class 10) What i'm doing wrong ?! What could i verify ? Any idea ? Thanks guys 0 Quote
Igor Posted October 28, 2022 Posted October 28, 2022 6 hours ago, neoxnitro said: a lot of weird characters Also on the image that is working? Strange. You sure you have V2, not V1? Perhaps some memory configuration that is not supported with mainline boot loader? RK3399 can be booted with open source or closed source loader. We changed to open source at some point, but not on all boards. Perhaps this is the issue? We have a few of those acting as a build runners - no issues whatsoever: Spoiler _ _ ____ _ __ __ _ ___ ______ | \ | | _ \(_) | \/ | || \ \ / /___ \ | \| | |_) | | | |\/| | || |\ \ / / __) | | |\ | __/| | | | | |__ _\ V / / __/ |_| \_|_| |_| |_| |_| |_| \_/ |_____| Welcome to Armbian 22.08.6 Jammy with Linux 5.15.52-rockchip64 System load: 2% Up time: 74 days 4:04 Memory usage: 8% of 3.77G Zram usage: 3% of 1.89G IP: 172.17.0.1 10.0.40.22 CPU temp: 35°C Usage of /: 27% of 58G RX today: 2.5 MiB 0 Quote
neoxnitro Posted October 28, 2022 Author Posted October 28, 2022 (edited) 1 hour ago, Igor said: Also on the image that is working? Yes, may be is related to my USB to Serial adaptor ?! 1 hour ago, Igor said: Strange. You sure you have V2, not V1? Perhaps some memory configuration that is not supported with mainline boot loader? RK3399 can be booted with open source or closed source loader. We changed to open source at some point, but not on all boards. Perhaps this is the issue? I verified ... it's well a V2 ... but i noticed something weird, i only have 2 Go of RAM ... and in the output you shared you have 4 Go RAM, does it possible that my boot problem came from there ?! Edited October 28, 2022 by neoxnitro 0 Quote
Igor Posted October 28, 2022 Posted October 28, 2022 38 minutes ago, neoxnitro said: Yes, may be is related to my USB to Serial adaptor ?! Highly possible. Not all are capable of going higher then 115200 40 minutes ago, neoxnitro said: i only have 2 Go of RAM ... and in the output you shared you have 4 Go RAM, does it possible that my boot problem came from there ?! Like I said, unsupported memory chip in boot loader would explain those troubles. Probably it would work if you flash nonworking image with a u-boot from a working one. You can find them here: https://imola.armbian.com/apt/pool/main/l/linux-u-boot-nanopim4v2-current/ 0 Quote
neoxnitro Posted October 29, 2022 Author Posted October 29, 2022 15 hours ago, Igor said: Like I said, unsupported memory chip in boot loader would explain those troubles. Probably it would work if you flash nonworking image with a u-boot from a working one. You can find them here: https://imola.armbian.com/apt/pool/main/l/linux-u-boot-nanopim4v2-current/ What is the seek and bs parameters values for the dd command to flash the .deb file into the SD card ? where can i find them ? 0 Quote
Igor Posted October 29, 2022 Posted October 29, 2022 12 minutes ago, neoxnitro said: where can i find them ? u-boot deb package contains a script for flashing. 0 Quote
neoxnitro Posted October 29, 2022 Author Posted October 29, 2022 (edited) sudo dpkg -i linux-u-boot-current-nanopim4v2_21.02.3_arm64.deb (Reading database ... 81517 files and directories currently installed.) Preparing to unpack linux-u-boot-current-nanopim4v2_21.02.3_arm64.deb ... Unpacking linux-u-boot-nanopim4v2-current (21.02.3) over (21.02.1) ... Setting up linux-u-boot-nanopim4v2-current (21.02.3) ... I installed the package into my current system and ... boom ... the sd booted ... how does it possible, it's magic !! ... thanks dude Ok, i said "Yesss" too quickly ... aftet the reboot, the system booted via the micro SD, i copied the sd content to emmc (via armbian-config tool) and after that, nothing boot anymore I installed again "buster" version ... but this time, i will flash bootloader of SD card via armbian-config tool ... Edited October 29, 2022 by neoxnitro 0 Quote
Igor Posted October 29, 2022 Posted October 29, 2022 I didn't say installing package will do the job Explore .deb file. Flashing is purposefully manual - via armbian-config - if your system is up and working. 0 Quote
Solution neoxnitro Posted October 29, 2022 Author Solution Posted October 29, 2022 Hehe 😅 Ok, everythings works ! For people with same problem than mine, this is what i did Install u-boot Debian package, one that you knows works (download via: https://imola.armbian.com/apt/pool/main/l/linux-u-boot-nanopim4v2-current/) dpkg -i linux-u-boot-current-nanopim4v2_xxxxxx_arm64.deb Launch armbian-config tool sudo armbian-config System -> Install -> Install/update the bootloader SD/eMMC The SD is now bootable Thx again to Igor for his help 🤜🤛 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.