random-mirrors/easytarget-MQ-Pro-IO
1
0
Fork 0
mirror of https://github.com/easytarget/MQ-Pro-IO.git synced 2025-09-11 17:55:52 +01:00
Code Issues Packages Projects Releases Wiki Activity
easytarget-MQ-Pro-IO/alt-trees
History
Owen Carter 520118f143
Update tooling for custom kernels (#6) 
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
2024-09-19 14:52:55 +02:00
..
hat
Update tooling for custom kernels (#6)
2024-09-19 14:52:55 +02:00
lora-hat
Update tooling for custom kernels (#6)
2024-09-19 14:52:55 +02:00
serial
Update tooling for custom kernels (#6)
2024-09-19 14:52:55 +02:00
spi-i2c
Update tooling for custom kernels (#6)
2024-09-19 14:52:55 +02:00
README.md
Update tooling for custom kernels (#6)
2024-09-19 14:52:55 +02:00

README.md

Alternate device tree Examples:

Each folder contains a .dts file and a README showing the GPIO pin mappings.

Use

Copy the desired .dts file(s) to the build-trees folder and follow the readme there to build the device-tree binaries.

There are instructions at the end of that document on how to make this permanent across reboots and kernel upgrades, some example flash-kernel database entries are given below for convenience.

Caveat

The issue with using these trees is that if the upstream device tree or includes is modified you need to manually rebuild these trees.

EG any changes to the upstream sun20i-d1-mangopi-mq-pro.dts source needs to be detected and applied too. You need to examine file histories to do this.

  • Fortunately this should not be an issue in practice; the kernel should remain very stable going forward. Ubuntu 24.04.1 is a LTS release..

HAT

Emulates a standard PI hat pinout

  • 1x SPI
  • 2x I2C
  • Console UART only
  • 16 unassigned GPIO pins

LoRa HAT

Expanded HAT pinout for my LoRa hat use

  • 1x SPI
  • 2x I2C
  • 1x UART (plus the console uart)
  • 4x PWM
  • 11 unassigned GPIO pins

SPI and I2C

SPI plus I2C interfaces

  • 1x SPI
  • 4x I2C
  • 3x UART (plus the console uart)
  • 6 unassigned GPIO pins

Serial

Four UART interfaces

  • 4x UART (plus the console uart)
    • UART3 has RTC/CTS pins available too
  • 2x I2C
  • 12 unassigned GPIO pins

Example /etc/flash-kernel/db entries

# Custom kernels

Machine: MQpro HAT
Kernel-Flavors: any
DTB-Id: custom/mqpro-hat.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.uboot-generic
Required-Packages: u-boot-tools

Machine: MQpro LoRa HAT
Kernel-Flavors: any
DTB-Id: custom/mqpro-lora-hat.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.uboot-generic
Required-Packages: u-boot-tools

Machine: MQpro Serial
Kernel-Flavors: any
DTB-Id: custom/mqpro-serial.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.uboot-generic
Required-Packages: u-boot-tools

Machine: MQpro SPI I2C
Kernel-Flavors: any
DTB-Id: custom/mqpro-spi-i2c.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.uboot-generic
Required-Packages: u-boot-tools