| - chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 00:10 | |
| - paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@107.159.213.145) | 03:09 | |
| - 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 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.5.33) | 05:50 | |
| + Ar|stote|is (~linx@149.210.5.33) | 05:51 | |
| + lanodan (~lanodan@2a01:e0a:d6:9930::35) | 06:19 | |
| - lanodan (QUIT: Quit: WeeChat 4.5.2) (~lanodan@2a01:e0a:d6:9930::35) | 06:44 | |
| + lanodan (~lanodan@2a01:e0a:d6:9930::35) | 06:48 | |
| + d_m (~d_m@user/d-m/x-5109880) | 07:26 | |
| minute | gsora: i'm sorry to hear it. we can send a replacement screen of course | 09:11 |
|---|---|---|
| minute | murphnj: standby switch needs to be on for flashing | 09:11 |
| minute | murphnj: or disconnected from the motherboard, for that matter | 09:12 |
| minute | kfx: oh ok? but how does edk2 know that you have a reform2? | 09:12 |
| minute | ohh this is talking about dtb override functionality https://github.com/edk2-porting/edk2-rk3588/releases/tag/v1.1 | 09:15 |
| minute | > Additional base DTB locations: custom path configurable in the setup menu + \dtb and \dtb\rockchip. | 09:15 |
| josch | i also managed to prevent gnome from shutting down at 0% -- one needs AllowRiskyCriticalPowerAction=true | 09:58 |
| + gustav28 (~gustav@c-78-82-53-92.bbcust.telenor.se) | 10:02 | |
| gsora | minute: that would be great. I sent a video and a photo detailing the issue to support@ in the meantime. would it be the entire upper screen assembly or just the panel? what would you think might’ve happened to the screen connection to trigger the flashy behavior? | 10:06 |
| + andreas-e (~Andreas@2001:861:c4:f2f0::c64) | 10:13 | |
| - andreas-e (QUIT: Client Quit) (~Andreas@2001:861:c4:f2f0::c64) | 10:13 | |
| gsora | fwiw | 10:17 |
| gsora | oof, misclick! anyway, wanted to say my PD-enabled power bank charges the reform just fine! it reports 2.1A at 2V | 10:17 |
| gsora | no wait, 20v! | 10:18 |
| - wiedi (QUIT: Quit: ^Z) (~wiedi@ip5f581498.dynamic.kabel-deutschland.de) | 10:36 | |
| + wiedi (~wiedi@ip5f581498.dynamic.kabel-deutschland.de) | 10:45 | |
| CephonAltera | josch: where did you set that setting? | 10:48 |
| josch | CephonAltera: in /etc/UPower/UPower.conf -- I'm in the process of writing a longer forum post | 10:49 |
| - Ar|stote|is (QUIT: Read error: Connection reset by peer) (~linx@149.210.5.33) | 11:40 | |
| + Ar|stote|is (~linx@149.210.5.33) | 11:47 | |
| - gsora (QUIT: Read error: Connection reset by peer) (~gsora@user/gsora) | 11:51 | |
| + gsora (~gsora@user/gsora) | 11:59 | |
| + dook_ (c9db4a6425@2a03:6000:1812:100::1222) | 12:04 | |
| + bail_ (585c46d254@2a03:6000:1812:100::f91) | 12:05 | |
| - Guest3230 (QUIT: Ping timeout: 260 seconds) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 12:05 | |
| + iank_ (~iank@fsf/staff/iank) | 12:05 | |
| + sadplan (sadplan@tilde.club) | 12:06 | |
| + pinsl_ (c01623b131@2a03:6000:1812:100::121d) | 12:06 | |
| + jfred-linode_ (quassel@libera/sponsor/jfred) | 12:07 | |
| + d_m_ (~d_m@vein.plastic-idolatry.com) | 12:08 | |
| + frickler_ (~jens@user/frickler) | 12:08 | |
| + anuejn_ (~quassel@46.101.193.235) | 12:08 | |
| - iank (QUIT: *.net *.split) (~iank@fsf/staff/iank) | 12:14 | |
| - BoostisBetter (QUIT: *.net *.split) (4a410829d7@irc.cheogram.com) | 12:14 | |
| - SavagePeanut (QUIT: *.net *.split) (59eaa45ac7@irc.cheogram.com) | 12:14 | |
| - d_m (QUIT: *.net *.split) (~d_m@user/d-m/x-5109880) | 12:14 | |
| - anuejn (QUIT: *.net *.split) (~quassel@46.101.193.235) | 12:14 | |
| - sad_plan (QUIT: *.net *.split) (sadplan@tilde.club) | 12:14 | |
| - dook (QUIT: *.net *.split) (c9db4a6425@2a03:6000:1812:100::1222) | 12:14 | |
| - pinsl (QUIT: *.net *.split) (c01623b131@2a03:6000:1812:100::121d) | 12:14 | |
| - bail (QUIT: *.net *.split) (585c46d254@2a03:6000:1812:100::f91) | 12:14 | |
| - Flax_ (QUIT: *.net *.split) (d8f5445b71@2a03:6000:1812:100::1a1) | 12:14 | |
| - jfred-linode (QUIT: *.net *.split) (quassel@libera/sponsor/jfred) | 12:14 | |
| - frickler (QUIT: *.net *.split) (~jens@user/frickler) | 12:14 | |
| * bail_ -> bail | 12:14 | |
| * dook_ -> dook | 12:14 | |
| * pinsl_ -> pinsl | 12:14 | |
| + Flax_ (d8f5445b71@2a03:6000:1812:100::1a1) | 12:19 | |
| + SavagePeanut (59eaa45ac7@irc.cheogram.com) | 12:24 | |
| + chomwitt (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 13:15 | |
| + arminweigl_ (~arminweig@sourcehut/user/arminweigl) | 13:20 | |
| - arminweigl (QUIT: Ping timeout: 252 seconds) (~arminweig@sourcehut/user/arminweigl) | 13:21 | |
| * arminweigl_ -> arminweigl | 13:21 | |
| - chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 13:23 | |
| + chomwitt (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 13:33 | |
| - qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit) | 13:45 | |
| * frickler_ -> frickler | 13:48 | |
| + paperManu (~paperManu@107.159.213.145) | 13:56 | |
| + qbit (~qbit@user/qbit) | 14:00 | |
| - voltagex (QUIT: Killed (NickServ (GHOST command used by voltagex__!~voltagex@user/voltagex))) (bb9d16d177@user/voltagex) | 14:03 | |
| + voltagex_ (bb9d16d177@user/voltagex) | 14:05 | |
| - chomwitt (QUIT: Ping timeout: 245 seconds) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 14:19 | |
| + chomwitt (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 15:23 | |
| + BoostisBetter (4a410829d7@irc.cheogram.com) | 16:00 | |
| - svp (QUIT: Quit: Gateway shutdown) (~svp@host-79-7-240-189.business.telecomitalia.it) | 16:05 | |
| - yuu (QUIT: Ping timeout: 244 seconds) (sid267332@ilkley.irccloud.com) | 16:07 | |
| + yuu (sid267332@id-267332.ilkley.irccloud.com) | 16:11 | |
| + svp (~svp@host-79-7-240-189.business.telecomitalia.it) | 16:23 | |
| - svp (QUIT: Quit: Gateway shutdown) (~svp@host-79-7-240-189.business.telecomitalia.it) | 16:31 | |
| + svp (~svp@host-79-7-240-189.business.telecomitalia.it) | 16:34 | |
| + qbit_ (~qbit@user/qbit) | 17:20 | |
| + chomwitt1 (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 17:24 | |
| - svp (QUIT: *.net *.split) (~svp@host-79-7-240-189.business.telecomitalia.it) | 17:28 | |
| - BoostisBetter (QUIT: *.net *.split) (4a410829d7@irc.cheogram.com) | 17:28 | |
| - chomwitt (QUIT: *.net *.split) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 17:28 | |
| - qbit (QUIT: *.net *.split) (~qbit@user/qbit) | 17:28 | |
| - SavagePeanut (QUIT: *.net *.split) (59eaa45ac7@irc.cheogram.com) | 17:28 | |
| + svp (~svp@host-79-7-240-189.business.telecomitalia.it) | 17:36 | |
| CephonAltera | I have made progress on my journey to run LXDE on the pocket reform under Xorg. To continue from my previous message. It seems like the cause of the weird mouse bug is me having a second monitor connected via micro-hdmi. | 17:53 |
| + BoostisBetter (4a410829d7@irc.cheogram.com) | 18:28 | |
| * sadplan -> sad_plan | 18:33 | |
| - BoostisBetter (QUIT: *.net *.split) (4a410829d7@irc.cheogram.com) | 18:42 | |
| - L29Ah (QUIT: Read error: Connection timed out) (~L29Ah@wikipedia/L29Ah) | 18:47 | |
| + BoostisBetter (4a410829d7@irc.cheogram.com) | 18:55 | |
| murphnj | @minute, Thanks! I'll do that later when I have a chance, see if I can finally get it back working again. | 18:57 |
| gsora | is there a suggested place to attach the WiFi antenna plastic thingy to? | 19:14 |
| josch | gsora: you mean the transparent acrylic sheet with the singular hole at the corner? | 19:16 |
| gsora | yup | 19:17 |
| gsora | I think… I figured out why there’s a standoff in the envelope lol | 19:17 |
| minute | gsora: probably the panel | 19:21 |
| minute | gsora: the panel answer was to an earlier question | 19:22 |
| minute | gsora: about the standoff yeah, i think that is described in the rcore manual. | 19:22 |
| gsora | ah, was looking in the operator manual! | 19:23 |
| gsora | wooo my mpcie adapted mediatek WiFi chip works! | 19:33 |
| gsora | pushes close to 1gbps, nice | 19:33 |
| josch | wow o0 | 19:41 |
| gsora | yeah! not bad for a 40 bucks | 19:45 |
| gsora | including a m2 to mpcie adapter | 19:46 |
| gsora | re: display, I think the issues are two: the cable might be bad, and the panel might be faulty | 19:46 |
| gsora | also, the display logic thingy gets quite hot to the touch | 19:48 |
| gsora | here’s what | 19:50 |
| gsora | happens: https://files.catbox.moe/n2lysc.mov | 19:50 |
| josch | wow that video kills the a311d -- 100% on all six cores and it's still a slideshow | 19:55 |
| gsora | for whatever reason my phone decided it was a good idea to record hdr with Dolby vision | 19:59 |
| minute | gsora: noice @ wifi | 19:59 |
| josch | gsora: doesn't help that it's 3840x2160 :D | 20:00 |
| gsora | that as well haha | 20:01 |
| - Gooberpatrol_66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66) | 20:14 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 20:19 | |
| josch | minute: This now has EFI booting via systemd-boot-efi: https://source.mnt.re/reform/reform-system-image/-/merge_requests/133 | 20:36 |
| josch | minute: try running mkimage with --arch=amd64 --boot=efi reform-system-any | 20:36 |
| minute | josch: awesome!! | 20:39 |
| * qbit_ -> qbit | 20:56 | |
| + LainIwakura (~LainIwaku@user/LainIwakura) | 21:10 | |
| - LainIwakura (QUIT: Client Quit) (~LainIwaku@user/LainIwakura) | 21:12 | |
| + LainIwakura (~LainIwaku@user/LainIwakura) | 21:16 | |
| + CephonAltera_ (~cephonalt@5.180.61.56) | 21:19 | |
| - LainIwakura (QUIT: Ping timeout: 272 seconds) (~LainIwaku@user/LainIwakura) | 21:22 | |
| - CephonAltera (QUIT: Ping timeout: 260 seconds) (~cephonalt@user/CephonAltera) | 21:22 | |
| - CephonAltera_ (QUIT: Remote host closed the connection) (~cephonalt@5.180.61.56) | 21:30 | |
| - wiedi (QUIT: Read error: Connection reset by peer) (~wiedi@ip5f581498.dynamic.kabel-deutschland.de) | 21:40 | |
| + wiedi (~wiedi@2a01:138:a015:15:a173:8d9:2f2f:5ace) | 21:47 | |
| potatoespotatoes | hi, totally silly question, but if I am flashing uboot onto the pocket+rk3588, does the boot partition go onto mmcblk0boot0 or mmcblk0boot1? | 21:47 |
| potatoespotatoes | where can I read more about what these devices are fore? | 21:48 |
| murphnj | Having trouble building firmware, very frustrating. | 21:49 |
| potatoespotatoes | murphnj what are you running into? I've been doing a bit of that, of late | 21:50 |
| murphnj | Are you on the forums? I've just posted all the details there. I can repeat here if needed. | 21:52 |
| potatoespotatoes | can you drop a link here? | 21:53 |
| potatoespotatoes | "may have made a bad mistake"? | 21:53 |
| murphnj | https://community.mnt.re/t/may-have-made-a-bad-mistake/3420 | 21:53 |
| murphnj | That would be the one. | 21:54 |
| murphnj | I'm way down at the bottom of that thread at this point. | 21:54 |
| murphnj | Following the directions in the handbook. | 21:55 |
| murphnj | I don't seem to have the PICO_SDK_PATH set. | 21:55 |
| potatoespotatoes | okay, cool. I'm caught up | 21:57 |
| potatoespotatoes | it's been a while so I won't write a forum reply, but the quick answer to the PICO_SDK | 21:58 |
| potatoespotatoes | PATH issue is that you need to clone... | 21:58 |
| potatoespotatoes | https://github.com/raspberrypi/pico-sdk | 21:58 |
| potatoespotatoes | it has been a long time since I last did this, but happy to stumble through it with you for a bit | 21:59 |
| potatoespotatoes | set the clone path to that environment variable, | 22:00 |
| potatoespotatoes | I was using the build scripts from https://source.mnt.re/reform/reform/-/blob/master/reform2-keyboard4-fw/build.sh?ref_type=heads#L3 | 22:01 |
| potatoespotatoes | which does set the path directly of where the cloned pico-sdk repo should live | 22:01 |
| potatoespotatoes | RE: "this CAN be run from an x86_64 machine, right?" IIRC I did flash this all on an x86 machine | 22:02 |
| potatoespotatoes | but you will probably run into a dependency issue very quickly if this is not the case. | 22:03 |
| potatoespotatoes | I can't imagine rpi development being locked to arm64. that would be a bit nuts | 22:03 |
| murphnj | This isn't the keyboard firmware any more. It's the system since I appear to have upgraded the keyboard firmware over the system. I have the thing taken apart, and I'm in the internal USB connection. | 22:04 |
| murphnj | I don't understand why the directions don't mention that the raspi sdk has to be cloned as well. I would think that the "install-fw-dependencies.sh" would get that, and if not give a warning, and/or instructions to do so. | 22:05 |
| murphnj | I feel like an idiot. I'm not experienced with this specifically, but not new to Linux. I can follow instructions, and learn on the way, but this seems a bit much. | 22:06 |
| murphnj | There is a pico-sdk directory in the cloned directory, but it isn't in the right env variable? | 22:07 |
| murphnj | It's the pico sdk. | 22:07 |
| potatoespotatoes | Hmm... it looks like it might be fetched directly via cmake: https://source.mnt.re/search?search=pico-sdk&nav_source=navbar&project_id=6&group_id=7&search_code=true&repository_ref=master | 22:08 |
| murphnj | It's in the pocket-reform directory. | 22:08 |
| potatoespotatoes | but back when I did this (like ~6-8months ago) I recall some weirdness and having to do that step by hand | 22:09 |
| murphnj | there is a pico_sdk_init.cmake, does that need to be run, or something? | 22:10 |
| potatoespotatoes | wait, do you have the repo placed in /usr/src/pico-sdk, then? | 22:11 |
| murphnj | no. | 22:11 |
| murphnj | I think that the install_depenencies script got it, but didn't finish the job, I guess? | 22:11 |
| potatoespotatoes | yeah, it looks like install-fw-dependencies does do this step: https://source.mnt.re/reform/pocket-reform/-/blob/main/install-fw-dependencies.sh#L26-31 | 22:12 |
| potatoespotatoes | (I was in the wrong repo) | 22:12 |
| potatoespotatoes | it also sets the correct tags | 22:12 |
| potatoespotatoes | so possibly your script crashed halfway | 22:13 |
| murphnj | Seemed like it worked OK. I can delete the directory, and redo the whole thing. Not like it has worked anyway. | 22:13 |
| potatoespotatoes | note that I'm asking about /usr/src/pico-sdk because of this line: | 22:14 |
| potatoespotatoes | https://source.mnt.re/reform/pocket-reform/-/blob/main/pocket-reform-sysctl-fw/build.sh?ref_type=heads#L3 | 22:14 |
| potatoespotatoes | no need to delete anything. I think the main issue is you just need to line up this hardcoded path with where pico-sdk actually got cloned | 22:14 |
| + SavagePeanut (59eaa45ac7@irc.cheogram.com) | 22:15 | |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-53-92.bbcust.telenor.se) | 22:15 | |
| murphnj | Not sure why they would do that. I had updated my firmware on it before, (fropm the pocket itself) so maybe they make some assumptions based on how the pocket is set up. | 22:15 |
| potatoespotatoes | putting things in /usr/src seems very odd to me, too. that's a very specific location with different OSs recommending different permissions in there | 22:15 |
| murphnj | I'll change it and give it a shot. | 22:16 |
| potatoespotatoes | oh, yeah -- maybe that's a debian thing. definitely not a universal rec | 22:16 |
| murphnj | This is on debian. | 22:17 |
| murphnj | hm. Changed the directory in build.sh to where that directory is located, and I get the same error. | 22:19 |
| potatoespotatoes | can you make sure you are using an absolute path? | 22:21 |
| murphnj | I am. When I do an echo pn PICO_SDK_PATH, it showed nothing. (Of course I'm not in the script) I just copied that out, and ran the line, and now it shows. I'm going to try to run again. | 22:22 |
| murphnj | Nope, same exact error. | 22:22 |
| murphnj | (This is where my env variable experience in bash is failing me.) | 22:22 |
| potatoespotatoes | next thing i would do is start littering cmake with messages to see where things fail | 22:23 |
| potatoespotatoes | it looks like cmake loads https://source.mnt.re/reform/pocket-reform/-/blob/main/pocket-reform-sysctl-fw/lib/pico_sdk_import.cmake?ref_type=heads | 22:23 |
| murphnj | It really appears that the docs are leaving something to be desired. | 22:23 |
| potatoespotatoes | haha, that's just open source software for you : P | 22:24 |
| potatoespotatoes | there's always places for improvement | 22:24 |
| potatoespotatoes | but we build it together and make things better! it's just sometimes a bit slow to get to a really good UX | 22:25 |
| murphnj | I'm really felling like an f-ing idiot. | 22:25 |
| potatoespotatoes | haha, you are not alone | 22:26 |
| potatoespotatoes | So looking at this code again. I think that pico_sdk_import.cmake is really the culprit. If the last `include` statement succeeds, you should get the pico-sdk's functions and compilation should begin | 22:28 |
| potatoespotatoes | do you see any of the messages on lines 8,13,or 18? | 22:29 |
| murphnj | But that doesn't seem to define it within itself, looks like it wants to get it from build.sh. | 22:29 |
| potatoespotatoes | at this point I would just c/p the ./build.sh steps into a terminal | 22:29 |
| murphnj | Will try. | 22:30 |
| potatoespotatoes | yeah, Cmake can look up environment variables | 22:30 |
| potatoespotatoes | (I mean, it will look up variables in ENV if they are not defined) | 22:31 |
| murphnj | at the "cmake .." line, I get the exact same error. | 22:31 |
| zeha | debian's pico-sdk-source package puts the pico-sdk into /usr/src, but you can pick any other path | 22:31 |
| murphnj | but when I "echo $PICO/SDK_PATH" I get the correct directory. | 22:32 |
| potatoespotatoes | what directory are you in? I am expecting it to be... | 22:33 |
| zeha | can you trash the build directory, and do the steps manually? | 22:33 |
| potatoespotatoes | pocket-reform/pocket-reform-sysctl-fw/build | 22:33 |
| zeha | i.e. rm -rf build ; mkdir build ; cd build ; cmake .. | 22:33 |
| murphnj | sure. | 22:34 |
| murphnj | Seems to have run. WTF?? | 22:35 |
| murphnj | Did it hang onto a remnant of a partial earlier run? | 22:35 |
| zeha | certainly possible | 22:35 |
| zeha | cmake has a cache etc | 22:35 |
| potatoespotatoes | oooh! yes -- nuke that cache! | 22:36 |
| murphnj | Ok, give me a couple of minutes, I need to re-prep the board to be flashed. Then I'll do the next step, and see if it flashes. (I don't trust past me, will make sure all of the jumpers and switches are in the right position.) | 22:36 |
| zeha | do you need a special build or wouldnt a known good build be better? | 22:38 |
| potatoespotatoes | aside: does anyone know which device is eMMC on the rk3588-pocket? | 22:42 |
| potatoespotatoes | omg finally found it: https://source.mnt.re/reform/reform-tools/-/blob/main/machines/MNT%20Pocket%20Reform%20with%20RCORE%20RK3588%20Module.conf#L10 | 22:44 |
| murphnj | zeha: What do you mean? I cloned the repo as outlined in the instructions, I assumed that would do what it's supposed to. | 22:44 |
| zeha | you can, but also you can download the latest uf2 from https://source.mnt.re/reform/pocket-reform/-/jobs/9937/artifacts/browse/pocket-reform-sysctl-fw/build/ | 22:46 |
| zeha | potatoespotatoes: was gonna link you that, but i was slow :D | 22:47 |
| murphnj | Looks like I don't see the sysctl.uf2 in the build directory for the actual flashing step. | 22:49 |
| potatoespotatoes | zeha: ugh, I'm just in this horrible nightmare of building shitty images that I think are working (for guix support), but apparently I've just been loading images from eMMC. | 22:49 |
| potatoespotatoes | big facepalm moment over here | 22:49 |
| zeha | hmm? | 22:50 |
| murphnj | I'll try just running build.sh again from the right location, and see if it spits it out. | 22:50 |
| zeha | murphnj: if you cmake .. && make, it should make a sysctl.uf2 | 22:50 |
| murphnj | I did the ./build.sh, and it seems to have generated it. | 22:51 |
| murphnj | I also see the board from the laptop with lsusb, so, let's try the flash again. | 22:51 |
| murphnj | Hm, says it worked. I'll have to re-assemble it, and see if it lives again. | 22:52 |
| potatoespotatoes | okay, I have to run -- best of luck, murphnj! | 22:53 |
| murphnj | thanks! | 22:59 |
| murphnj | Well, it doesn't appear to be powering on. | 22:59 |
| murphnj | The light on the charging board appears to be purple, when I plug in a charging cable. | 23:02 |
| murphnj | It's blue when unplugged. | 23:02 |
| murphnj | Oh, nvm, it appears to be on. | 23:03 |
| murphnj | It is on, working with external keyboard. Pregress! | 23:05 |
| minute | zeha: ah yeah there seems to be an "apt-get --update" in the install-fw-dependencies script | 23:06 |
| murphnj | No internal keyboard, but an external is working. | 23:06 |
| minute | (instead of apt-get update) | 23:06 |
| murphnj | That's OK, as it turns out, with a sufficiently new version of apt. | 23:06 |
| minute | oh ok | 23:07 |
| murphnj | This has been a bit of a long road so far. | 23:07 |
| murphnj | Now I have to try to flash the keyboard, which is how I bricked it in the first place. | 23:07 |
| zeha | yeah it wants a new enough apt; otoh i'm now not sure which pico-sdk the official builds use | 23:07 |
| zeha | need to look at a build log | 23:07 |
| murphnj | I'm a little nervous that the keyboard is dead. I wasn't able to flash it successfully. | 23:09 |
| murphnj | If the keyboard isn't responsive, and I can't see the menu, is there a way to get it into programming mode? | 23:11 |
| murphnj | "No accessible devices in BOOTSEL were found on bus 1. | 23:13 |
| zeha | where are you running picotool? | 23:13 |
| zeha | "bus 1" looks sus | 23:13 |
| murphnj | From the pocket itself. I may shut it down, toggle the power, and see if it responds. | 23:14 |
| zeha | can you paste lsusb output first? | 23:14 |
| murphnj | I'm following the keyboard/trackball firmware instrcutions int he handbook, but with the keyboard unresponsive, I can't get into programming mode, probably why it isn't working. | 23:14 |
| murphnj | I'll post the lsusb output in the forum, if you can check there. | 23:20 |
| zeha | heh | 23:23 |
| zeha | yeah you have two rp2040 thinking they are sysctls | 23:24 |
| murphnj | Any way o tell them apart? | 23:24 |
| murphnj | (to) | 23:24 |
| zeha | i think the one on bus 3 is the real sysctl, but not sure. i'll check mine | 23:28 |
| zeha | schematics suggest thats probably right | 23:31 |
| murphnj | ok, trying bus 3 | 23:36 |
| murphnj | same error, but bus 3 | 23:37 |
| zeha | bus 3 (probably) has the real sysctl, so you dont want to flash the keyboard fw into that | 23:37 |
| zeha | and: the newer firmware no longer identifies itself as a generic rp2040. you need to put it into flash mode | 23:38 |
| zeha | let me see how to do that with reform-mcu-tool | 23:38 |
| murphnj | Sorry, had just stepped out to grab something for dinner, did not read fully. Good that it didn't flash, then. | 23:38 |
| murphnj | The original problem was flashing the keyboard firmware, so I likely messed something up there. | 23:39 |
| zeha | not sure reform-mcu-tool can deal with this status :/ | 23:40 |
| zeha | hm | 23:42 |
| zeha | it might work | 23:42 |
| zeha | so you could try `reform-mcu-tool bootsel pocket-sysctl-1.0` and then see with `lsusb` if the sysctl previously listed on bus 1 is gone | 23:43 |
| zeha | if yes, then you can use picotool load ... | 23:43 |
| murphnj | i"ll try | 23:44 |
| zeha | if no, run `reform-mcu-tool reset rp2040-boot` to get the rp2040 back into sysctl mode | 23:44 |
| murphnj | gave a bunch of errors. | 23:46 |
| murphnj | did I need to sudo that reform..... command? | 23:48 |
| zeha | ah probably | 23:49 |
| murphnj | the first one? | 23:49 |
| murphnj | will redo. | 23:49 |
| murphnj | seems to have worked. | 23:50 |
| murphnj | the one on bus3 identifies as Raspberry Pi rp2 boot. | 23:50 |
| zeha | given thats likely the actual sysctl, you dont want to flash keyboard fw into that | 23:51 |
| zeha | maybe rerun reform-mcu-tool bootsel pocket-sysctl-1.0 | 23:51 |
| zeha | and then the one on bus1 should also switch into boot mode | 23:51 |
| murphnj | So, if I try to do the one on bus1, it fails, could it not be in programming mode? How can I get it in if it is unresponsive? | 23:53 |
| murphnj | Is there a way to check that the system FW is on the system controller? | 23:54 |
| zeha | if lsusb shows "Pocket Reform System Controller 1.0", then you have a sysctl fw there | 23:55 |
| murphnj | then maybe not. From before: | 23:55 |
| zeha | i think `picotool info` will also say 'sysctl' | 23:55 |
| murphnj | the one on bus3 identifies as Raspberry Pi rp2 boot. | 23:55 |
| zeha | did you run reform-mcu-tool bootsel pocket-sysctl-1.0 a second time? | 23:55 |
| murphnj | That it does. but it doesn't say which one it is reading. | 23:56 |
| zeha | yes, because it assumes you only have one of each | 23:56 |
| zeha | but i think it just picks one and acts on that | 23:56 |
| zeha | as soon as it switched one into boot mode, running it again will have it pick the other one | 23:57 |
| murphnj | Any ideas on how to get the keyboard one into programming mode so that it can be re-flashed? | 23:59 |
| zeha | my idea is above | 23:59 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!