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

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

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

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

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

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?

@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?

@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

@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.

I recompiled chirpstack gateway bridge as following the steps below:

export GOARCH=mipsle
export GOOS=linux
make build

root@OpenWrt:~# file /opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge

/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge: ELF 32-bit LSB executable, MIPS, MIPS32 version 1 (SYSV), statically linked, Go BuildID=VcvuifmDnNysO-WpZUz5/FGFca5Lt5vpptRtlLTBo/l2QuqgekGwKVygyjsXAL/6lmuYGmDGU2RDGrxxamU, stripped

The result is the same doesn't work on openwrt 19.07...

@tjoseph1 Thank you for your help. I was on a vacation sorry for late...

I replaced "/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge" with the file that you sent. But result is same, dont work and so no ram change(on openwrt 19.07)..
Do you have another idea to find the reason of this issue?