This page (revision-9) was last changed on 2021-03-20 08:24 by Murray Altheim

This page was created on 2021-03-19 04:37 by Murray Altheim

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
9 2021-03-20 08:24 5 KB Murray Altheim to previous
8 2021-03-20 08:11 5 KB Murray Altheim to previous | to last
7 2021-03-20 07:54 4 KB Murray Altheim to previous | to last
6 2021-03-20 07:48 3 KB Murray Altheim to previous | to last
5 2021-03-19 05:05 3 KB Murray Altheim to previous | to last
4 2021-03-19 04:56 3 KB Murray Altheim to previous | to last
3 2021-03-19 04:49 2 KB Murray Altheim to previous | to last
2 2021-03-19 04:47 2 KB Murray Altheim to previous | to last
1 2021-03-19 04:37 1 KB Murray Altheim to last

Page References

Incoming links Outgoing links
Nano Pi Fire 3
NanoPiFire3

Version management

Difference between version and

At line 19 added one line
! Raspberry Pi Compatibility
At line 21 added 2 lines
The GPIO pins are configured differently to the Raspberry Pi so that Pi hats and devices that connect directly to the GPIO pins won't necessarily work (notably I2C devices). This can be worked around, see below under ''Fire3 GPIO Pinout''.
At line 56 added one line
On a Pi pins 3 and 5 are part of the I2C bus 1, whereas on the Fire3 they are assigned to bus 0 (why?!). __I2C Bus 1's SDA and SCL pins are pins 27 and 28 respectively__, so if you get your 3.3v and ground from somewhere on the GPIO bus and SDA and SCL from pins 27 and 28 you can use Pi I2C devices without resorting to altering Python library code (as most seem hard-coded on bus 1, a generally safe assumption). Why NanoPi and Orange Pi alter the locations of their I2C bus pins and still claim Raspberry Pi GPIO compatibility is a bit of a mystery.
At line 58 added one line
This page (revision-9) was last changed on 2021-03-20 08:24 by Murray AltheimTop