d5916c5501
133: build(deps): bump cortex-m-rtic from 0.5.4 to 0.5.5 r=jordens a=dependabot[bot] Bumps [cortex-m-rtic](https://github.com/rtic-rs/cortex-m-rtic) from 0.5.4 to 0.5.5. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rtic-rs/cortex-m-rtic/blob/master/CHANGELOG.md">cortex-m-rtic's changelog</a>.</em></p> <blockquote> <h2>[v0.5.5] - 2020-08-27</h2> <ul> <li>Includes the previous soundness fix.</li> <li>Fixes wrong use of the <code>cortex_m</code> crate which can cause some projects to stop compiling.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/rtic-rs/cortex-m-rtic/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cortex-m-rtic&package-manager=cargo&previous-version=0.5.4&new-version=0.5.5)](https://help.github.com/articles/configuring-automated-security-fixes) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
---|---|---|
.cargo | ||
.github | ||
ad9959 | ||
doc | ||
src | ||
.gitignore | ||
.rustfmt.toml | ||
CHANGELOG.md | ||
Cargo.lock | ||
Cargo.toml | ||
LICENSE | ||
README.md | ||
cargosha256.nix | ||
memory.x | ||
openocd.gdb | ||
pounder_test.py | ||
stabilizer.cfg | ||
stabilizer.py | ||
stabilizer_pid.png | ||
stabilizer_pid.svg |
README.md
Stabilizer Firmware
Features
- dual channel
- SPI ADC
- SPI DAC
- 500 kHz rate, timed sampling
- 2 µs latency, unmatched between channels
- f32 IIR math
- generic biquad (second order) IIR filter
- anti-windup
- derivative kick avoidance
Limitations/TODOs
- Fixed AFE gains
- The IP and MAC address are hardcoded
- Expose configurable limits
- 100Base-T only
- Digital IO, GPIO header, AFE header, EEM header are not handled
Hardware
See https://github.com/sinara-hw/Stabilizer
Minimal bootstrapping documentation
- Clone or download this
- Get rustup
- Get cargo-binutils
rustup target add thumbv7em-none-eabihf
cargo build --release
- Do not try the debug (default) mode. It is guaranteed to panic.
Using GDB/OpenOCD
- Get a recent openocd, a JTAG adapter ("st-link" or some clone) and everything connected and permissions setup. Most Nucleo boards have a detachable ST-Link v2 and are cheap.1
- Get a multiarch
gdb
(or a cross arm gdb and edit.cargo/config
accordingly) openocd -f stabilizer.cfg
and leave it runningcargo run --release
Using USB-DFU
- Install the DFU USB tool (
dfu-util
) - Connect to the Micro USB connector below the RJ45
- Short JC2/BOOT
cargo objcopy --release --bin stabilizer -- -O binary stabilizer.bin
orarm-none-eabi-objcopy -O binary target/thumbv7em-none-eabihf/release/stabilizer stabilizer.bin
dfu-util -a 0 -s 0x08000000:leave -D stabilizer.bin
Using ST-Link virtual mass storage
cargo objcopy --release --bin stabilizer -- -O binary stabilizer.bin
orarm-none-eabi-objcopy -O binary target/thumbv7em-none-eabihf/release/stabilizer stabilizer.bin
- Connect the ST-Link debugger
- copy
stabilizer.bin
to theNODE_H743ZI
USB disk
Protocol
Stabilizer can be configured via newline-delimited JSON over TCP. It listens on port 1235. stabilizer.py contains a reference implementation of the protocol.
-
Build a cable: connect a standard 8 conductor ribbon with the wires numbered
1-8
to the pins on the St-Link v2 single row 2.54mm connector as647513(82)
((i)
marks an unused wire) and to the 1.27mm dual row on Stabilizer as657483x2x1
(x
marks an unused pin, enumeration is standard for dual row, as in the schematic). It's just folding the ribbon between wires5
and6
. The signals on the ribbon are thenNRST,TDI,TDO,TCK,TMS,3V3,GND,GND
. ↩︎