mirror of
https://github.com/tillitis/tillitis-key1.git
synced 2024-10-01 01:45:38 -04:00
doc: update to refs to in-tree TP-1 firmware
Signed-off-by: Daniel Lublin <daniel@lublin.se>
This commit is contained in:
parent
65e3ea015d
commit
ea7d64c29f
@ -141,32 +141,32 @@ The circuit board designs were all created in [KiCad
|
|||||||
|
|
||||||
## MTA1-USB-V1 and TP-1 programming board firmware
|
## MTA1-USB-V1 and TP-1 programming board firmware
|
||||||
|
|
||||||
The programmer boards are running a custom firmware developed by
|
The TP-1 programming boards runs a custom firmware developed by
|
||||||
Blinkinlabs. The source code for this firnware is available on
|
Blinkinlabs. Source code for this firmware can be found at
|
||||||
Github: https://github.com/Blinkinlabs/ice40_flasher
|
[hw/boards/tp1/firmware/](../hw/boards/tp1/firmware/). There is also a
|
||||||
|
pre-built firmware binary at
|
||||||
There is also a pre built firmware binary available for the
|
[hw/boards/tp1/firmware/bin/main.uf2](../hw/boards/tp1/firmware/bin/main.uf2).
|
||||||
programmer board:
|
|
||||||
https://github.com/Blinkinlabs/ice40_flasher/tree/main/bin
|
|
||||||
|
|
||||||
To update the firmware on the programmer board, either build the file
|
To update the firmware on the programmer board, either build the file
|
||||||
"main.uf2", or download the pre built file to your host computer.
|
`main.uf2` (more instructions below), or get the pre-built file to
|
||||||
Then do the following:
|
your host computer. Then do the following:
|
||||||
|
|
||||||
1. Disconnect the programming board from the host computer
|
1. Disconnect the programming board from the host computer
|
||||||
2. Press and hold the "BOOTSEL" button on the RPi2040 sub board on
|
2. Press and hold the "BOOTSEL" button on the RPi2040 sub-board on the
|
||||||
the programming board
|
programming board
|
||||||
3. Reconnect the programming board to the host computer
|
3. Reconnect the programming board to the host computer
|
||||||
4. Release the "BOOTSEL" button after connecting the programming
|
4. Release the "BOOTSEL" button after connecting the programming board
|
||||||
board to the host. The board should now appear to the host as a
|
to the host. The board should now appear to the host as a USB
|
||||||
USB connected storage device
|
connected storage device
|
||||||
5. Open the storage device and drop the firmware file ("main.uf2")
|
5. Open the storage device and drop the firmware file `main.uf2` into
|
||||||
into the storage device
|
the storage device
|
||||||
|
|
||||||
The programmer will update its firmware with the file and restart
|
The programmer will update its firmware with the file and restart
|
||||||
itself. After reboot the storage device will automatically be
|
itself. After reboot the storage device will automatically be
|
||||||
disconnected.
|
disconnected.
|
||||||
|
|
||||||
|
### Building the TP-1 firmware
|
||||||
|
|
||||||
The firmware requires the Raspberry Pi Pico SDK:
|
The firmware requires the Raspberry Pi Pico SDK:
|
||||||
|
|
||||||
cd ~
|
cd ~
|
||||||
@ -174,10 +174,13 @@ The firmware requires the Raspberry Pi Pico SDK:
|
|||||||
cd pico-sdk
|
cd pico-sdk
|
||||||
git submodule update --init
|
git submodule update --init
|
||||||
|
|
||||||
Note that the Docker image places the pico-sdk directory in
|
Note that our container image places the pico-sdk directory in
|
||||||
/usr/local. For normal development, it is usually left in the
|
/usr/local. For normal development, it is usually left in the
|
||||||
users home directory.
|
users home directory.
|
||||||
|
|
||||||
|
See
|
||||||
|
[hw/boards/tp1/firmware/README.md](../hw/boards/tp1/firmware/README.md)
|
||||||
|
for further instructions.
|
||||||
|
|
||||||
## CH552 USB to Serial firmware
|
## CH552 USB to Serial firmware
|
||||||
|
|
||||||
|
BIN
hw/boards/tp1/firmware/bin/main.uf2
Normal file
BIN
hw/boards/tp1/firmware/bin/main.uf2
Normal file
Binary file not shown.
Loading…
Reference in New Issue
Block a user