Minix-u1 2015/01/01 at boot time

Help & Support Installation & Booting
1

If no network, date at boot time is 2015/01/01. It was an issue in the early version of libreelec

minix-u1 coreelec dts
…
rtc {
compatible = “amlogic, aml_vrtc”;
alarm_reg_addr = < 0xc81000a8 >;
timer_e_addr = < 0xc1109988 >;
init_date = “2015/01/01”;
status = “okay”;
};
minix-u1 libreelec dts
…
rtc_hym8563 {
compatible = “amlogic, rtc_hym8563”;
dev_name = “rtc_hym8563”;
status = “okay”;
reg = <0x51>;
interrupts = <0x0 0x40 0x1>;
gpio-rtc-irq = <0xf 0x51 0x0>;
};
…
rtc {
compatible = “amlogic, aml_vrtc”;
alarm_reg_addr = <0xc81000a8>;
timer_e_addr = <0xc1109988>;
init_date = “2015/01/01”;
status = “disabled”;
};

2

And what would you like it to be?

Edit: The RTC section in both DTBs is identical.


3

the dts came from the dtb.img included in the corelec 9.01 image for minix-u1 using an hexadecimal editor and a dtc compiler.

4

Ok… Here’s a DTB with rtc enabled and rtc_hym8563 disabled.
Give it a try and report if there’s any difference.
gxbb_p200_2G_minix_neo_u1.zip (10.1 KB)

5

In the gxbb_p200_2G_minix_neo_u1.dtb the status of rtc is disabled and rtc_hym8563 has an ok pk status
I have no tool to transform .dtb to .img. Could you give me a pointer for a program that can do it?

6

What? The DTB I attached above has rtc set to okay and rtc_hym8563 disabled.

7

Rename the file to dtb.img, no tool necessary.

8

You are right i have used the wrong dts.

9

So did this DTB solve the problem or not?

10

This dtb did not. Since the kernel is still 3.14.xx i try the dtb from wxrtasy libreelec 8.4.1 an after boot with no network the time is now correct .I carefully watch tis dtb and rtc_hym8563 is ok and aml_vrtc is disabled. Is is correct to use dtb libreelec 8.4.1 with coreelec 9.0.1

  • List item
11

Please upload the DTB that showed the time correctly without network.
And no, it’s not correct to use LE DTB with CE.

12

I can’t upload dtb libreelec 8.4.1. I have this message " Sorry, new users can not upload attachments."

13

I have disassembled the dtb.img from libteelec 8.4.1
dtc -I dtb dtb.img -O dts -o dtb.dts
and the results for rtc
…
rtc_hym8563 {
compatible = “amlogic, rtc_hym8563”;
dev_name = “rtc_hym8563”;
status = “okay”;
reg = < 0x51 >;
interrupts = < 0x00 0x40 0x01 >;
gpio-rtc-irq = < 0x0f 0x51 0x00 >;
};
…
rtc {
compatible = “amlogic, aml_vrtc”;
alarm_reg_addr = < 0xc81000a8 >;
timer_e_addr = < 0xc1109988 >;
init_date = “2015/01/01”;
status = “disabled”;
};

14

This is identical to CE’s original DTB

rtc_hym8563 {
	compatible = "amlogic, rtc_hym8563";
	dev_name = "rtc_hym8563";
	status = "okay";
	reg = <0x51>;
	interrupts = <0x0 0x40 0x1>;
	gpio-rtc-irq = <0xf 0x51 0x0>;
};

…

rtc {
	compatible = "amlogic, aml_vrtc";
	alarm_reg_addr = <0xc81000a8>;
	timer_e_addr = <0xc1109988>;
	init_date = "2015/01/01";
	status = "disabled";
};

Try uploading dmesg log after a reboot.
dmesg | paste, and post the url here.

15

If you try
strings dtb.img |less
an search for rtc pattern you will seel many times
…
amlogic, aml_vrtc
2015/01/01
okay
wifi
amlogic, aml_wifi
…
Same result with an hexadecimal editor.

My point is the dtb included in the package minix-u1 is not the dtb for minix u1.

16

That’s not what I asked for, though.
The included DTB is meant to work with the U1. If it doesn’t work right, it’s a different issue.

17

CoreELEC:~ # dmesg | grep rtc
[ 1.980209@0] aml_vrtc rtc.29: rtc core: registered aml_vrtc as rtc0
[ 4.364064@0] aml_vrtc rtc.29: setting system clock to 2015-01-01 00:00:07 UTC (1420070407)

rtc_hym8563 found in dmesg

no

18

of course is “no rtc_hym8563 found in dmesg”

19

@chalister none of us can quite understand what your saying, you need to explain better.

20

I try to explain that the dtb included in the minix-u1 packages is wrong.
How do you explain that in the source of the dtb

rtc {
	compatible = "amlogic, aml_vrtc";
	alarm_reg_addr = <0xc81000a8>;
	timer_e_addr = <0xc1109988>;
	init_date = "2015/01/01";
	status = "disabled";
};

and at the boot time 
CoreELEC:~ # dmesg | grep rtc
[ 1.980209@0] aml_vrtc rtc.29: rtc core: registered aml_vrtc as rtc0
[ 4.364064@0] aml_vrtc rtc.29: setting system clock to 2015-01-01 00:00:07 UTC (1420070407)

How do you explain that when i disassemble the dtb i have

rtc {
compatible = “amlogic, aml_vrtc”;
alarm_reg_addr = < 0xc81000a8 >;
timer_e_addr = < 0xc1109988 >;
init_date = “2015/01/01”;
status = “okay”;
};

how do you explain strings dtb.img |less
…
amlogic, aml_vrtc
2015/01/01
okay
wifi
amlogic, aml_wifi

 For me the only explanation is that aml_vrtc is enabled in the dtb

Libreelec 9.01 (semi official ) has not this problem of date and time at boot time if no network
for me it is ok because if i do
strings dtb.img |less ant search for rtc i see
.....
rtc_hym8563
amlogic, rtc_hym8563
rtc_hym8563
okay

Can i use the libreelec 9.01 dtb in coreelect 9.01 ?