bgilsrud Posted November 11, 2022 Share Posted November 11, 2022 I downloaded the latest Armbian 22.08 image for the NanoPi M4V2 (https://armbian.chi.auroradev.org/dl/nanopim4v2/archive/Armbian_22.08.8_Nanopim4v2_jammy_current_5.15.75.img.xz), flashed it to an sd card and tried to boot my NanoPi M4 (non-V2 board). It crashes every time with the attached log. I have tried 4 different power supplies, so I don't think that's the issue. Quote DDR Version 1.25 20210517 In Channel 0: DDR3, 933MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 933MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1 Release Time: May 29 2020 17:36:36, version: 1.26 CPUId = 0x0 ChipType = 0x10, 330 mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! emmc reinit mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! emmc reinit mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! SdmmcInit=2 1 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=61056MB FwPartOffset=2000 , 0 StorageInit ok = 44930 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3335db8 signature is wrong recovery gpt... GPT 0x3335db8 signature is wrong recovery gpt fail! Trust Addr:0x4000, 0x58334c42 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xdee30 RunBL31 0x40000 @ 164649 us NOTICE: BL31: v1.3(release):845ee93 NOTICE: BL31: Built : 15:51:11, Jul 22 2020 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1196): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2022.07-armbian (Oct 29 2022 - 20:26:35 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: FriendlyElec NanoPi M4V2 DRAM: 2 GiB PMIC: RK808 Core: 288 devices, 29 uclasses, devicetree: separate MMC: mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from MMC... Card did not respond to voltage select! : -110 *** Warning - No block device, using default environment In: serial Out: serial Err: serial Model: FriendlyElec NanoPi M4V2 Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 starting USB... Bus usb@fe380000: ehci_generic usb@fe380000: Failed to get clocks (ret=-19) Port not available. Bus usb@fe3c0000: ehci_generic usb@fe3c0000: Failed to get clocks (ret=-19) Port not available. Bus usb@fe900000: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe900000 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3252 bytes read in 5 ms (634.8 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 117 bytes read in 4 ms (28.3 KiB/s) 22780598 bytes read in 967 ms (22.5 MiB/s) 30540288 bytes read in 1293 ms (22.5 MiB/s) 77017 bytes read in 13 ms (5.6 MiB/s) 2698 bytes read in 7 ms (376 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=3fc0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 22780534 Bytes = 21.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 7894d000, end 79f06a76 ... OK Loading Device Tree to 00000000788d1000, end 000000007894cfff ... OK Starting kernel ... efi_free_pool: illegal free 0x0000000078f09040 efi_free_pool: illegal free 0x0000000078f06040 [ 4.380673] Internal error: implementation fault (unsupported exclusive): 96000035 [#1] PREEMPT SMP [ 4.381500] Modules linked in: [ 4.381788] CPU: 1 PID: 9 Comm: kworker/u12:0 Not tainted 5.15.75-rockchip64 #22.08.8 [ 4.382500] Hardware name: FriendlyElec NanoPi M4 Ver2.0 (DT) [ 4.383023] Workqueue: events_unbound deferred_probe_work_func [ 4.383570] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 4.384205] pc : ww_mutex_lock_interruptible+0x1a4/0x308 [ 4.384700] lr : phy_power_off+0x28/0xd8 [ 4.385071] sp : ffff800009e7bab0 [ 4.385377] x29: ffff800009e7bab0 x28: 00000000fffffffe x27: 0000000000a000c4 [ 4.386040] x26: 0000000000a000c4 x25: 0000000010624dd3 x24: 0000000000900004 [ 4.386701] x23: 0000000000900004 x22: 0000000000000000 x21: ffff80000f000300 [ 4.387361] x20: 0000000104d58b05 x19: ffff80000f000000 x18: 0000000000000001 [ 4.388022] x17: 7469772074756f65 x16: 6d697420316e6567 x15: 00000000000001d9 [ 4.388682] x14: ffff800009e7b730 x13: 00000000ffffffea x12: ffff800009b1fd10 [ 4.389342] x11: 0000000000000003 x10: ffff800009b07cd0 x9 : ffff800009b07d28 [ 4.390003] x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001 [ 4.390663] x5 : 0000000000057fa8 x4 : 0000000000000000 x3 : ffff80000f000300 [ 4.391323] x2 : ffff0000006a8000 x1 : 0000000000000000 x0 : ffff80000f000300 [ 4.391984] Call trace: [ 4.392212] ww_mutex_lock_interruptible+0x1a4/0x308 [ 4.392674] phy_power_off+0x28/0xd8 [ 4.393012] rockchip_pcie_host_init_port+0x564/0x5a0 [ 4.393486] rockchip_pcie_probe+0xf8/0x4c0 [ 4.393880] platform_probe+0x68/0xd8 [ 4.394229] really_probe+0xbc/0x428 [ 4.394566] __driver_probe_device+0x114/0x188 [ 4.394981] driver_probe_device+0xb0/0x110 [ 4.395373] __device_attach_driver+0xbc/0x158 [ 4.395786] bus_for_each_drv+0x7c/0xd0 [ 4.396153] __device_attach+0xec/0x1a8 [ 4.396514] device_initial_probe+0x14/0x20 [ 4.396905] bus_probe_device+0x9c/0xa8 [ 4.397265] deferred_probe_work_func+0x9c/0xf0 [ 4.397687] process_one_work+0x20c/0x4c8 [ 4.398069] worker_thread+0x208/0x478 [ 4.398424] kthread+0x138/0x150 [ 4.398733] ret_from_fork+0x10/0x20 [ 4.399082] Code: c8017e60 35ffffa1 17fffd08 f9800071 (c85ffc60) [ 4.399640] ---[ end trace 0c6488f3033d79a6 ]--- I tried the Bullseye CLI image and it fails in the same way. The Sid server image works fine. Any ideas? Thanks, Ben 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted November 11, 2022 Share Posted November 11, 2022 4 minutes ago, bgilsrud said: NanoPi M4V2 4 minutes ago, bgilsrud said: boot my NanoPi M4 (non-V2 board) So you download the wrong image and wonder why it does not work? M4 (non V2 does not have a maintainer attached (feel free to volunteer) and therefore no images are directly provided for download. You can try those from archive: https://fi.mirror.armbian.de/archive/nanopim4/archive/ 0 Quote Link to comment Share on other sites More sharing options...
Andrey84 Posted December 28, 2022 Share Posted December 28, 2022 I get this error too with Armbian_22.08.8_Nanopim4_jammy_current_5.15.75_xfce_desktop.img I checked both images on my nanopi m4 and found that unsupported image for nanopi-m4 does not work on it. But image for nanopi m4 v2 (Armbian_22.11.1_Nanopim4v2_jammy_current_5.15.80.img) works on nanopi m4 and I think that probably on nanopi m4 v2 too. Somewhere in this forum I saw that if one image can run on several devices that image will be supported, so I think that it is good to have one image for both nanopi devices. it should be mentioned that v2 image supports v1 device, so users won't doubt. 0 Quote Link to comment Share on other sites More sharing options...
koftikes Posted December 29, 2022 Share Posted December 29, 2022 11.11.2022 в 17:08, bgilsrud сказал: I tried the Bullseye CLI image and it fails in the same way. The Sid server image works fine. Any ideas? Can you provide full hardware config of your device? I mean board version, additional adapters, eMMC, power supply etc ... 0 Quote Link to comment Share on other sites More sharing options...
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.