Posts by Tobias

First, i made a mistake above - the key at row 11, column 5 is the CBM key - but on a C16 keyboard (see the rightmost columns in that table). So you really want to change the key at row 7, column 5.

That said, don't get misleaded by those ASCII chars - the USB HID codes are not ASCII at all To find the right byte to modify, it helps a lot if your hex editor allows you to show arbitrary number of bytes per line.... when i set mine to 8 (the maximum number of columns) then you can clearly see (and edit) the matrix, it looks like this (beginning of cbm_us.bin):

So, the value you want to change is supposed to be at row 7, column 5 - meaning the offset in the file is (7*8) + 5 = 61 (hex 0x3d). If you look at the file now, at this offset you will find the hex value 0xe2 - which is "left alt", exactly whats expected And indeed, it should be changed to 0xe3 (the pdf you found is the same that i am looking at, so all good).

Well, in the zip there is the source code and indeed a windows .exe file - so yes, if you have access to a windows box using that one might be easier

Ok i forgot... since you are on a Mac, you'll have to produce the mkkeymap program yourself - you'll have to install the developer tools. then in the unpacked mkkeymap archive type "make", it should then compile the program. You can then use it within that directory by prefixing with ./

This is an interesting issue actually - i did not think about it at all before (yet it seems so obvious)...

The Keymap just contains a binary array, the layout is in the manual, the values are the USB HID keycodes. However, to flash the keymap you'll have to convert it into uf2 format first. Somehow i forgot to write proper instructions and publish the little tool i made for this when Keyrah V3 was released...

Anyway, i have attached the tool, and the default keymaps. In order to do what you want:

- pick the 4 cbm keymaps, and merge them into one file in the following order (see 3.7.1): cbm_us.bin, cbm_us_emu.bin, cbm_de.bin, cbm_de_emu.bin

- now the tables in 3.7.1 tell you the basic layout of the resulting file

- now find the key you want to remap in the table for your keyboard in 3.7.2 (CBM is row 11, column 5)

- calculate the offset into the keymap file (again look at 3.7.1). eg for the US "emu" keymap would be 0x400 (start of cbm_us_emu.bin) + 8 * 11 (row) + 5 (column)

- change the value to whatever you like (use USB HID specs)

- repeat

- convert the resulting binary file to a uf2 file using mkkeymap and flash it. mkkeymap will take care of adding the "tags" mentioned in the manual.

- if you screw up, flash the reset.uf2 file (that will basically delete all custom mapping data)

Keep in mind that the system/keyboard jumpers have no effect when a custom mapping was flashed

Hope that helps

I will use this thread to derive proper docs from it later, so don't hesitate to ask if you have further questions.

(Also, please tell what information is missing for you in 3.7.x so i can add it. I thought all required info is there - but it surely is very condensed and technical, i admit :))

Quote

The only CRT file it will not support is Gmod2 as far as I remember.

It is actually not the only one by far - here is a more or less complete list. So the right thing to say would be that Chameleon supports all "common" ones (except gmod2)

Really sounds like a VICE issue then If you have some sort of "controller test" in macOS (somewhere in the system settings?) it would be interesting to know if keyrah works in it (my guess would be that it does). In that case unfortunately the only thing you can do is wait for VICE to be fixed.

OK, you might be seeing a general (not keyrah related) problem. If you can build it yourself, it might be worth trying the current development version (homebrew has a recipe for it).

You need the last VICE release (3.8) and use the default positional keymap - else you will get all kinds of strange effects. do NOT use the "keyrah" keymap provided with VICE - this is for v2.

Quote

the RP2040 is the main suspect

Wait, wasn't the defective unit a keyrah v2?

First thing to try would be updating it via USB, that might just do the trick and bring it back to life

The most important thing for you to know is probably that, while the Chameleon is an accelerator, it is not a SCPU (nor compatible with it). That means that things that absolutely require a SCPU will not work. Fortunately that list would be small (regarding games, it is only Metal Dust that would not work, i think) - also see http://wiki.icomp.de/wiki/Chameleon#Turbo

"modern ATX PSU" is actually one of the worst options available, see our Power Supply FAQ.

Lucky you

There is also a small chance that this is caused by a stuck key (shift lock perhaps?)

First of all, use a recent VICE build, ie 3.8 - see https://github.com/VICE-Team/svn-mirror/releases/tag/3.8.0 (or while you are at it, just use a snapshot build from https://github.com/VICE-Team/svn-mirror/releases

You'll have to select the keyrah v3 keymap that is provided with VICE, the default keymap does not work for C128

He did (#3)

I mean the C64, not the Chameleon

Also, do you have a way to measure voltage? Like a multimeter?

Could you open it and make a picture of the board, so we can see what board revision it is? Perhaps it has the same problem as mine (that also was a breadbin C64).

What kind of powersupply is it then?

Also, what kind of C64? I had (Jens fixed it for me) one C64 myself where the clock would drift significantly over time - i can see how Chameleon would not like this