docker.io/mgos/esp32-build:4.2-r1-dbg1then building again. It builds Ok, but when I OTA the update, it still shows
esp32_main.c:65 ESP-IDF 4.2-r1in the boot. I’ll DM you the
build.logto see if you can see what’s going wrong.
m using to setup a relay to be off at start ->GPIO.write(4,0);
I've had mos running on a Raspberry Pi for a couple of years using the above, but I've just tried to install on a new build and I'm getting errors as below:
go version go1.13.4 linux/arm GOOS= GOARCH= CC= CXX= \ /usr/local/go/bin/go build -mod=vendor -tags '' -ldflags '-s -w ''' -o mos github.com/mongoose-os/mos/cli # pkg-config --cflags -- libftdi1 Package libftdi1 was not found in the pkg-config search path. Perhaps you should add the directory containing `libftdi1.pc' to the PKG_CONFIG_PATH environment variable No package 'libftdi1' found pkg-config: exit status 1 Makefile:93: recipe for target 'build-mos' failed make: *** [build-mos] Error 2
Anyone got any suggestions what might be causing this?
sudo apt-get install libftdi1
libftdi1 is already the newest version (0.20-4). libftdi1 set to manually installed.
ldconfigdoes the trick of providing the needed info. I read you manually installed it, try running ldconfig as root.
env | grep PKG_CONFIG_PATHto see what the paths are
which lifftdi1to see where that is installed. compare and contrast the base directory of lifftdi1 to the PKG_CONFIG_PATH
go version go1.15.7 linux/arm GOOS= GOARCH= CC= CXX= \ /usr/local/go/bin/go build -mod=vendor -tags '' -ldflags '-s -w ''' -o mos github.com/mongoose-os/mos/cli # runtime /usr/local/go/src/runtime/mgclarge.go:142:26: mheap_.treapalloc undefined (type mheap has no field or method treapalloc) /usr/local/go/src/runtime/mgclarge.go:193:8: mheap_.treapalloc undefined (type mheap has no field or method treapalloc) /usr/local/go/src/runtime/mgclarge.go:249:9: undefined: scavengeTreapNode /usr/local/go/src/runtime/signal_unix.go:525:5: crashing redeclared in this block previous declaration at /usr/local/go/src/runtime/signal_sighandler.go:15:5 /usr/local/go/src/runtime/signal_unix.go:530:5: testSigtrap redeclared in this block previous declaration at /usr/local/go/src/runtime/signal_sighandler.go:20:5 /usr/local/go/src/runtime/signal_unix.go:544:6: sighandler redeclared in this block previous declaration at /usr/local/go/src/runtime/signal_sighandler.go:33:69 /usr/local/go/src/runtime/unaligned2.go:12:6: readUnaligned32 redeclared in this block previous declaration at /usr/local/go/src/runtime/alg.go:374:40 /usr/local/go/src/runtime/unaligned2.go:17:6: readUnaligned64 redeclared in this block previous declaration at /usr/local/go/src/runtime/alg.go:382:40 Makefile:93: recipe for target 'build-mos' failed make: *** [build-mos] Error 2
Hi, I am working around an project with esp8266 and pi loaded ubuntu as host. I have flash the firmware to esp and connected to n/w. The logs shows it first try to connect with n/w and get failed with error code 3 or 202. After 2/3 second again try to connect with n/w and got connected. And shows the ip as well and also on network device, the esp shows up in connected device list. After that I ran
mos call Sys.GetInfo it shows :
}' while the network device still shows it as connected
Any idea what could be the issue ?