lgw connect () did not return success-UP Squared LoRA Edge IP68 (915Mhz)

gvnura

Hi,

I have followed the steps on a previous post ( https://forum.up-community.org/discussion/3920/solved-problem-with-bringing-lora-server-on-upsquared-edge-computer) to resolve the _lgw connect () did not return success _ issue but still I am getting the errors (OS- Ubuntu 18.04). I tried to reinstall the OS (downgrading to Ubuntu 16.04) now i am getting hardware errors. Please refer to the image attached

please help

DCleri

Hello @gvnura

That error is strange, but please do not use Ubuntu 16.04 anymore.

You should install Ubuntu 18.04 as per our procedure (including our kernel): https://github.com/up-board/up-community/wiki/Ubuntu_18.04
Then install the SPI ACPI override: https://github.com/up-board/up-community/wiki/Pinout_UP2#spi-ports

Then follow the procedure for the lora driver and packet forwarder but please review the configuration files and update to use the correct frequencies for the 915Mhz version:
https://github.com/AAEONAEU-SW/packet_forwarder/tree/master/lora_pkt_fwd

Editing the global_conf.json file

DCleri

also please use this as reference to update the global_conf.json for your specific location: https://github.com/TheThingsNetwork/gateway-conf

rogertsai(AAEON)

@gvnura
I share my test image with you for SPI to LoRa testing, click the link below to download the image file
2018-12-17-03-ip68gateway-img
Please unzip the image file and put the file to your USB drive, then use Clonezilla to restore the image
In Clonezilla, please choose "Expert mode" and enable "icds" and -k1 option. OS login password is 123456.

How to test
Open linux terminal and test the commands below

cd /opt/ttn-geteway/lora_gateway/util_spi_stress
./util_spi_stress

If LoRA & SPI is working properly, you will see the messages like below

If you want to test the GPIO430 to reset LoRa, try the command below

echo 430 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio430/direction
echo 1 > /sys/class/gpio/gpio430/value
echo 0 > /sys/class/gpio/gpio430/value

Next, just change the config file to 915Mhz frequency

gerfen

@DCleri @rogertsai(AAEON) I'm going to install Ubuntu on an AAEON AOIT-IP6801, Is Ubuntu 18.04 preferred over Ubuntu 20.04? Thanks!

gerfen

@DCleri @rogertsai @Pratik_Kushwaha

While following the directions to install Ubuntu 18.04, when I execute:

sudo apt-get autoremove --purge 'linux-.*generic'

I get the following error:

E: Aborting removal of the running kernel
dpkg: error processing package linux-image-5.4.0-77-generic (--remove):
 installed linux-image-5.4.0-77-generic package pre-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 linux-image-5.4.0-77-generic
Processing was halted because there were too many errors.

I'm not able add the AAEON kernel update and rebooting results in

Alert! /dev/mapper//ubuntu--vg-ubuntu--lv does not exist.  Dropping to a shell! 

I see the same behavior if I try to install Ubuntu 20.04 following the directions from the Wiki. I'm pretty much dead in the water at this point. I've successfully setup a AOIT-IP6801 in the past following the instructions for Ubuntu 16.04. Ideally, I would make the jump to Ubuntu 20.04.

Any advice on how to proceed?

rogertsai(AAEON)

@gerfen
Have you tried to reinstall your ubuntu OS with ISO below, and then follow the steps from UP Wiki
https://releases.ubuntu.com/bionic/ubuntu-18.04.5-desktop-amd64.iso
or 20.04.2
https://releases.ubuntu.com/20.04/ubuntu-20.04.2.0-desktop-amd64.iso

gerfen

@rogertsai(AAEON) I followed the instructions for Ubuntu 18.04 and Ubuntu 20.04 . I pretty much had the same issues for both distros. FWIW, using the instructions for Ubuntu 16.04 I was able to successfully get my gateway configured. Have the instructions for 18.04 and 20.04 been tested or just copied from 16.04 and modified? From my experience they do not work.

rogertsai(AAEON)

@gerfen

What the step you do when you execute the command below to remove all the generic installed kernel
sudo apt-get autoremove --purge 'linux-.*generic'

In general, you should hit the Y key to continue the operation and then choose as the answer when you see the message about kernel removal

BTW, what’s BIOS version you use?

gerfen

@rogertsai(AAEON) I'm just getting back around to trying to install Ubuntu 18.04. My BIOS version is

AIOT-IP6801 R1.3 (AP68AM13) (09/28/2018)

Note that I have screenshots from installing Ubuntu if those would be helpful. Here are my full logs from following the instruction in the Wiki:

*******************************:~$ sudo add-apt-repository ppa:aaeon-cm/5.4-upboard
 UP kernel 5.4.0-1 support
 More info: https://launchpad.net/~aaeon-cm/+archive/ubuntu/5.4-upboard
Press [ENTER] to continue or Ctrl-c to cancel adding it.

Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://ppa.launchpad.net/aaeon-cm/5.4-upboard/ubuntu bionic InRelease [15.9 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:6 http://ppa.launchpad.net/aaeon-cm/5.4-upboard/ubuntu bionic/main amd64 Packages [6008 B]
Get:7 http://ppa.launchpad.net/aaeon-cm/5.4-upboard/ubuntu bionic/main Translation-en [3944 B]
Fetched 278 kB in 2s (127 kB/s)
Reading package lists... Done
gerfen@evolution_outdoor_2:~$


*******************************:~$ sudo apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Hit:3 http://ppa.launchpad.net/aaeon-cm/5.4-upboard/ubuntu bionic InRelease
Get:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Fetched 252 kB in 1s (190 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
65 packages can be upgraded. Run 'apt list --upgradable' to see them.


*******************************:~$ sudo apt-get autoremove --purge 'linux-.*generic'

update-initramfs: deferring update (trigger activated)
Removing intel-microcode (3.20210608.0ubuntu0.18.04.1) ...
update-initramfs: deferring update (trigger activated)
Removing iucode-tool (2.3.1-1) ...
Removing thermald (1.7.0-5ubuntu5) ...
Removing libdbus-glib-1-2:amd64 (0.110-2) ...
Removing linux-headers-generic (4.15.0.147.134) ...
Removing linux-headers-4.15.0-147-generic (4.15.0-147.151) ...
Removing linux-headers-4.15.0-147 (4.15.0-147.151) ...
Removing linux-modules-extra-4.15.0-147-generic (4.15.0-147.151) ...
Removing linux-image-4.15.0-147-generic (4.15.0-147.151) …

E: Aborting removal of the running kernel
dpkg: error processing package linux-image-4.15.0-147-generic (--remove):
 installed linux-image-4.15.0-147-generic package pre-removal script subprocess returned error exit status 1
dpkg: linux-modules-4.15.0-147-generic: dependency problems, but removing anyway as you requested:
 linux-image-4.15.0-147-generic depends on linux-modules-4.15.0-147-generic.

Removing linux-modules-4.15.0-147-generic (4.15.0-147.151) ...
Errors were encountered while processing:
 linux-image-4.15.0-147-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)


*******************************:~$ sudo apt-get install linux-generic-hwe-18.04-5.4-upboard
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 linux-generic-hwe-18.04-5.4-upboard : Depends: linux-image-generic-hwe-18.04-5.4-upboard (= 5.4.0.1.5000~upboard2) but it is not going to be installed
                                       Depends: linux-headers-generic-hwe-18.04-5.4-upboard (= 5.4.0.1.5000~upboard2) but it is not going to be installed
 linux-image-4.15.0-147-generic : Depends: linux-modules-4.15.0-147-generic but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

DCleri

You should select No on the question "Abort Kernel Removal" otherwise it won't work

gerfen

@DCleri That was indeed the issue. It would be very helpful if the WiKi instructions (both Ubuntu 18.04 and Ubuntu 20.04) included this piece of information. That would have saved me many hours of banging my head against a wall.

Also it might be a good idea to include a step for running the spi_enable scripts for folks trying to use SPI.

Thanks!

DCleri

Thanks @gerfen for the suggestions, we will make it more clear in our wiki to avoid such problems in the future.

About the spi_enable, we already provide steps in our wiki but, as the acpi override are board specific, we include the instructions in the pinout page of each board, instead of the generic Ubuntu installation page.

Please check out the spi_enable for UP Squared: https://github.com/up-board/up-community/wiki/Pinout_UP2#spi-ports