v5.0.0
Breaking Changes
- driver: MAX11300 driver interface changed considerably
- spi: Order of arguments of the
SpiHandle
DMA functions changed - dma:
SpiHandle
previously usedDMA1_Stream7
, now usesDMA2_Stream2
andDMA2_Stream3
Features
- spi:
SpiHandle
now has callbacks before and after a DMA transaction starts (can be used for software driven chip select) - spi:
SpiHandle
now supports simultaneous transmit and receive with DMA usingSpiHandle::DmaTransmitAndReceive()
- spi: added
MultiSlaveSpiHandle
that allows to connect to multiple SPI slave devices on a shared bus - driver: MAX11300 now supports multiple chips on a shared bus
- driver: MAX11300 now uses DMA to handle updates without blocking
- driver: MAX11300 now updates the chips continuously until manually stopped
- driver: MAX11300 can now call a user-provided callback after an update is complete
- debugging: added additional debugging aids to the HardFault handler
- gatein: added invert init parameter for reading from different input circuits from the GateIn class.
- ui: added
OnUserInteraction
virtual function to UI framework to allow for tracking user activity
Bug Fixes
- logger: Added 10ms delay at the end of
StartLog
function. Without this, messages immediatly following theStartLog
function were getting missed whenwait_for_pc
is set totrue
. - testing: debugging configuration now uses
lldb
debugging extension to support unit test debugging on macOS with Apple Silicon - driver: oled_ssd130x.h - Add the SpiHandle:Config struct to SSD130x4WireTransport:Config to allow full access to the SPI peripheral configuration.
- hid: fixed issue in
AnalogControl
where computed coeff could be out of range with certain block sizes - driver: added missing alternate function pin mappings for SPI2, and UART for pins available on the patch_sm hardware
- usb: fixed issue with MIDI output from USB
- driver: fixed off-by-one error in qspi erase function.
Other
- driver: improved debouncing for
Switch
, andEncoder
classes (limiting debouncing to 1kHz max frequency internally).
Migrating
SPI
// Old
SpiHandle::Result DmaTransmit(uint8_t* buff,
size_t size,
SpiHandle::CallbackFunctionPtr callback,
void* callback_context);
// New
SpiHandle::Result DmaTransmit(uint8_t* buff,
size_t size,
SpiHandle::StartCallbackFunctionPtr start_callback,
SpiHandle::EndCallbackFunctionPtr end_callback,
void* callback_context);
// Same for DmaReceive and DmaTransmitAndReceive
MAX11300
// Old: MAX11300 takes no template arguments
MAX11300 max11300driver;
// New: MAX11300 takes number of chips as template argument
constexpr size_t num_devices = 4;
MAX11300<num_devices> max11300driver;
// Old: constructor only takes a config struct
max11300driver.Init(config);
// New: constructor takes a DMA buffer situated in non-cached and DMA-accessible memory
MAX11300Types::DmaBuffer DMA_BUFFER_MEM_SECTION max11300DmaBuffer;
max11300driver.Init(config, &max11300DmaBuffer);
// Old: most types are inside the MAX11300 classname scope
daisy::MAX11300::PIN_0
daisy::MAX11300::AdcVoltageRange
// New: types are in a separate namespace to keep them independent from the "num_devices" template argument
daisy::MAX11300Types::PIN_0
daisy::MAX11300Types::AdcVoltageRange
// Old: only a single chip was handled by the driver
max11300driver.ConfigurePinAsAnalogRead(daisy::MAX11300::PIN_0, daisy::MAX11300::AdcVoltageRange::NEGATIVE_5_TO_5);
max11300driver.ConfigurePinAsAnalogWrite(daisy::MAX11300::PIN_1, daisy::MAX11300::DacVoltageRange::NEGATIVE_5_TO_5);
// New: each function now takes an additional argument, the index of the chip
max11300driver.ConfigurePinAsAnalogRead(0, daisy::MAX11300Types::PIN_0, daisy::MAX11300Types::AdcVoltageRange::NEGATIVE_5_TO_5);
max11300driver.ConfigurePinAsAnalogWrite(1, daisy::MAX11300Types::PIN_1, daisy::MAX11300Types::DacVoltageRange::NEGATIVE_5_TO_5);
// Old: Update() synchronously updates the chip and blocks until the update is complete
max11300driver.Update(); // blocks
// New: - Start() works asynchronously in the background using DMA
// - Start() will retrigger updates itself automatically, until stopped by calling Stop()
// - A callback can be called after each update cycle that was completed successfully
void MyUpdateCompleteCallback(void* context) {
// The context is the pointer you passed when calling `.Update()`
// This callback comes from an interrupt, keep is fast.
}
max11300driver.Start(
&MyUpdateCompleteCallback, // or nullptr if you don't need a callback. default: nullptr
&someThingThatYouWantToGetPassedToYourCallback // callback context, or nullptr if not needed
);
// you don't have to specify the arguments, then the defaults will be used
max11300driver.Start();
// you can stop the auto update after you started it
max11300driver.Stop();