adafruit / adafruit/M.2

Standard Discussion

Open
#2 32 comments 4 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
35
Forks
8
PR merge metrics
No merged PRs in 30d

Description

I guess might as well post some random ideas/observations, to start the discussion, they might be a bit chaotic ;)

- The terminology should be catchy and easy to understand, like Feather - FeatherWing
- The carrier connector should be well documented, it seems m.2 has multiple connector configurations, both in the number of pins and notch location. The MicroMod connector is a TE 2199230-4, I'm also ordering a few LOTES APCI0108-P001A connectors from LCSC to confirm that they are a compatible cheaper replacement.
- The dimensions of the processor board should be well defined, including the location and the size of the lock screw.
- Speaking of dimensions, also the constraints should be defined, is the processor board allowed to be wider or longer as long as the connector and pinout are compatible?
- I think having multiple allowed lengths of the processor board would be a good idea, as the current micromod spec of 22x22 mm limits the actual usable size to 22x15mm (because of the screw cutout), it would be nice to be able to have at least a 20x20 square.
- Multiple lengths could be done by having the carrier boards have multiple standoffs like computer motherboards:
![image](https://user-images.githubusercontent.com/249082/97082044-fb7fbe80-1606-11eb-874c-771bb3fa02f8.png)
This however poses a problem where there might be some places on the back of the processor board where taller parts could not be placed because they would collide with the standoffs (Like if you used the 3rd standoff, the first 2 would be under the board and in the way)
- For the pinout, having an option to have JTAG pins (instead of or in addition to SWD, TBD) would make the spec more attractive to the FPGA community
- Would be nice to at least try to agree on which GPIOs are used for specific functions, so example code would be more portable. For example, if all LCD-having carriers used the same GPIO for LCD "DC" pin, or same GPIO for a Neopixel.
- Having ready-to-go symbols, footprints, and templates for KiCad, Eagle, EasyEDA, etc. would make it a lot easier for people to use the spec.

I know this might look like a list of demands, but these are just my thoughts so start a discussion, and I'm open to changing my opinion on many of the items above, so let's get talking!

Contributor guide

No contributing guide indexed for this repository

Research direction

No file, test, or entry point is named. Begin by reviewing the repository's existing M.2 standard materials, then resolve the connector, dimensions, pinout, and CAD-library questions raised in the discussion. Done would require an agreed, documented scope rather than a single edit.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.