mirror of
https://github.com/mfulz/qmk_firmware.git
synced 2025-11-03 23:02:34 +01:00
last changes
This commit is contained in:
Jack Humbert
parent
bf63363c1d
commit
47e350f5ea
@ -1,71 +1,3 @@
|
|||||||
# jj40
|
# Planck Through Hole Kit
|
||||||
|
|
||||||
|
Fuses I used are `-U lfuse:w:0xcf:m -U hfuse:w:0x90:m`, and I hit the ESC to bootup normally (just a work-around right now).
|
||||||
|
|
||||||
A compact 40% (12x4) ortholinear keyboard kit made and KPRepublic on AliExpress.
|
|
||||||
|
|
||||||
Keyboard Maintainer: [QMK Community](https://github.com/qmk)
|
|
||||||
Hardware Supported: Atmega32A
|
|
||||||
Hardware Availability: [AliExpress](https://www.aliexpress.com/store/product/jj40-Custom-Mechanical-Keyboard-40-PCB-programmed-40-planck-layouts-bface-firmware-gh40/3034003_32828781103.html)
|
|
||||||
|
|
||||||
Make example for this keyboard (after setting up your build environment):
|
|
||||||
|
|
||||||
make jj40:default:program
|
|
||||||
|
|
||||||
See [build environment setup](https://docs.qmk.fm/build_environment_setup.html) then the [make instructions](https://docs.qmk.fm/make_instructions.html) for more information.
|
|
||||||
|
|
||||||
Note that this is a complete replacement for the firmware, so you won't be
|
|
||||||
using Bootmapper Client to change any keyboard settings, since not all the
|
|
||||||
USB report options are supported.
|
|
||||||
|
|
||||||
In addition you may need the AVR toolchain and `bootloadHID` ([GitHub repo](https://github.com/whiteneon/bootloadHID)) for flashing:
|
|
||||||
|
|
||||||
For macOS:
|
|
||||||
```
|
|
||||||
$ brew cask install crosspack-avr
|
|
||||||
$ brew install --HEAD https://raw.githubusercontent.com/robertgzr/homebrew-tap/master/bootloadhid.rb
|
|
||||||
```
|
|
||||||
|
|
||||||
For Linux:
|
|
||||||
```
|
|
||||||
$ sudo apt install libusb-dev
|
|
||||||
$ wget https://www.obdev.at/downloads/vusb/bootloadHID.2012-12-08.tar.gz
|
|
||||||
$ tar -xzf bootloadHID.2012-12-08.tar.gz
|
|
||||||
$ cd bootloadHID.2012-12-08/commandline
|
|
||||||
$ make
|
|
||||||
$ sudo cp bootloadHID /usr/bin
|
|
||||||
```
|
|
||||||
|
|
||||||
In order to use the `./program` script, which can reboot the board into
|
|
||||||
the bootloader, you'll need Python 2 with PyUSB installed:
|
|
||||||
|
|
||||||
```
|
|
||||||
$ pip install pyusb
|
|
||||||
```
|
|
||||||
|
|
||||||
If you prefer (or are having issues with a `program` flash), you can just build it (`make jj40:<keymap-name>` and flash the firmware (`.hex` file) directly with
|
|
||||||
`bootloadHID` if you boot the board while holding down `Backspace` (`Top Right Key`) to keep it
|
|
||||||
in the bootloader:
|
|
||||||
|
|
||||||
```
|
|
||||||
$ make jj40
|
|
||||||
$ bootloadHID -r jj40_default.hex
|
|
||||||
```
|
|
||||||
|
|
||||||
For Windows 10:
|
|
||||||
Windows sometimes doesn't recognize the jj40. The easiest way of flashing a new layout is probably using [HIDBootFlash](http://vusb.wikidot.com/project:hidbootflash).
|
|
||||||
1. Go to Windows Device Manager and find the keyboard (plug it in while holding down `Backspace` (`Top Right Key`)). It can be found under Human Interface Devices or under Keyboards.
|
|
||||||
2. Go to properties and the Details tab to find the hardware ID. You want the VID and the PID (code after the underscore). Plug them into HIDBootFlash and hit Find Device.
|
|
||||||
3. Use `make jj40:<keymap-name>` to generate the .hex file in the qmk basis folder. Select the .hex file in HIDBootFlash and press Flash Device.
|
|
||||||
|
|
||||||
|
|
||||||
## Troubleshooting
|
|
||||||
|
|
||||||
1. Try plugging the board in while pressing `Backspace` (`Top Right Key`). This will force it
|
|
||||||
to boot only the bootloader without loading the firmware. Once this is
|
|
||||||
done, just reflash the board with the original firmware.
|
|
||||||
2. Sometimes USB hubs can act weird, so try connecting the board directly
|
|
||||||
to your computer or plugging/unplugging the USB hub.
|
|
||||||
3. If you get an error such as "Resource Unavailable" when attemting to flash
|
|
||||||
on Linux, you may want to compile and run `tools/usb_detach.c`. See `tools/README.md`
|
|
||||||
for more info.
|
|
||||||
|
|||||||
@ -1,16 +0,0 @@
|
|||||||
# JJ40 Tools
|
|
||||||
|
|
||||||
## usb_detach.c
|
|
||||||
|
|
||||||
When trying to flash on Linux, you may encounter a "Resource Unavailable" error. This means that Linux's HID driver has taken exclusive control of the keyboard, and the program script can't flash it.
|
|
||||||
This program can force Linux to give up a device, so that the programming script can reset it.
|
|
||||||
|
|
||||||
### To compile:
|
|
||||||
```
|
|
||||||
gcc usb_detach.c -o usb_detach
|
|
||||||
```
|
|
||||||
|
|
||||||
### To run:
|
|
||||||
1. Use `lsusb` to discover the Bus and Device numbers for your keyboard.
|
|
||||||
2. Run the program: `sudo ./usb_detach /dev/bus/usb/<BUS>/<DEVICE>`.
|
|
||||||
3. Build and program the firmware as normal.
|
|
||||||
@ -1,33 +0,0 @@
|
|||||||
/* Found at https://www.linuxquestions.org/questions/linux-hardware-18/how-to-unclaim-usb-device-558138/#post3406986 */
|
|
||||||
#include <stdio.h>
|
|
||||||
#include <sys/types.h>
|
|
||||||
#include <sys/stat.h>
|
|
||||||
#include <fcntl.h>
|
|
||||||
#include <linux/ioctl.h>
|
|
||||||
#include <linux/usbdevice_fs.h>
|
|
||||||
|
|
||||||
int main(int argc, char**argv)
|
|
||||||
{
|
|
||||||
struct usbdevfs_ioctl command;
|
|
||||||
int ret;
|
|
||||||
int fd;
|
|
||||||
int i;
|
|
||||||
if (argc>1) {
|
|
||||||
fd = open(argv[1],O_RDWR);
|
|
||||||
if (fd<1){
|
|
||||||
perror("unable to open file");
|
|
||||||
return 1;
|
|
||||||
}
|
|
||||||
for (i=0;i<255;i++){ // hack: should fetch how many interface there is.
|
|
||||||
command.ifno = i;
|
|
||||||
command.ioctl_code = USBDEVFS_DISCONNECT;
|
|
||||||
command.data = NULL;
|
|
||||||
ret = ioctl(fd, USBDEVFS_IOCTL, &command);
|
|
||||||
if(ret!=-1)
|
|
||||||
printf("un claimed interface %d %d\n",i,ret);
|
|
||||||
}
|
|
||||||
} else {
|
|
||||||
printf ("usage: %s /dev/bus/usb/BUS/DEVICE\n",argv[0]);
|
|
||||||
printf("Release all interfaces of this usb device for usage in virtualisation\n");
|
|
||||||
}
|
|
||||||
}
|
|
||||||
Loading…
x
Reference in New Issue
Block a user