NanoPi m2 - doesn't boot

ole
Hi,
I'm trying to boot my NanoPi M2 for the first time, but without success. I
followed the instructions on
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_M2#Install_Debian_Pack...

but the M2 board fails to load kernel. 
Here is the flashing log:

ole@pc:~/Downloads/nanopi/m2/sd-fuse_nanopi2$ ./fusing.sh /dev/sdc debian
Re-running script under sudo...
Warn: Image not found for Debian, download now (Y/N)? Y
> wget --spider --tries=1
http://112.124.9.243/dvdfiles/S5P4418/images-for-eflasher/debian-jessie-...
Spider mode enabled. Check if remote file exists.
--2016-12-17 21:58:05-- 
http://112.124.9.243/dvdfiles/S5P4418/images-for-eflasher/debian-jessie-...
Connecting to 112.124.9.243:80... 
connected.
HTTP request sent, awaiting response... 404 Not Found
Remote file does not exist -- broken link!!!

> wget
http://wiki.friendlyarm.com/download/S5P4418/images-for-eflasher/debian-...
--2016-12-17 21:58:06-- 
http://wiki.friendlyarm.com/download/S5P4418/images-for-eflasher/debian-...
Resolving wiki.friendlyarm.com (wiki.friendlyarm.com)... 45.79.108.206
Connecting to wiki.friendlyarm.com
(wiki.friendlyarm.com)|45.79.108.206|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 59 [application/x-md5]
Saving to: ‘debian-jessie-images.tgz.hash.md5’

debian-jessie-images.tgz.hash.md5        
100%[===========================================================================
=======>]
     59  --.-KB/s    in 0s      

2016-12-17 21:58:06 (3.20 MB/s) - ‘debian-jessie-images.tgz.hash.md5’ saved
[59/59]

> wget --spider --tries=1
http://112.124.9.243/dvdfiles/S5P4418/images-for-eflasher/debian-jessie-...
Spider mode enabled. Check if remote file exists.
--2016-12-17 21:58:06-- 
http://112.124.9.243/dvdfiles/S5P4418/images-for-eflasher/debian-jessie-...
Connecting to 112.124.9.243:80... connected.
HTTP request sent, awaiting response... 404 Not Found
Remote file does not exist -- broken link!!!

> wget
http://wiki.friendlyarm.com/download/S5P4418/images-for-eflasher/debian-...
--2016-12-17 21:58:07-- 
http://wiki.friendlyarm.com/download/S5P4418/images-for-eflasher/debian-...
Resolving wiki.friendlyarm.com (wiki.friendlyarm.com)... 45.79.108.206
Connecting to wiki.friendlyarm.com
(wiki.friendlyarm.com)|45.79.108.206|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 776027904 (740M) [application/x-gzip]
Saving to: ‘debian-jessie-images.tgz’

debian-jessie-images.tgz                 
100%[===========================================================================
=======>]
740.08M  4.30MB/s    in 2m 43s  

2016-12-17 22:00:51 (4.55 MB/s) - ‘debian-jessie-images.tgz’ saved
[776027904/776027904]

debian-jessie-images.tgz: OK
> tar xzvf debian-jessie-images.tgz -C debian
boot.img
partmap.txt
rootfs.img
---------------------------------
2ndboot fusing
36+1 records in
36+1 records out
18760 bytes (19 kB, 18 KiB) copied, 0.00449633 s, 4.2 MB/s
---------------------------------
bootloader fusing
1+0 records in
1+0 records out
512 bytes copied, 0.00717741 s, 71.3 kB/s
481+1 records in
481+1 records out
246632 bytes (247 kB, 241 KiB) copied, 0.0590639 s, 4.2 MB/s
---------------------------------
Bootloader image is fused successfully.

---------------------------------
Debian filesystem fusing
Image root: ./debian

