image does not boot ? - Githubissues

SadarSSI commented 7 months ago

First of all, thank you for this incredible work!

I am having an issue with the image as it does not boot. I have tried the 3 available releases but none of them boot.

I followed the instructions which are the same as for a Nanopi R5S with which I had no problem booting with the images provided. But the R6C images do not boot: the red LED on the sys is lit and stays that way.

The NanoPi R6C has never been installed with FriendlyElec, is this a problem?

Any idea ?

SadarSSI commented 7 months ago

Okay, I booted with the SD card with the FriendlyElec Bookworm and then copied nanopi-r6c_bookworm-v12-6.7-rc7.img.xz to eMMC.

xzcat --verbose nanopi-r6c_bookworm-v12-6.7-rc7.img.xz > /dev/mmcblk2

dd bs=4K status=progress seek=8 if=idbloader.img of=/dev/mmcblk2
dd bs=4K status=progress seek=2048 if=u-boot.itb of=/dev/mmcblk2

Two observations:

With the R5S version, the keyboard works on the console in HDMI --> this does not work with the R6C, but it also does not work with the FriendlyElec Bookworm version (maybe a problem with the dtb file...)
The htop command does not return the temperature (libsensor is installed); it works with the R5S

Additional thanks for the work done!

inindev commented 7 months ago

First of all, thank you for this incredible work!

I am having an issue with the image as it does not boot. I have tried the 3 available releases but none of them boot.

I followed the instructions which are the same as for a Nanopi R5S with which I had no problem booting with the images provided. But the R6C images do not boot: the red LED on the sys is lit and stays that way.

The NanoPi R6C has never been installed with FriendlyElec, is this a problem?

Any idea ?

I am unsure why the one here is not booting, do you have the ability to capture a serial log?

I have updated images here: https://github.com/inindev/debian-image/releases Possibly you would have better luck with this?

SadarSSI commented 7 months ago

Hello, thank you for your answer.

Yesterday I tried several solutions: the Ubuntu and Debian distributions made available by FriendlyElec, the update that you offered me but it does not work: no boot, nothing on the HDMI interface.

I tried to connect the debug output with a USB-C cable and the driver offered for Windows (https://www.wch-ic.com/downloads/CH341SER_ZIP.html), but it displays unreadable characters

Finally, I tested the armbian solution. The version made available on https://fi.mirror.armbian.de/archive/nanopi-r6s/archive/ works: no boot problem, HMDI output and keyboard are OK. This works with a version "Linux nanopi-r6c 6.7.0-rc1-edge-rockchip-rk3588".

The other sdcard images (FriendlyElec, etc...) are all later than this version, I don't know if that's the problem

Ideally I would prefer to use your solution which is a classic Debian solution.

I tried to make an sdcard with the DTB file that works with armbian, but it didn't work. I tried to reinstall the uboot part on the sdcard but the boot did not work.

I had the opportunity to use versions of uboot which displayed a message during startup allowing you to modify the variables, boot path, etc. I haven't seen or found this feature in the provided uboot. I tried pressing the escape keys, or other keys without it displaying a message from uboot

That's it, I'm going to look in more detail at your procedure for creating an image, to see if I get a bootable sdcard

growler commented 4 months ago

I'm having a similar issue with R6C. The eMMC has FriendlyWRT installed and boots, the MMC with the latest image (nanopi-r6c_bookworm-v12-6.7-rc7) does not, the serial output follows:

DDR V1.12 52218f4949 cym 23/07/06-19:46:50
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0x1
CH0 RX Vref:27.5%, TX Vref:18.8%,18.8%
CH1 RX Vref:25.9%, TX Vref:20.8%,20.8%
CH2 RX Vref:25.8%, TX Vref:20.8%,20.8%
CH3 RX Vref:27.1%, TX Vref:19.8%,19.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-g82417168bf-230508 #root (Sep 08 2023 - 20:53:43)
unknown raw ID 0 0 0
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
No misc partition
spl: partition error
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(bb1bbbc832...) + OK
## Checking u-boot 0x00a00000 ... sha256(c71482afc8...) + OK
## Checking fdt-1 0x00acfe10 ... sha256(8ca95a3e50...) + OK
## Checking atf-2 0x000f0000 ... sha256(30812190d0...) + OK
## Checking atf-3 0xff100000 ... sha256(cb7bdbec2b...) + OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 199.90/350.172 ms

Otherwise I can mount MMC just fine and even chroot into the the debian environment. I would gladly try to debug this issue given just a little bit of direction.

inindev commented 4 months ago

I'm having a similar issue with R6C. The eMMC has FriendlyWRT installed and boots, the MMC with the latest image (nanopi-r6c_bookworm-v12-6.7-rc7) does not, the serial output follows:

DDR V1.12 52218f4949 cym 23/07/06-19:46:50
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0x1
CH0 RX Vref:27.5%, TX Vref:18.8%,18.8%
CH1 RX Vref:25.9%, TX Vref:20.8%,20.8%
CH2 RX Vref:25.8%, TX Vref:20.8%,20.8%
CH3 RX Vref:27.1%, TX Vref:19.8%,19.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-g82417168bf-230508 #root (Sep 08 2023 - 20:53:43)
unknown raw ID 0 0 0
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
No misc partition
spl: partition error
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(bb1bbbc832...) + OK
## Checking u-boot 0x00a00000 ... sha256(c71482afc8...) + OK
## Checking fdt-1 0x00acfe10 ... sha256(8ca95a3e50...) + OK
## Checking atf-2 0x000f0000 ... sha256(30812190d0...) + OK
## Checking atf-3 0xff100000 ... sha256(cb7bdbec2b...) + OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 199.90/350.172 ms

Otherwise I can mount MMC just fine and even chroot into the the debian environment. I would gladly try to debug this issue given just a little bit of direction.

This is not using the correct u-boot: U-Boot SPL 2017.09-g82417168bf-230508 #root (Sep 08 2023 - 20:53:43)

The u-boot in this distro is "2024.01": https://github.com/inindev/nanopi-r6/releases

You may be booting from the u-boot flashed on the SPI? You have to hold the mask button to bypass that.

growler commented 4 months ago

When I hold the mask button when connecting the power nothing happens. No serial and nothing on HDMI. Should I try to upgrade the pre-installed loader on the eMMC?

inindev commented 4 months ago

That is a good option.

growler commented 4 months ago

Worked! Thank you.

inindev / nanopi-r6

image does not boot ? #1