I'm having trouble compiling my hex. I've installed MSYS2 on windows according to the instructions on these two pages.

https://docs.qmk.fm/getting_started_build_tools.html

http://www.msys2.org/

I also updated the necessary things with "pacman -Syu", "pacman -Su" and "util/msys2_install.sh"

After that it told me that it was ready for use. In the terminal I navigated to the "qmk_master-firmware" folder. I tried to compile my hex with

make AMJpad:owl_custom:all

but it gives me the message

make: *** No rule to make target 'AMJpad:owl_custom:all'. Stop.
Makefile:523: *** recipe commences before first target.  Stop.

So I thought maybe it was something that I messed up with my layout so I tried to compile one of the default layouts on other keyboards and it gives me the same message. I even tried the make command to make all the layouts for all the keyboards but same message. Not sure what to try next. Any insight?

Run this from the QMK root folder and make sure amjpad is lower case since the directory name is so.

Running it from that folder got rid of the second message but I'm still getting the "make: *** No rule to make target 'amjpad:owl_custom:all'. Stop." message. I also tried other keyboards layouts for good measure but I got the same message.

Did you install MSYS2 in a directory with a space in its name?

I installed it directly in my C drive. I vaguely remember that note about directories with spaces in them so I avoided installing it in a place like Program Files.

assuming owl_custom is your keymap.

make amjpad:owl_custom

assuming owl_custom is your keymap.

Code: [Select]

make amjpad:owl_custom

I’ve tried that, or the equivalent. It won’t let me compile any layout. I’ve even tried “make all”

Try cloning the repo again. They made many changes in the past few weeks.

https://www.reddit.com/r/olkb/comments/76ey0y/changes_to_the_make_system_in_qmk/

No dice. I recloned the repository and still get the same message.

Albert@Leviathan MINGW64 /d/keyboard_programming/qmk_master
$ make amjpad:owl_custom
make: *** No rule to make target 'amjpad:owl_custom'.  Stop.

Albert@Leviathan MINGW64 /d/keyboard_programming/qmk_master
$ make amjpad:default
make: *** No rule to make target 'amjpad:default'.  Stop.

Albert@Leviathan MINGW64 /d/keyboard_programming/qmk_master
$ make ergodox_infinity:default
make: *** No rule to make target 'ergodox_infinity:default'.  Stop.


Just get rid of the layout parameter. Try with make ergodox_infinity, or you can also try with simple make. It would compile every firmware in the repository but you can kill the task after the first few ones, just to confirm it works.

I'm really starting to think there's a bug with MSYS2. I'm having no issue at all on a Virtualbox machine with Ubuntu.

Yeah I’m just going to go the Linux route. I was avoiding it since I have zero experience with Linux but I’ve had no luck compiling in Windows.

For the time being I can compile the source for you, if you upload it somewhere. Just give me a couple of hours to get some stuff sorted.

Thanks! I'll send you a PM.

Here's your firmware. I also fixed your keymap.c because it required the MAXKEYMAP keymap in order to split 2u keys.
That keymap splits all the 2u into two 1u yet, since I don't own the hardware, I had no idea which of the two 1u is actually wired to the 2u, so I defined either with the same keycode for the Zero and the Enter.
Reading the code will get you a better idea.

One last thing: when you compile, use the -r argument after make.

Awesome! Thank you very much!

As for the split 2u’s I’m sure I’ll be able to figure which is which with a little trial and error.

This might be off topic but I’m trying to alter the standard Planck layout in QMK and have no idea where to start. I have done a good amount of research but am still lost. I have my layout saved in KLE and could use a push in the right direction. Are there any good tutorials on YouTube to get me started?

https://docs.qmk.fm/getting_started_build_tools.html

This first link has the information you'll need to set up your build environment. It has instructions on how to do that in multiple operating systems but based on my recent experience, and others recommendation, I would suggest compile in something other than windows. Installing Ubuntu on a virtual machine is what I plan to do.


https://github.com/qmk/qmk_firmware

From this link you'll want to clone the QMK repository. Once you've saved it on your computer, you can edit the layout you want in the Planck folder.

I can't really give you step by step instructions because I'm still learning but most of the stuff I've learned has been from poking around through different pages in the guide I posted at the top. I'd like to help more but I don't know enough yet. Best of luck!

The layouts from top to bottom are default, lower, raise, lower + raise.

Here's your firmware. I also fixed your keymap.c because it required the MAXKEYMAP keymap in order to split 2u keys.
That keymap splits all the 2u into two 1u yet, since I don't own the hardware, I had no idea which of the two 1u is actually wired to the 2u, so I defined either with the same keycode for the Zero and the Enter.
Reading the code will get you a better idea.

One last thing: when you compile, use the -r argument after make.

I got busy and hadn't touched this thing for a while but I seem to have bricked my amjpad. I previously was able to flash the default hex layout but after trying this last one I haven't been able to flash anything else. I've tried to flash it with flip, qmk flasher and qmk toolbox. Flip simply says that it can't read/write to the device, qmk flasher freezes and, strangely, qmk toolbox deletes all its necessary files when I try to flash. Reinstalling qmk toolbox fixes it but I find that reaction the strangest. Is this what usually happens when a keyboard is bricked?

Bricking a keyboard is actually not that easy. If you can put it into bootloader mode you can still flash it.
Assuming you're running Windows, open the device manager, press the reset button on your PCB and see if you device shows up under LibUSB-Win32 Devices.

When I plug it in it doesn't show up but when I press reset it shows up under "Atmel USB Devices" with the name "ATmega32U4". So it does show up but I never hear the connect/disconnect sound what windows normally plays. I don't think I'm able to get it into bootloader mode since I'm not able to flash it with any of the three flashers I have installed. Plus I get the weird QMK toolbox reaction with it essentially uninstalling itself when I try to flash.

Code: [Select]

dfu-programmer atmega32u4 flash D:\Keyboard_Programming\AMJpad hex\amjpad_default.hex


It's not recognizing the blank space.
Do this: go to the dfu-programmer folder and create a .bat file with this code.
@echo off
SET dfu=%~dp0dfu-programmer.exe atmega32u4
pause
%dfu% erase --force
%dfu% flash %1
%dfu% reset
pause
All you have to do now is to drag your firmware file on this batch script. It will erase, flash and reset your keyboard automatically.

where might I be able to find the dfu-programmer folder?

I would look into the QMK flasher folder.

Let's set aside the dfu-programmer for a moment then.

Just go to your D:\Keyboard_Programming\AMJpad hex\ folder and remove the blank space between AMJpad and hex, then try flashing again.

It works!

Told you that bricking ain't easy. 

I wonder if the folder with the space was also the reason QMK toolbox was essentially uninstalling itself. It’s one of the most bizarre things I’ve seen happen. Before flashing, all it’s folders and files would be in place. Then after trying to flash it would crash and all its files would be missing. It would do the same thing with the standalone exe version, minus the files of course.

Unlikely. That could be a bug in the software.