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

Version management

Difference between version and

At line 55 changed one line
While it claims to be, the Fire3's GPIO is actually not compatible with the Raspberry Pi, notably the I²C bus is different. Most I²C software on the Pi uses pins 3 and 5, which are assigned to I²C __bus #1__, whereas on the Fire3 those two pins are assigned to __bus #0__.
While it claims to be, the Fire3's GPIO is actually not compatible with the [Raspberry Pi], notably the [I²C] bus is different. Most I²C software on the Pi uses pins 3 and 5, which are assigned to I²C __bus #1__, whereas on the Fire3 those two pins are assigned to __bus #0__.
At line 61 changed one line
Why FriendlyArm (who make the Fire3) and Orange Pi alter the locations of their I²C bus pins and still claim Raspberry Pi GPIO compatibility is a bit of a mystery. Sadly, on the Orange Pi there are no extant pins for I²C bus #1 at all. There may be some way of initialising a new bus in software and reassigning pins to be compatible with the Pi but that's beyond me (or my interest, frankly).
Why FriendlyArm (who make the Fire3) and [Orange Pi] alter the locations of their I²C bus pins and still claim [Raspberry Pi] [GPIO] compatibility is a bit of a mystery. Sadly, on the Orange Pi there are no extant pins for I²C bus #1 at all. There may be some way of initialising a new bus in software and reassigning pins to be compatible with the Pi but that's beyond me (or my interest, frankly).