Is qmk_pok3r stable for Pok3r RGB?

[blanclemjk]

I'd like to use qmk on my Pok3r RGB. I've looked around and from the last records I found here, I understand it would be somewhat unstable. Anything to be worried of? If so, is development still going on?
Thanks in advance!

[blanclemjk]

up^

[me0wday]

interested too

[scarab5q]

Yeah I'm interested

[unicorn855]

Has there been any major setback with this project? I recently got a pok3r rgb as well, and was thus wondering why this whole project has not been requested to be merged with the qmk master repo @ChaoticEnigma ? Maybe there is renewed significance now since VIA is a thing :)

[ChaoticEnigma]

The setback is that qmk_pok3r does not work (hardfaults) with flash security enabled on the MCU (the way it comes from the factory). This is very difficult to debug, because flash security makes it impossible to use a debugger. So qmk_pok3r is only usable if you connect a hardware debugger to program the firmware.

I thought about attempting to merge with upstream qmk, but there were a number of changes I had to make to get the drivers to work that would make that difficult.

[unicorn855]

Thank you @ChaoticEnigma for that quick response :) I don't know if you mean difficult in the sense that it shouldn't be attempted, or that it is 'just' more work. In the latter case, perhaps it could be made into a collaborative effort, so that all the qmk-things are in one place? Another related question I have would then be if you know whether VIA will work with your modified version of qmk?

[ChaoticEnigma]

"Difficult" meaning I wasn't going to attempt it until I had exhausted my other options (rewriting the whole firmware lol). If someone wants to dig into it, I'll help how I can.

I don't know much about VIA, because it seems to have very sparse documentation. I don't know if the client/configurator itself is open source?

Whatever protocol VIA uses to program the keys is not supported in qmk_pok3r, but it should be possible to implement. I have my own configurator for qmk_pok3r, though, so I probably wouldn't be the one to add support to VIA.

[unicorn855]

I mentioned this in the official qmk discord, and people there referred to https://docs.qmk.fm/#/platformdev_selecting_arm_mcu
I just thought I would add that here :) feel free to drop into the qmk discord and talk about things if you want @ChaoticEnigma :)

[me0wday]

Hi friends, I just got my j-link and am going to attempt the flash today. Can I confirm two things, the device only needs to be unlocked once to flash? And then it no longer needs the j-link?
And can I put the original firmware back on?

[ChaoticEnigma]

@thinkv This is for the pok3r RGB right? Just FYI, I don't believe qmk-pok3r for the pok3r RGB is stable, but i guess some people have had some luck with it?

You need to mass-erase/unlock the flash, and then write the bootloader. After that, you can use the bootloader to flash the main firmware via USB, so you shouldn't need the JLink anymore.

You can re-flash the original firmware with the bootloader, yes.

[me0wday]

Thanks Charlie. Yes it’s the RGB. Do you know why it’s unstable or where it needs work?

…

On Wed, 14 Oct 2020 at 8:07 am, Charlie Waters ***@***.***> wrote: @thinkv <https://github.com/thinkv> This is for the pok3r RGB right? Just FYI, I don't believe qmk-pok3r for the pok3r RGB is stable, but i guess some people have had some luck with it? You need to mass-erase/unlock the flash, and then write the bootloader <https://github.com/pok3r-custom/pok3r_re_firmware/blob/master/disassemble/pok3r_rgb/builtin_rgb/builtin_rgb_patched.bin>. After that, you can use the bootloader to flash the main firmware via USB, so you shouldn't need the JLink anymore. You can re-flash the original firmware with the bootloader, yes. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA436JO3VXNIRLCXNM7G37DSKS6RVANCNFSM4G3A5C4Q> .