maurddz wrote:
All is good now. I installed Armbian and now I see the full 1024 MB of ram. My OLED screen doesn't work anymore so I am figuring that out, any suggestions?
Sorry I cant help here... I also got a normal Neo (not Neo2) with OLED-Hat, but the display will only run with a (in my opinion) kernel-module/software which isnt available in armbian.
The OLED-Hat-Wiki at
http://wiki.friendlyarm.com/wiki/index.php/NanoHat_OLEDtell us to use a customized ROM-image with
xxx-OLED-xxx (Section
Install Software)
There must be something "special" inside .
The
/etc/rc.local is starting
/usr/local/bin/oled-startwhich then is starting
/root/NanoHatOLED/NanoHatOLEDMaybe it will be only a copy of the directory
/root/NanoHatOLED/ and
/usr/local/bin/oled-startand starting
/usr/local/bin/oled-start in the
/etc/rc.local of armbian?
[EDIT]I did try it - but it didnt work

I gziped NanoHatOLED and copied and extracted it,
I copied
-
/usr/local/bin/oled-start-
/usr/local/bin/gpio-
/root/NanoHatOLED/NanoHatOLEDI installed WiringNpi in /root via the instructions at
https://github.com/friendlyarm/WiringNPAnd checked in the OLED-Image which hardware has to be enabled:
I2C0, I2C1, I2C2, SPI0
But after a reboot the /System/Hardwaretoogle in armbian-config couldnt start up because of
ls: sed: -e expression #1, char 8: unterminated `s' command
sed: -e expression #1, char 13: unterminated `s' command
cannot access '/boot/dtb/overlay/Binary': No such file or directory
ls: cannot access 'file': No such file or directory
ls: cannot access '(standard': No such file or directory
ls: cannot access 'input)': No such file or directory
ls: cannot access 'matches*.dtbo': No such file or directory
Maybe the WiringNP-Installation did broke armbian
