Jump to content

Bring up for Odroid N2 (Meson G12B)


Brad
 Share

Recommended Posts

1 hour ago, m][sko said:

good source of kernel patches are here


Where do you think they came from and why are not yet in the mainline? :)

 

1 hour ago, m][sko said:

multimedia like HDMI audio or video decoding or what?


It seems nothing out of advanced functions really works atm.

But at least we are now attached to the mainline + patches.Which needs maintenance attention if we want to move on faster..

Link to comment
Share on other sites

Armbian Linux community supported weekly builds download

8 hours ago, Igor said:


Where do you think they came from and why are not yet in the mainline? :)

 


It seems nothing out of advanced functions really works atm.

But at least we are now attached to the mainline + patches.Which needs maintenance attention if we want to move on faster..

 

mainline rules :thumbup: All amlogic boards are also on mainline

mainline u-boot will be also fine. it should work I think

 

so some users can try lima drivers on odroid c2

and if anybody want arm opengl es drivers on odroid n2 

And as always mainline kernel has better stability. 

 

Btw what about passing coherent_pool=4M to kernel. Any plan to add it? I saw your post 

Link to comment
Share on other sites

Hello,

it's me again :). After having my board set up and in use as previously described I wanted to have a look at the temperature, but nowhere it is displayed. Example:

root@OdroidN2:~# armbianmonitor -z
Preparing benchmark. Be patient please...

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=de_DE@euro,Utf16=on,HugeFiles=on,64 bits,6 CPUs LE)

LE
CPU Freq:  1701  1701  1702  1701  1699  1701  1702  1701  1701

RAM size:    3698 MB,  # CPU hardware threads:   6
RAM usage:   1323 MB,  # Benchmark threads:      6

                       Compressing  |                  Decompressing
Dict     Speed Usage    R/U Rating  |      Speed Usage    R/U Rating
         KiB/s     %   MIPS   MIPS  |      KiB/s     %   MIPS   MIPS

22:       5435   499   1059   5287  |     109229   514   1811   9315
23:       5061   479   1076   5158  |     103965   502   1792   8996
24:       4582   453   1089   4927  |     101166   499   1780   8880
25:       4797   494   1109   5478  |     101562   517   1747   9039
----------------------------------  | ------------------------------
Avr:             481   1083   5212  |              508   1782   9057
Tot:             495   1433   7135

Monitoring output recorded while running the benchmark:

Time       big.LITTLE   load %cpu %sys %usr %nice %io %irq   CPU  C.St.
15:24:11: 1704/1896MHz  2.18  11%   1%   6%   0%   2%   0%     °C  0/10
15:24:16: 1704/1896MHz  2.17  10%   1%   6%   0%   0%   0%     °C  0/10
15:24:21: 1704/1896MHz  1.99  10%   2%   7%   0%   0%   0%     °C  0/10
15:24:28: 1704/1896MHz  2.16  63%   2%  59%   0%   0%   0%     °C  0/10
15:24:34: 1704/1896MHz  2.46  88%   2%  85%   0%   0%   0%     °C  0/10
15:24:44: 1704/1896MHz  2.83  91%   3%  86%   0%   0%   0%     °C  0/10
15:24:50: 1704/1896MHz  3.78  98%   4%  92%   0%   0%   1%     °C  0/10
15:24:55: 1704/1896MHz  3.87  97%   3%  92%   0%   0%   1%     °C  0/10
15:25:00: 1704/1896MHz  3.72  74%   3%  69%   0%   0%   0%     °C  0/10
15:25:06: 1704/1896MHz  4.39  97%   5%  90%   0%   0%   1%     °C  0/10
15:25:12: 1704/1896MHz  5.47  98%   5%  91%   0%   0%   1%     °C  0/10
15:25:21: 1704/1896MHz  6.08  98%   3%  90%   0%   3%   0%     °C  0/10

The same is true for top or htop, no display of temperature.

 

What to do?

 

edit:

Attached armbianmonitor -u // and noticed that it produces an error:

root@OdroidN2:~# armbianmonitor -u
System diagnosis information will now be uploaded to /usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
http://ix.io/2iWa
Please post the URL in the forum where you've been asked for.

Further information:

 

root@OdroidN2:/sys/class/hwmon# cat /sys/devices/virtual/thermal/thermal_zone0/temp
cat: /sys/devices/virtual/thermal/thermal_zone0/temp: Invalid argument

 

Thanks for helping.

 

 

Link to comment
Share on other sites

On 4/21/2020 at 3:29 PM, Burschi500 said:

Attached armbianmonitor -u // and noticed that it produces an error:


root@OdroidN2:~# armbianmonitor -u
System diagnosis information will now be uploaded to /usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
/usr/bin/armbianmonitor: line 388: read: read error: 0: Invalid argument
/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected
http://ix.io/2iWa
Please post the URL in the forum where you've been asked for.

 

 

 

Can you try executing as bash -x armbianmonitor -u to get more defails?

If the output gets very long you can use a paste servce like https://paste.debian.net/

Check the output before uploading and if necessary censor ip addresses.

Link to comment
Share on other sites

@Burschi500

 

AFAIK temperature readings are not yet supported (or just broken) in modern kernel which is why script is throwing out errors. (we can only fix armbianmonitor to not show errors at this point, but not really critical) 

 

Modern kernel is still very much a development area and one should be happy that you don't need to use stock outdated 4.9.y

 

On 3/30/2020 at 10:28 PM, iav said:

I see no /dev/watchdog device. What's wrong? Should I tune something?


You can join and do something about. Anything.

 

Modern kernel is in development and it will stay this way for several more months, before we could say its support is matured. Until then, many things will simply not be working or working bad. But kernel is in usable shape.

Link to comment
Share on other sites

Hmm. Now I checked for N2 (ArmbianTV) , the temperature and the rest shows correctly with the core 5.7-rc2.

 

root@arm-64:~# armbianmonitor -m
Stop monitoring using [ctrl]-[c]
Time       big.LITTLE   load %cpu %sys %usr %nice %io %irq   CPU  C.St.

12:52:01: 1908/1992MHz  6.13  73%  10%  62%   0%   0%   0% 56.5°C  0/11
12:52:06: 1908/1992MHz  6.12  99%  10%  88%   0%   0%   0% 56.5°C  0/11
12:52:11: 1908/1992MHz  6.11  99%  15%  83%   0%   0%   0% 56.0°C  0/11
12:52:17: 1908/1992MHz  6.10  98%  19%  78%   0%   0%   1% 56.6°C  0/11
12:52:22: 1908/1992MHz  6.10  99%  15%  82%   0%   0%   0% 56.0°C  0/11^C

Link to comment
Share on other sites

I'm running the balbes150 Armbian_20.10_Arm-64_focal_current_5.9.0-rc7_desktop and I'm very happy with it.  Using the performance governor and highest selectable CPU frequency (1992 MHz by Armbian-config), CPU temperature is normally below 40C and CPU frequencies are 1.91/1.99 GHz for big/LITTLE cores respectively.  However, htop reports 1.99 GHz for all cores.  If I execute cat /sys/devices/system/cpu/cpufreq/policy*/scaling_cur_freq the values 1992000 and 1908000 are returned.

 

Link to comment
Share on other sites

On 10/7/2020 at 1:40 AM, Curmudgeon said:

I'm running the balbes150 Armbian_20.10_Arm-64_focal_current_5.9.0-rc7_desktop and I'm very happy with it.  Using the performance governor and highest selectable CPU frequency (1992 MHz by Armbian-config), CPU temperature is normally below 40C and CPU frequencies are 1.91/1.99 GHz for big/LITTLE cores respectively.  However, htop reports 1.99 GHz for all cores.  If I execute cat /sys/devices/system/cpu/cpufreq/policy*/scaling_cur_freq the values 1992000 and 1908000 are returned.

 

And where you got that kernel? Where I can to look into patches? dts and config?

Link to comment
Share on other sites

Currently no /dev/watchdog device on N2 with -current and -dev armbian kkernel.

But watchdog present in -legacy.

 

I see meson-wdt kernel module on image, I transplant meson_wdt segment from dts file of legacy kernel to dev and current.

 

No success.

No any sign watchdog presence.

 

What I miss?

 

wd5.8-meson-g12b-odroid-n2.dts.patch

Link to comment
Share on other sites

On 10/25/2020 at 5:10 PM, iav said:

And where you got that kernel? Where I can to look into patches? dts and config?

I got the kernel from users.armbian.com/balbes150/arm-64 via forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw-aarch64-armv8 but I am currently reconsidering whether to continue using this kernel or not because balbes150 seems to have taken on an unfavourable, possibly even malevolent attitude towards AMlogic SoC's.

Link to comment
Share on other sites

1 hour ago, Curmudgeon said:

I got the kernel from users.armbian.com/balbes150/arm-64 via forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw-aarch64-armv8 but I am currently reconsidering whether to continue using this kernel or not because balbes150 seems to have taken on an unfavourable, possibly even malevolent attitude towards AMlogic SoC's.

Just a quick reminder: In any case if you decide to use unofficial images or kernels that are spread around the web and are not from Armbian's repository or download page you do this at your own risk.

Link to comment
Share on other sites

I have a Odroid N2+ without eMMC and try to start Armbian directly from USB without success.

 

I downloaded Armbian_20.11.3_Odroidn2_buster_current_5.9.14.img.xz and flashed it to an SSD connected via USB.

Booting in spi mode. Petitboot dev.20201218 loads and after a short while USB drive is detected,  [sda1] Parsed U-boot script from /boot/boot.ini

 

When I select the disk (No Label) to boot my screen goes goes in standby and and the image never boots.

 

Am I doing something wrong?

 

 

 

Link to comment
Share on other sites

9 minutes ago, MisterIks said:

