Thunderborg not found
Forums:
After I installed an OLED display I got frequent VNC break downs when running the Monsterborg.
I suspected due to not sufficient power, I therefore deinstalled the display, no I can't connect to the
Thunderborg:
Loading ThunderBorg on bus 1, address 15 Missing ThunderBorg at 15 ThunderBorg was not found Are you sure your ThunderBorg is properly attached, the correct address is used, and the I2C drivers are running? Scanning I²C bus #1 No ThunderBorg boards found, is bus #1 correct (should be 0 for Rev 1, 1 for Rev 2) No ThunderBorg found, check you are attached :)
The I2c is enabled but sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
and ls /dev
autofs loop3 ram14 tty12 tty37 tty61 vcsa3 block loop4 ram15 tty13 tty38 tty62 vcsa4 btrfs-control loop5 ram2 tty14 tty39 tty63 vcsa5 bus loop6 ram3 tty15 tty4 tty7 vcsa6 cachefiles loop7 ram4 tty16 tty40 tty8 vcsa7 char loop8 ram5 tty17 tty41 tty9 vcsm-cma console loop9 ram6 tty18 tty42 ttyAMA0 vcsu cuse loop-control ram7 tty19 tty43 ttyprintk vcsu1 disk mapper ram8 tty2 tty44 ttyS0 vcsu2 dma_heap media0 ram9 tty20 tty45 uhid vcsu3 fb0 media1 random tty21 tty46 uinput vcsu4 fd mem raw tty22 tty47 urandom vcsu5 full mmcblk0 rfkill tty23 tty48 v4l vcsu6 fuse mmcblk0p1 serial0 tty24 tty49 vchiq vcsu7 gpiochip0 mmcblk0p2 serial1 tty25 tty5 vcio vhci gpiochip1 mqueue shm tty26 tty50 vc-mem video0 gpiochip2 net snd tty27 tty51 vcs video10 gpiomem null spidev0.0 tty28 tty52 vcs1 video11 hwrng ppp spidev0.1 tty29 tty53 vcs2 video12 i2c-1 ptmx stderr tty3 tty54 vcs3 video13 initctl pts stdin tty30 tty55 vcs4 video14 input ram0 stdout tty31 tty56 vcs5 video15 kmsg ram1 tty tty32 tty57 vcs6 video16 log ram10 tty0 tty33 tty58 vcs7 video18 loop0 ram11 tty1 tty34 tty59 vcsa watchdog loop1 ram12 tty10 tty35 tty6 vcsa1 watchdog0 loop2 ram13 tty11 tty36 tty60 vcsa2 zero
I tried also cd ~/thunderborg ./install.sh
Now I tried to check the GPIO pins with wiringPI
gpio readall +-----+-----+---------+------+---+---Pi 3B--+---+------+---------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | | | 3.3v | | | 1 || 2 | | | 5v | | | | 2 | 8 | SDA.1 | ALT0 | 0 | 3 || 4 | | | 5v | | | | 3 | 9 | SCL.1 | ALT0 | 0 | 5 || 6 | | | 0v | | | | 4 | 7 | GPIO. 7 | IN | 0 | 7 || 8 | 1 | ALT5 | TxD | 15 | 14 | | | | 0v | | | 9 || 10 | 1 | ALT5 | RxD | 16 | 15 | | 17 | 0 | GPIO. 0 | IN | 0 | 11 || 12 | 0 | IN | GPIO. 1 | 1 | 18 | | 27 | 2 | GPIO. 2 | IN | 0 | 13 || 14 | | | 0v | | | | 22 | 3 | GPIO. 3 | IN | 0 | 15 || 16 | 0 | IN | GPIO. 4 | 4 | 23 | | | | 3.3v | | | 17 || 18 | 0 | IN | GPIO. 5 | 5 | 24 | | 10 | 12 | MOSI | ALT0 | 0 | 19 || 20 | | | 0v | | | | 9 | 13 | MISO | ALT0 | 0 | 21 || 22 | 0 | IN | GPIO. 6 | 6 | 25 | | 11 | 14 | SCLK | ALT0 | 0 | 23 || 24 | 1 | OUT | CE0 | 10 | 8 | | | | 0v | | | 25 || 26 | 1 | OUT | CE1 | 11 | 7 | | 0 | 30 | SDA.0 | IN | 0 | 27 || 28 | 0 | IN | SCL.0 | 31 | 1 | | 5 | 21 | GPIO.21 | IN | 1 | 29 || 30 | | | 0v | | | | 6 | 22 | GPIO.22 | IN | 1 | 31 || 32 | 0 | IN | GPIO.26 | 26 | 12 | | 13 | 23 | GPIO.23 | IN | 0 | 33 || 34 | | | 0v | | | | 19 | 24 | GPIO.24 | IN | 0 | 35 || 36 | 0 | IN | GPIO.27 | 27 | 16 | | 26 | 25 | GPIO.25 | IN | 0 | 37 || 38 | 0 | IN | GPIO.28 | 28 | 20 | | | | 0v | | | 39 || 40 | 0 | IN | GPIO.29 | 29 | 21 | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | B
but I'm not able to get the pintest running ????
~/wiringPi/gpio/pintest bash: /home/pi/wiringPi/gpio/pintest: No such file or directory
what do I do wrong?
Any advice?
Thanks in advance Peter
piborg
Fri, 05/05/2023 - 11:23
Permalink
WiringPi pintest
I think the last step didn't work because the 'W' in WiringPi needs to be upper case :)
Download and build the WiringPi code:
After it has built run the GPIO pin tester:
Do the LEDs on the ThunderBorg turn on when you turn on the power?
Devil p
Fri, 05/05/2023 - 13:55
Permalink
GPIO failure
Hi Kimberly, thanks for fast reply (like always).
It's embarrissing, I tried different versions but yours worked,
with the Thunderborg detached it gives :
The 5 SPI pins 10:14: OK
The serial pins 15:16: OK
The I2C pins 8: 9: Pin 8 failure - expected 1, got 0
Pin 9 failure - expected 1, got 0
2 faults detected
Does not look good, can I do anything about it ?
The LED turn on when I power the Monster.
Thanks and regards Peter
piborg
Sat, 05/06/2023 - 11:46
Permalink
Failed I2C pins
Unfortunately it seems like the I2C pins were damaged on the Raspberry Pi itself, so it will need to be replaced :(
My best guess is that the I2C pins were connected to 5V levels at some point with the OLED attached. The GPIO pins on the Pi are designed for 3.3V levels and are easily damaged when driven to higher voltages.
The good news is that the ThunderBorg is probably fine.
Devil p
Sat, 05/06/2023 - 15:06
Permalink
Thanks for your reply. I
Thanks for your reply. I replaced the RPi and got the Monster driving again, also
the VPN break downs seem to be fixed. :-))
The display looked really nice on the Monster but I won't try it again :-(((
Thanks again for your help
Regards Peter