Guru
Joined: 17/05/2016
Location: United StatesPosts: 3751
| Posted: 01:55pm 01 Apr 2020 |
I was getting "bad gpio" messages on my pi-ZW when starting "sudo ./mmbasic". I loaded the latest (I think) pi-cromite from this thread:
2019-05-05_211935_mmbasic.zip
I'm still getting "bad gpio" and when I enter (no prompt) "print date$", I get a pigpio diagnostic message. "sudo apt-get upgrade pigpio" says I have the latest version.
I haven't used pi-cromite in a while; what am I doing wrong?
[code]
:~ $ sudo ./mmbasic
2020-04-01 10:50:23 gpioWrite: bad gpio (110)
2020-04-01 10:50:23 gpioSetMode: bad gpio (110)
2020-04-01 10:50:23 gpioSetMode: bad gpio (110)
2020-04-01 10:50:23 gpioWrite: bad gpio (110)
2020-04-01 10:50:23 gpioSetMode: bad gpio (110)
2020-04-01 10:50:23 gpioWrite: bad gpio (110)
2020-04-01 10:50:23 gpioSetMode: bad gpio (110)
2020-04-01 10:50:23 gpioWrite: bad gpio (110)
2020-04-01 10:50:23 gpioSetMode: bad gpio (110)
2020-04-01 10:50:23 gpioSetMode: bad gpio (110)
2020-04-01 10:50:23 gpioSetMode: bad gpio (110)
2020-04-01 10:50:23 gpioSetPullUpDown: bad gpio (110)
2020-04-01 10:50:23 gpioSetMode: bad gpio (110)
print date$
^C2020-04-01 10:50:42 sigHandler: Unhandled signal 2, terminating
#####################################################
pigpio version=64 internals=200
micros=1 allocMode=1 dmaInitCbs=2 DMARestarts=1
samples 1 maxSamples 1300 maxEmit 0 emitFrags 0
cbTicks 71765, cbCalls 8023
pipe: good 0, short 0, would block 0
alertTicks 6384, lateTicks 0, moreToDo 1637
7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11 294 12183 102032 422623 98755 13439 523 30 3 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 18
#####################################################
[/code]
PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on FOTS