7f295285da
28: Read MAC address from EEPROM r=jordens a=cjbe Try and read the unique MAC address from EEPROM. If the EEPROM can not be read (e.g. on the unpatched hardware version 1.0 where the EEPROM is unpowered) a hardcoded default of 10:E2:D5:00:03:00 is used. The MAC address found / used is logged. At the moment the only way of accessing this log is via semihosting. Closes #23 30: build(deps): bump serde from 1.0.99 to 1.0.100 r=jordens a=dependabot-preview[bot] Bumps [serde](https://github.com/serde-rs/serde) from 1.0.99 to 1.0.100. <details> <summary>Release notes</summary> *Sourced from [serde's releases](https://github.com/serde-rs/serde/releases).* > ## v1.0.100 > - Provide `serde::ser::StdError` and `serde:🇩🇪:StdError` which are either a re-export of `std::error::Error` (if Serde's "std" feature is enabled) or a new identical trait (otherwise). > > ```rust > #[cfg(feature = "std")] > pub use std::error::Error as StdError; > > #[cfg(not(feature = "std"))] > pub trait StdError: Debug + Display { > fn source(&self) -> Option<&(StdError + 'static)> { None } > } > ``` > > Serde's error traits `serde::ser::Error` and `serde:🇩🇪:Error` require `std::error::Error` as a supertrait, but only when Serde is built with "std" enabled. Data formats that don't care about no\_std support should generally provide their error types with a `std::error::Error` impl directly: > > ```rust > #[derive(Debug)] > struct MySerError {...} > > impl serde::ser::Error for MySerError {...} > > impl std::fmt::Display for MySerError {...} > > // We don't support no_std! > impl std::error::Error for MySerError {} > ``` > > Data formats that *do* support no\_std may either have a "std" feature of their own as has been required in the past: > > ```toml > [features] > std = ["serde/std"] > ``` > > ```rust > #[cfg(feature = "std")] > impl std::error::Error for MySerError {} > ``` > > ... or else now may provide the std Error impl unconditionally via Serde's re-export: > > ```rust > impl serde::ser::StdError for MySerError {} > ``` </details> <details> <summary>Commits</summary> - [`b6a77c4`]( |
||
|---|---|---|
| .cargo | ||
| .github | ||
| doc | ||
| src | ||
| .gitignore | ||
| .travis.yml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE | ||
| memory.x | ||
| openocd.gdb | ||
| README.md | ||
| stabilizer_pid.png | ||
| stabilizer_pid.svg | ||
| stabilizer.cfg | ||
| stabilizer.py | ||
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
rustup override add nightlyrustup target add thumbv7em-none-eabihfcargo 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/configaccordingly) openocd -f stabilizer.cfgand 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.binorarm-none-eabi-objcopy -O binary target/thumbv7em-none-eabihf/release/stabilizer stabilizer.bindfu-util -a 0 -s 0x08000000:leave -D stabilizer.bin
Using ST-Link virtual mass storage
cargo objcopy --release --bin stabilizer -- -O binary stabilizer.binorarm-none-eabi-objcopy -O binary target/thumbv7em-none-eabihf/release/stabilizer stabilizer.bin- Connect the ST-Link debugger
- copy
stabilizer.binto theNODE_H743ZIUSB 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-8to 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(xmarks an unused pin, enumeration is standard for dual row, as in the schematic). It's just folding the ribbon between wires5and6. The signals on the ribbon are thenNRST,TDI,TDO,TCK,TMS,3V3,GND,GND. ↩︎