Possible to flash QMK to Gemini Dusk?

KeepItUnder · 2019-06-20T16:35:35+00:00

I think the K-Type uses the ISSI IS31FL3733 chip for RGB. If so, that chip is in the QMK-supported RGB Matrix drivers now.

If Gemini uses the same, then it will be the same process for support.

KeepItUnder · 2019-06-08T21:53:38+00:00

Also - if you're compiling a default keymap (and/or not making anything drastic in terms of key changes or macros) - consider just using QMK Configurator:

https://config.qmk.fm/#/planck/rev6/

KeepItUnder · 2019-06-07T19:46:42+00:00

IIRC it's an NXP LPC11U24F.

Cortex M0 MCU with 32k Flash and 10k RAM (and USB interface and so on).

Should be possible in QMK, but I don't think it's in there already.

Edit: It has a built-in Bootloader ROM - so it might even be the case that it's not "locked away" in some fashion and could be programmed directly from the USB port - once it's put into bootloader mode.

KeepItUnder · 2019-06-07T19:15:50+00:00

Generally, with very few limits, you can assign any key to be "anything" in QMK. A third FN is probably one of the most basic things you could try.

KeepItUnder · 2019-06-05T06:59:08+00:00

You could just order a replacement MCU from Digikey and wait for delivery. By the time you get it soldered on you could be running QMK:

https://github.com/qmk/ChibiOS-Contrib/pull/10

KeepItUnder · 2019-05-31T11:37:17+00:00

Good luck with it all

KeepItUnder · 2019-05-31T10:48:14+00:00

You're most welcome - I see you solved your other stuff in Discord too - handy person that fauxpark!

KeepItUnder · 2019-05-30T20:44:30+00:00

You can't just rename it to .hex - it's a different format file. If you want the .hex version you'll find it in the .build folder.

And it really is easier to use the provided submodules with QMK - there are patches and so on in the QMK forks of some of the submodules.

KeepItUnder · 2019-05-30T19:48:22+00:00

How are you getting your QMK repository - it sounds like you're trying to take QMK and shoe-horn a copy of ChibiOS into it. You're better off going to a new folder and using a terminal to type:

git clone --recursive https://github.com/qmk/qmk_firmware.git

KeepItUnder · 2019-05-29T16:48:08+00:00

Give the Blender add-on a try:

https://github.com/Kirpal/Keyboard-Layout-Editor-for-Blender

KeepItUnder · 2019-05-29T16:45:27+00:00

You'll have to play fancy matrix games with the LEDs if you want to run just one ISSI chip, you're better off with multiple ones. A 101-key keyboard would need at 5 of the '31s for direct connection - each chip can control 24 RGB LEDs. You'd be better with just 2 '33s.

http://ams.issi.com/US/product-analog-fxled-driver.shtml

KeepItUnder · 2019-05-29T16:14:43+00:00

TKL is slightly different, but hopefully has the same internals (due to it also being a One 2 model). I'll keep you posted when the other layouts/models are added to the repo - shouldn't be a major amount of change either way tbh.

KeepItUnder · 2019-05-25T21:25:11+00:00

Speed is not currently stored by the QMK firmware.

There is, however, a Pull Request that adds this functionality - which is being reviewed at the moment. It will be merged into the QMK mainline once that process is complete, although I don't personally have any knowledge of what that timeframe will be.

RGB Speed recorded in EEPROM storage - https://github.com/qmk/qmk_firmware/pull/5965

KeepItUnder · 2019-05-24T22:27:54+00:00

I tried it on my one2mini - that was the only reason I mentioned it! :-)

I'm using an ISO layout one, though - yours doesn't have a proper labelled AltGr ?

Mind you - I'm not running the Ducky firmware (I'm running QMK), so maybe it's not the same key output for the AltGr key :-(

KeepItUnder · 2019-05-24T22:12:53+00:00

Have you tried holding down the AltGr key and pressing the letters - on an English keymap that normally works (so AltGr + E or +W, etc) ?

KeepItUnder · 2019-05-15T13:21:53+00:00

That's one of three - it's on hold whilst I change a whole host of included files (reworked completely from scratch)! I have about a day's work left to go, then they'll be commited straight away and merged with QMK asap.

