Odroid N2 & Airspy - Now running!

Thanks found the problem, seems to be working again :slight_smile:

@ wiedehopf Some attention to your FA 1090 build from source needs some attention, as well as air spy conf. I got this error trying to set up my next N2.
interactive.c:52:20: fatal error: curses.h: No such file or directory #include <curses.h> ^ compilation terminated. Makefile:45: recipe for target 'interactive.o' failed make[2]: *** [interactive.o] Error 1 make[2]: Leaving directory '/tmp/dump1090-fa' dh_auto_build: make -j1 RTLSDR=yes BLADERF=yes DUMP1090_VERSION=3.7.2 returned exit code 2 debian/rules:23: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/tmp/dump1090-fa' debian/rules:32: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 root@odroidn2:/tmp/dump1090-fa# sudo dpkg -i /tmp/dump1090-fa_*.deb dpkg: error: cannot access archive '/tmp/dump1090-fa_*.deb': No such file or directory root@odroidn2:/tmp/dump1090-fa#
I also noted a number of your scripts are referring to 3.7.1. When last used about 4 weeks ago, it was fine :frowning: I also noted some conflicting descriptions with airspy conf in the Odroid N2 and feeding page where you say i(requires dump1090-fa to be already installed) yet on your air spy git hub page, it states (The script will even install dump1090-fa for you, not piaware though) Piaware from source seems up to date and error free.

debian/rules build dh build --with=systemd dh_testdir dh_update_autotools_config dh_auto_configure debian/rules override_dh_auto_build make[1]: Entering directory '/tmp/dump1090-fa' dh_auto_build -- RTLSDR=yes BLADERF=yes DUMP1090_VERSION=3.7.2 make -j1 RTLSDR=yes BLADERF=yes DUMP1090_VERSION=3.7.2 make[2]: Entering directory '/tmp/dump1090-fa' cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION=\"3.7.2\" -DMODES_DUMP1090_VARIANT=\"dump1090-fa\" -DENABLE_RTLSDR -DENABLE_BLADERF -g -O2 -fdebug-prefix-map=/tmp/dump1090-fa=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -I/usr/include/ -I/usr/include/ -c dump1090.c -o dump1090.o cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION=\"3.7.2\" -DMODES_DUMP1090_VARIANT=\"dump1090-fa\" -DENABLE_RTLSDR -DENABLE_BLADERF -g -O2 -fdebug-prefix-map=/tmp/dump1090-fa=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -I/usr/include/ -I/usr/include/ -c anet.c -o anet.o cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION=\"3.7.2\" -DMODES_DUMP1090_VARIANT=\"dump1090-fa\" -DENABLE_RTLSDR -DENABLE_BLADERF -g -O2 -fdebug-prefix-map=/tmp/dump1090-fa=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -I/usr/include/ -I/usr/include/ -c interactive.c -o interactive.o interactive.c:52:20: fatal error: curses.h: No such file or directory #include <curses.h> ^ compilation terminated. Makefile:45: recipe for target 'interactive.o' failed make[2]: *** [interactive.o] Error 1 make[2]: Leaving directory '/tmp/dump1090-fa' dh_auto_build: make -j1 RTLSDR=yes BLADERF=yes DUMP1090_VERSION=3.7.2 returned exit code 2 debian/rules:23: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/tmp/dump1090-fa' debian/rules:32: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 root@odroidn2:/tmp/dump1090-fa# sudo dpkg -i /tmp/dump1090-fa_*.deb dpkg: error: cannot access archive '/tmp/dump1090-fa_*.deb': No such file or directory root@odroidn2:/tmp/dump1090-fa#

I’m going to go out on a limb here, but I think there is a clue nested in there. Did happen to forget any dependencies like libncurses5-dev for example?

ahhh I just cut and paste what ever is on the site, if it has been left out, not by the operator. Thats what the problem is, the script has got an issue

To which script are you referring? This thread has been all over the place, so impossible to ascertain from reading back what you are working with. Secondly, best to not rely on scripts because one will never learn to change their own flat tire. :slight_smile:

If I had to guess, that could be from Joe’s script…which is indeed out of date so far as Buster is concerned.

The one that failed was the 1090 fa from source right at the end,
``

sudo dpkg -i /tmp/dump1090-fa_*.deb

``
whilst one day I might have enough experience with linux to just fix it, not yet by a long way. Thats why you boffins amaze me with your banter :slight_smile:

root@odroidn2:~# sudo apt install piaware
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
piaware:armhf : Depends: tcllib:armhf but it is not installable
E: Unable to correct problems, you have held broken packages.
root@odroidn2:~#

In that case compile piaware as well.

Well that’s for the typical RPi installation, it can’t install dump1090-fa on non armhf architectures.

I’ve added the dependency for building dump1090-fa

You’ll have to compile piaware from source then instead of installing the repository version.
(It says right there in the guide. But i guess there is no need even attempt the apt install)

And it also says if it doesn’t work, use the source. Both the piaware and 1090 fa failed from the repository. BUT after formatting both emmc’s and following each step, ablet having to use the source feeds, both emmc’s have now successfully installed. So it must have been the emmc’s not properly prepared. All up and working. You possibly still need to sort out the wording, there is definitely a contradiction between your Odroid N2 & airspsy and the airspy.conf that will perplex someone with less knowledge than me, on what they are suppose to do. None of this has been having a go at you, only pointing out a possible problem that turns out a furphy which is good and that little contradiction. :slight_smile: