V1.1.0
This release marks the start of the transition from the "legacy firmware" towards a more safe, stable, and extendable firmware. More concretely, this is the last release where we updated the current tpi tool
and BMC API server
as we aim to replace these userspace applications. (Note that we will keep supporting the current BMC API for now).
no .swu package available
This release also contains kernel updates, which the .swu update mechanism does not support. We know of this inconvenience and aim to gradually deploy a new firmware update mechanism throughout the upcoming releases.
What's Changed
- The BMC can flash raspberry pi cm4 modules via images stored locally on the SD card. ( we will further improve this experience in upcoming releases)
- USB configuration and Power settings are persisted. After a reboot, the previous state will be restored.
- Calling
tpi -p on -n 1
actually only turn on node 1 - mDNS is enabled. The TP board can be found via
<hostname>.local
. By default, this is:turingpi.local
- Key_1 now has two modes: a long and short press. Toggle-ing the button powers off or on the active (set by the user) nodes. Long press resets this configuration. If all nodes were on, all nodes will turn off long pressing the KEY_1 button. With three or fewer nodes on, all nodes will be turned on.
- the BMC API is extended with the following options:
- flash operation:
http://%s/api/bmc?opt=set&type=flash&file=%s&node=%d
- node_to_msd:
http://%s/api/bmc?opt=set&type=node_to_msd&node=%d'
- clear_usb_boot:
http://%s/api/bmc?opt=set&type=clear_usb_boot&node=%d'
- reset node:
http://%s/api/bmc?opt=set&type=reset&node=%d'
- USB opt is extended with a boot pin option:
http://%s/api/bmc?opt=set&type=usb&mode=0&node=%d&boot_pin=1'
- flash operation:
- tpi tool has been updated to reflect these changes
- startup and memory improvements
- bug fixes
Please give us some time to update the documentation accordingly:)
New Contributors
Full Changelog: v1.0.2...1.1.0