[ODroid-N2 RTC not work in linux-image-current-meson64=20.02.8 5.4.28-meson64]

Reporting back

Working out of the box now with latest focal image. Thanks for the effort

[ODroid-N2 RTC not work in linux-image-current-meson64=20.02.8 5.4.28-meson64]

On 4/12/2020 at 1:59 AM, martinayotte said:

I'm one of the main Armbian devs, so, yes, I will add the DT overlay in builds in the near future ...

  

On 4/12/2020 at 1:59 AM, martinayotte said:

I'm one of the main Armbian devs, so, yes, I will add the DT overlay in builds in the near future ...

Hi martinayotte,

 

thanks for providing quick fix via device tree overlay. Also i am very happy to see we got Armbian and a much more recent kernel running on HK Odroid N2! Thx for all your hard work!

 

Do we lack full support for overlays atm? Even if we do as described for allwiner based boards?

'Cause i tried to use "user_overlays" and "overlay" options in "ArmbianEnv.txt" as described here:

https://docs.armbian.com/Hardware_Allwinner_overlays/

but couldn't get it to work.

Just wanna know if i am missing something/ doing it wrong or It's known/intended

 

/boot/armbianEnv.txt

verbosity=1
user_overlays=odroid-n2-ic2@1c000
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u <= AutoAdded so file seems to be found

adding the entries and copying the files myself didn't change anything.

adding useroverlay via armbian-add-overlay  => Overlays are supported only on A10... => Removing the allwiner sanity check from

/usr/sbin/armbian-add-overlay line 38-41

edits armbianEnv.txt correctly by adding "user_overlays" option and copying the files to "/boot/overlay-user/" which seems be the desired location. But no pcf8563 modules are loaded after boot. 

I also tried adding the dtbo to /boot/dtb/overlay /boot/dtb/amlogic/overlays and so on.

 

Your mentioned example rc.local works fine instead.

mkdir /sys/kernel/config/device-tree/overlays/i2c3a
cat /root/odroid-n2-ic2@1c000.dtbo > /sys/kernel/config/device-tree/overlays/i2c3a/dtbo

systemctl stop ntp
ntpd -qg
systemctl start ntp
hwclock --systohc -f /dev/rtc1

 

TIA

[Single Armbian image for RK + AML + AW (aarch64 ARMv8)]

HW: Beecool M8S Pro L S912 3G 16G DDR3 LB

 

Created sd card from latest arbian buster image with etcher and tried to boot it. Sadly the bootlogo keeps flickering.  Updating via Stock Rom throws the error mentioned here:  https://forum.armbian.com/topic/12988-armbian-for-amlogic-s905x3/?do=findComment&comment=94956

E:Map of '@/cache/recovery/block.map' failed 
E:failed to map file 
Installation aborted

If i got the instructions right i dont need to dd a uboot image to sd-card. I adjusted uEnv.txt to use meson-gxm-q201 or 200 dtb but that didnt work. under android it shows me the following DTB-ID

gxm-q20xrmii_3g

any tips you could give me?

[Armbian for Amlogic S905X3]

Wow thanks thats a leap forward in using armbian on the M8S Pro L S912 LB, as it quits with the same error.

Thanks for your explanation and help. Could you also point out, on how to dump and reflash uboot env with root terminal,twrp or fastboot

as far as i checked against /dev/block/env it is the same enviroment as in your u-boot

On 2/11/2020 at 1:04 AM, 5p0ng3b0b said:

 

The solution:

 

I didn't want to go down the uart/uboot route as I don't know where the tx/rx points are on this box and my eyesight isn't that great anymore. Plus my soldering days were over many years ago. I was able to boot into a twrp.zip via stock recovery, but there was no setenv command in the twrp console to enter the info manually. Perhaps there is a command I could enter to run the aml_autoscript from here, I have no idea. I decided the way forward was to extract the env partition with twrp (you can just as easily do it with dd or fastboot) and hack it before flashing it back. I opened the file up with a hex editor and could see what looked like a uboot environment with fatload commands etc, a 4 byte header at the start of the file then each command separated by a null byte. I'm looking at yet another brick if I bork it, so I'm not doing this with a hex editor. Convert it to a text file, make the changes and convert the text file back to the original 8mb image format was the plan. All I had to do was trim the trailing zeros and replace the remaining null bytes with a newline. I copied the file to my PC to do the job but it can all be done from a rooted box with busybox installed.