Building QMK firmware doesn't work

[samboosa5k]

After following steps to get QMK firmware built and flashed, keyboard can not boot into bootloader mode.

Using the VIA appimage and the via/qmk json layout from "https://epomaker.com/blogs/via-json/epomaker-galaxy100-json", they keyboard is not recognized.

The command line does recognize my device but I cannotg customize it:

Bus 003 Device 020: ID 342d:e489 epomaker Galaxy100 QMK

[FrostyApeOne]

Hello mate,
Unfortunately I got the same issue, did you manage to fix yours?

[samboosa5k]

@FrostyApeOne - The original epomaker qmk source code repo is broken/incomplete in several places, I managed to fix all the issues and forked the Epomaker firmware here: https://github.com/samboosa5k/galaxy100

_Anything done here is done at your own risk, please be careful 😅 _

• Which issue do you currently have?

[FrostyApeOne]

Thank you, I found your PR and managed to fix the issue. You saved me a big headache mate 🙏
I just couldn't reset to bootloader after using their code.

[FrostyApeOne]

Hello my friend,
I found a new bug with the firmware, as soon as I flash the keyboard using your fixed version. My End, PRTSC and NUM key lights stop working
The keys themselves work but the lights not.
Would you please be able to have a look see why this happens?

[samboosa5k]

This is because the Epomaker firmware does not have this configuredd correctly in the following parts of their firmware:

galaxy100.c
Function: rgb_matrix_indicators_advanced_kb

config.h
This lacks the num lock/end/printscreen pin numbers which we would need to call in the function above

Led pin definitions: https://docs.qmk.fm/features/led_indicators

I tried to troubleshoot this after a few hours my only conclusion is this is an Epomaker problem --> their firmware is broken.

All they need to do is update these sections, unless you have enough knowledge of C or C++ to fix this?

[samboosa5k]

Hello my friend, I found a new bug with the firmware, as soon as I flash the keyboard using your fixed version. My End, PRTSC and NUM key lights stop working The keys themselves work but the lights not. Would you please be able to have a look see why this happens?

Advice:

• Revert changes from my repo to see if the issues still remain. You might find some luck on reddit but Epomaker has not communicated about any of this :/

[FrostyApeOne]

I see, well
I myself spent over 4 hours on it with no luck.
I write a function in the galaxy100.c class that turns off all the leds and then light them up one by one based on their index, and interestingly, even though I went through 0 to 120 to cover all the leds still when it gets to those keys the light stays off, rather strange as this test should tuen them on no matter what if the issue was simply led pins not defined. As I literally go through a range to cover all leds.
I have contacted them see what they say but it's really annoying. Will return it if it does t get fixed and stick to VIA only 😩
The problem is not your changes, it's also in their original version.

[samboosa5k]

I have reset everything as well, and if you check the keymap.c, the rotary encoder is displayed only as a KC_PAUSE, but in via on the wiring diagram you will see it is not connected to anything 🫩

I have opened issues on their other repo's asking to fix this because they should fix this before releasing other broken repo's.

[FrostyApeOne]

Fixed it all my friend @samboosa5k

https://github.com/FrostyApeOne/galaxy100/tree/rgb_matrix_fix

Raised a PR, hopefully they will approve and merge it in!

Thanks very much for all your help

[samboosa5k]

@FrostyApeOne - You fixed it! 😄

I have closed my PR in favor of Your PR I'm happy to see all the colors back!

[lichenophile]

Sorry if this isn't the appropriate place to ask for help, but I'm having trouble compiling successfully and perhaps someone here has insight as to what I'm doing wrong.

I'm running windows and followed the linked https://docs.qmk.fm/newbs_getting_started guide to set up QMK MSYS

I downloaded https://github.com/FrostyApeOne/galaxy100 as a zip and extracted the files to C:\Users\myusername\qmk_firmware\keyboards\epomaker\galaxy100

attempting to compile goes like this:

$ qmk compile -kb "epomaker/galaxy100" -km default
Ψ Compiling keymap with make -r -R -f builddefs/build_keyboard.mk -s KEYBOARD=epomaker/galaxy100 KEYMAP=default KEYBOARD_FILESAFE=epomaker_galaxy100 TARGET=epomaker_galaxy100_default VERBOSE=false COLOR=true SILENT=false QMK_BIN="qmk"


⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
arm-none-eabi-gcc.exe (GCC) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiling: keyboards/epomaker/galaxy100/rgb_record/rgb_record.c                                    In file included from <command-line>:
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c: In function 'rgbrec_update_current_channel':
./keyboards/epomaker/galaxy100/config.h:62:48: error: 'EECONFIG_USER_DATABLOCK' undeclared (first use in this function); did you mean 'EECONFIG_USER_DATA_SIZE'?
   62 | #define RGBREC_EECONFIG_ADDR       (uint8_t *)(EECONFIG_USER_DATABLOCK)
      |                                                ^~~~~~~~~~~~~~~~~~~~~~~
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c:133:23: note: in expansion of macro 'RGBREC_EECONFIG_ADDR'
  133 |     addr = (uint32_t)(RGBREC_EECONFIG_ADDR) + (channel * sizeof(rgbrec_buffer));
      |                       ^~~~~~~~~~~~~~~~~~~~
./keyboards/epomaker/galaxy100/config.h:62:48: note: each undeclared identifier is reported only once for each function it appears in
   62 | #define RGBREC_EECONFIG_ADDR       (uint8_t *)(EECONFIG_USER_DATABLOCK)
      |                                                ^~~~~~~~~~~~~~~~~~~~~~~
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c:133:23: note: in expansion of macro 'RGBREC_EECONFIG_ADDR'
  133 |     addr = (uint32_t)(RGBREC_EECONFIG_ADDR) + (channel * sizeof(rgbrec_buffer));
      |                       ^~~~~~~~~~~~~~~~~~~~
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c: In function 'rgbrec_read_current_channel':
./keyboards/epomaker/galaxy100/config.h:62:48: error: 'EECONFIG_USER_DATABLOCK' undeclared (first use in this function); did you mean 'EECONFIG_USER_DATA_SIZE'?
   62 | #define RGBREC_EECONFIG_ADDR       (uint8_t *)(EECONFIG_USER_DATABLOCK)
      |                                                ^~~~~~~~~~~~~~~~~~~~~~~
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c:198:23: note: in expansion of macro 'RGBREC_EECONFIG_ADDR'
  198 |     addr = (uint32_t)(RGBREC_EECONFIG_ADDR) + (channel * sizeof(rgbrec_buffer));
      |                       ^~~~~~~~~~~~~~~~~~~~
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c: In function 'record_color_read_data':
./keyboards/epomaker/galaxy100/config.h:62:48: error: 'EECONFIG_USER_DATABLOCK' undeclared (first use in this function); did you mean 'EECONFIG_USER_DATA_SIZE'?
   62 | #define RGBREC_EECONFIG_ADDR       (uint8_t *)(EECONFIG_USER_DATABLOCK)
      |                                                ^~~~~~~~~~~~~~~~~~~~~~~
./keyboards/epomaker/galaxy100/config.h:63:59: note: in expansion of macro 'RGBREC_EECONFIG_ADDR'
   63 | #define CONFINFO_EECONFIG_ADDR     (uint32_t *)((uint32_t)RGBREC_EECONFIG_ADDR + (uint32_t)EECONFIG_RGBREC_USE_SIZE)
      |                                                           ^~~~~~~~~~~~~~~~~~~~
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c:268:55: note: in expansion of macro 'CONFINFO_EECONFIG_ADDR'
  268 |     const uint8_t *ptr = (const uint8_t *)(((uint32_t)CONFINFO_EECONFIG_ADDR + 4) + hs_mode);
      |                                                       ^~~~~~~~~~~~~~~~~~~~~~
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c: In function 'record_color_hsv':
./keyboards/epomaker/galaxy100/config.h:62:48: error: 'EECONFIG_USER_DATABLOCK' undeclared (first use in this function); did you mean 'EECONFIG_USER_DATA_SIZE'?
   62 | #define RGBREC_EECONFIG_ADDR       (uint8_t *)(EECONFIG_USER_DATABLOCK)
      |                                                ^~~~~~~~~~~~~~~~~~~~~~~
