Hi,
Any idea where is the curly bracket key on the pocket reform?
I am using the european layout I think.
Thanks.
Lloyd
1 Like
For { press Hyper + Shift + O and } press Hyper + Shift + P.
2 Likes
Yep, I found those as well, but I am curious about where the tilde key is. Anyone know?
At Hyper + Shift + Esc
1 Like
Check out the āinput devicesā section of the manual! I often have it open in the browser while Iām using the device and have been slowly learning.
You can see the pdf version here https://mntre.com/documentation/pocket-reform-handbook.pdf but the html version is much more useful and should be on your device (and so can be used offline etc). Open it with pocket-reform-handbook in the terminal and bookmark it in your browser.
2 Likes
Iāve had trouble with f12. I can use f11 with hyper-q, but hyper-w for f12 doesnāt seem to work.
Any ideas?
You may have another program catching the keystroke. you could try a keycode reporting site like. https://www.toptal.com/developers/keycode
I tried the site, hyper-shift q gives f11, as it should
hyper-shift e gives an event.code of f13 (unexpectedly)
but hyper-shift w gives nothing.
f12 doesnāt even work on the text login screen (labeled as āpowerā as an option)
F12 works fine on my pocket reform (hyper-w).
If w and hyper are both working on your keyboard, its unlikely to be a hardware problem. This may be a firmware bug from an early keyboard firmware.
I suggest trying to update the keyboard firmware to the latest version to see if it fixes the problem with f12.
The latest keyboard firmware will be here Reform / MNT Pocket Reform Ā· GitLab
It looks like the compiled recent firmwares can be gotten from here
or directly here at the moment
https://source.mnt.re/reform/pocket-reform/-/jobs/6894/artifacts/download?file_type=archive
1 Like
This does include the keyboard firmware, however the script included does not actual update the keyboard controller.
Right, you can download the complete pocket reform repository, install the tools to build the firmware, then build and update as described in the manual.
That sounds pretty involved. Iāll have to try when I have some spare time.
As far as the firmware I have. Itās SYSR120240830
and HID20240416, which I take it isnāt the latest.
You may want to follow the instructions from the manual for keyboard and trackball firmware. Section 7.4.2
If you donāt edit the matrix.h file it should flash the original layout.
You will need an external keyboard and a tool to flip the main power switch off and on. ( about 15 minutes)
Something that had puzzled me. For the benefit of others, that section number appears to only be in the PDF, not the HTML version of the handbook. Same with @pff 's suggestion in case anyone else was wondering. Will look into this soon.
Itās been a bit, but I finally tried to do the keyboard firmware flash, and hit a snag, the ./build.sh failed with: āDirectory ā/usr/src/pico-sdkā not foundā
I suspect that some step that has to happen prior is not in the instructions, or that I missed them. Iāll look it over again, but let me know if thereās something that may have been overlooked.
There is a file install-fw-dependencies.sh in the pocket-reform git repository main directory.
Did you run that script before building the firmware?
It should install the necessary dependencies for compiling and flashing the firmwareā¦ but perhaps there is something broken.
Yes, I did run that, and it installed the directory in a subdirectory of where I did the git clone from.
~/firmware/pocket-reform/pico-sdk$
instead of where it is trying to find it, as above (āDirectory ā/usr/src/pico-sdkā not foundā)
I could try to symlink it, but that seems like a path to a cascade of trying to point to the alternate directory. What is the right way to resolve this?
I was also annoyed by this ā I tried putting export PICO_SDK_PATH=../../pico-sdk in build.sh (for the system controller) but it didnāt seem to help. It seems like the build script isnāt set up well. I installed the debian package pico-sdk-source to work around it. I donāt know if it matters that itās 2.0.2 instead of 1.5.1.
When I was upgrading the system controller I also ran into an issue where flash.sh is going to try and use picotool to flash it, which will fail. I used sudo fwupdtool install build/sysctl.cab instead (and you may need to install fwupd).
Iām not sure this stuff is documented anywhere except in a way that is scattered across several forum topics, but it probably should be! I suspect most people arenāt upgrading their system controller much, or if they are they might be using the artifacts from gitlab builds.
Thanks for the info, Iāve started, but Iām not upgrading the system controller, but the keyboard firmware, will these instructions still work? (In conjunction with 7.4.2 in the handbook?)