I received my Neutis Dev Kit in yesterday. A very nicely build board.
Has anyone gotten the instructions on how to “Build your own Linux OS” here. to work ? and as a side note, why hasn’t EMLID added this full build to the download page over the neutis-minimal-image one? Yet another note, anyone have a clue how to get a debian baised version using yocto for this.
I followed those instructions on a VM (Virtual Box & VMWare Player) and after 6 hours of building I could not get the VM’s to connect to the board. UGh…(So for others be warned and try to connect first). I then installed Linux Ubuntu on my laptop, and before building I made sure Neutis Flasher would connect. It did so I started the build again and 4.5 hours later it was done successfully.
Now here is where things get unclear in the docs.
It says “You will find your image here: $BUILD/tmp/deploy/images/neutis-n5/*.sunxi-sdimg”
There are 2 files in that folder that can fulfill this statement, so which one is the correct one ?
#1) neutis-image-neutis-n5.sunxi-sdimg
#2) neutis-image-neutis-n5-20181002061537.rootfs.sunxi-sdimg.
In any event I tried both, and when the device boots up it gets stuck at “Starting kernel …”.
Below is the terminal output when its reset.
U-Boot SPL 2018.07-g8c5d4fd (Oct 02 2018 - 08:54:38 +0000)
DRAM: 512 MiB
Trying to boot from MMC2
U-Boot 2018.07-g8c5d4fd (Oct 02 2018 - 08:54:38 +0000) Allwinner Technology
CPU: Allwinner H5 (SUN50I)
Model: Emlid Neutis N5
DRAM: 512 MiB
MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment
Failed (-5)
In: serial
Out: serial
Err: serial
Net: No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
1870 bytes read in 1 ms (1.8 MiB/s)
## Executing script at 4fc00000
U-boot loaded from eMMC
403 bytes read in 0 ms
27247 bytes read in 2 ms (13 MiB/s)
266 bytes read in 1 ms (259.8 KiB/s)
Applying DT overlay sun50i-h5-spi0-status-okay.dtbo
577 bytes read in 2 ms (281.3 KiB/s)
Applying DT overlay sun50i-h5-uart1.dtbo
577 bytes read in 1 ms (563.5 KiB/s)
Applying DT overlay sun50i-h5-uart2.dtbo
577 bytes read in 1 ms (563.5 KiB/s)
Applying DT overlay sun50i-h5-uart3.dtbo
510 bytes read in 2 ms (249 KiB/s)
Applying DT overlay sun50i-h5-r-uart.dtbo
374 bytes read in 1 ms (365.2 KiB/s)
Applying DT overlay sun50i-h5-i2c0.dtbo
374 bytes read in 1 ms (365.2 KiB/s)
Applying DT overlay sun50i-h5-i2c1.dtbo
374 bytes read in 1 ms (365.2 KiB/s)
Applying DT overlay sun50i-h5-i2c2.dtbo
375 bytes read in 1 ms (366.2 KiB/s)
Applying DT overlay sun50i-h5-r-i2c.dtbo
504 bytes read in 2 ms (246.1 KiB/s)
Applying DT overlay sun50i-h5-usbhost0.dtbo
504 bytes read in 2 ms (246.1 KiB/s)
Applying DT overlay sun50i-h5-usbhost1.dtbo
504 bytes read in 1 ms (492.2 KiB/s)
Applying DT overlay sun50i-h5-usbhost2.dtbo
504 bytes read in 1 ms (492.2 KiB/s)
Applying DT overlay sun50i-h5-usbhost3.dtbo
532 bytes read in 1 ms (519.5 KiB/s)
Applying DT overlay sun50i-h5-ethernet-100.dtbo
363 bytes read in 1 ms (354.5 KiB/s)
Applying DT overlay sun50i-h5-analog-codec.dtbo
501 bytes read in 1 ms (489.3 KiB/s)
Applying DT overlay sun50i-h5-camera-status-okay.dtbo
1132 bytes read in 1 ms (1.1 MiB/s)
Applying DT overlay sun50i-h5-hdmi.dtbo
3254784 bytes read in 156 ms (19.9 MiB/s)
4509466 bytes read in 216 ms (19.9 MiB/s)
## Loading init Ramdisk from Legacy Image at 41080000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (uncompressed)
Data Size: 4509402 Bytes = 4.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
Booting using the fdt blob at 0x4fa00000
Loading Ramdisk to 49bb3000, end 49fffeda ... OK
reserving fdt memory region: addr=4fa00000 size=6c000
Loading Device Tree to 0000000049b44000, end 0000000049bb2fff ... OK
Starting kernel ...