-
Notifications
You must be signed in to change notification settings - Fork 3
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
Unable to pair #6
Comments
The right side will only work if paired to the left side. So if the left is plugged in, and the right is powered ( battery or USB ) testing on the right should show on the left side as keys . If this does not work I suggest flashing the right side with the left firmware to see if it registers keys. Also see the ZMK discord as they might have more debugging tips https://discord.com/channels/719497620560543766/1027622967263367259 . USB logging might also help. |
Hi vattern, I've tried flashing the right with the left firmware and it does not register any keys. This is the 2nd PCB with a brand new Holyiot 18010, the first one I tried had the same issues, I thought my soldering was bad on the first one so I ordered a new 18010 and soldered it onto a new PCB. Maybe JLPCB messed up something EDIT: Flashing right with left firmware does register a few keys |
Connecting to right side and using
Left side showing this:
I think the right side is having issues connecting to the left, key presses on right are showing in debug:
|
This is something zmk related, your best bet is the zmk discord
…On Sat, 11 Mar 2023, 17:01 webhostsg, ***@***.***> wrote:
Connecting to right side and using tio, this is what i get
[00:00:10.428,649] <err> zmk: Security failed: CD:39:B1:A7:84:C3 (random) level 1 err 9
[00:00:10.428,833] <dbg> zmk: disconnected: Disconnected from CD:39:B1:A7:84:C3 (random) (reason 0x3d)
[00:00:10.428,833] <dbg> zmk: disconnected: Active profile disconnected
[00:00:10.428,863] <dbg> zmk: update_advertising: advertising from 0 to 2
[00:00:10.429,534] <dbg> zmk: get_selected_endpoint: No endpoints are ready.
[00:00:15.567,260] <dbg> zmk: connected: Connected thread: 0x200039b0
[00:00:15.567,352] <dbg> zmk: connected: Connected CD:39:B1:A7:84:C3 (random)
[00:00:15.568,572] <dbg> zmk: update_advertising: advertising from 0 to 0
[00:00:15.568,572] <dbg> zmk: connected: Active profile connected
[00:00:15.569,915] <dbg> zmk: get_selected_endpoint: Only BLE is ready.
[00:00:15.600,830] <err> zmk: Security failed: CD:39:B1:A7:84:C3 (random) level 1 err 9
[00:00:15.600,982] <dbg> zmk: disconnected: Disconnected from CD:39:B1:A7:84:C3 (random) (reason 0x3d)
[00:00:15.601,013] <dbg> zmk: disconnected: Active profile disconnected
[00:00:15.601,043] <dbg> zmk: update_advertising: advertising from 0 to 2
[00:00:15.601,715] <dbg> zmk: get_selected_endpoint: No endpoints are ready.
[00:00:19.796,478] <dbg> zmk: connected: Connected thread: 0x200039b0
[00:00:19.796,569] <dbg> zmk: connected: Connected CD:39:B1:A7:84:C3 (random)
[00:00:19.797,729] <dbg> zmk: update_advertising: advertising from 0 to 0
[00:00:19.797,729] <dbg> zmk: connected: Active profile connected
[00:00:19.799,072] <dbg> zmk: get_selected_endpoint: Only BLE is ready.
[00:00:19.827,606] <dbg> zmk: split_svc_pos_state_ccc: value 1
[00:00:19.827,789] <dbg> zmk: security_changed: Security changed: CD:39:B1:A7:84:C3 (random) level 2
Left side showing this:
[00:00:41.290,740] <dbg> zmk: split_central_service_discovery_func: Discover complete
[00:00:41.292,968] <err> zmk: Security failed: DE:08:45:67:61:AA (random) level 1 err 9
[00:00:41.293,151] <dbg> zmk: split_central_disconnected: Disconnected: DE:08:45:67:61:AA (random) (reason 8)
[00:00:41.293,182] <dbg> zmk: release_peripheral_slot: Releasing peripheral slot at 0
[00:00:41.293,487] <dbg> zmk: start_scan: Scanning successfully started
[00:00:41.293,701] <dbg> zmk: disconnected: Disconnected from DE:08:45:67:61:AA (random) (reason 0x08)
[00:00:41.293,701] <dbg> zmk: disconnected: SKIPPING FOR ROLE 0
[00:00:41.299,865] <dbg> zmk: split_central_device_found: [DEVICE]: 20:61:E7:F3:AE:68 (public), AD evt type 0, AD data len 24, RSSI -78
[00:00:41.299,865] <dbg> zmk: split_central_eir_found: [AD]: 1 data_len 1
[00:00:41.299,896] <dbg> zmk: split_central_eir_found: [AD]: 3 data_len 2
[00:00:41.299,896] <dbg> zmk: split_central_eir_found: [AD]: 9 data_len 15
[00:00:41.443,969] <dbg> zmk: split_central_device_found: [DEVICE]: DE:08:45:67:61:AA (random), AD evt type 0, AD data len 25, RSSI -39
[00:00:41.444,000] <dbg> zmk: split_central_eir_found: [AD]: 1 data_len 1
[00:00:41.444,000] <dbg> zmk: split_central_eir_found: [AD]: 2 data_len 2
[00:00:41.444,000] <dbg> zmk: split_central_eir_found: [AD]: 7 data_len 16
[00:00:41.444,030] <dbg> zmk: split_central_eir_found: Found the split service
[00:00:41.444,610] <dbg> zmk: split_central_eir_found: Initiating new connnection
[00:00:41.553,497] <dbg> zmk: split_central_connected: Connected: DE:08:45:67:61:AA (random)
[00:00:41.553,527] <dbg> zmk: split_central_process_connection: Current security for connection: 1
[00:00:41.554,626] <dbg> zmk: split_central_process_connection: New connection params: Interval: 6, Latency: 30, PHY: 1
[00:00:41.554,626] <dbg> zmk: connected: Connected thread: 0x20004f38
[00:00:41.554,656] <dbg> zmk: connected: SKIPPING FOR ROLE 0
[00:00:41.817,382] <dbg> zmk: security_changed: Security changed: DE:08:45:67:61:AA (random) level 2
[00:00:41.832,977] <dbg> zmk: split_central_service_discovery_func: [ATTRIBUTE] handle 42
[00:00:41.832,977] <dbg> zmk: split_central_service_discovery_func: Found split service
[00:00:41.854,949] <dbg> zmk: split_central_chrc_discovery_func: [ATTRIBUTE] handle 43
[00:00:41.854,949] <dbg> zmk: split_central_chrc_discovery_func: Found position state characteristic
[00:00:41.855,041] <dbg> zmk: split_central_subscribe: [SUBSCRIBED]
[00:00:41.884,948] <dbg> zmk: split_central_chrc_discovery_func: [ATTRIBUTE] handle 46
[00:00:41.884,979] <dbg> zmk: split_central_chrc_discovery_func: Found run behavior handle
[00:01:00.412,384] <dbg> zmk: bvd_sample_fetch: ADC raw 863 ~ 632 mV => 886 mV
[00:01:00.412,414] <dbg> zmk: bvd_sample_fetch: Percent: 0
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDWJ24CXIEEMA3EXQMTLCLW3SVXTANCNFSM6AAAAAAVWZG7P4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Yes, got it fixed with some help from zmk discord. Thank you so much for your great work! |
Still a work in progress. I've decided to go with holiot-carrier for my Scylla. JLPCB did PCB with most of the SMDs soldered. Purchased Holyiot 18010 from AliExpress and soldered it on.
Used J-link to flash pca10056_bootloader-0.7.0_s140_6.1.1.hex
bootloader. Copied the zmk-config.
I was able to upload firmware on both, my Mac detected scylla, but I'm unable to connect to it successfully.
Connected left via USB and using https://keyboardchecker.com/ all the left keys registered. Plug in the right side via USB does not detect, not sure if this is the expected result.
Plugged in the battery on both the left and right and was able to detect it, but I still can't pair it. Even tried it on my Android phone and it just would not pair.
What am I doing wrong? Posted on the discord but nobody replied.
The text was updated successfully, but these errors were encountered: