msperl

Hi! So as an update: I have taken your latest version with commit: 7256b4267f3815dba1c7c4e3a2451273ab76e9db And then I ran the following sketch on a FeatherM0: ``` #define POWER_PIN 11 /* Create...

@amcmahon01: my experience is that - contrary to original assumptions - it is not related to a rollover, because sometimes it takes just a few hours other times it takes...

Wrapping them up should be relatively straight-forward... ``` /dts-v1/; /plugin/; / { compatible = "brcm,bcm2835", "brcm,bcm2708", "brcm,bcm2709"; fragment@0 { target = ; __overlay__ { status = "okay"; }; }; fragment@1...

If I remember correctly then I have passed both CLK and MOSI thru the 74HCT125 and connected the enable (/OE) to the chip-select. What else can you do? Check with...

this may be due to some bugs - please try the latest version I have just published

I would need a bit more details! Things like: spi clock speed configured Description of test setup Description of test - how are you testing? Description of can bus parameters...

Looking at it some more I came to realize: You seem to be using: * a Raspberry Pi 3* * using spi 0.1 - so i guess that that you...

note that the implementation of the spi-bcm2708 (done by @notro) is not really complete with regards to the read side of things. This to such an extend that not even...

there is this commit: ab3f074, but with the above limitations...

it is untested, as I have no Idea what device could get used to test (and I do not own any). Again: the "read" code is not implemented in a...