Hi all,

 

Successfully Installed Armbian_20.02.1_Nanopineo2black_buster_current_5.4.20.img on a NanoPi Neo2 Black using an SD Card. The board is fitted with a 16GB eMMC card via the optional adapter. 

 

Ran apt-update && apt-upgrade && armbian-config (“Install” “Install to/update boot loader” -> Install/Update the bootloader on SD/eMMC" - that was the only option available.)

 

Proceeded with 'nand-sata-install' only to be presented with the same 'Install/Update the bootloader on SD/eMMC' and nothing else.

 

Poked about, no mention of the eMMC card during boot (via dmesg) and no '/dev/mmbblk1' - which I thought might be the appropriate device.

 

Checked the eMMC card using a microSD adaptor on another machine - shows up as a device so suspect it's okay for use.

 

Have scanned the forum and found similar instances where eMMC support hasn't been enabled. Patches are available for those systems and look to have been implemented. Was wondering is someone far more knowledgeable than myself could confirm if eMMC support is enabled in the image I installed and if not, outline the steps needed to enable it.

 

Thanks in advance, -- Adrian 

Providing logs with 

armbianmonitor -u

 significantly raises chances that issue is getting addressed.

 

It works for me.

9 minutes ago, Igor said:

Providing logs with 

armbianmonitor -u

 significantly raises chances that issue is getting addressed.

 

It works for me.

Many thanks. Very new here. Will post the output asap.

30 minutes ago, Igor said:

Providing logs with 

armbianmonitor -u

 significantly raises chances that issue is getting addressed.

 

It works for me.

The output is listed here. This is from 1st boot on a fresh SD card. 

This image: https://dl.armbian.com/nanopineo2black/archive/Armbian_20.02.1_Nanopineo2black_buster_current_5.4.20.7z

eMMC is normally recognized.

cat /proc/partitions 
major minor  #blocks  name

 179        0   62367744 mmcblk0
 179        1   61739968 mmcblk0p1
 179       32   30535680 mmcblk2
 179       33   30226224 mmcblk2p1
 252        0      51200 zram0
 252        1     506600 zram1

Perhaps your eMMC is dead / not compatible?
 

1 hour ago, Igor said:

eMMC is normally recognized.

It is when you insert it for the third time and you get a confirmatory click as the connector engages! Things are now looking more promising. mmcblk2 now appears (still unpartitioned so no mmcblk2p1.) Thank you for your help especially being able to demonstrate that the current release does support eMMC.