Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a note about the BOARD_ID logic #13

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cscott
Copy link

@cscott cscott commented Jul 7, 2024

I've tested the firmware logic and found that it does not handle the
two possible pads for the keyboard symmetrically. This patch updates
the spec, but another option would be to patch the EC firmware to
recognize keyboard-sized modules with their primary connection on
the right hand side.

@@ -80,6 +80,10 @@ The Framework Laptop 16 has a protection scheme in place to prevent Input Module
Module detection is done using the BOARD_ID pin. It is possible to override this setting on the system, but at the risk of shorting the system
or modules.

Note that although a "keyboard size" module has pads on the left and right
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean? It does not have pads on both sides.

It may look like the pad could be on the either side from a mechanical point of view when looking at the keyboard. But nothing about the system is designed to handle that (neither firmware, mechanical or electrical).
There also isn't an easy way you could mod the keyboard to have the pads on the other side, so I don't think it's accurate to say there are pads on both sides.

Maybe we could add that note to the mechanical documentation? The only case where you need to know about this, is when you want to build your own module.
But really on the other side of the module there isn't enough space to put a microcontroller and pads 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants