142: Make stabilizer.py work on v0.4.0+ r=jordens a=HarryMakes
This is a "dirty" fix to have `stabilizer.py` working with the new API since v0.4.0, by applying the new JSON format for the IIRs as follows:
```json
{
"req": "Write",
"attribute": "stabilizer/iir?/state",
"value": {
"channel":1,
"iir":{
"ba":[b0,b1,b2,a1,a2],
"y_offset":?,
"y_min":?,
"y_max":?
}
}
}
```
The actual ASCII data sent will convert the innermost `"` to `'`, then wrap the curly-bracketed tree of `value` with `"`.
Co-authored-by: Harry Ho <hh@m-labs.hk>
144: Fix syntax for taking core peripherals (required by cortex-m-rtic v0.5.5) r=jordens a=HarryMakes
This is to fix a panicking upon initialization problem that is caused by a now undefined behaviour in our code from the perspective of the latest release of the cortex-m-rtic crate.
As per conversation in https://github.com/rtic-rs/cortex-m-rtic/issues/361, `context.core` should now be used instead of `cortex_m::Peripherals::take()`, which would cause some unexpected behaviour.
On a side note, a similar symptom where the Ethernet PHY does not get reset, as discussed in #141, might have also arisen from this new version of rtic. However, the reset delay still seems a bit too short to me.
Co-authored-by: Harry Ho <hh@m-labs.hk>
