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

SPLIT_KEYBARD F_CPU = 8000000 #14951

Closed
jmwolner opened this issue Oct 25, 2021 · 10 comments
Closed

SPLIT_KEYBARD F_CPU = 8000000 #14951

jmwolner opened this issue Oct 25, 2021 · 10 comments
Labels
stale Issues or pull requests that have become inactive without resolution.

Comments

@jmwolner
Copy link

When using itsy bitsy 3v the CPU must be set to 8mzh. When I set split keyboard, after flashing to the board, the USB device is no longer recognized. When I remove split keyboard, the USB device is working. Something is up with the split keyboard code.

@drashna
Copy link
Member

drashna commented Dec 13, 2021

You're using serial for the communication, correct? And this is the atmega32u4 controller?

If so, it may be that it's very sensitive to timing, and may need to be adjusted to fix that.

Also, the serial drivers for split uses interrupt, which may be art of the issue.

@jmwolner
Copy link
Author

Yes this is a atmega32u4 running at 8mzh. I can get it to work as one side without an issue. Soon as I add SPLIT_KEYBOARD = yes, and re-flash the controller, the USB device is no longer detected. So there is something up with the code for SPLIT_KEYBOARD. I was guessing it was maybe with the timing...but wasn't sure where to find that code and make some changes.

My wiring is using a TRRS for I2C. Based on the Redox Handwire. https://hackaday.io/project/160610-redox-keyboard/log/151316-redox-handwire. I was just wiring directly to SCL and SDA with VCC and Ground between the controllers.

I thought I would try the Pterodactyl keyboard definition, since it uses a Feather(very much like the Itsy Bitsy, but it uses an IO expander. https://marcyoung.us/post/pterodactyl/ Since I don't have an IO expander, it never recognizes it.

Any help and guidance is much appreciated how to change the code so SPLIT_KEYBOARD will work at 8mzh.

@drashna
Copy link
Member

drashna commented Dec 14, 2021

You have #define USE_I2C correct?

@jmwolner
Copy link
Author

Yes in the /keymaps/default/config.h

The keyboard(left side) boots ok and puts out keystrokes when I have the SPLIT_KEYBOARD commented out. Soon as I change it use in the rules.mk and recompile/reflash the controller is when the USB device is no longer recognized.

@drashna
Copy link
Member

drashna commented Dec 15, 2021

Do you have the same issue if you remove the USE_I2C and default to serial comms?

@jmwolner
Copy link
Author

USE_SERIAL worked and the HID was detected. But nothing was coming from the right side. I moved the SOFT_SERIAL_PIN to D2 to see if that was the issue and it wasn't. I eventually figured it out that I needed #define SPLIT_USB_DETECT.
It would appear that I2C won't work.
I've been struggling with this for months I extremely appreciate your reply and assistance.

@doctorkelp
Copy link

This is an issue for me, too! i2c is borked

@Kriechi
Copy link
Contributor

Kriechi commented Mar 5, 2022

SERIAL vs. I2C issues might be related to #15217

@stale
Copy link

stale bot commented Jun 12, 2022

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

@stale stale bot added the stale Issues or pull requests that have become inactive without resolution. label Jun 12, 2022
@github-actions
Copy link

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know.
// [stale-action-closed]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues or pull requests that have become inactive without resolution.
Projects
None yet
Development

No branches or pull requests

4 participants