Bring up for Odroid N2 (Meson G12B)

Brad

By Brad,
in Development

 Share
13 13

Recommended Posts

Igor

Igor 2301

Posted
Posted
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..

0
Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

m][sko

m][sko 12

Posted
Posted
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 

0
Link to post
Share on other sites
Burschi500

Burschi500 0

Posted
Posted

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.

 

 

0
Link to post
Share on other sites
Werner

Werner 409

Posted
Posted
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.

0
Link to post
Share on other sites
Igor

Igor 2301

Posted
Posted

@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.

0
Link to post
Share on other sites
balbes150

balbes150 897

Posted
Posted

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

0
Link to post
Share on other sites
Curmudgeon

Curmudgeon 1

Posted
Posted

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.

 

0
Link to post
Share on other sites
iav

iav 4

Posted
Posted
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?

0
Link to post
Share on other sites
Curmudgeon

Curmudgeon 1

Posted
Posted
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.

1
Link to post
Share on other sites
Werner

Werner 409

Posted
Posted
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.

0
Link to post
Share on other sites
MisterIks

MisterIks 0

Posted
Posted

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?

 

 

 

0
Link to post
Share on other sites
Werner

Werner 409

Posted
Posted
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?

0
Link to post
Share on other sites
JMCC

JMCC 341

Posted
Posted
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?

0
Link to post
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
13 13
Go to topic listing