./keyboards/epomaker/galaxy100/config.h:63:59: note: in expansion of macro 'RGBREC_EECONFIG_ADDR'
   63 | #define CONFINFO_EECONFIG_ADDR     (uint32_t *)((uint32_t)RGBREC_EECONFIG_ADDR + (uint32_t)EECONFIG_RGBREC_USE_SIZE)
      |                                                           ^~~~~~~~~~~~~~~~~~~~
keyboards/epomaker/galaxy100/rgb_record/rgb_record.c:295:43: note: in expansion of macro 'CONFINFO_EECONFIG_ADDR'
  295 |     uint8_t *ptr = (uint8_t *)(((uint32_t)CONFINFO_EECONFIG_ADDR + 4) + find_index());
      |                                           ^~~~~~~~~~~~~~~~~~~~~~
 [ERRORS]
 |
 |
 |
make: *** [builddefs/common_rules.mk:362: .build/obj_epomaker_galaxy100_default/rgb_record/rgb_record.o] Error 1

I also tried the command from the repo readme.md

$ make epomaker/galaxy100:default
make: *** No rule to make target 'epomaker/galaxy100:default'.  Stop.

It's probably obvious that I'm new to QMK and I'm probably missing something obvious to have failed so hard, but any pointers in the right direction are appreciated

[FrostyApeOne]

Hello @lichenophile
Apologise I just saw this, I can have a look and create a check list for you just to make sure you are compiling it the right way. I'll get back to you later today (6.30 am in the UK at)

[FrostyApeOne]

@lichenophile
Could you please follow the instructions here and setup your environment.

https://docs.qmk.fm/newbs_getting_started

Please make sure you install both QMK Toolbox and QMK MSYS

You don't need to set default layout or key map, just run the setup command in QMK CLI as per instructions in the above page.
Please let me know once done!

[lichenophile]

Unfortunately that is indeed the exact process I followed. But to be sure it set up correctly, I removed my qmk_firmware folder and re-ran qmk setup and chose the option 1. Delete and reclone qmk/qmk_firmware. This without problem and has recreated the qmk_firmware folder

Also have also previously set up QMK Toolbox and installed drivers which also executed without error

[FrostyApeOne]

@lichenophile
It is strange, I just deleted everything, installed again and downloaded the same firmware I got on GitHub (I usually clone it but as you said you downloaded it I did the same to ensure it matches what you did)
and ran the following command:

qmk compile -kb epomaker/galaxy100 -km default

And it just worked.

Could it be that your setup/ log level (not sure how) is set to break the compiling process if there is a warning, because there are some warnings when building it, and my compiler just ignore it.

⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
Generating: .build/obj_epomaker_galaxy100_default/src/community_modules.c                           [WARNINGS]
 |
 | ⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
 | ☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
 |
arm-none-eabi-gcc.exe (GCC) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Size before:
   text    data     bss     dec     hex filename
      0   56012       0   56012    dacc epomaker_galaxy100_default.bin

Generating: .build/obj_epomaker_galaxy100_default/src/info_config.h                                 [WARNINGS]
 |
 | ⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
 | ☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
 |
Generating: .build/obj_epomaker_galaxy100_default/src/community_modules.h                           [WARNINGS]
 |
 | ⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
 | ☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
 |
Generating: .build/obj_epomaker_galaxy100_default/src/community_modules_introspection.c             [WARNINGS]
 |
 | ⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
 | ☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
 |
Generating: .build/obj_epomaker_galaxy100_default/src/community_modules_introspection.h             [WARNINGS]
 |
 | ⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
 | ☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
 |
Generating: .build/obj_epomaker_galaxy100_default/src/default_keyboard.c                            [WARNINGS]
 |
 | ⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
 | ☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
 |
Generating: .build/obj_epomaker_galaxy100_default/src/default_keyboard.h                            [WARNINGS]
 |
 | ⚠ epomaker/galaxy100: Layout "LAYOUT" is offset on Y axis by 0.25
 | ☒ epomaker/galaxy100: Keycode USE_TASK has no short form alias
 |
Compiling: .build/obj_epomaker_galaxy100_default/src/community_modules.c                            [OK]