Patrick Van OosterwijckMy contract manufacturer built 200 piece of the M4-Shim, here are some pictures:
As you can see, I had half of them built with horizontal USB connector, like a normal Feather, and half of them with a vertical USB connector.
The reason for this is that I have some internal uses I'll probably want to use some of these for, that involve having a stack of 3 PCBs: the PoE-FeatherWing on the bottom; a custom, application specific shim with application specific connectors sticking out the back; and the M4-Shim above that. The "middle shim"'s connectors would likely interfere with the M4-Shim's USB connector if that was also facing back. So I made the ones with vertical USB to solve that issue. By my calculation, with the M4-Shim at the top of the stack, the USB should just clear the top of the PoE-FeatherWing's flyback transformer with enough space for the wall of a plastic case.
Next the CM needs to program and test them, but I'm waiting for the official 6.2.0 release of CircuitPython, the first to support the M4-Shim, before I can send them all the binaries.
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
I'd be interested in these!
Are you sure? yes | no
They now are available on Amazon and Tindie!
https://www.amazon.com/M4-Shim-Feather-PoE-FeatherWing-Ultra-Compact-Horizontal/dp/B0971PHFDR/
https://www.tindie.com/products/silicognition/m4-shim/
Are you sure? yes | no
I finally got around to trying the ones I got. I updated CircuitPython to 7.0.0 (which I got here: https://circuitpython.org/board/silicognition-m4-shim/), and ran into this issue: "ImportError: no module named 'types'" when importing "adafruit_request". "types" is a language built-in module. I also tried 7.1.0-rc.1, same issue Unfortunately, I don't have another CP Feather around right now to try a different Python, so I'm not sure if it's a board-specific issue or not. Any ideas?
Are you sure? yes | no
Ah, nvm. It's a bug in the latest version of adafruit_requests.py. Solved by going back to 1.10.2, but a fix should be in soon.
Are you sure? yes | no