2026-02-28.log

+ kensanata8 (~alex@user/kensanata)00:03
- kensanata (QUIT: Ping timeout: 255 seconds) (~alex@user/kensanata)00:05
* kensanata8 -> kensanata00:05
+ paperManu_ (~paperManu@146.71.9.156)00:29
+ Seeker919 (~ircbot@2600:1007:b032:42a0:dde5:1d:f949:55ed)00:42
- nsc (QUIT: Ping timeout: 245 seconds) (~nicolas@i5C74DC1C.versanet.de)00:42
- Seeker919 (QUIT: Excess Flood) (~ircbot@2600:1007:b032:42a0:dde5:1d:f949:55ed)00:42
+ Seeker919 (~ircbot@2600:1007:b032:42a0:dde5:1d:f949:55ed)00:45
- Seeker919 (QUIT: Excess Flood) (~ircbot@2600:1007:b032:42a0:dde5:1d:f949:55ed)00:46
- chomwitt (QUIT: Quit: WeeChat 4.6.3) (~chomwitt@2a02:85f:9af1:5c00:1ac0:4dff:fedb:a3f1)00:46
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.0.129)01:00
+ Ar|stote|is (~linx@149.210.0.129)01:00
+ nsc (~nicolas@i5C74DC1C.versanet.de)01:29
- pomel0 (QUIT: Ping timeout: 248 seconds) (~pomel0@user/pomel0)01:59
+ pomel0 (~pomel0@user/pomel0)02:07
- mjw (QUIT: Ping timeout: 255 seconds) (~mjw@gnu.wildebeest.org)02:20
- paperManu_ (QUIT: Ping timeout: 255 seconds) (~paperManu@146.71.9.156)02:21
- nsc (QUIT: Ping timeout: 245 seconds) (~nicolas@i5C74DC1C.versanet.de)03:31
+ nsc (~nicolas@i5C74DEE7.versanet.de)03:33
- paperManu (QUIT: Ping timeout: 248 seconds) (~paperManu@146.71.9.156)03:58
- pomel0 (QUIT: Remote host closed the connection) (~pomel0@user/pomel0)05:11
+ pomel0 (~pomel0@user/pomel0)05:49
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)06:12
- chorc (QUIT: Quit: ZNC 1.9.1 - https://znc.in) (~chorc@user/chorc)07:25
+ chorc (~chorc@user/chorc)07:26
- se6astian (QUIT: ) (~quassel@2a03:b0c0:3:f0:0:1:9e0a:7000)07:34
- BAndiT1983 (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@2a03:b0c0:3:f0:0:1:9e0a:7000)07:34
- anuejn (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@2a03:b0c0:3:f0:0:1:9e0a:7000)07:34
+ BAndiT1983 (~quassel@2a03:b0c0:3:f0:0:1:9e0a:7000)08:25
+ se6astian (~quassel@2a03:b0c0:3:f0:0:1:9e0a:7000)08:25
+ anuejn (~quassel@2a03:b0c0:3:f0:0:1:9e0a:7000)08:25
+ mlarkin (~mlarkin@syn-076-081-194-027.biz.spectrum.com)09:34
+ AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net)11:01
+ andreas-e (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net)11:05
grimmwarejfred: power saving stuff still hasn't really been figured out11:48
grimmware[tj] started doing some profiling but got caught up in life11:48
+ mjw (~mjw@gnu.wildebeest.org)11:52
* ChanServ changed mode (+o, minute)12:11
orvaOut of curiosity: how does one measure 'poweroff' power draw? Lab power supply and volt meter around the board?12:30
orvaI have done power optimization for applications which is fairly straightforward (other than "just" removing the noise from the system)12:31
+ paperManu (~paperManu@146.71.9.156)13:22
+ spew (~spew@user/spew)14:50
+ bkeys (~Thunderbi@98.19.131.29)15:07
+ wielaard (~mjw@gnu.wildebeest.org)15:16
- spew (QUIT: Ping timeout: 255 seconds) (~spew@user/spew)15:16
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)15:16
- wielaard (QUIT: Ping timeout: 265 seconds) (~mjw@gnu.wildebeest.org)15:21
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@98.19.131.29)16:05
qbitI noticed some discussion about pico sdk yesterday - didn't think much of it.. but now I am trying to update my keyboard firmware :D16:37
qbitwas there an easy solution to getting it installed?16:37
qbit pico-sdk-source : Depends: libnewlib-arm-none-eabi but it is not going to be installed16:38
- pomel0 (QUIT: Ping timeout: 264 seconds) (~pomel0@user/pomel0)16:46
+ siviq (~siviq@user/siviq)16:48
- siviq (QUIT: Quit: Client closed) (~siviq@user/siviq)16:56
+ pomel0 (~pomel0@user/pomel0)17:16
- paperManu (QUIT: Ping timeout: 265 seconds) (~paperManu@146.71.9.156)18:06
+ bkeys (~Thunderbi@98.19.131.29)18:23
joschqbit: with the pocket-reform git repo you usually use a git clone of pico-sdk and not the pico-sdk-source package from Debian19:22
qbitah (i am specifically on the plain old reform repo :D) thanks!19:45
qbitseems i need to build reform2-keyboard-fw anyway (og keyboard - version shows R2 20250609 - which I built back then to be colemak..)20:13
qbitACTION takes notes this time :D20:13
minutegrimmware: jfred: on keyboard 1.5 i built in a little power-saving aid, but not sure yet how much that changes overnight drain20:17
minuteqbit: pocket-reform repo now has a script that helps with getting a working pico-sdk set up on debian... (install-fw-dependencies.sh)20:18
qbitah, nice - i was going through the build-all.sh stuff, but then realized i don'tthink i need it for the og fw20:18
grimmwareminute: is that a different mcu?20:19
kfxI thought it was the same mcu but a different libc in the sdk20:21
minutegrimmware: no, same mcu. but i redid the layout (should be much better now) and put in a power switch for the LED 5V rail20:34
minutegrimmware: the rp2040 can go pretty low power, it's just some effort/mess to wake up from that and have the usb stack be ok etc20:34
minutegrimmware: (full reset would be best probably)20:34
grimmwareminute: the keyboard -> sysctl usb/uart btw, is that just uart over the data lines or does there need to be usb enumeration too?20:35
minutekfx: i think we're talking about 2 separate things that happened in a similar timeframe. 1. i made a ne keyboard version 2. pico-sdk libc was changed for/in debian (not sure why that happened)20:35
minutegrimmware: that's just uart20:36
minutegrimmware: the usb and uart are not coupled20:36
grimmwarehmm, that's not good that my probe I just put together isn't able to get any data on it then :/20:36
minutegrimmware: on what, the uart output from the keyboard?20:36
minutegrimmware: does the keyboard have 3v3 power?20:36
minutegrimmware: if you don't supply that, the rp2040 is not running20:37
grimmwarethe keyboard's currently bricked because I used some recovery instructions that were apparently wrong. I'm actually trying to use the qwiic port to send uart to tell the sysctl to wake up the SoM so I can just plug in a USB keyboard and fix it but so far I've not had any luck20:37
grimmwarelike, honestly the biggest problem I have at the moment is that every time the keyboard shits the bed you have to hard power off to recover and it shits the bed *a lot* and if the keyboard doesn't work you can't boot the machine to use the onboard USB to reflash20:38
grimmwareit's kind of the achilles heel of the thing because the keyboard firmware has never really been all that stable20:38
- pomel0 (QUIT: Ping timeout: 248 seconds) (~pomel0@user/pomel0)20:41
kfxminute: sorry, I definitely mixed those up20:42
+ pomel0 (~pomel0@user/pomel0)20:58
+ Guest48 (~Guest48@c-92-35-8-186.bbcust.telenor.se)21:01
- Guest48 (QUIT: Client Quit) (~Guest48@c-92-35-8-186.bbcust.telenor.se)21:01
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)21:02
+ pomel0 (~pomel0@user/pomel0)21:09
+ Seeker650 (~ircbot@2600:1007:b0aa:8b43:ce12:4aeb:9e00:a741)21:10
- Seeker650 (QUIT: Excess Flood) (~ircbot@2600:1007:b0aa:8b43:ce12:4aeb:9e00:a741)21:10
+ paperManu (~paperManu@146.71.9.156)21:12
+ Seeker650 (~ircbot@2600:1007:b0aa:8b43:ce12:4aeb:9e00:a741)21:14
- Seeker650 (QUIT: Excess Flood) (~ircbot@2600:1007:b0aa:8b43:ce12:4aeb:9e00:a741)21:14
+ Seeker650 (~ircbot@185.sub-174-245-26.myvzw.com)21:17
- Seeker650 (QUIT: Excess Flood) (~ircbot@185.sub-174-245-26.myvzw.com)21:18
+ Seeker278 (~ircbot@2600:1007:b055:52e7:9c05:a8bd:6b1c:4bda)21:37
- Seeker278 (QUIT: Excess Flood) (~ircbot@2600:1007:b055:52e7:9c05:a8bd:6b1c:4bda)21:37
- RandyK (QUIT: Remote host closed the connection) (~RandyK@user/randyk)21:43
+ RandyK (~RandyK@user/randyk)21:43
+ Seeker278 (~ircbot@2600:1007:b055:52e7:9c05:a8bd:6b1c:4bda)21:45
- Seeker278 (QUIT: Excess Flood) (~ircbot@2600:1007:b055:52e7:9c05:a8bd:6b1c:4bda)21:45
- andreas-e (QUIT: Quit: Leaving) (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net)23:20
minutegrimmware: i basically never have this problem, sorry that you're so plagued by it. we could perhaps send you a 1.5 keyboard pcb, do you have some choc switches?23:42
+ mjw (~mjw@2a02-a472-ffa1-1-f2e6-4728-2974-38b8.fixed6.kpn.net)23:42
minutegrimmware: couldn't you just reflash the sysctl with the recovery firmware? it will turn on automatically when plugging in usb-c then23:43
minutegrimmware: step 2ff show how to flash the sysctl directly via usb-c https://support.mnt.re/#devices/pocket_reform/unbricking23:44
minutegrimmware: another option is we send you thea's usb-c adapter for the keyboard. it will also soon go in the shop. but the recovery option via sysctl recovery firmware is the quickest way (if you have a second computer)23:46
grimmwareThe sysctl is fine (I can talk to it over usb and it’s logging normally), it’s the keyboard which is currently down and I want to figure out how to do this so I can tap the UART between the keyboard and sysctl so I can add in a way to inject a 1p without taking the case off so I can rescue it with a usb keyboard instead of a whole other computer23:48
grimmwareI know that [tj] has these recurrent problems with the keyboard too.23:53
minutegrimmware: ah ok. i'm not sure i 100% understand which part will send the 1p then if the keyboard doesn't work23:57
grimmwareA separate rp2040 device with a screen and buttons that I had lying around and a spliced qwiic cable23:58
minutegrimmware: ahhh.23:58
grimmwareI’ve got it sniffing uart and injecting for other devices but the sysctl didn’t respond to it23:59
minutegrimmware: so you just want to send the string "1p" to the sysctl over uart? or you're modifying sysctl firmware to take commands from somewhere else, like the i2c port?23:59

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