Writing environment to /dev/sdc...
Done
-----------------------------------------------------------------------------
[/dev/sdc] capacity = 3724MB, 3904897024 bytes
current /dev/sdc partition:
MBR.0 start : 0x0000100000 size 0x0004000000  kB
MBR.1 start : 0x0004100000 size 0x002f200000  kB
MBR.2 start : 0x0033300000 size 0x001ac00000  kB
MBR.3 start : 0x004df00000 size 0x009ad00000 Ext kB
MBR.4 start : 0x004e000000 size 0x0000800000  kB
MBR.5 start : 0x004e900000 size 0x0001600000  kB
MBR.6 start : 0x0050000000 size 0x0098c00000  kB
-----------------------------------------------------------------------------
parsing ./debian/partmap.txt:
part.0 flash=mmc,0:2ndboot:2nd:0x200,0x8e00::[RAW] 
part.1 flash=mmc,0:bootloader:boot:0x8000,0x77000::[RAW] 
part.2 flash=mmc,0:boot:fat:0x100000,0x4000000:boot.img:[MBR]
./debian/boot.img
part.3 flash=mmc,0:rootfs:ext4:0x4100000,0x0:rootfs.img:[MBR]
./debian/rootfs.img
-----------------------------------------------------------------------------
create new MBR 2:
[MBR.0] start : 0x0000100000 size 0x0004000000 
[MBR.1] start : 0x0004100000 size 0x0000000000 
-----------------------------------------------------------------------------
copy from: ./debian to /dev/sdc
[MBR.0] part.2 :    18755828 ./debian/boot.img   > 100% : done.
[MBR.1] part.3 :  2031453340 ./debian/rootfs.img > 100% : done.
-----------------------------------------------------------------------------
/dev/sdc: msdos partitions 1 2
resize2fs 1.42.13 (17-May-2015)
Filesystem at /dev/sdc2 is mounted on /media/ole/rootfs; on-line resizing
required
old_desc_blocks = 1, new_desc_blocks = 1
resize2fs: Invalid argument While checking for on-line resizing support
---------------------------------
Debian is fused successfully.
All done.






And when the SD card is correctly unmounted and inserted to NanoPi m2 it
prints this:

EMA VALUE : 001
123
Lock value  = 159
GATE CYC    = 0x00008421
GATE CODE   = 0x3A3B3A3D
Loading from sdmmc...
 Image Loading Done!
Launch to 0x42C00000


U-Boot 2014.07-g3493520 (Jun 25 2016 - 18:22:58)

PLL : [0] =  550000000, [1] =  800000000, [2] =  800000000, [3] = 
614399000
PLL1: CPU FCLK =  800000000, HCLK = 200000000
PLL2: BUS BCLK =  400000000, PCLK = 200000000
PLL2: MEM MCLK =  800000000, DCLK = 800000000, BCLK = 400000000, PCLK =
200000000
PLL0: G3D BCLK =  550000000
PLL2: MPG BCLK =  400000000, PCLK = 200000000
I2C:   ready
DRAM:  256 MiB
Heap = 0x43000000~0x45000000
Code = 0x42c00000~0x42c73984
GLD  = 0x42bffeb8
GLBD = 0x42bffe68
SP   = 0x42bffe68,0x42bffe50(CURR)
PC   = 0x42c06114
TAGS = 0x40000100
PAGE = 0x42c80000~0x42c8c000
MACH = [4330]
VER  = 1
BOARD= [NanoPi M2]
LCD  = N/A (-1)
MMC:   NXP DWMMC: 0, NXP DWMMC: 1, NXP DWMMC: 2
In:    serial
Out:   serial
Err:   serial
switch to partitions #0, OK
mmc0 is current device
Writing to MMC(0)... done
HDMI: display.0, preset 0 (1280 *  720)
HDMI: PHY Ready!!!
 ** ext4fs_devread read error - block
DONE: Logo bmp 800 by 480 (3bpp), len=1152056 
DRAW: 0x47000000 -> 0x46000000 
Hit any key to stop autoboot:  0 
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
s5p4418# 

I also tried to flash android image but it gives the same error during
boot. I also tried different SD card (different vendor) with the same
error. Note the 'FRIENDLY ARM' boot logo is displayed correctly, so the SD
card and boot filesystem must be recognised otherwise the logo would not
display. I also inserted the sdcard into my PC and I can see the files and
partitions all working correctly (I can read and write to SD card as
superuser, no error on the PC).

Any idea what to do or how to fix it? Thank you.

ole
Update: managed to make it to boot. Solution: use SANDISK SD card (as
hinted on the Wiki page). Previously tried with Verbatim and Integral brand
- they don't work with nano pi m2 (but work on other development boards).
Anybody else had the same issue? Are only Sandisk SD cards supported? Or is
is the uboot issue?

bob
kingston uSD (4-8GB) gave me many problems, it works 1 on 8 i have. move to
samsung uSD 16GB, it is ok.
i wonder why nanopi M2 does not accept kingstone uSD as samsung.