1 1
TonyMac32

NanoPi K2 General Topics

Recommended Posts

Like Le Potato, status of support.  Unlike Le Potato, WIP board without official support, 90% of this is incidental to improved mainline support/easy adaptation of fixes for other boards.

 

Current next image kernel:  4.14

 

Dec. 14 2017:  Functions working for me (N=1 sample size)

  • WiFi functioned for me out of the box.
  • HDMI (I added this functionality some time ago)
  • HDMI Sound (Added as of 1:45 Dec.14, not part of any image/build yet)
  • USB
  • Ethernet (no long-term stability testing yet)

Jan. 24 2018: small bugfix

  • Board now reports 2 GB RAM instead of 1

July 8, 2018:  "Next" kernel (4.17) bugfix

  • HDMI audio repaired (in build system, images not built yet)
  • DVFS better, but still throwing errors
  • [BUG]  No USB on K2. 

Share this post


Link to post
Share on other sites
19 minutes ago, m][sko said:

So :D

:lol:

 

The short answer is no, but I'll take a look at what I have in the K2 / Potato patchset, I haven't looked that closely since more basic functionality was missing/broken.  

 

The C2 is presently set up as a different kernel config as well from the other meson64 devices, so I'm not certain where it's development stands, only having access to the K2 and Le Potato, hardware wise.

Share this post


Link to post
Share on other sites
12 minutes ago, TonyMac32 said:

:lol:

 

The short answer is no, but I'll take a look at what I have in the K2 / Potato patchset, I haven't looked that closely since more basic functionality was missing/broken.  

 

The C2 is presently set up as a different kernel config as well from the other meson64 devices, so I'm not certain where it's development stands, only having access to the K2 and Le Potato, hardware wise.

I checked it now and it looks like whole VPU init part is missing

    0014-clk-meson-gxbb-Add-VPU-and-VAPB-clockids.patch
    0015-clk-meson-gxbb-Add-VPU-and-VAPB-clocks-data.patch
    0016-drm-meson-dw_hdmi-Add-support-for-an-optional-extern.patch
    0017-drm-meson-Add-missing-VPU-init.patch
I will rebuild image with this 4 

 

Share this post


Link to post
Share on other sites

I removed all patch from odroidc2-next and added patch set from meson64-next

And /dev/dri is there :)

 

but 

[    0.240500] meson_gx_pwrc_vpu c8100000.sys-ctrl:power-controller-vpu: failed to get reset line

it looks like some invalid data in dtsi  pwrc_vpu   resets

Share this post


Link to post
Share on other sites
1 hour ago, m][sko said:

I removed all patch from odroidc2-next and added patch set from meson64-next

And /dev/dri is there :)

 

but 

[    0.240500] meson_gx_pwrc_vpu c8100000.sys-ctrl:power-controller-vpu: failed to get reset line

it looks like some invalid data in dtsi  pwrc_vpu   resets

I was about to check for it's existence, but decided to check the forums first.  Alright then.  As for the patch, these are sort-of-WIP patches from BayLibre, who is working to get GX/L/M mainlined.  I expect there will be some rough edges.  ;-)  

 

Since you completely revised the patch set, make sure you didn't lose anything, I haven't thoroughly gone through the C2 patches to see if anything special is in there that would benefit the other Meson64 boards.

Share this post


Link to post
Share on other sites

this is list of patch set that I use on odroid c2

desktop is working, hdmi too, ethernet too,

mali driver loaded fine

I didn't check audio

 

0001-ARM64-dts-meson-gxm-Add-support-for-Khadas-VIM2.patch
0002-ARM64-dts-meson-gxbb-allow-child-devices-on-the-USB-.patch
0003-ARM64-dts-meson-gxbb-odroidc2-take-USB-hub-out-of-re.patch
0004-phy-meson-add-USB3-PHY-support-for-Meson-GXL.patch
0005-usb-host-add-a-generic-platform-USB-roothub-driver.patch
0006-usb-host-xhci-plat-integrate-the-platform-roothub.patch
0007-ARM64-dts-meson-gxl-add-USB-host-support.patch
0008-ARM64-dts-meson-gxm-add-GXM-specific-USB-host-config.patch
0009-ARM64-dts-meson-gx-Enable-USB-on-GXL-and-GXM-boards.patch
0014-clk-meson-gxbb-Add-VPU-and-VAPB-clockids.patch
0015-clk-meson-gxbb-Add-VPU-and-VAPB-clocks-data.patch
0016-drm-meson-dw_hdmi-Add-support-for-an-optional-extern.patch
0017-drm-meson-Add-missing-VPU-init.patch
0018-reset-meson-add-level-reset-support-for-GX-SoC-famil.patch
0019-soc-amlogic-add-Meson-GX-VPU-Domains-driver.patch
0020-soc-amlogic-meson-gx-pwrc-vpu-fix-power-off-when-pow.patch
0021-ASoC-meson-add-meson-audio-core-driver.patch
0022-ASoC-meson-add-register-definitions.patch
0023-ASoC-meson-add-aiu-i2s-dma-support.patch
0024-ASoC-meson-add-initial-i2s-dai-support.patch
0025-snd-meson-activate-HDMI-audio-path.patch
0026-drm-meson-select-dw-hdmi-i2s-audio-for-meson-hdmi.patch
0028-ARM64-dts-meson-gx-add-audio-controller-nodes.patch
0029-ARM64-dts-meson-gxl-add-sound-dai-cells-to-HDMI-node.patch
0031-ARM64-dts-meson-gxl-Take-eMMC-data-strobe-out-of-eMM.patch
0032-ARM64-dts-meson-gx-add-VPU-power-domain.patch
0033-ARM64-dts-meson-gx-Add-HDMI_5V-regulator-on-selected.patch
0034-ARM64-dts-meson-gx-grow-reset-controller-memory-zone.patch
0035-ARM64-dts-odroid-c2-Add-HDMI-and-CEC-Nodes.patch
0036-ARM64-dts-meson-activate-hdmi-audio-HDMI-enabled-boa.patch
1010_GXBB_NanoPi_K2_DTS_HDMI.patch
1020_GXBB_memory_allocation_meson_GX.patch
1030_GXBB_NanoPi_K2_DTS_HDMI_sound.patch
90-01-add_8812au_8821au_with_monitor_mode_and_frame_injection.patch
90-01-add_8812au_8821au_with_monitor_mode_and_frame_injection_update.patch
90-02-add_8814au_with_monitor_mode_and_frame_injection.patch
90-02-add_8814au_with_monitor_mode_and_frame_injection_update.patch
arm64_increasing_DMA_block_memory_allocation_to_2048.patch
arm64-set-default-target-to-Image.patch
aufs.4.14.patch1
bash_to_afterinstall.patch
odroidc2-enable-scpi-dvfs.patch
packaging-4.x-NEXT-with-postinstall-scripts.patch
patch-4.13.10-rt3.patch.disabled
 

Share this post


Link to post
Share on other sites

The board the K2 is based from, and so the board support package I started with, #defined ram size explicitly as 1 GB.  For the other Amlogic board I have that ram size is detected at boot, so I didn't check on the K2.

Share this post


Link to post
Share on other sites

Nanopik2. Works only armbian 5.38 xenial. Lost ethernet connection every time after 10-15 minutes. Wifi works good. Synaptic works on 5.38 . In armbian 5.42 does not..... when you search a package 100% cpu usage system hungs.

Armbian 5.38 only chromium works properly. Firefox hungs every time after 5-10 minutes. On Armbian 5.42 no browser works - hungs after 5-10 minutes... ( I think browsers hung when play video i think ) 5.38 and 5.42 no hdmi sound. recognized usb external sound card.  Both strange amount of SWAP 789MB.

Share this post


Link to post
Share on other sites

There is a memory and firmware allocation issue, unfortunately as a WIP board I haven't spent a ton of time on it, however I should be able to sort it out as I work to end the "blobtastrophy" that was our U-boot situation before.  I only have to ask @Neil Armstrong if BayLibre has NanoPi K2 in the list of GXBB devices to get mainlined.  Most of the work is done thanks to the Odroid C2, so worst case eventually I'll look at it.

Share this post


Link to post
Share on other sites

I am new so please forgive me. I had been trying different images on my friendly arm pi k2 and now suddenly i have no hdmi out. i can ssh in but i cant get the display out to work anymore. is this a hardware issue or is there someway to determine if its a software issue?

 

Thanks

Share this post


Link to post
Share on other sites
3 hours ago, hough said:

I had been trying different images on my friendly arm pi k2 and now suddenly i have no hdmi out.


Hotplugging might not work but when you boot you should get a screen. I don't recall any troubles of this kind. Try another cable.

Share this post


Link to post
Share on other sites

uname -a Linux nanopik2 4.16.0-meson64 #15 SMP PREEMPT Thu Apr 5 16:51:35 CEST 2018 aarch64 aarch64 aarch64 GNU/Linux

linux-u-boot 5.38 and armbian-firmware 5.38 linux-xenial-root 5.38., armbian-tools-xenial 5.44, armbian-config 5.45

System is hanging from time to time. I dont know why... every next boot eth0 is loosing connection after 10 minutes, so i disabled et0 and use wifi....

Previous armbians have audio meson audio, now is dummy output - i have to use external usb sound card.

I have tried images to ordroid C2 and lapotato but they dont work

 

Share this post


Link to post
Share on other sites
On 5/19/2018 at 2:21 AM, Igor said:

Hotplugging might not work

I'll check on that.  I have the hotplug service on Rockchip (not hardware dependent), and added it to the XU4, should we just move it to bsp/common/lib and add it to the boards that need it?  the only other thing in there is 71-axp-power-button.rules at the moment.

 

@constantius If you can build it yourself I've just pushed an update on the K2 to go to u-boot 2018.03, which has a ton of improvements to the handling of memory/device drivers.  I need to do some more tests on K2, but since it was broken before I felt the limited testing I've done so far has been sufficient. 

Share this post


Link to post
Share on other sites

I have discovered that the K2 (S905) appears to not "make up numbers" as the S905X boards do, I'm playing with sysbench.  I came to this because it is running significantly hotter than Le Potato, which is S905X.  I'm going to switch it to conservative, for the boards with firmwares that "make it up" on the front end this will most likely do nothing, but at least on K2 it will cool it down.

Share this post


Link to post
Share on other sites

"Tony MAC.; If you can build it yourself I've just pushed an update on the K2 to go to u-boot 2018.03, which has a ton of improvements to the handling of memory/device drivers.  I need to do some more tests on K2, but since it was broken before I felt the limited testing I've done so far has been sufficient". 

 

Yes please i will build the image myself

 

Share this post


Link to post
Share on other sites

Now that is an error I have never seen.  I built multiple images last night,  but they were all xenial, not that that should impact it...

 

@Igor your thoughts?  The board config specifies meson64 like it always has...  

Share this post


Link to post
Share on other sites
25 minutes ago, TonyMac32 said:

your thoughts?  The board config specifies meson64 like it always has...  


Probably running compilation with wrong parameters ... or using a broken build script. He probably still has the old configuration without -s905

 

It is working here.

Share this post


Link to post
Share on other sites
1 1