kiibohd / controller

Kiibohd Controller
GNU General Public License v3.0
807 stars 270 forks source link

dfu hangs, leaving ergodox in flash state #138

Closed F1LT3R closed 8 years ago

F1LT3R commented 8 years ago

Steps to reproduce:

cd keyboards
./infinity.bash
cd IC60.gcc
# Put left Inifinity Ergodox controller into Flash (red LCD on left)
./load

I get the same effect when using ./load as I do using dfu-util -D kiibohd.dfu.bin.

Output:

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/

Match vendor ID from file: 1c11
Match product ID from file: b007
Deducing device DFU version from functional descriptor length
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%        28576 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
dfu-util: unable to read DFU status after completion

This behavior does not happen when using the bin file from the Input Club Configurator

Any ideas what I am doing wrong here?

haata commented 8 years ago

Oh, it sounds like you flashed the wrong firmware.

Use the ./ergodox.bash script instead.

F1LT3R commented 8 years ago

Ok thanks, I will give that a shot later.

F1LT3R commented 8 years ago

Ok thanks @haata I am able to flash now. Do I have to flash each side separately with this repo, plugging each side in individually? (I ask because the Input Club Configurator seems to flash both at the same time.)

Actually I found that I did have to flash each half separately to get this to work.

jceaser commented 7 years ago

Oldish post, but if your here from google, @haata's Aug 2 comment fixed this for me.