Posts by Merlin475

Quote from chewitt

It's not the answer you're looking for, but our current RK codebase "is what it is" until the current rebase against a mainline kernel and changes to reimplement how RK uses ffmpeg (moving to a proper stateless V4L2 stack) has completed. And before you ask, there is no timeline or schedule for either of those

Thank you for answering,

Since my Nano Pi K2 didn't work, I bought this board hoping it will work well but it really doesn't. (Everything is fine except 4K HEVC)

Maybe I try to buy another board, any suggestion would be nice.

Also I got the RTC Working.

I have a Firefly ROC-RK3328-CC 1GB version 1.2 and they have added a jumper for RTC backup battery as I have showed it in the picture below,

All you have to do is to connect a 3V battery with 1.25mm jack to it and set the time. (Left pin +, Right pin -)

In this image you can see that I have DS3231 connected as well but it doesn't work since I2C 0 is disabled by default and you can see an extra IR receiver because the box is fully metal and when it's closed my remote won't work. For IR receiver you can simply connect the data pin to the data pin of the onboard IR receiver.

reading the date and time from RK805 chip

cat /proc/driver/rtc

setting date and time via software #This should be GMT time at the time you will set it.

date -s "2018-11-25 13:53:00"

setting date and time into RK805

hwclock -w

finally reading software time and time from RK805 again

hwclock -r
cat /proc/driver/rtc

if everything is right, reboot and after that go to Setting and then Interface then Regional and set your country.

in my case there is a 21 seconds delay between hardware and software so when you are setting the GMT time, set it with +21 second delay.

Hello everyone,

I have a weird problem with 4k hvec files, everything is fine with 1080p h264 files but when I play 4 hvec videos after a while colors constantly get higher and lower.

I don't know how to explain it properly, the video plays fine but after a while it gets jumpy like as if someone is playing with settings, colors are fine then they are too much then again fine then too much... it keeps jump too high and OK.

I have set the setting color to limited and it got a little better but then again it's not completely fixed.

I'm using hardware decoding, Prime, Direct to plane.

Also Prime EGL has no picture (its fine with 1080p h264 files), any fix for this?

and another thing would be using a rtc module with this board, i got DS3231 but dunno how to use it.

Thank you very much for reading this thread .

Quote from chewitt

I looked at the FriendlyARM wiki and It looks like you need to provide u-boot on the SD card. I'll have a think..

Thank you for writing back,

There is only one uboot patch available for this board and it's not working with anything above LibreELEC-NanoPiK2.arm-8.0-8.0.1j.img.

This is the log from LibreELEC-S905.arm-8.90.007.img after patching it.

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
no sdio debug board detected 
TE: 177291

BL2 Built : 12:06:06, Jun 13 2016. 
gxb g176ecdb - laiyin.mo@droid12-sz

set vcck to 1100 mv
set vddee to 1000 mv
Board ID = 8
CPU clk: 1536MHz
DDR chl: Rank0+1 same @ 792MHz
DDR0: 2048MB(auto)-2T-11
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK. 
Run bl30...
Load bl31 from SD, src: 0x00020200, des: 0x1010000[, size: 0x00013140
Image: gxb_v1.1.3134-b387442 2016-06-16 14:48:44 yun.cai@droid06]

OPS=0x13

77 6f c1 25 27 9e ab 53 12 f5 9d f6 [0.272593 Inits done]

secure task start!
high task start!
low task start!
Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x0006afc0
NOTICE:  BL3-1: v1.0(debug):c813a61
NOTICE:  BL3-1: Built : 14:47:05, Jun 16 2016
INFO:    BL3-1: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2015.01-00014-g4ef665ff6c-dirty (May 06 2017 - 20:32:09)

DRAM:  2 GiB
Relocation Offset is: 76f3b000
register usb cfg[1][0] = 0000000077f96b78
register usb cfg[0][1] = 0000000077f96b98
register usb cfg[2][0] = 0000000077f96bb8
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
MMC:   SDIO Port B: 0, SDIO Port C: 1
[mmc_init] mmc init success
In:    serial
Out:   serial
Err:   serial
reboot_mode=cold_boot
hpd_state=0
cvbs performance type = 4, table = 0
Net:   Meson_Ethernet
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]addr=0x3d800000 width=5760, height=2160

Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
There is no valid bmp file at the given address
Hit Enter or space or Ctrl+C key to stop autoboot -- :  3  2  1  0 
(Re)start USB...
USB0:   dwc_usb driver version: 2.94 6-June-2012
USB (1) peri reg base: c0000020
USB (1) use clock source: XTAL input, div: 1
USB (1) base addr: 0xc9100000
Force id mode: Host
dwc_otg: Highspeed device found !

scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
Device: SDIO Port B
Manufacturer ID: 41
OEM: 3432
Name: SD16G 
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 7.5 GiB
mmc clock: 40000000
Bus Width: 4-bit
reading s905_autoscript
1773 bytes read in 4 ms (432.6 KiB/s)
## Executing script at 01020000
reading kernel.img
9578496 bytes read in 529 ms (17.3 MiB/s)
reading uEnv.ini
197 bytes read in 4 ms (47.9 KiB/s)
reading /dtb.img
38576 bytes read in 6 ms (6.1 MiB/s)
ee_gate_off ...
## Booting Android Image at 0x01080000 ...
reloc_addr =73f55d20
copy done
load dtb from 0x1000000 ......
board_usb_stop cfg: 0
   Uncompressing Kernel Image ... OK
   kernel loaded at 0x01080000, end = 0x01a89b18
   Loading Ramdisk to 3fbd5000, end 3ffffc00 ... OK
   Loading Device Tree to 000000001fff3000, end 000000001ffff6af ... OK

Starting kernel ...

uboot time: 8648078 us

Nothing happen after this and the screen is completely black but it's not off. (Just a black screen on TV 1080p60hz).

Link to the files I've been able to find,

Patch from piboard

1496080309668-nanopi-k2-patch-by-kicker22004.tar.gz

Nanopi k2 uboot and kernel

attachment.php?id=1132

I have no idea how to use it's kernel but the uboot is the same with the other file.

any thoughts?

Quote from chewitt

I don't have this hardware for testing but if you're installing mainline u-boot to internal storage and using a 4.19 kernel image I know that NanoPi-K2 requires specific u-boot (boot FIP) changes to create a working image. If it's possible to boot from an SD card, it should work as-normal.

Thank you for answering,

This board does not have any internal storage, I'm using SD card (a few of them, different brand different type).

If it helps, I'm able to provide the log from uart port.

Just tell me which image and dtb I use or simply tell me what to do.

Hey

Can I use this with my Nano Pi K2? Which file should I use and which device tree file will work with my board?

Thank you very much 🙏

Hi everyone,

I'm very new to this but I have been spending a few days reading all the topics related to Amlogic S905 and Nano PI K2.

I've tested many things but there is only one image that works and it contain kodi 17.1

https://drive.google.com/uc?id=1xpznetnxyi8tsonwh5g6x7qa0jshgi4v&export=download

But I want to use The latest version that has kodi 18 beta 5

So far my understanding is that I need to have a correct image with correct kernel and correct device tree (dtb.img) to be able to correctly boot up but so far everything I tried was a failure.

I tried to use Odroid C2 image but on uart port it says this is unauthorized and I should contact kernel support...

I also tired to update the one that already work but after successfully updating it, it will give me black screen and nothing works.

Has anyone managed to successfully do this? or can anyone help me make this thing work?

I only have dtb.img for version 3.14.29 but it needs the 4.19 to work. (I assume)

Thank you very much for reading this.