keyboardio / Model01-Firmware

The "standard" Keyboardio Model 01 Firmware sketch.
GNU General Public License v3.0
172 stars 302 forks source link

make flash error on macOS #44

Closed masukomi closed 5 years ago

masukomi commented 6 years ago

after following setup instructions in README

Keyboard was plugged in. Confirmed by lit LEDs and having typed on it.

After hitting ENTER lights went out.

make flash
BOARD_HARDWARE_PATH="/Users/masukomi/Documents/Arduino/hardware" /Users/masukomi/Documents/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/bin//kaleidoscope-builder flash
Building output/Model01-Firmware/Model01-Firmware (0.0.0-gv1.22-3-gb745) ...
Press ENTER when ready...

Connecting to programmer: .avrdude: butterfly_recv(): programmer is not responding

avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
Found programmer: Id = "��"; type = w
    Software Version = .; Hardware Version = .
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: error: buffered memory access not supported. Maybe it isn't
a butterfly/AVR109 but a AVR910 device?
avrdude: initialization failed, rc=-1
         Double check connections and try again, or use -F to override
         this check.

avrdude: butterfly_recv(): programmer is not responding
avrdude: error: programmer did not respond to command: leave prog mode
avrdude: butterfly_recv(): programmer is not responding
avrdude: error: programmer did not respond to command: exit bootloader
Connecting to programmer: .avrdude: butterfly_recv(): programmer is not responding

avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
Found programmer: Id = "��"; type = G
    Software Version = .; Hardware Version = �.
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: error: buffered memory access not supported. Maybe it isn't
a butterfly/AVR109 but a AVR910 device?
avrdude: initialization failed, rc=-1
         Double check connections and try again, or use -F to override
         this check.

avrdude: butterfly_recv(): programmer is not responding
avrdude: error: programmer did not respond to command: leave prog mode
avrdude: butterfly_recv(): programmer is not responding
avrdude: error: programmer did not respond to command: exit bootloader

seemed to continue on in this vein. Tried to ^C out of it but that didn't work.

Unplugging keyboard did kill it.

obra commented 6 years ago

Hi,

Did you hold down the 'Prog' key while trying to flash?

On Wed, Feb 28, 2018 at 4:08 PM, masukomi (a.k.a. Kay Rhodes) < notifications@github.com> wrote:

after following setup instructions in README

Keyboard was plugged in. Confirmed by lit LEDs and having typed on it.

After hitting ENTER lights went out.

make flash BOARD_HARDWARE_PATH="/Users/masukomi/Documents/Arduino/hardware" /Users/masukomi/Documents/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/bin//kaleidoscope-builder flash Building output/Model01-Firmware/Model01-Firmware (0.0.0-gv1.22-3-gb745) ... Press ENTER when ready...

Connecting to programmer: .avrdude: butterfly_recv(): programmer is not responding

avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding Found programmer: Id = "��"; type = w Software Version = .; Hardware Version = . avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding avrdude: error: buffered memory access not supported. Maybe it isn't a butterfly/AVR109 but a AVR910 device? avrdude: initialization failed, rc=-1 Double check connections and try again, or use -F to override this check.

avrdude: butterfly_recv(): programmer is not responding avrdude: error: programmer did not respond to command: leave prog mode avrdude: butterfly_recv(): programmer is not responding avrdude: error: programmer did not respond to command: exit bootloader Connecting to programmer: .avrdude: butterfly_recv(): programmer is not responding

avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding Found programmer: Id = "��"; type = G Software Version = .; Hardware Version = �. avrdude: butterfly_recv(): programmer is not responding avrdude: butterfly_recv(): programmer is not responding avrdude: error: buffered memory access not supported. Maybe it isn't a butterfly/AVR109 but a AVR910 device? avrdude: initialization failed, rc=-1 Double check connections and try again, or use -F to override this check.

avrdude: butterfly_recv(): programmer is not responding avrdude: error: programmer did not respond to command: leave prog mode avrdude: butterfly_recv(): programmer is not responding avrdude: error: programmer did not respond to command: exit bootloader

seemed to continue on in this vein. Tried to ^C out of it but that didn't work.

Unplugging keyboard did kill it.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/keyboardio/Model01-Firmware/issues/44, or mute the thread https://github.com/notifications/unsubscribe-auth/AACxaFQUYQcma9ojJx_xiMnxnhM9yDntks5tZzv2gaJpZM4SXjoD .

masukomi commented 6 years ago

I did not. I was waiting for the prior instruction to complete.

Might it be better to change the command line instructions to be what they actually need to be rather than half of what they need to be? That is to say

Press ENTER when ready

should be

Hold down prog and press ENTER when ready

Possibly even "and continue holding down prog until ..."

masukomi commented 6 years ago

and thank you @obra that did address the problem.

algernon commented 6 years ago

Yep, changing the line printed would be great. Do you want to make a pull request that does so? :)

Gastove commented 6 years ago

@algernon I was poking at Kaleidoscope anyways, and it turns out the instruction comes from there. Voila.

gedankenexperimenter commented 5 years ago

I believe this issue has been fully addressed in 39601fc.

algernon commented 5 years ago

Indeed, it is. Thanks for digging up the fix!