2026-03-01.log

minutegrimmware: ah, is it a 3-way connection, i.e. the rx and tx are connected from your rp2040 device to the keyboard _and_ the sysctl uart ports?00:00
grimmwareJust sending the string. I’m not sure why it’s not working with my code hence why I was asking if USB actually encapsulated in some way rather than just using D+ and D- as tx and rx00:00
grimmwareNo I unplugged the keyboard to do it00:01
minutegrimmware: hmm ok. maybe you're using the wrong port? it's not using D+ and D-00:01
minutegrimmware: the keyboard has two cables going to the mainboard00:01
minutegrimmware: one is uart and 3v3, the other is usb and 5v00:01
grimmwareThis is the one going in near where it says sysctl00:01
minutegrimmware: the correct one is in the top left corner of the motherboard00:02
minutegrimmware: left to the 6 "prongs" for soc uarts00:02
grimmwareYeah that’s the one00:03
minutegrimmware: i wonder why you mention usb then00:03
minutegrimmware: it should be GND RX TX 3v300:03
grimmwareBecause it’s labelled usb/uart in the handbook00:04
minutegrimmware: ok that sounds like a mistake. let me check00:04
minutegrimmware: you mean this graphic probably? https://mntre.com/documentation/pocket-reform-handbook/_images/hardware-pocket-diagram-halves.png00:05
grimmwareNo in the schematic (sorry I’d be more useful but I’m on my phone and pinned down by a sleeping dog)00:05
minutegrimmware: because here there are separate callouts for "UART to keyboard" and "USB to keyboard" https://mntre.com/documentation/pocket-reform-handbook/_images/hardware-pocket-reform-render-motherboard-callouts.png00:05
minutegrimmware: ah the headline in the schematic says > Internal USB/UART (Keyboard/TB Interface)00:07
grimmwareYeah, just found it again and I ca see my misunderstanding :)00:07
minutegrimmware: right, i see how that could be misinterpreted, thanks. J5 and J6 are separate below it, but there's only one headline.00:07
^alexis there a mr. understanding?00:07
minute^alex: chuckles00:08
minutegrimmware: if you connect your external RX to TX and TX to RX, and GND to GND, and do 115200 baud and send a newline after the command, and probably send the command twice (might be in a weird state before), it should totally work. 00:09
grimmwareOkay cool, that means either my code or my wiring is jacked up then! Also the D+ and the D- are reinforced by the green and white cables for tx and rx !00:09
minutegrimmware: i have a panel pcb with power button for desktop reform (soon to reveal a new name!) that has an attiny in it and when you press the power button for 2 seconds it sends 1p / 0p depending on the power state. for example. the whole point of the uart interface was to make it as easily hackable as possible :D00:10
grimmwareThat’s effectively the sort of thing I was trying to emulate, but I figured a general purpose uart sniffer and injector would be a good first step anyway :) I quite like the idea of also hooking it up to the power rails to the keyboard to hard reset it.00:13
grimmwareAnyway I’d better drop or I won’t sleep, thanks for helping me out!00:14
- mjw (QUIT: Ping timeout: 272 seconds) (~mjw@2a02-a472-ffa1-1-f2e6-4728-2974-38b8.fixed6.kpn.net)01:05
- nsc (QUIT: Ping timeout: 245 seconds) (~nicolas@i5C74DEE7.versanet.de)01:07
- AnimaInvicta (PART: !!unknown attribute: msg!!) (~AnimaInvi@88-120-179-216.subs.proxad.net)01:51
+ nsc (~nicolas@i5C74DEE7.versanet.de)01:52
+ siviq (~siviq@user/siviq)02:26
- siviq (QUIT: Client Quit) (~siviq@user/siviq)02:28
- op_4 (QUIT: Remote host closed the connection) (~tslil@user/op-4/x-9116473)04:05
+ op_4 (~tslil@user/op-4/x-9116473)04:05
+ robin_ (~robin@user/terpri)04:11
- robin (QUIT: Ping timeout: 255 seconds) (~robin@user/terpri)04:14
jfredI've had a lot of issues with the pocket reform's keyboard as well (especially lately)... someone on the forum mentioned that the position of the lid made a difference for them and indeed it seems to for me as well04:19
jfredand e.g. I'd noticed that the keyboard connector seemed to have been pulled out slightly a while back/it clicked slightly when I pushed it back in04:19
jfredmy gut's telling me something's getting pulled or pinched somehow, maybe tomorrow I'll pull off the keyboard cover and look inside while I'm moving the lid04:20
jfredit does feel to me like at one particular lid position the keyboard tends to reset/fail to connect more often, and I'm usually able to fix that by opening the lid to a slightly wider position04:22
+ robin__ (~robin@user/terpri)06:38
- robin_ (QUIT: Ping timeout: 268 seconds) (~robin@user/terpri)06:41
+ bpye_ (~bpye@node-1w7jr9plpv701huh47f4wj5kk.ipv6.telus.net)06:42
- bpye (QUIT: Ping timeout: 256 seconds) (~bpye@user/bpye)06:44
- enwu (QUIT: Quit: -) (~enwu@user/enwu)10:23
+ enwu (~enwu@user/enwu)10:45
- enwu (QUIT: Quit: -) (~enwu@user/enwu)11:02
+ enwu (~enwu@user/enwu)11:11
- orva (QUIT: Remote host closed the connection) (16abab341f@2a01:4f9:c012:b611::1)11:20
+ orva (16abab341f@2a01:4f9:c012:b611::1)11:20
+ mjw (~mjw@2a02-a472-ffa1-1-f2e6-4728-2974-38b8.fixed6.kpn.net)12:21
+ andreas-e (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net)12:28
- chrcav (QUIT: Quit: leaving) (~chrcav@user/chrcav)13:40
+ chrcav (~chrcav@user/chrcav)13:41
[tj]jfred: hmm I bet that tracks for me. I get the most issues if I move the pocket and it is closed.14:12
- mhoye (QUIT: Ping timeout: 264 seconds) (~mhoye@li319-32.members.linode.com)14:55
- C-Keen (QUIT: Ping timeout: 264 seconds) (cckeen@krieg.pestilenz.org)14:55
- chorc (QUIT: Ping timeout: 264 seconds) (~chorc@user/chorc)14:56
- sbp (QUIT: Ping timeout: 264 seconds) (~sbp@apache/doge/sbp)14:56
+ chorc_ (~chorc@user/chorc)14:56
+ mhoye (~mhoye@li319-32.members.linode.com)14:57
+ C-Keen (cckeen@krieg.pestilenz.org)15:00
+ sbp (~sbp@2001:19f0:6800:1102:5400:ff:fe11:39a1)15:01
minutejfred: makes sense15:17
+ skipwich (~skipwich@user/skipwich)15:44
- sbp (QUIT: Changing host) (~sbp@2001:19f0:6800:1102:5400:ff:fe11:39a1)16:00
+ sbp (~sbp@apache/doge/sbp)16:00
- pomel0 (QUIT: Remote host closed the connection) (~pomel0@user/pomel0)16:56
+ pomel0 (~pomel0@user/pomel0)17:04
MartiniMoeHi, does anyone know, if pocket reforms from mnt are being shipped currently? I ordered in September and have not heard anything until now. The support also does not respond to my ticket and I am getting worried something might be wrong with my order :/17:09
mhoyeIf I replace the motherboard in my 1stgen Reform (plus the sideplates) but not the SOC board, do we foresee that working?17:20
joschMartiniMoe: did you order after 2025-09-10?17:57
joschmhoye: replace with motherboard 3.0?17:57
MartiniMoejosch: yes, on 20th september17:57
joschMartiniMoe: according to the table here https://mntre.com/faq.html that is waiting for the keyboard and motherboard update17:58
joschMartiniMoe: both keyboard and motherboard are receiving a big overhaul right now17:58
MartiniMoeThe FAQ table sais 4-5 month, which passed by now, so I was confused17:58
- mjw (QUIT: Ping timeout: 245 seconds) (~mjw@2a02-a472-ffa1-1-f2e6-4728-2974-38b8.fixed6.kpn.net)18:16
mhoyejosch: Yeah.18:27
mhoyehoping for that sweet, sweet USB-C power.18:27
mhoyeAlso I haven't been able to make HDMI out work on this thing so that too.18:28
- pomel0 (QUIT: Ping timeout: 255 seconds) (~pomel0@user/pomel0)18:39
+ pomel0 (~pomel0@user/pomel0)18:43
joschmhoye: you had imx8mq? I can confirm that imx8mq works fine with motherboard 3.019:07
joschMartiniMoe: the table is probbaly out-of-date as I think minute is still working on both motherboard and keyboard -- you can see minute's recent changes to the design files for motherboard 1.5 and keyboard 1.1 here: https://source.mnt.re/reform/pocket-reform/activity19:09
MartiniMoejosch: oh okay thanks. So I will wait a bit longer... :D19:10
+ siviq (~siviq@user/siviq)19:11
joschMartiniMoe: i'd expect the next monthly newsletter to have an update on the current situation19:12
+ mjw (~mjw@178.230.39.36)19:18
- cli (QUIT: Remote host closed the connection) (~m-vsauiy@user/cli)19:35
+ cli (~m-vsauiy@user/cli)19:37
+ ephase (~ephase@2a01:e0a:2a:5300:3049:c4ff:fe72:a63c)19:46
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@178.230.39.36)19:55
- siviq (QUIT: Quit: Client closed) (~siviq@user/siviq)20:05
+ mjw (~mjw@178.230.39.36)20:22
- ephase (QUIT: Quit: WeeChat 4.8.1) (~ephase@2a01:e0a:2a:5300:3049:c4ff:fe72:a63c)20:26
+ wielaard (~mjw@178.230.60.94)20:33
- mjw (QUIT: Ping timeout: 276 seconds) (~mjw@178.230.39.36)20:36
- pomel0 (QUIT: Ping timeout: 255 seconds) (~pomel0@user/pomel0)20:38
+ pomel0 (~pomel0@user/pomel0)20:39
- wielaard (QUIT: Read error: Connection reset by peer) (~mjw@178.230.60.94)20:40
+ wielaard (~mjw@178.230.60.94)20:41
- wielaard (QUIT: Remote host closed the connection) (~mjw@178.230.60.94)20:42
- pomel0 (QUIT: Ping timeout: 245 seconds) (~pomel0@user/pomel0)20:58
+ pomel0 (~pomel0@user/pomel0)20:58
+ ephase (~ephase@2a01:e0a:2a:5300:3049:c4ff:fe72:a63c)20:58
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)21:02
+ pomel0 (~pomel0@user/pomel0)21:03
- pomel0 (QUIT: Ping timeout: 255 seconds) (~pomel0@user/pomel0)21:25
+ pomel0 (~pomel0@user/pomel0)21:26
- pomel0 (QUIT: Ping timeout: 264 seconds) (~pomel0@user/pomel0)21:33
+ pomel0 (~pomel0@user/pomel0)21:33
+ mjw (~mjw@gnu.wildebeest.org)21:38
- pomel0 (QUIT: Ping timeout: 255 seconds) (~pomel0@user/pomel0)21:42
+ pomel0 (~pomel0@user/pomel0)21:42
- pomel0 (QUIT: Read error: Connection reset by peer) (~pomel0@user/pomel0)21:46
+ pomel0 (~pomel0@user/pomel0)21:46
- cli (QUIT: Ping timeout: 264 seconds) (~m-vsauiy@user/cli)22:02
+ voltaire28_ (~jlafon@28.162.2.93.rev.sfr.net)22:03
+ cli (~m-vsauiy@user/cli)22:03
- pomel0 (QUIT: Ping timeout: 245 seconds) (~pomel0@user/pomel0)22:32
- voltaire28_ (QUIT: Ping timeout: 255 seconds) (~jlafon@28.162.2.93.rev.sfr.net)23:22
+ siviq (~siviq@user/siviq)23:24
- siviq (QUIT: Client Quit) (~siviq@user/siviq)23:24
+ voltaire28_ (~jlafon@28.162.2.93.rev.sfr.net)23:47
minuteMartiniMoe: support does not respond? what's your ticket number?23:57

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!