I downloaded Armbian_20.11.3_Odroidn2_buster_current_5.9.14.img.xz and flashed it to an SSD connected via USB.

Have you tried the supported way by flashing Armbian to a sd card and then use nand-sata-install?

Link to comment
Share on other sites

6 hours ago, MisterIks said:

Booting in spi mode.

I can only boot from emmc with the switch on the "emmc" position. On the SPI position, I get the heartbeat on the led as if the kernel starts, but no HDMI output nor network.

 

I wasn't able to make a standard USB-UART bridge work with the N2+, to debug the problem. Anybody got to connect some USB-UART module, other than official Hardkernel's?

Link to comment
Share on other sites

I have two questions regarding mainline (5.10.x) kernel on Odroid N2(+), hope it is fine to ask them here:

  1. It is expected that the boot.ini contains legacy kernel command-line parameters, which are not supported by mainline kernel anymore, including HDMI settings, HPD, overscan, CPU count and clock, right? I saw https://github.com/armbian/build/pull/2629 but the CPU frequency settings are still/again ignored, the CPU always runs at highest possible frequencies. However, it is not a big issue since min/max frequencies can be easily set via CPUFreq API. Interestingly, when using display_autodetect "true", hdmimode "custombuilt" and modeline are set and "hdmitx edid" seems to create two related files in /boot, but all without effect, it seems?
  2. I did RAM R/W benchmarks by writing and reading back a ~2 GiB file to /tmp (tmpfs) and evicting filesystem cache between both steps (sync; echo 3 > /proc/sys/vm/drop_caches), via dd (+conv=fdatasync on write step) which reports back the read/write speeds. Somehow with Linux 4.9 provided by Hardkernel (e.g. with the image provided by Meveric here: https://oph.mdrjr.net/meveric/images/Buster/), I get ~doubled speeds, compared to Armbian Linux 5.10 (reproducible, with nice -19, no other significant processes running etc). I have not yet tested the Armbian image with legacy kernel, but has anyone an idea what the reason could be, or whether the benchmark method is faulty for some reason?
Link to comment
Share on other sites

For 1.  We're continuely with odroid uboot and cant get to mainline uboot on it unlike other amlogic boards we have.

 

Lots of wonkiness and inconsistencies for that.  And yeah the keys for video in boot.ini don't apply to mainline

 

2. Could easily be a regression.   

 

Link to comment
Share on other sites

Interesting, I just flashed a fresh Armbian with Bullseye + Linux 5.10 build from today, which uses boot.cmd and boot.scr now (hence not Odroid U-Boot anymore)? Also the boot.cmd vs boot.ini has been adjusted to not pass legacy Odroid parameter boot kernel command-line anymore, looks much more consistent now. Not sure whether coincidence or a reaction to my post, any way many thanks for this update and alignment with other Armbian images :).

 

Also I found the reason for the low RAM R/W speed: tmpfs I/O highly depends on current the CPU frequency, which on my system is very low on idle, hence during the benchmark frequencies stood at low to middle level. Using performance governor restored full R/W speeds. Armbian by default ships with ondemand governor, very low up_threshold and io_is_busy, which in combination with more background process activity on a fresh image doesn't make that issue visible, but when I apply this to a minimal image, frequencies still stay at low level. It seems that io_is_busy does not apply in case of RAM/tmpfs I/O. The big cores actually stay at max frequency, but the little ones stay at minimum 100 MHz. Only applying performance governor to the small cores is indeed sufficient to restart high benchmark results. Somehow an interesting find. Would be great if there was a possibility to have the little cores frequency raised automatically during (RAM/tmpfs) I/O, but I cannot think of any when ondemand io_is_busy does not do it :huh:.

Link to comment
Share on other sites

On 12/23/2020 at 7:23 PM, lanefu said:

Petitboot currently has a compatibility issue with armbian

Petitboot does not support my HDMI-DVI-Adapter connected 1280x1024 Display. Only my 1080p HD display produces output via a direct HDMI port. It also can't boot my preferred distribution. Therfore I deleted Petitboot and dropped mainline u-boot in my SPI NOR. Now both displays produce an output and my OS is loaded from MicroSD, USB and probably eMMC as well. I can't test eMMC yet, as I don't have one at the moment, but I don't see any reason why it shouldn't work. If there is interest, I am happy to discuss my findings.

Link to comment
Share on other sites

14 minutes ago, usual user said:

my OS is loaded from MicroSD, USB and probably eMMC as well.

uBoot on USB? I can petitboot a mini root from usb,  but don't know how to load Armbian without a µSD or eMMC stub.

Link to comment
Share on other sites

1 hour ago, rob said:

uBoot on USB?

I have replaced Petitboot by u-boot. U-boot sits in SPI NOR and scans eMMC, MicroSD and USB storage for a loadable OS.

It loads Armbian  and even my NanoPC-T4 MicroSD sitting in a card-reader plugged in an USB port. The MicroSD has NanoPc-T4 u-boot in place and would not boot in the Odroid N2+ SD slot natively.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...