Posts by Elicity

I'll let them know

I don't like writing to chips more than I need to because there is always that chance things might go bad.

rpi-eeprom-config always writes to the eeprom not matter what, and that just seems wrong.

A simple "Save changes to eeprom (y/n)" would be sufficient.

Okay, good to know. I'm no expert, I just used the descriptions from the board itself:

So the HDMI-A-1 is the HDMI0 port on board ?

Afaict setting the hotplug value might work for him.

As a last resort I found in /flash/config.txt which could be related, but IDK.

# Don't send initial active source message.
# Avoids bringing CEC (enabled TV) out of standby and channel switch when
# rebooting.
hdmi_ignore_cec_init=1

Try the latest nightly from 2025-04-16, it solved a bunch of issues for me:
Its at the bottom of the nightly page: https://test.libreelec.tv/12.0/RPi/RPi5/
LibreELEC-RPi5.aarch64-12.0-nightly-20250416-e25b5e0.img.gz (sha256) 2025-04-16 15:44 143.5M

I used the official hdmi-cable from RPI, so I could have 4K@60hz with my SamsungTV (2024).
All works just fine here

edit 1:

I could reproduce some I think: I use the HDMI-0 (closest to power-port), when I use the other one HDMI-1 the CEC does not work.

edit 2:

I tried changing HDMI-port number from 1 to 2 , that did not work
I tried changing physical address from 0 to 1 and 2 but that did not work either. (assuming those are addresses?)

So I went to the pulse-eight website to get some clarification on the options: https://libcec.pulse-eight.com/FAQ/Index/104
* HDMI port number: the HDMI port number that you connected the CEC adapter to on your TV or AVR. (Default: 1)
* Connected to HDMI device: the logical address of the HDMI device that you connected the CEC adapter to. 0 for TV, 5 for an AVR (Default: 0)
So a bit of a dead end there.

Then I went to https://github.com/Pulse-Eight/libcec and under vendor specific notes:

Raspberry Pi

• If your TV cannot detect the Raspberry Pi's CEC, or if the the Pi can't detect the TV, try adding the following line in /boot/config.txt and reboot the Pi: hdmi_force_hotplug=1

So that might be an option, but I cant test it because it works fine here on HDMI-0 just not HDMI-1

Good luck !

balbes150

So I can confirm this works on the NanoPi-r6C

I have no experience installing u-boot, but with some dd magic and pure luck I got it to boot, albeit with an outdated/limited device tree so I have no audio atm. (although i see it loading the current dtb in the log). But it boots and it was fun to see that it works.

After examination:
00000000	MBR
00008000	RKNS/idbloader/bootloader
00800000	u-boot
00C00000	trust.img

So I used the OpenWRT image and skipped the EFI/MBR part and wrote from 0x8000 to 0x00c00000 (12M)

$ dd if=owrt bs=1 skip=$((0x8000)) count=$((0x00c00000-0x8000)) seek=$((0x8000)) of=/dev/sda
12550144+0 records in
12550144+0 records out
12550144 bytes (13 MB, 12 MiB) copied, 20,1171 s, 624 kB/s
$ 

Bootlog:

DDR 9fffbe1e78 cym 24/02/04-10:09:20,fwver: v1.16
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:26.3%, TX Vref:20.8%,20.8%
CH1 RX Vref:25.8%, TX Vref:19.8%,19.8%
CH2 RX Vref:27.1%, TX Vref:18.8%,18.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 2024.10-OpenWrt-r28427-6df0e3d02a (Feb 03 2025 - 23:09:37 +0000)
Trying to boot from MMC1
## Checking hash(es) for config config-1 ... OK
## Checking hash(es) for Image atf-1 ... sha256+ OK
## Checking hash(es) for Image u-boot ... sha256+ OK
## Checking hash(es) for Image fdt-1 ... sha256+ OK
## Checking hash(es) for Image atf-2 ... sha256+ OK
## Checking hash(es) for Image atf-3 ... sha256+ OK
INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-682-g4ca8a8422:derrick.huang, fwver: v1.45
NOTICE:  BL31: Built : 10:11:21, Dec 27 2023
INFO:    spec: 0x13
INFO:    code: 0x88
INFO:    ext 32k is not valid
INFO:    ddr: stride-en 4CH
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO:    l3 cache partition cfg-0
INFO:    system boots from cpu-hwid-0
INFO:    disable memory repair
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO:    BL31: Initialising Exception Handling Framework
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 = 0xa00000
INFO:    SPSR = 0x3c9


U-Boot 2024.10-OpenWrt-r28427-6df0e3d02a (Feb 03 2025 - 23:09:37 +0000)