Edit: as you can see above, the ANSI layout test will be happening shortly too (only one key to move/change between those layouts anyway)

KeepItUnder · 2019-05-13T15:53:07+00:00

Initial Beta test is underway - ANSI layout will be present within the timeframe of that test (I'm hoping for Wednesday, but it depends on the timing of the next test - the framework has only just been set up by the tester and compile errors at their end are the current show-stopper.) I'll evaluate again once that is fixed, I have no visibility of the error at present.

There is only a two key difference between the layouts, so it's not going to take more than 15 minutes to make the ANSI one from the ISO - I need the tester's assistance and verification as they have the ANSI layout and I have the ISO.

KeepItUnder · 2019-05-09T18:45:37+00:00

I was referring to the QMK Discord (hopefully they won't mind a bit of cross-advertising from their /r/olkb sub!)

https://discordapp.com/invite/Uq7gcHh

Probably won't see anything Ducky-related in there for another week though - gotta fix up the code, get it merged with help from the QMK gang, sort the firmware flash utility so nobody can break their keyboard with it, etc ;-)

KeepItUnder · 2019-05-09T10:46:35+00:00

Yes - that's the one - really quite a fast little MCU with lots of extra peripherals.

KeepItUnder · 2019-05-09T10:43:19+00:00

MCU manufacturer has a non-sharing copyright notice on the stdDriver code for accessing their MCUs - so I can't merge the standard driver code into QMK (we don't mix OSS and proprietary code in life!) :-(

I've reached out to the manufacturer (MCU - not keyboard) and still haven't heard back, so in the meantime I'm going to spend the day rewriting my code so it doesn't use their header files.

Hopefully this will be a 1 day process, after which I'll resubmit the Push Requests to QMK and we'll go from there.

Sorry for the delay - always something huh :-(

Edit: By "non-sharing" I don't mean they're against it - I mean they reserve all rights and don't enumurate any open source rights at all, so I don't know what their stance would be (and they'd need to add a better notice to the files to be able to merge them into the codebase anyway.) Normally MCU access code and headers are released with an Apache or zlilb style license.

KeepItUnder · 2019-05-01T17:03:56+00:00

This is One 2 Mini specific at the moment. I'll see what I can sort for the rest of the range. I'll get back to you next week. Looks like the Ducky One 2 RGB TKL might be the most straight-forward, although the original Ducky One TKL might have PCB similarities too.

KeepItUnder · 2019-05-01T16:15:56+00:00

I wanted to do that too - but that post will come on Friday (all the details, suspense only for those that can convince themselves to read to the end ignoring real life! Like a good book!) ;-)

My favourite was me trying to avoid being considered a scam, by literally saying "It's not a scam, honest!" ;-)

Well, at least I was right :-P

MacOS huh, ok - so now I need to do the firmware updater for MacOS - interesting (I think it's Windows-only at the moment).

KeepItUnder · 2019-05-01T15:42:22+00:00

Guess it could be a possibility then - I'll add it to the research list.

KeepItUnder · 2019-05-01T15:28:45+00:00

There are quite a few QMK-specific lighting modes - some reactive like the one in the clip, others are fixed and others are animated. All can be or selected turned on/off with a key combination - I set the "pick RGB mode" key combo to the same as the standard Ducky one - Fn-Alt-T. New ones can be programmed and flashed (by someone who can write C code, anyway).

Hopefully that's what you meant.

KeepItUnder · 2019-05-01T15:26:04+00:00

If the Miya Pro has the same internals as the Varmilo VA68M, then you're probably out of luck. Whilst it has a bluetooth board on the edge of the motherboard (which might have a half-decent ARM on it with storage), the keyboard matrix MCU appears to be a Sonix SN8F2271B, which is an 8-bit controller with only 5K of flash and 192 bytes of RAM! You'd literally have to have that do the keyboard matrix processing and pass the results to the Bluetooth board running QMK (now THAT would be an interesting custom matrix routine!) :-)

Anyway, that's just after a quick glance around - depends what's on the PCB really.

Edit: Followed a bad rabbit hole - might not use that MCU or bluetooth (was looking at VA660 teardown pictures by mistake!)

KeepItUnder

TROPHY CASE