linuswck
/
kirdy-firmware
forked from M-Labs/kirdy
1
0
Fork 0
Code Pull Requests Activity
92 Commits 5 Branches 0 Tags 2.1 MiB
Rust 89.8%
Nix 9.4%
GDB 0.8%
Go to file
Sébastien Bourdeauducq 4c331dd319 add BSD build instructions 2024-02-12 18:33:06 +08:00
.cargo rm unused cargo config target definition 2024-01-26 16:56:55 +08:00
src Fix Power Up Hw Issue 2024-02-07 12:46:13 +08:00
.gitignore current source working 2022-10-22 01:58:18 +08:00
BSD.md add BSD build instructions 2024-02-12 18:33:06 +08:00
Cargo.lock pid: Use IDSP impl of Pid, Add Eth Pid Ctrl Cmds 2024-02-07 11:56:38 +08:00
Cargo.toml pid: Use IDSP impl of Pid, Add Eth Pid Ctrl Cmds 2024-02-07 11:56:38 +08:00
LICENSE project init 2022-10-20 15:17:43 +08:00
README.md add BSD build instructions 2024-02-12 18:33:06 +08:00
build.rs project init 2022-10-20 15:17:43 +08:00
eth_cmd_test.py pid: Use IDSP impl of Pid, Add Eth Pid Ctrl Cmds 2024-02-07 11:56:38 +08:00
flake.lock Update stm32-eth cargo crate to 0.15.2 2023-12-15 16:40:55 +08:00
flake.nix Update stm32-eth cargo crate to 0.15.2 2023-12-15 16:40:55 +08:00
memory.x memory.x: Add comment on the reserved flash sector 2024-01-16 15:27:43 +08:00
openocd.gdb project init 2022-10-20 15:17:43 +08:00

README.md

Testing Firmware for the Sinara 1550 Kirdy

  • This repo is for testing only. Not intended for production use.

Building

Reproducible build with Nix

kirdy firmware is packaged using the Nix Flakes system. Install Nix 2.4+ and enable flakes by adding experimental-features = nix-command flakes to nix.conf (e.g. ~/.config/nix/nix.conf).

Once you have Flakes enabled, you can use nix build to build the firmware.

Development environment

Clone this repository and with Nix Flakes enabled, use the following commands:

nix develop
cargo build

The resulting ELF file will be located under target/thumbv7em-none-eabihf/release/kirdy.

Alternatively, you can install the Rust toolchain without Nix using rustup; see the Rust manifest file pulled in flake.nix to determine which Rust version to use.

For building on FreeBSD or OpenBSD, see BSD.md.

Debugging

Connect SWDIO/SWCLK/RST/GND to a programmer such as ST-Link v2.1. Run OpenOCD:

openocd -f interface/stlink.cfg -f target/stm32f4x.cfg

You may need to power up the programmer before powering the device. Leave OpenOCD running. Run the GNU debugger:

gdb target/thumbv7em-none-eabihf/release/kirdy

(gdb) source openocd.gdb

Flashing

There are several options for flashing kirdy. DFU requires only a USB-C connector, whereas OpenOCD needs a JTAG/SWD adapter.

dfu-util on Linux

  • Install the DFU USB tool (dfu-util).
  • Convert firmware from ELF to BIN: arm-none-eabi-objcopy -O binary kirdy kirdy.bin (you can skip this step if using the BIN from Hydra)
  • Connect to the USB Type C connector to kirdy above the RJ45.
  • Add jumper to kirdy v2.0 across 2-pin jumper adjacent to JTAG connector.
  • Cycle board power to put it in DFU update mode
  • Push firmware to flash: dfu-util -a 0 -s 0x08000000:leave -D kirdy.bin
  • Remove jumper
  • Cycle power to leave DFU update mode

st.com DfuSe tool on Windows

On a Windows machine install st.com DfuSe USB device firmware upgrade (DFU) software. link.

  • add jumper to kirdy across 2-pin jumper adjacent to JTAG connector
  • cycle board power to put it in DFU update mode
  • connect USB Type C to PC
  • use st.com software to upload firmware
  • remove jumper
  • cycle power to leave DFU update mode

OpenOCD

openocd -f interface/stlink.cfg -f target/stm32f4x.cfg -c "program target/thumbv7em-none-eabihf/debug/kirdy verify reset; exit"