Model: FriendlyElec NanoPi R6C
DRAM:  8 GiB
Core:  331 devices, 29 uclasses, devicetree: separate
MMC:   mmc@fe2c0000: 0, mmc@fe2e0000: 1
Loading Environment from nowhere... OK
In:    serial@feb50000
Out:   serial@feb50000
Err:   serial@feb50000
Model: FriendlyElec NanoPi R6C
Net:   eth0: ethernet@fe1c0000
Hit any key to stop autoboot:  2  1  0 
Scanning for bootflows in all bootdevs
Seq  Method       State   Uclass    Part  Name                      Filename
---  -----------  ------  --------  ----  ------------------------  ----------------
Scanning global bootmeth 'efi_mgr':
7[r[999;999H[6n8No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
  0  efi_mgr      ready   (none)       0  <NULL>                    
** Booting bootflow '<NULL>' with efi_mgr
Loading Boot0000 'mmc 0' failed
Loading Boot0001 'mmc 1' failed
EFI boot manager: Cannot load any image
Boot failed (err=-14)
Scanning bootdev 'mmc@fe2e0000.bootdev':
Scanning bootdev 'mmc@fe2c0000.bootdev':
  1  extlinux     ready   mmc          1  mmc@fe2c0000.bootdev.part /extlinux/extlinux.conf
** Booting bootflow 'mmc@fe2c0000.bootdev.part_1' with extlinux
1:	LibreELEC
Retrieving file: /KERNEL
append: boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet console=ttyS2,1500000 console=tty0 systemd.debug_shell=ttyS2 coherent_pool=2M cec.debounce_ms=5000
Retrieving file: /dtb/rockchip/rk3588s-nanopi-r6c.dtb
## Flattened Device Tree blob at 12000000
   Booting using the fdt blob at 0x12000000
Working FDT set to 12000000
   Loading Device Tree to 00000000ecb8b000, end 00000000ecbb3988 ... OK
Working FDT set to ecb8b000

Starting kernel ...

[    2.257086] platform physmap-flash.0: failed to claim resource 0: [mem 0x08000000-0x07ffffff]
[    2.263332] rk_gmac-dwmac fe1c0000.ethernet: Can not read property: rx_delay.
[    2.263963] rk_gmac-dwmac fe1c0000.ethernet: set rx_delay to 0x10
[    2.417783] cpufreq: Unable to obtain ARMCLK: -2
[    2.502384] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to create device link (0x180) with supplier spi2.0 for /power-management@fd8d8000/power-controller/power-domain@12
[!p]104[?7h[6n[32766;32766H[6n[53;1H[!p]104[?7h[6n[32766;32766H[6n[53;1H[?25h[1;32mLibreELEC[1;32m:[1;34m/ [0m#

I moved my backups to the network since the sdcard had limited storage. I could see and select a backup for restore, but it just sat there idle instead of doing its thing. An error message would have been nice

NanoPi-r6c won't boot

Steps I took:

1. Booted OpenWRT (link) to test if debug-console was working and it was.

screen /dev/ttyUSB0 1500000

2. Verified checksum successfully:

2186b184bb88272b2522841679b3bc99a7a7ae9aa376cc3d4b375b12381c4919

 LibreELEC-ARMv8.aarch64-13.0-devel-20250607193042-e5590fa-rk3588-roc-pc.img.gz

3. Wrote test-image to sdcard and changed FTD to NanoPi-r6c

$ diff extlinux.conf extlinux.conf.bak 
3c3
<   FDT /dtb/rockchip/rk3588s-nanopi-r6c.dtb
---
>   FDT /dtb/rockchip/rk3588s-roc-pc.dtb

4. Inserted sdcard into NanoP, no output on debug-console, unfortunately it does not boot.

Thanks for all the hard work.

Hi,

I noticed that backup/restore is not working with SMB. However I did notice that when I use

mount -o user=$USER //server/share ~/Backup

it works just fine.

Disappointing I'll bet, my late response does not help either I'm afraid. But its very much appreciated, like all the other work you guys have been doing.

That's was all I was allowed to attach, but you can start the video, then hit pause. It does not need to be playing, it just has to be started.

Take a look, I'm not that versed in video tech but its x265 hevc if those are the right terms.

Attachment triggers the GUI-palet shift on rpi5.

Most colors switch to a "brighter" version of themselves, but its best seen if you select "brown" under settings>interface>skin>colors

In the GUI brown just switches to red when playing that file.

Afaict its just a one off after I tested more x265 and they do not seem to have this issue.

However converting it to a different container or with different encoder does not seem to matter.

The problems shifts along, its weird.

I'll put in a request, referring to this thread.

Quote from Elicity

The GUI-colors are off too while playing, its weird

So I thought I'd take some screenshots, to show the issue. Now here comes the kicker: they are snapped when colors are not right, but display fine when I look at them. When I play x265 GUI-colors are off, when I select another video-type x264, the GUI-colors snap back.

There is another underlying issue. Maybe driver related idk.

Thanks for all the help, its awesome!

Quote from maple

If you try to play this in any version of Kodi released since March 18 it will immediately crash Kodi hard. If it doesn't for you than maybe it is GPU related although I don't think Kodi uses the GPU for that kind of file, as best I could tell all the decoding was done in software.

I tried on latest LE12 nightly (2025-04-04) and it works just fine. It uses SW decoding because of YUV422, but if you want HW decoding and save tons of space convert it using:

ffmpeg -i test_recording.ts -acodec copy -pix_fmt yuv420p10le -c:v hevc test_recording.mp4

This will reduce it to ~3.5mb which is a 93% reduction or ~16x smaller.

-rw-r--r-- 1 kodi kodi 54689388 Apr 7 01:15 /dev/shm/test_recording.ts
-rw-r--r-- 1 kodi kodi 3453886 Apr 7 01:22 /dev/shm/test_recording.mp4

First of all, for future reference. Make a backup once in a while. I do it every other week for LE.

You can find all installed/downloaded packages under /storage/.kodi/addons/packages.

Make a LE backup first and then try installing them manually one-by-one (pick lastest version)

HiassofT Thank you very much, you guys are too fast

edit:

So I updated to latest LE12 (2025-04-04), Immediately for some constructive feedback.

The black screen problem has been fixed, yay!

However the other issue i still present:

Quote from Elicity

Everything works fine except for Zoom Mode, when I cycle to that nothing happens. If I do it from the video-menu it does work, but I have to increase or decrease the percentage and set it back.

(afaict the zoom value is not applied when switching to zoom mode)

Its working fine for everything else, just not x265. The GUI-colors are off too while playing, its weird

Something isn't right with x265, but it does not really matter. I'm happy its playing at all. I'll report it once I have some more time on my hands.

Thanks, that saves me the trouble

edit:

still broken on nightly-20250328-47483e0 (RPi5.aarch64)

I dont know if this is related, but I have reported some issues with x265 here