Rob Gillan

Hello, bit of a strange one here. Using Armbian 21.02.3 Bionic with Linux 5.10.21-sunxi on a NanoPi Neo Core. Using nmtui to set a static IP on the Ethernet interface and all is good. On reboot, a second interface is added (dhcp) and the static interface disabled. Any help at keeping a static IP that survives a restart would be very much appreciated, Cheers Rob

We resolved it with the module manufacturer and once done it simply popped up as soon as the USB was connected (using the default qualcomm module). Thanks for your responsiveness

Thanks for the prompt response, and digging I do see the qcserial module. When I plug in the device via USB its not showing up so I think I need to go digging and find out why (hopefully not a hardware issue). I plugged in a simple serial to USB converter and it appears as ttyUSB0 so don't expect it's an armbian issue (at least not yet)

Hello, Trying to compile the Qualcomm Gobi serial USB drivers for a Simcom wireless chip on a NanoPi Neo2 (sunxi64). I've loaded the kernel headers via armbian-config and typically this specific header file would be in drivers/usb/serial. We're using the pre-built image. Is there an easy way to get this into our kernel or do we have to embark on a full compile? Any help very much appreciated Rob

Hello, We've enabled pps-gpio in armbianEnv and will hopefully soon have our GPS/PPS source sync'ing the Neo2. We are also trying to have the Neo2 as a PPS generator when there is no local GPS/PPS connected and it's sync'd on the LAN from another Neo2 that has the GPS/PPS. To make all this work we'd like to be able to activate a PPS generator (output), along the lines of: https://github.com/jsln/pps-gen-gpio Think we understand the device-tree process well enough, but how (and where) would we put the driver code and have it compiled in and usable? Is this something that can be done on top of the nightly build we're using, or would we have to do this in the full build environment (obviously not our preference)? Any help very much appreciated. Rob

OK, digging through some other H3/SPI posts here, it seems that the device overlay for SPI needs to know what bus to enable, so putting the following line: param_spidev_spi_bus=0 in /boot/armbianEnv.txt and rebooting did the trick

and in /boot/armbianEnv.txt: root@nanopineo2:/boot/dtb/allwinner/overlay# cat /boot/armbianEnv.txt verbosity=1 console=both overlay_prefix=sun50i-h5 overlays=pps-gpio spi-spidev usbhost1 usbhost2 rootdev=UUID=75d8ed70-73a7-43cc-8b06-81f884b6b711 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u after armbian-config, and it looks like spi-spidev should be there.

Hello, Just started on the latest Neo2 Ubuntu (Armbian_5.34.171121_Nanopineo2_Ubuntu_xenial_next_4.13.14) as we were tired trying to get around the challenges of the Ubuntu Core provided by FriendlyARM. Have enabled SPI we think (armbian-config->system/hardware/spi-spidev) and rebooted, but even after full power cycle we don't see anything in /dev/spi*. Is there anything special/additional we need to do to get SPI working (which we know does from our Ubuntu Core build). Thanks Rob