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 changed one line
! Raspberry Pi Compatibility
!! Raspberry Pi Compatibility
At line 21 changed one line
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''.
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 I²C devices). This can be worked around, see below under ''Fire3 GPIO Pinout''.
!! Specifications
At line 23 removed 2 lines
! Specifications
At line 30 changed one line
* Dynamic Voltage Control
* Dynamic Voltage Control
At line 37 changed 2 lines
* 5mm Pitch FPC Socket supports DVP Camera (8-Bit ITU-R BT 601-658 / I/O, I2C included)
* 54mm pitch Raspberry Pi compatible 40-Pin GPIO / PWM, I2C, UART, I/O, and SPI included
* 5mm Pitch FPC Socket supports DVP Camera (8-Bit ITU-R BT 601-658 / I/O, I²C included)
* 54mm pitch Raspberry Pi compatible 40-Pin GPIO / PWM, I²C, UART, I/O, and SPI included
At line 53 changed one line
! Fire3 GPIO Pinout
!! Fire3 GPIO Pinout
At line 55 changed 2 lines
While it claims to be, the Fire3's GPIO is actually not compatible with the Raspberry Pi, notably the I2C bus is different.
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.
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 57 added one line
On the Fire 3 __I²C Bus #1's SDA and SCL pins are pins 27 and 28 respectively__ rather than pins 3 and 5 as on the Raspberry Pi, 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 I²C devices without resorting to altering Python library code (as most seem hard-coded on bus 1, a generally safe assumption).
At line 59 changed 21 lines
|Pin#|Name|Pin#|Name
|1|%%red SYS_3.3V %%|2| __%%(color:purple) VDD_5V %%__
|3|__%%(color:#aaaaaa) I2C0_SDA %%__|4| __%%(color:purple) VDD_5V %%__
|5|__%%(color:#aaaaaa) I2C0_SCL %%__|6|__DGND__
|7|GPIOD8/PPM|8|UART3_TXD/GPIOD21
|9|__DGND__|10|UART3_RXD/GPIOD17
|11|UART4_TX/GPIOB29|12|GPIOD1/PWM0
|13|GPIOB30|14|__DGND__
|15|GPIOB31|16|GPIOC14/PWM2
|17|%%red SYS_3.3V %%|18|GPIOB27
|19|SPI0_MOSI/GPIOC31|20| __DGND__
|21|SPI0_MISO/GPIOD0|22|UART4_RX/GPIOB28
|23|SPI0_CLK/GPIOC29|24|SPI0_CS/GPIOC30
|25|__DGND__|26|GPIOB26
|__27__|__%%(color:#ff5500) I2C1_SDA%%__ | __28__ | __%%(color:#ff5500) I2C1_SCL %%__
|29|GPIOC8|30| __DGND__
|31|GPIOC7|32|GPIOC28
|33|GPIOC13/PWM1|34|__DGND__
|35|SPI2_MISO/GPIOC11|36|SPI2_CS/GPIOC10
|37|AliveGPIO3|38|SPI2_MOSI/GPIOC12
|39|__DGND__|40|SPI2_CLK/GPIOC9
%%information
__%%(font-size:large)Grumble...%%__ \\
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).
%%
At line 81 changed one line
! Links
||Pin # ||Name ||Pin # ||Name
||1| %%red SYS_3.3V %% ||2 | __%%(color:purple) VDD_5V %%__
||3|__%%(color:#aaaaaa) I²C0_SDA %%__ ||4| __%%(color:purple) VDD_5V %%__
||5|__%%(color:#aaaaaa) I²C0_SCL %%__ ||6| __DGND__
||7| GPIOD8/PPM ||8 | UART3_TXD/GPIOD21
||9| __DGND__ ||10 | UART3_RXD/GPIOD17
||11| UART4_TX/GPIOB29 ||12 | GPIOD1/PWM0
||13| GPIOB30 ||14 | __DGND__
||15| GPIOB31 ||16 | GPIOC14/PWM2
||17| %%red SYS_3.3V %% ||18 | GPIOB27
||19| SPI0_MOSI/GPIOC31 ||20 | __DGND__
||21| SPI0_MISO/GPIOD0 ||22 | UART4_RX/GPIOB28
||23| SPI0_CLK/GPIOC29 ||24 | SPI0_CS/GPIOC30
||25| __DGND__ ||26 | GPIOB26
||27| __%%(color:#ff5500) I²C1_SDA%%__ || 28 | __%%(color:#ff5500) I²C1_SCL %%__
||29| GPIOC8 ||30 | __DGND__
||31| GPIOC7 ||32 | GPIOC28
||33| GPIOC13/PWM1 ||34 | __DGND__
||35| SPI2_MISO/GPIOC11 ||36 | SPI2_CS/GPIOC10
||37| AliveGPIO3 ||38 | SPI2_MOSI/GPIOC12
||39| __DGND__ ||40 | SPI2_CLK/GPIOC9
At line 86 added 4 lines
!! Links
This page (revision-9) was last changed on 2021-03-20 08:24 by Murray AltheimTop