mirror of
https://github.com/easytarget/MQ-Pro-IO.git
synced 2025-09-11 17:55:52 +01:00
Improve support for custom device trees when kernel updates are received * Modified make-trees.sh so that it builds for all installed kernels. * A new script flash-latest.sh that copies the resulting .dtb files into the /etc/flash-kernel/dtbs/ override folder. The build-trees README is updated for this, and shows how to configure flash-kernel to use the custom .dtbs. Kernel upgrade should now go: [after a new kernel upgrade is installed] * Upgrade source: cd source && apt source linux-riscv * Build dtb's: cd build-trees &&; ./make_dtbs.sh * Install device tree via softlinks ./flash_latest.sh * Reboot
50 lines
3.0 KiB
Markdown
50 lines
3.0 KiB
Markdown
## `list-pins.py`
|
|
This is a tool that displays a ascii-art 'map' of the current pinmux assignments on the GPIO header
|
|
|
|
To run the pin list tool you need to be in the tools directory, then run:
|
|
```console
|
|
$ python3 list-pins.py MangoPi-MQ-Pro
|
|
```
|
|
* The script requires root acces (via sudo) to read the pin maps.
|
|
* Running the script produces the same map I use in this documentation.
|
|
* The data used to assemble the `.gpio` map files identifies which interface a pin is attached to, but not it's specific function for the interface.
|
|
* eg it can say 'pinX and pinY are mapped to UART2', but cannot identify which pin is the TX and which is the RX; a limitation of the data, my apologies..
|
|
* You therefore need to reference the [D1 pin mapping table](../reference/d1-pins.pdf) to get the exact functions for pins when running this for yourself.
|
|
|
|
|
|
### Default output
|
|
This is the default output for the MQ-Pro with the default device tree:
|
|
```
|
|
MangoPI MQ Pro GPIO header (dtb name: MangoPi MQ Pro)
|
|
|
|
Gpio Header:
|
|
func des pin pin des func
|
|
3v3 1 --o o-- 2 5v
|
|
free (205) PG13 3 --o o-- 4 5v
|
|
free (204) PG12 5 --o o-- 6 gnd
|
|
free (39) PB7 7 --o o-- 8 PB8 uart0 (2500000.serial:40)
|
|
gnd 9 --o o-- 10 PB9 uart0 (2500000.serial:41)
|
|
free (117) PD21 11 --o o-- 12 PB5 free (37)
|
|
free (118) PD22 13 --o o-- 14 gnd
|
|
free (32) PB0 15 --o o-- 16 PB1 free (33)
|
|
3v3 17 --o o-- 18 PD14 free (110)
|
|
free (108) PD12 19 --o o-- 20 gnd
|
|
free (109) PD13 21 --o o-- 22 PC1 free (65)
|
|
free (107) PD11 23 --o o-- 24 PD10 free (106)
|
|
gnd 25 --o o-- 26 PD15 free (111)
|
|
free (145) PE17 27 --o o-- 28 PE16 free (144)
|
|
free (42) PB10 29 --o o-- 30 gnd
|
|
free (43) PB11 31 --o o-- 32 PC0 free (64)
|
|
free (44) PB12 33 --o o-- 34 gnd
|
|
free (38) PB6 35 --o o-- 36 PB2 free (34)
|
|
free (113) PD17 37 --o o-- 38 PB3 free (35)
|
|
gnd 39 --o o-- 40 PB4 free (36)
|
|
|
|
Other gpio outputs of interest:
|
|
-- PD18: Blue Status Led - gpio (2000000.pinctrl:114)
|
|
|
|
Notes:
|
|
- I2C pins 3,5,27 and 28 (PG13, PG12, PE17 and PE16) have 10K pullup resistors to 3v3
|
|
- The Status LED (PD18) is common with the LED_PWM pin on the DSI/LVDS output
|
|
```
|