Carter Nelson

That's probably expected behavior for the scenario. Not having `Serial` is pretty rare, since that's a pretty basic Arduino feature. As a work around, can try just deleting `Adafruit_BusIO_Register.h` and...

This looks like a dupe of #111

Is there a known way to check for this across all platforms? The preprocessor logic in this PR doesn't seem to work in the case of STM32 BSP: https://github.com/adafruit/Adafruit_BusIO/pull/112 Adding...

Good catch. It needs a `HEX` parameter like other similar debug prints, ex: https://github.com/adafruit/Adafruit_BusIO/blob/e1aa388418ef4d2a326a58dd62620fb954799ccf/Adafruit_I2CDevice.cpp#L135 Want to PR a fix? No worries if you don't. But this would make for a...

Could this be done more generically, similar to how I2C does chunks? https://github.com/adafruit/Adafruit_BusIO/blob/bb7c77ad093ddbe44e9608f21e2dd37311ad13b6/Adafruit_I2CDevice.cpp#L176-L183

Right. But couldn't you work directly on the buffer passed in: ```cpp bool read(uint8_t *buffer, size_t len, uint8_t sendvalue = 0xFF); bool write(const uint8_t *buffer, size_t len, const uint8_t *prefix_buffer...

It seems like this really comes down to using `SPI.transfer(buffer, size);` in chunks instead of looping on `SPI.transfer(val);` byte-by-byte. What prevents this from being implemented on AVR?

Can you try implementing without using STL or a custom template class? The buffer can just be: ```cpp uint8_t chunkBuffer[maxBufferSizeForChunkedTransfer]; ``` Yes, you lose the convenience methods of the `array`...

Just to be sure - it's relying on the use of the `array` template class that's preventing this from working on AVR? Are there potentially other architectures that also do...

Your arguments for templates and STL usage are all fine. But for these Arduino libraries, it's generally preferred to keep things simple and avoid using these unless really necessary. This...