installing an ipk package and incompatible with the architecture error

optech

@tjoseph1 Thank you again for your help.

I compiled the hello world go app as following...:

export GOARCH=mipsle
export GOOS=linux
export GOMIPS=softfloat
go build hello.go

if i dont use "GOMIPS=softfloat", it works on openWRT 18.06 but dont work on openWRT 19.07 as giving following error:

root@OpenWrt:~# ./hello
Illegal instruction

with "GOMIPS=softfloat" option, it works on openWRT 19.07..

But after seeing that, i compiled chirpstack-gateway-bridge app with same options. But it still doesnt work on openWRT 19.07

chirpstack-gateway-bridge$ export GOARCH=mipsle
chirpstack-gateway-bridge$ export GOOS=linux
chirpstack-gateway-bridge$ export GOMIPS=softfloat
chirpstack-gateway-bridge$ make build

i feel near to solution but i have no idea for now.

optech

@optech by the way, i first setup the chirpstack-gateway-bridge ipk file which you sent before, then i replace the exe in opt/chirpstack-gateway-bridge with i compiled. then it didnt work on openwrt 19.07

crispyoz

@optech Have you checked that the make file is not redefining those exports?

crispyoz

This post is deleted!

tjoseph1

@optech

In the Makefile, the "build" option has parameters:
<<<
.PHONY: build clean test package serve run-compose-test
VERSION := $(shell git describe --always |sed -e "s/^v//")

build:
@echo "Compiling source"
@mkdir -p build
GOOS=linux GOARCH=mipsle GOMIPS=softfloat go build $(GO_EXTRA_BUILD_ARGS) -ldflags "-s -w -X main.version=$(VERSION)" -o build/chirpstack-gateway-bridge cmd/chirpstack-gateway-bridge/main.go
<<<

Is that how you compile?

Try running the "chirpstack .." exe from Omega2's command line with -h or --help option under stock 19.07.
If that runs, then try running the exe under the custom build.

Thanks.

optech

@tjoseph1 @crispyoz

When I check makefile i see:

.PHONY: build clean test package serve run-compose-test
VERSION := $(shell git describe --always |sed -e "s/^v//")

build:
	@echo "Compiling source"
	@mkdir -p build
	go build $(GO_EXTRA_BUILD_ARGS) -ldflags "-s -w -X main.version=$(VERSION)" -o build/chirpstack-gateway-bridge cmd/chirpstack-gateway-bridge/main.go

so makefile has no redefining options for "GOOS=linux GOARCH=mipsle GOMIPS=softfloat".

when i tried stock omega 19.07 binary, it was didnt work. but after you told me about softfloat option, i tried to change some options while custom compilation of openwrt by make menuconfig. I set softfloat by default from advanced compile options and i set MIPS FPU emulator enable. after making this custom binary for openwrt, even the first chirpstack-gateway-bridge exe, that you sent me before, works well in my custom openwrt compilation I guess this way is ok, right? can i will have side effects of it for future with another app? Thank you for your all support

But i couldnt find how i can make ipk file after chirpstack-gateway-bridge compilation.. Could you inform me about it how i make ipk packages?

crispyoz

@optech If you have set chirpstack in make menuconfig to M the ipk will be in <source>/staging_dir/packages/ramips

I would be interested to know if transferring the package to your earlier 19 system gives you the same error as I suspect this may be an issue related to the included libs.

optech

@crispyoz

There is no chirpstack option in "make menuconfig" in openwrt, maybe i couldnt see

i think go lang uses mips float point but i guess there is no hardware fpu in MT7688, so instructions doesnt work when go compile with default GOMIPS option. Then when i make chances on make menuconfig about float point options while compiling custom openwrt, it will be ok even go uses float point option.. What do you think about this explanation?

optech

i compiled chirpstack-packet-multiplexer application. But i couldnt make ipk file. So i duplicated chirpstack-gateway-bridge files on working system, then i replaced with chirpstack-packet-multiplexer files and edited init.d script

Could you inform me about how can i make ipk packages after compilation of an application?

