| - Gooberpatrol66 (QUIT: Ping timeout: 246 seconds) (~Gooberpat@user/gooberpatrol66) | 00:18 | |
| chartreuse | minute: Oh sweet, and here I was thinking something like that would need to be done from scratch bare metal | 00:39 |
|---|---|---|
| henesy | minute: [12:20:29 <minute> henesy: are these protected battery boards?] ⇒ they're whatever came with the mnt reform 2 | 00:49 |
| henesy | i haven't changed anything about the cells/internals wrt power | 00:49 |
| henesy | the only non-stock is the nvme ssd and wifi card, both of which worked fine with power for almost a year or so it felt like | 00:50 |
| henesy | you think the cells are cooked? not sure why they would be | 00:58 |
| henesy | how expensive/where would one get new battery cells if that was the case? | 00:58 |
| minute | henesy: just trying to understand what's going on there. is this a mnt reform bought recently from crowd supply? if you pull out a battery cell, are there little chips on the battery board? (then it's the protected one). do you have a multimeter to check cell voltage? | 01:13 |
| minute | henesy: ah, now i read again, the reform is a year in use already? did you have a longer break recently where it wasn't used, or it was ok all the time and then just suddenly no more charging? | 01:14 |
| chartreuse | I'm kinda convinced looking at the 9front and linux stuff on the wm8960 that whatever minor changes 9front has is just managing to barely mask the symptoms of the resistor divider issue of the jack detect. I'm not noticing anything really that'd make a difference. My one guess is something with the headphone caps providing enough sink to drop the voltage on JD3 when the headphones are plugged in, | 01:43 |
| chartreuse | and with 9front there's then a 20k centering resistor on the caps, but on linux the default 500 ohm is used, and somehow that's causing an overshoot again and popping it back to speaker. But that's the opposite behaviour I was seeing, where speaker would turn to headphone | 01:43 |
| chartreuse | I'm still convinced the right fix is to change the resistors (either weaken the pullup or increase the pulldown) so the jack detect is safely in the low/high zones when inserted/removed. Since otherwise it's relying on it somehow undershooting when plugged in from the load of the headphones or such, then sitting in the middle undefined region relying on the schmidt trigger input | 01:44 |
| henesy | minute: april 2023-ish crowd supply reform | 01:49 |
| henesy | there was probably a 2 month gap or so where i didnt touch the reform -- do the cells die completely? | 01:50 |
| henesy | it was ok the whole time and then just never charged again after that gap | 01:50 |
| henesy | i have a multimeter *somewhere* | 01:50 |
| chartreuse | With the unprotected board it's possible, though I thought the protected boards were out by then | 01:56 |
| chartreuse | I had that happen on mine where I forgot to leave it plugged in while off on a bit of an extended vacation and it took the cells down too low and killed a couple of them | 01:56 |
| chartreuse | Did the problems happen immediately after that gap? Or later down the line | 01:58 |
| chartreuse | With an unprotected reform you definitly want to unplug the cells if leaving it for too long, as the keyboard controller and standby power supply still draw a small amount of power when off. But with a protected board that's not a problem as it'll disconnect the cells before they get too low and can be damaged | 02:00 |
| - mtm (QUIT: Ping timeout: 240 seconds) (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 02:02 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 02:03 | |
| + mtm (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 02:05 | |
| - mjw (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org) | 02:07 | |
| - cobra (QUIT: Quit: ZNC 1.8.2 - https://znc.in) (~cobra@user/Cobra) | 02:18 | |
| + photomattmills (~photomatt@184-23-21-40.fiber.dynamic.sonic.net) | 02:25 | |
| - photomattmills (QUIT: Quit: Client closed) (~photomatt@184-23-21-40.fiber.dynamic.sonic.net) | 02:32 | |
| + cobra (~cobra@user/Cobra) | 02:33 | |
| chartreuse | josch: Decided to put your Debian stable (backport kernel) image on an sd card to try out and it's booting fine on the imx8mq. Don't see any dmesg errors that aren't normal on the testing image. Though the default editor being micro instead of vi threw me off a bit XD | 03:38 |
| chartreuse | Not used to seeing Apt bug reports in stable though, though I guess I mostly use x86 | 03:45 |
| chartreuse | Oh oops, might be a worthwhile feature on first boot to prompt to expand the partition, just noticed I had no space left | 03:48 |
| sigrid | chartreuse: sounds like a good explanation re hp jack detect | 03:51 |
| sigrid | biggest issue is that not everyone will be able to change the resistor :D | 03:51 |
| sigrid | maybe a future revision could have that updated | 03:53 |
| sigrid | along with better caps cause the bass is very low | 03:53 |
| chartreuse | Yeah, I'm assuming you saw my cap mod a few years back. I've got a couple through hole 330uF 6.3v electrolytics tacked down to the 0603 pads | 03:59 |
| + Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66) | 03:59 | |
| chartreuse | Might be worth trying that 20k midpoint bias setting under linux, but I'd need to change the 220k resistor back to the 47k to know | 04:00 |
| - Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66) | 04:00 | |
| chartreuse | I think the newer motherboards do have more capacitance (I want to say 100uF?) but even that still isn't really enough and I think they're still ceramic which also isn't ideal | 04:01 |
| - nsc (QUIT: Ping timeout: 268 seconds) (~nicolas@220-99-142-46.pool.kielnet.net) | 04:02 | |
| + nsc (~nicolas@213-98-142-46.pool.kielnet.net) | 04:03 | |
| chartreuse | Would be nice to find a way to have it work reliably for people so the dtb changes can be merged into the packages. I guess they could be added as alternate dtbs kinda like how the hdmi and non-hdmi ones are, but that also limits scope | 04:03 |
| mtm | after I flash my Pocket keyboard it stays in programming mode until a hard reset. The new firmware is successfully loaded, but the need to do the reset seems odd. Anyone else seeing this? | 04:21 |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 04:37 | |
| - Gooberpatrol_66 (QUIT: Ping timeout: 268 seconds) (~Gooberpat@user/gooberpatrol66) | 04:37 | |
| - Gooberpatrol66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66) | 05:17 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 05:18 | |
| - sbp (QUIT: Server closed connection) (~sbp@apache/doge/sbp) | 06:13 | |
| + sbp (~sbp@2001:19f0:6800:1102:5400:ff:fe11:39a1) | 06:14 | |
| henesy | chartreuse: i'll take a look later tonight at the board | 06:45 |
| - ptrc (QUIT: Server closed connection) (~ptrc@ptrc.gay) | 07:08 | |
| + ptrc (~ptrc@ptrc.gay) | 07:08 | |
| josch | chartreuse: re "feature on first boot to prompt to expand the partition" oh you mean this one? https://source.mnt.re/reform/reform-system-image/-/merge_requests/43 | 07:08 |
| - Gooberpatrol66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66) | 07:49 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 07:51 | |
| op_4 | minute: awesome, thanks | 08:04 |
| - ehenter (QUIT: Server closed connection) (~ehenter@81-175-159-24.bb.dnainternet.fi) | 09:32 | |
| + ehenter (~ehenter@81-175-159-24.bb.dnainternet.fi) | 09:32 | |
| minute | chartreuse: if i want to replicate the jack detect thing, what's the final device tree snippet? | 09:51 |
| chartreuse | https://source.mnt.re/Chartreuse/reform-debian-packages/-/blob/wm8960-jackdetect/linux/imx8mq-mnt-reform2-hdmi.dts?ref_type=heads | 11:04 |
| chartreuse | I've only done if for the imx8mq, though I think the imx8mp has the same gpio setup | 11:04 |
| josch | minute: are users like paul here https://community.mnt.re/t/odd-power-situation-not-charging/2033/9 supposed to use the delayed charging patch you shared here? | 11:51 |
| * Guest3664 -> mjw | 12:00 | |
| - whereiseveryone (QUIT: Server closed connection) (206ba86c98@2a03:6000:1812:100::2e4) | 13:43 | |
| + whereiseveryone (206ba86c98@2a03:6000:1812:100::2e4) | 13:43 | |
| [tj] | mhoye: chartreuse nxp have an sdk and a lot of documentation for the m4 core | 13:52 |
| - mtm (QUIT: Ping timeout: 256 seconds) (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 14:04 | |
| + mtm (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 14:06 | |
| - ch (QUIT: Ping timeout: 246 seconds) (~ch@user/meow/ch) | 15:04 | |
| + ch (~ch@user/meow/ch) | 15:04 | |
| - Zaba (QUIT: Server closed connection) (80b9b4b35e@2a03:6000:1812:100::116) | 15:19 | |
| + Zaba (80b9b4b35e@2a03:6000:1812:100::116) | 15:19 | |
| sigrid | reform survived first night with no hangs after the change I've made | 15:25 |
| chartreuse | Seems there's a command disparity between the Pocket Reform's keyboard controller and the regular reform's. https://community.mnt.re/t/help-running-kbdgfx/2246/5 The xWBIT command on the pocket seems to require a leading 0x40 to the screen data to send (the raw command byte to the OLED), while the original firmware does not. There's even a bit of a FIXME hack in the function there that was never | 16:01 |
| chartreuse | changed. | 16:01 |
| amospalla | chartreuse: hi, thank you for sending a new kbdgfx.c!, I just tested it, running it with only one parameter does not change keyboard leds, and when running with a second parameter (a bitmap) nothing happens on the OLED. | 16:10 |
| chartreuse | It shouldn't change the leds any just the oled. For the bitmap are you sending one of the specially created raw bitmaps that the example scripts generate or a windows bmp file? It should be the former | 16:12 |
| chartreuse | Running `./kbdgfx /dev/hidraw2` or whatever hidraw port is correct should show the sine demo though | 16:14 |
| amospalla | chartreuse: right, we are only talking about oled, but I'm just trying to be verbose. | 16:14 |
| amospalla | it does not show the demo on my pocket. | 16:14 |
| amospalla | For the bitmap I am using a raw bitmap as per `convert -size 128x32 -background black -font Inter-Bold -pointsize 10 -fill white -gravity center caption:hello -depth 8 -flatten gray:temp.bin` | 16:15 |
| amospalla | At least, that is the original command used on the original reform repository (not the pocket one) to build the bitmap. | 16:16 |
| amospalla | It's size is exactly 4096 bytes, 128 * 32 * 1byte, so I guess that must be raw. | 16:18 |
| chartreuse | Yeah that should be fine. Does the keyboard led demo work on the pocket? Trying to see what's different | 16:18 |
| chartreuse | (The one that draws to the backlight leds) | 16:18 |
| amospalla | chartreuse: no, the keyboard demo does not show (./kbdgfx /dev/hidraw0, there is no other /dev/hidraw*). | 16:19 |
| amospalla | Maybe I sent some garbage by trying things and now the controller does not accept input? Just guessing. | 16:20 |
| chartreuse | Okay so something else is wrong then on the pocket besides that 0x40 byte missing. I wonder if maybe there's a udev rule or such changing the hidraw to something else, or if there's something else broken | 16:20 |
| vkoskiv | My project dealt with udev rules, I have the files handy | 16:20 |
| amospalla | I openend the oled menu, and did a keyboard reset on it. Dmesg shows usb disconnect, followed by it connecting again (input,hidraw0). | 16:23 |
| amospalla | /dev/hidraw0 has been re-created, I know because I set 0777 to it and after reset it has 0644 again. | 16:24 |
| vkoskiv | I have this in my refmon project: | 16:25 |
| vkoskiv | cat config/usr/lib/udev/rules.d/90-mnt-reform2-hidraw.rules | 16:25 |
| vkoskiv | SUBSYSTEM=="hidraw", ATTRS{idVendor}=="03eb", ATTRS{manufacturer}=="MNT", MODE="0666" | 16:25 |
| chartreuse | That's for the reform2, is there similar rules for the pocket or does the same apply? | 16:26 |
| vkoskiv | That just gets copied in the install target, and it's been working well. Though a better approach would be to have a group that can access the OLED | 16:26 |
| vkoskiv | I'm not sure, I only have the full size Reform | 16:26 |
| chartreuse | amospalla: If you leave something showing on the oled like the status, then run `echo -n 'xWCLR' | sudo tee /dev/hidraw0` does the display clear? | 16:27 |
| amospalla | chartreuse: no, it does not clear. | 16:27 |
| amospalla | reform-tools package has a 99-reform.rules, but it only adds a rule for the sound card. | 16:29 |
| minute | josch: yes! | 16:30 |
| minute | regarding OLED stuff, i'm a bit too busy with other stuff at the moment but will look into it after all that business (unless you figure it out first) | 16:32 |
| chartreuse | Seems like somehow it's not responding to any hidraw commands which is a bit weird, something must have broken in a patch or such since I presume the demos were working before | 16:33 |
| amospalla | Thank you for your help :) | 16:34 |
| chartreuse | One thing I'm seeing is that the pocket keyboard is checking that | 16:41 |
| chartreuse | if (report_type == 2) { | 16:41 |
| chartreuse | While the regular one doesn't seem to care about the report type. https://www.kernel.org/doc/Documentation/hid/hidraw.txt mentions that the first byte to wrie should be the report type, but on the main one if I try sending a \0 or \02 it doesn't work | 16:43 |
| chartreuse | Maybe try `echo -ne '\02xWCLR' | sudo tee /dev/hidraw0` and see if that has an effect? | 16:43 |
| amospalla | chartreuse: with \02x has no effect either. | 16:45 |
| sigrid | at some point kbd fw for reform2 did not have clearing working, see https://source.mnt.re/sigrid/reform/-/commit/52551df3d9f69663846ee298d71693cf74095556 | 16:47 |
| sigrid | idk if pocket one had the same issue or not | 16:47 |
| chartreuse | I was just using it as a different test, but maybe try xLOGO then, and \02xLOGO | 16:49 |
| amospalla | chartreuse: no luck with LOGO either. | 16:54 |
| mtm | after I flash my Pocket keyboard it stays in programming mode until a hard reset. The new firmware is successfully loaded, but the need to do the reset seems odd. Anyone else seeing this? | 16:55 |
| sigrid | does it have a programming switch? is it still in programming position? | 16:56 |
| mtm | hmm, didn't think the pocket worked that way. let me check | 16:57 |
| chartreuse | I'm fairly sure I left my programming switch on on my reform and it's still fine. I did that when I was writing the original power save code for it and I don't think I flicked it back since I could then hit the programming button from under the bezel without taking everything apart | 16:59 |
| mtm | seems the pocket is using a soft switch (from the OLED menu you hit 'x' to put it in programming mode) | 16:59 |
| mtm | I -am- tempted to make a small hole in the keyboard top plate so I can hit the keyboard reset button with a paperclip | 17:01 |
| mtm | but I'll resist for now: don't want to mar the awesome finish | 17:02 |
| chartreuse | I believe I could hit it with a plastic spudger on the reform2 without taking the bezel off but I'd need to take it off to know the spot again to do so | 17:03 |
| chartreuse | Oh wait I see it, right above F4 | 17:03 |
| chartreuse | (At least on the first model keyboard) | 17:04 |
| mtm | yes, above F3 there is a momentary contact 'prog' button, probably useful if the firmware gets borked and can't put itself into programming mode. Also, I assume that is used to load the firmware during build out | 17:09 |
| + reform1046 (~yuval@2001:871:251:b63f::4f3) | 17:34 | |
| reform1046 | hmm | 17:34 |
| reform1046 | q | 17:34 |
| reform1046 | q | 17:34 |
| - reform1046 (QUIT: Client Quit) (~yuval@2001:871:251:b63f::4f3) | 17:34 | |
| amospalla | chartreuse: I resetted my pocket with the physical switch. Now I can send xLRGB, and kbdgfx demo from pocket repository works. | 17:37 |
| amospalla | I suspect something I sent to it in some test, broke it. | 17:40 |
| amospalla | And needed a reset. | 17:40 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 17:44 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 18:19 | |
| * mjw -> Guest6755 | 18:21 | |
| - Guest6755 (QUIT: Killed (tantalum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 18:21 | |
| * mark_ -> mjw | 18:21 | |
| + Guest6755 (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 18:22 | |
| josch | vagrantc: how is your experience with the DC ROMA so far? | 19:06 |
| + gustav28 (~gustav@c-1134524e.019-141-67626730.bbcust.telenor.se) | 20:02 | |
| - xktr (QUIT: Quit: leaving) (~xktr@user/xktr) | 20:26 | |
| vagrantc | josch: minimal experience | 20:29 |
| + xktr (~xktr@user/xktr) | 20:37 | |
| - hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu) | 21:03 | |
| + hairu (m-uotkmd@user/hairu) | 21:05 | |
| - ex-parrot (QUIT: Quit: _b) (~fincham@user/ex-parrot) | 21:49 | |
| + ex-parrot (~fincham@user/ex-parrot) | 21:50 | |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-1134524e.019-141-67626730.bbcust.telenor.se) | 22:15 | |
| + Jonas (~Jonas@82-65-231-86.subs.proxad.net) | 22:20 | |
| Jonas | Hi there, new Pocket reform owner here. It's non booting and I'm not sure how I can troubleshoot it. I was able to boot it upon,g reception and access Debian for about 5 minutes and after that it shut itself of abruptly and I wasn't able to boot it again. Both batteries are 3.8V+, and I'm not sure how I can see that their are charging since the OLED isn't powering on either | 22:25 |
| Jonas | If anyone wants to help me troubleshoot it I'm all ears! | 22:26 |
| op_4 | Jonas: low hanging fruit, are you sure the suspend switch on the side is in the "on" position? | 22:30 |
| Jonas | Also the manual isn't clear about the position of the switch to allow charging of the batteries | 22:31 |
| Jonas | thanks for you feedback @op_4 | 22:31 |
| Jonas | or messages crossed, I'm not sure what's the on position | 22:32 |
| Jonas | our messages* | 22:32 |
| op_4 | try both :) | 22:32 |
| op_4 | afair charging is only possible in the "on" position | 22:33 |
| + gustav28 (~gustav@c-1134524e.019-141-67626730.bbcust.telenor.se) | 22:33 | |
| Jonas | I guess the on position is the position where the switch close the circuit? I can test that | 22:34 |
| mtm | the switch on the side of left side of the display needs to be "up" when the lid is open. You should see a pink-ish glow coming from the right side of the display if the batteries are charging | 22:41 |
| Jonas | thanks @mtm. No pinkish glow sadly | 22:46 |
| Jonas | do you know if the battery controller (U1) should be running hot? It's currently at 126°C (thermal camera) | 22:46 |
| mtm | that is excessive | 22:47 |
| mtm | I would remove power immediatley | 22:47 |
| mtm | unless you meant °F | 22:48 |
| Jonas | That's what I was thinking | 22:50 |
| Jonas | it's Celsius sadly | 22:50 |
| vkoskiv | U1 is the processor slot, according to the schematics | 22:51 |
| Jonas | I'm looking at the datasheet and the temperature junction is quite high at aroiund 260°C but still I never saw a chip running that high | 22:51 |
| vkoskiv | I was just hunting for that Tj value myself too :D | 22:52 |
| Jonas | U1 on the charging board | 22:52 |
| mtm | each scematic has it's own U1 :) | 22:53 |
| vkoskiv | That would explain it. | 22:53 |
| Jonas | https://www.monolithicpower.com/en/documentview/productdocument/index/version/2/document_type/Datasheet/lang/en/sku/MP2650GV/document_id/9664/ | 22:54 |
| Jonas | MP2650 datasheet | 22:54 |
| vkoskiv | Ah, that makes sense now, it's on a separate board on the Pocket | 22:54 |
| vkoskiv | I was just looking at the motherboard schematic | 22:54 |
| Jonas | junction temp is 150°C (260°C is soldering temp) | 22:55 |
| mtm | "Operating junction temp (TJ).....-40°C to +125°C" | 22:55 |
| vkoskiv | Chips of this modern age almost always have a high temp cutoff where they shut down to prevent damage though, I would think? | 22:55 |
| Jonas | ok so do you think mine is busted? | 22:56 |
| mtm | at any rate, no way should it be getting that hot normally | 22:56 |
| Jonas | ok | 22:56 |
| Jonas | is it possible to power the pocket without the charging circuit/batteries? | 22:57 |
| mtm | not sure | 22:57 |
| Jonas | ok I'll investigate | 22:57 |
| mtm | anecdotally, even when charging with completely flat batteries, the bottom of the case was barely warm to the touch | 22:58 |
| Jonas | the bottom of the case is not hot, just the charging chip (as the pocket wasn't booting I've opened both side and lokk at it with my thermal camera) | 22:59 |
| mtm | yeah, later I'll see what temp. mine gets to (I only have an IR thermometer, but it should get me in the ball park). I'll let the batteries drain for now | 23:01 |
| Jonas | ok. This is frustrating after all these years of waiting but at least there's schematics and a community so I can see what is wrong with my unit. It be interesting to try with another charging PCB to see if the fault is here of elsewhere. | 23:03 |
| mtm | I mean, looking at the charts on page 14 of the data sheet for the chip seems to indicate that it will operate at those temps. so maybe its okay? | 23:03 |
| Jonas | Do anyone here knows if there's an advanced manual to help troubleshooting? I'm seeing all these test points but I didn't find any procedure to use them to know whether a board is ok or not | 23:04 |
| Jonas | that be an hell of a documentation for sure | 23:05 |
| mtm | but if it's dumping that much current through it I would expect to at least see some indication (light) that it's charging | 23:05 |
| Jonas | I'm going to reopen the CPU side, do you know where the led is? | 23:07 |
| Jonas | On the 5minutes hte pocket worked I didn't notice any glowing led | 23:08 |
| Jonas | s/hte/the | 23:09 |
| Jonas | is it D10? if yes it's not glowing while the pocket is plugged in with switch posered on (circuit opened) | 23:13 |
| Jonas | powered* | 23:13 |
| Jonas | I tried with two USB-PD charger from Anker, one 65W and a 100W one (Gan charger A2343). The cable I'm using is from my USB-PD Pinecil and it's charging well my Fairphone and all USB-PD devices I'm throwing at it | 23:15 |
| josch | Jonas: what continent are you on? Might be easiest to send it to MNT for repair? | 23:30 |
| Jonas | Europe | 23:32 |
| Jonas | I've opened a support ticket, maybe I've received a defective unit but I'd like to be sure before sending it back | 23:34 |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-1134524e.019-141-67626730.bbcust.telenor.se) | 23:41 | |
| - Jonas (QUIT: Ping timeout: 256 seconds) (~Jonas@82-65-231-86.subs.proxad.net) | 23:51 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!