Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infinity ErgoDox not starting up with QMK #10067

Closed
3 tasks
mwil opened this issue Aug 17, 2020 · 6 comments
Closed
3 tasks

Infinity ErgoDox not starting up with QMK #10067

mwil opened this issue Aug 17, 2020 · 6 comments

Comments

@mwil
Copy link

mwil commented Aug 17, 2020

I'm currently trying out different types of firmware for my Infinity ErgoDox (Rev 1.1d) on OSX. Using the Kiibodh Configurator software works fine, as does building from fredizzimo/infinity_ergodox.

Using QMK, the build seems fine, the flashing process looks the same as in the other tools ... but the keyboard just stays in the flashing mode (red backlight). Same result with the QMK Toolbox.

It looks like the compiled binary is not compatible with the controller for some reason.

Describe the Bug

The keyboard does not leave the red flashing mode after completion.

System Information

  • Keyboard: Infinity ErgoDox
    • Revision (if applicable): 1.1d
  • Operating system: OSX 0.15.6 (19G73)
  • ARM GCC version: 8.3.1 20190703 (release) [gcc-8-branch revision 273027]
  • QMK Firmware version: 0.9.52
  • Any keyboard related software installed?
    • AutoHotKey
    • Karabiner
    • Other:

Additional Context

Console Output

$ make ergodox_infinity:default:dfu-util
QMK Firmware 0.9.52
Making ergodox_infinity with keymap default and target dfu-util

arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 8-2019-q3-update) 8.3.1 20190703 (release) [gcc-8-branch revision 273027]
Copyright (C) 2018 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	  63592	      0	  63592	   f868	.build/ergodox_infinity_default.hex

Compiling: keyboards/ergodox_infinity/keymaps/default/keymap.c                                      [OK]
Compiling: tmk_core/common/command.c                                                                [OK]
Linking: .build/ergodox_infinity_default.elf                                                        [OK]
Creating binary load file for flashing: .build/ergodox_infinity_default.bin                         [OK]
Creating load file for flashing: .build/ergodox_infinity_default.hex                                [OK]

Size after:
   text	   data	    bss	    dec	    hex	filename
      0	  63592	      0	  63592	   f868	.build/ergodox_infinity_default.hex

Copying ergodox_infinity_default.bin to qmk_firmware folder                                         [OK]
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Opening DFU capable USB device...
ID 1c11:b007
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 1024
Copying data from PC to DFU device
Download	[=========================] 100%        64172 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
dfu-util: unable to read DFU status after completion
@andresilva
Copy link
Contributor

Can confirm the issue. Seems to have been introduced by #9908, reverting that commit makes dfu-util work for me again.

@tzarc
Copy link
Member

tzarc commented Aug 21, 2020

I reverted it in master -- we'll see whether it can be reintroduced in a slightly more... functional... manner at some point in the near future.

@tzarc
Copy link
Member

tzarc commented Aug 21, 2020

If you folks can confirm that this is working on master again it'd be great!

@mwil
Copy link
Author

mwil commented Aug 21, 2020

I can confirm that it works again on master.

Restoring the line MCU_LDSCRIPT = MK20DX256BLDR8 seems to be sufficient to make it work again.
Thank you all for solving the issue!

@mwil mwil closed this as completed Aug 21, 2020
@andresilva
Copy link
Contributor

master works for me. Looking at #9908 it seems that all variables are being correctly set with the correct values so it's probably just some small bug that's not making it activate properly 🤷.

@fauxpark
Copy link
Member

@andresilva yes, see the above PR ^.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants