[NanoPi M4 V2 - M4 Image not working]

On 10/13/2019 at 8:04 PM, chwe said:

confidence got denied by looking into sources.. :-/

 

especially the android related stuff (https://gitlab.com/friendlyelec/rk3399-android-8.1) cause it seems to be the only repositories which are open around m4 v2... U-boot seems to be some 2014.x version (don't know it this is part of the normal rockchip u-boot package for an android build or just some random mess I don't understand - I assume it's a rockchip sourcedrop from the commit history - e.g. none except the few ones from friendlyelec added on top of it). Honestly I'm surprised (and not the good way).

 

I guess (since rockpi images boot), we can base an u-boot defconfig based on rockpi. @mindee are the sources for more recent u-boot versions (newer than 2014 based one from the android 8.1 package) not available for the board yet? Did I do a mistake and not find it? Or is it not planed to release? For those running friendly core on it, can you provide a uart boot dump? I would be interested which version of u-boot they use for everything except the android they provide.

 

Never the less I'm (still) confident that we can provide initial support to the board soon for a 4.4 legacy and recent mainline-ish kernel as well. I just didn't feel as comfortable to create those patches to the buildscript without having the hardware to test if it boots at least.

 

 

I have successfully compiled and run http://wiki.friendlyarm.com/wiki/index.php/Buildroot_for_RK3399 on a nanopi m4 v2.  I can confirm that uboot's makefile from these sources reports "version=2014".

My question is: how do I use the  working compiled uboot 2014 version with an armbian image? Is it possible to simply substitute some (compiled) file of the armbian image to do a first very raw try and see if the nanopi m4 v2 board boots and works?

 

Thank you and sorry for my very noob question

 

 

[Summer update. Bust.er4all boards]

On 8/19/2019 at 3:38 PM, NicoD said:

You could use balbes150 his N2 Buster image. This is with kernel 5.2. But almost everything works as it should.

Otherwise you could build a Buster image yourself if you've got an x86 pc.
https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

OK, thank you. I'm using Armbian_5.91_Odroidn2_Debian_buster_default_4.9.185.7z image and it works well: I've installed NextcloudPi and I'm successfully using it on daily basis, although dmesg reports some minor errors.

I also tried to build a Buster image strictly following the docker method described in the Armbian guide, but with no luck, as kernel compilation fails.

At this point, considering promising progresses of the linux-meson project, probably I'll wait for G12B SoC integration in the mainline before trying to compine a new kernel.

[Bring up for Odroid N2 (Meson G12B)]

Igor's odroid N2 image works...

 

Here are dmesg red lines that require investigation from somebody more expert than me:

• clkmsr ffd18004.meson_clk_msr: failed to get msr ring reg0
• cvbs_out: chrdev devno 263192576 for disp
• dmi: Firmware registration failed.
• perf_event: read sys_cpu_status0_offset failed, ret = -22
• meson-pwm ff802000.pwm: pwm pinmux : can't get pinctrl
  meson-pwm ffd1b000.pwm: pwm pinmux : can't get pinctrl
•  mtdoops: mtd device (mtddev=name/number) must be supplied
• drivers/amlogic/efuse/efuse_hw64.c:_efuse_read:196: read error!!!
• meson_cpufreq_probe: Registered platform drive
  [    2.063911] ff803000.serial: clock gate not found
• gpio-keypad ff800000.gpio_keypad: failed to get gpio index from dts
•  efuse efuse:  open efuse clk gate error!!
• di_get_vpu_clkb: get clk vpu error.
• PPMGRDRV: err: ppmgr_driver_probe called
  [    2.199532] Reserved memory: failed to init DMA memory pool at 0x00000000e3000000, size 0 MiB
• [    2.202554] meson-mmc: mmc driver version: 3.02, 2017-05-15: New Emmc Host Controller
  [    2.203254] meson-mmc: >>>>>>>>hostbase ffffff8008629000, dmode
  [    2.242335] meson-mmc: meson_mmc_probe() : success!
  [    2.249480] meson-mmc: >>>>>>>>hostbase ffffff8008632000, dmode
  [    2.249515] meson-mmc: gpio_cd = 1ca
  [    2.252739] meson-mmc: emmc: resp_timeout,vstat:0xa1ff2800,virqc:3fff
  [    2.252742] meson-mmc: emmc: err: wait for irq service, bus_fsm:0x8
  [    2.252759] meson-mmc: meson_mmc_irq_thread_v3 551 emmc: cmd:1
  [    2.252761] meson-mmc: meson_mmc_irq_thread_v3() 567: set 1st retry!
  [    2.252763] meson-mmc: retry cmd 1 the 3-th time(s)
  [    2.253757] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff
  [    2.253759] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7
  [    2.253765] meson-mmc: meson_mmc_irq_thread_v3 551 emmc: cmd:1
  [    2.253766] meson-mmc: retry cmd 1 the 2-th time(s)
  [    2.254757] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff
  [    2.254759] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7
  [    2.254765] meson-mmc: meson_mmc_irq_thread_v3 551 emmc: cmd:1
  [    2.254766] meson-mmc: retry cmd 1 the 1-th time(s)
  [    2.255757] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff
  [    2.255759] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7
  [    2.255764] meson-mmc: meson_mmc_irq_thread_v3 551 emmc: cmd:1
  [    2.255767] meson-mmc: Command retried failed line:585, cmd:1
  [    2.286325] meson-mmc: meson_mmc_probe() : success!
  [    2.286490] amlogic mtd driver init
  [    2.287074] cectx ff80023c.aocec: cec driver date:Ver 2019/1/7
• 
  [    2.287548] cectx ff80023c.aocec: not find 'port_num'
  [    2.287551] cectx ff80023c.aocec: using cec:1
  [    2.287580] cectx ff80023c.aocec: no hdmirx regs
  [    2.287582] cectx ff80023c.aocec: no hhi regs
  [    2.287586] cectx ff80023c.aocec: not find 'output'
  [    2.287591] cec: wake up flag:0
  [    2.289030] cectx ff80023c.aocec: irq cnt:2
  [    2.289243] cectx ff80023c.aocec: wakeup_reason:0x0
  [    2.289289] cectx ff80023c.aocec: cev val1: 0x0;val2: 0x0
  [    2.289292] cectx ff80023c.aocec: aml_cec_probe success end
•  defendkey ff630218.defendkey: Reserved memory is not enough!
•  aml_card_probe error ret:-517
•  cgroup: cgroup2: unknown option "nsdelegate"
•  meson-mmc: Tuning transfer error: nmatch=0 tuning_err:0xffffffac
• Error: Driver 'spdif-dit' is already registered, aborting...
  [    2.323264] asoc debug: aml_audio_controller_probe-115
  [    2.324305] aml_card_probe error ret:-517
   

Proof of work and complete dmesg is attached below

 

 

 

dmesg

[Summer update. Bust.er4all boards]

On 7/22/2019 at 10:14 AM, Franky66 said:

@Igor

My big thank to you for your work. I will check the images and will give feedback for errors etc.

Hello, I'm interested in armbian buster for odroid n2 too... Were you able to check it?