crispyoz

@optech ok sorry I thought you had added the package to menuconfig and were compiling that way. I haven't been following closely as @tjoseph1 has been doing a lot to help out.

Making an ipk is not well documented, well not that I found when I was trying to learn how to manually make them. So I made a script to create the ipk for my custom package I build outside of the build system. I need to clean out some proprietary stuff out of my script then I will post it here in a short time.

optech

@crispyoz thank you very much. i am looking forward your packaging script...

crispyoz

#!/bin/sh

File: make_ipk.sh

Author: Chris

Created on 22 September 2019, 01:40:00

while getopts "v:d:" opt;
do
case "${opt}" in
v) version=${OPTARG};;
d) directory=${OPTARG};;
esac
done

if [ -z "$version" ]
then
echo "Version not set, use parameter -v <version>"
exit 1;
fi

if [ -z "$directory" ]
then
echo "Output path for ipk not set, use parameter -d <path>"
exit 1;
fi

mkdir $directory
cd $directory
mkdir -p usr/sbin
mkdir -p etc/myapp/scripts
mkdir -p etc/myapp/certs
mkdir -p etc/opkg

cp -rf /home/chris/NetBeansProjects/MyApp/dist/Release/GNU_OpenWRT-Linux/myappd usr/sbin/
cp -rf /home/chris/source/files/www www
cp -rf /home/chris/source/files/etc/myapp/site etc/myapp
cp -rf /home/chris/source/files/etc/myapp/scripts etc/myapp
cp -rf /home/chris/source/files/etc/myapp/certs etc/myapp
cp -rf /home/chris/source/files/etc/myapp/crontab-input etc/myapp

#cp /home/chris/update_feeds.sh etc/myapp/scripts

copy certificates

#cp /home/chris/source/files/etc/myapp/certs/ca.crt etc/myapp/certs
#cp /home/chris/source/files/etc/myapp/certs/client.crt etc/myapp/certs
#cp /home/chris/source/files/etc/myapp/certs/client.key etc/myapp/certs

mkdir CONTROL

echo "Package: myapp" >> CONTROL/control
echo "Version: $version" >> CONTROL/control
echo "Description: MyApp" >> CONTROL/control
echo "Section: extras" >> CONTROL/control
echo "Priority: optional" >> CONTROL/control
echo "Maintainer: admin@myapp.com" >> CONTROL/control
echo "License: CLOSED" >> CONTROL/control
echo "Architecture: mipsel_24kc" >> CONTROL/control
echo "OE: myappd" >> CONTROL/control
echo "Homepage: www.myapp.com" >> CONTROL/control
echo "Depends: libc, libuci, libubus, libubox, libsqlite3, libgcrypt, libgnutls" >> CONTROL/control

echo "#!/bin/sh" >> CONTROL/preinst
echo "#Add your scripts here" >> CONTROL/preinst
echo "" >> CONTROL/preinst

chmod +x CONTROL/preinst

echo "#!/bin/sh" >> CONTROL/postinst
echo "#Add your scripts here" >> CONTROL/postinst
echo "cwv=$(/usr/sbin/myappd -n)" >> CONTROL/postinst
echo "" >> CONTROL/postinst
echo "uci set myapp.@main[0].version=$cwv" >> CONTROL/postinst
echo "uci set myapp.@main[0].version=$(myappd -n)" >> CONTROL/postinst
echo "ls=$(uci get myapp.@license[0].data_collection)" >> CONTROL/postinst
echo "uci commit myapp" >> CONTROL/postinst
echo "crontab /etc/myapp/crontab-input" >> CONTROL/postinst
echo "rm /etc/myapp/crontab-input" >> CONTROL/postinst
echo "/etc/init.d/cron restart" >> CONTROL/postinst
echo "" >> CONTROL/postinst

echo "/etc/myapp/scripts/update_banner.sh" >> CONTROL/postinst
#echo "/etc/myapp/scripts/update_feeds.sh" >> CONTROL/postinst
echo "/etc/init.d/myappd restart" >> CONTROL/postinst

chmod +x CONTROL/postinst

echo "#!/bin/sh" >> CONTROL/prerm
echo "#Add your scripts here" >> CONTROL/prerm
echo "" >> CONTROL/prerm
chmod +x CONTROL/prerm

echo "#!/bin/sh" >> CONTROL/postrm
echo "#Add your scripts here" >> CONTROL/postrm
echo "" >> CONTROL/postrm
chmod +x CONTROL/postrm

~/source/scripts/ipkg-build ./

Now we can create the repository files

#*********************************************************************************************************
export PATH="$PATH:/home/chris/source/staging_dir/host/bin"
echo "MyApp repository: private key XXXXXXXXXXXXX" >> myapp.key
echo "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" >> myapp.key
#**********************************************************************************************************

mkdir repo
mv *.ipk repo
cd repo
~/source/scripts/ipkg-make-index.sh . 2>/dev/null > Packages.manifest
grep -vE '^(Maintainer|LicenseFiles|Source|Require)' Packages.manifest > Packages
gzip -9nc Packages > Packages.gz
usign -S -m Packages -s ../myapp.key

rm Packages
rm Packages.manifest
rm ../myapp.key

crispyoz

@optech 2 points to note.

The script uses the build system scripts to create the final package, this script just makes it easy for me to copy the required files into the correct directory structure. You can see towards the end of the scripts ~/source/scripts/ipkg-build and ~/source/scripts/ipkg-make-index.sh
You need to sign your packages, so if you look at the section towards the end with ********************* this I have masked out my public and private keys. You need to create these using usign package. You can install usign like so:

git clone https://git.openwrt.org/project/usign.git
cd usign
cmake .
make
sudo make install

Then use usign to create your keys. I'll leave you to look at that.

optech

@crispyoz even simplifying script looks complex thanks again i will try to use it

crispyoz

@optech Just step line by line through the script, it's not that complex, it's just copying files to our packing folder in the structure we need the files placed on the target system. Then running a few command to create the files required for an opkg repository and signing them using usign.

The structure of the directories is the key to the building of the package. The cool parts are in the CONTROL directory where there are 4 files that get executed depending on what opkg is doing, ie before installing your package (CONTROL/preinst), after installing your package (CONTROL/postinst), before removing your package (CONTROL/prerm) and after removing your package (CONTROL/postrm)

The final ipk will be in the "repo" directory

tjoseph1

@optech
These parameters are added by me
GOOS=linux GOARCH=mipsle GOMIPS=softfloat \

Equivalent to:

$ CC= CXX=
etc. that we use while compiling .c, .cpp

As you have rightly pointed out, the following was the original command line:
go build $(GO_EXTRA_BUILD_ARGS) -ldflags "-s -w -X main.version=$(VERSION)" -o build/chirpstack-gateway-bridge cmd/chirpstack-gateway-bridge/main.go

By stock 19.07, I meant the "19.07 binary image" that we can download from openwrt download area, not the image that we build, even if we are using the build config + the same compiler/tools as openwrt used.

In my observation, the hello_world and the chirpstack-gateway-bridge will work with stock 19.07.7 if the softfloat option is used; not sure about other 19.07s.

Thanks.

optech

@tjoseph1 and @crispyoz, Thank you for all of your support. All information which you gave me was so useful for me.

crispyoz

@optech we're always happy to help, I hope you can complete your work successfully.

tjoseph1

@optech
Happy to know that the intial phase is over.

So, what is next?

https://github.com/OnionIoT/omega2-lmic-lorawan
-interfacing to Omega2 through SPI-I2C bridge,library supports SX1276/8)

https://www.seeedstudio.com/LoRa-E5-Wireless-Module-p-4745.html
-Cortex-M4+SX126X(ST Micro), Comes with factory loaded AT command fw,
supports ClassA/B/C, has built-in UART/ADC/I2C/GPIO.. & programmamable using ST CubeMX)

Or any other? Curious to know which is your pick..
(I was not aware of that this chirpy thing existed .. !!)

Thanks

Goddard152

This post is deleted!