librelist archives

« back to archive

Problem uploading firmware

Problem uploading firmware

From:
Jeremy Dunck
Date:
2015-07-22 @ 23:27
Hi, I am working on an a-star atreus, trying to upload from a Mac 10.10.4.
I searched github issues for similar things and found nothing.  Here's my
logs.  Any pointers?

Thanks,
   Jeremy


$ diff /tmp/dev-off /tmp/dev-on
17a18
> cu.usbmodem1411
194a196
> tty.usbmodem1411


$ ls -l /dev/cu.usbmodem1411
crw-rw-rw-  1 root  wheel   18,   9 Jul 22 16:15 /dev/cu.usbmodem1411

$ make upload USB=/dev/cu.usbmodem1411
cp -n layout_qwerty.h layout.h
avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o atreus.o
atreus.c
avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o
usb_keyboard.o usb_keyboard.c
avr-gcc -mmcu=atmega32u4 usb_keyboard.o atreus.o -o atreus
avr-size atreus
   text   data    bss    dec    hex filename
   2886    346    199   3431    d67 atreus
avr-objcopy -O ihex -R .eeprom atreus atreus.hex
while [ ! -r /dev/cu.usbmodem1411 ]; do sleep 1; done; \
avrdude -p atmega32u4 -c avr109 -U flash:w:atreus.hex -P
/dev/cu.usbmodem1411

Connecting to programmer: .avrdude: butterfly_recv(): programmer is not
responding
make: *** [upload] Error 1

Re: [atreus] Problem uploading firmware

From:
Andrew Griffith
Date:
2015-07-22 @ 23:42
Are you uploading for the first time or is this an update?  You have to
reset the controller manually the first time and then after that you can do
it by typing Fn+ESC and then Enter.

On Wed, Jul 22, 2015 at 4:27 PM, Jeremy Dunck <jdunck@gmail.com> wrote:

> Hi, I am working on an a-star atreus, trying to upload from a Mac
> 10.10.4.  I searched github issues for similar things and found nothing.
> Here's my logs.  Any pointers?
>
> Thanks,
>    Jeremy
>
>
> $ diff /tmp/dev-off /tmp/dev-on
> 17a18
> > cu.usbmodem1411
> 194a196
> > tty.usbmodem1411
>
>
> $ ls -l /dev/cu.usbmodem1411
> crw-rw-rw-  1 root  wheel   18,   9 Jul 22 16:15 /dev/cu.usbmodem1411
>
> $ make upload USB=/dev/cu.usbmodem1411
> cp -n layout_qwerty.h layout.h
> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o atreus.o
> atreus.c
> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o
> usb_keyboard.o usb_keyboard.c
> avr-gcc -mmcu=atmega32u4 usb_keyboard.o atreus.o -o atreus
> avr-size atre us
>    text   data    bss    dec    hex filename
>    2886    346    199   3431    d67 atreus
> avr-objcopy -O ihex -R .eeprom atreus atreus.hex
> while [ ! -r /dev/cu.usbmodem1411 ]; do sleep 1; done; \
> avrdude -p atmega32u4 -c avr109 -U flash:w:atreus.hex -P
> /dev/cu.usbmodem1411
>
> Connecting to programmer: .avrdude: butterfly_recv(): programmer is not
> responding
> make: *** [upload] Er ror 1
>

Re: [atreus] Problem uploading firmware

From:
Andrew Griffith
Date:
2015-07-22 @ 23:47
I guess I should say that is just the keyboard prep.  You still have to run
make upload.

If you need instructions on the manual reset I can explain. You have to
have physical access to the controller.

On Wed, Jul 22, 2015 at 4:42 PM, Andrew Griffith <andrewg@griffithind.com>
wrote:

> Are you uploading for the first time or is this an update?  You have to
> reset the controller manually the first time and then after that you can do
> it by typing Fn+ESC and then Enter.
>
> On Wed, Jul 22, 2015 at 4:27 PM, Jeremy Dunck <jdunck@gmail.com> wrote:
>
>> Hi, I am working on an a-star atreus, trying to upload from a Mac
>> 10.10.4.  I searched github issues for similar things and found nothing.
>> Here's my logs.  Any pointers?
>>
>> Thanks,
>>    Jeremy
>>
>>
>> $ diff /tmp/dev-off /tmp/dev-on
>> 17a18
>> > cu.usbmodem1411
>> 194a196
>> > tty.usbmodem1411
>>
>>
>> $ ls -l /dev/cu.usbmodem1411
>> crw-rw-rw-  1 root  wheel   18,   9 Jul 22 16:15 /dev/cu.usbmodem1411
>>
>> $ make upload USB=/dev/cu.usbmodem1411
>> cp -n layout_qwerty.h layout.h
>> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o
>> atreus.o atreus.c
>> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o
>> usb_keyboard.o usb_keyboard.c
>> avr-gcc -mmcu=atmega32u4 usb_keyboard.o atreus.o -o atreus
>> avr-size atre us
>>    text   data    bss    dec    hex filename
>>    2886    346    199   3431    d67 atreus
>> avr-objcopy -O ihex -R .eeprom atreus atreus.hex
>> while [ ! -r /dev/cu.usbmodem1411 ]; do sleep 1; done; \
>> avrdude -p atmega32u4 -c avr109 -U flash:w:atreus.hex -P
>> /dev/cu.usbmodem1411
>>
>> Connecting to programmer: .avrdude: butterfly_recv(): programmer is not
>> responding
>> make: *** [upload] Er ror 1
>>
>
>

Re: [atreus] Problem uploading firmware

From:
Jeremy Dunck
Date:
2015-07-22 @ 23:59
It's the first load.

Do you mean a hard reset is needed *before* upload?

The instructions on the firmware repo say "Run make upload with the
keyboard plugged in, and then activate the bootloader with reset (see
below).", which made me think it was needed *after* upload.


On Wed, Jul 22, 2015 at 4:47 PM, Andrew Griffith <andrewg@griffithind.com>
wrote:

> I guess I should say that is just the keyboard prep.  You still have to
> run make upload.
>
> If you need instructions on the manual reset I can explain. You have to
> have physical access to the controller.
>
> On Wed, Jul 22, 2015 at 4:42 PM, Andrew Griffith <andrewg@griffithind.com>
> wrote:
>
>> Are you uploading for the first time or is this an update?  You have to
>> reset the controller manually the first time and then after that you can do
>> it by typing Fn+ESC and then Enter.
>>
>> On Wed, Jul 22, 2015 at 4:27 PM, Jeremy Dunck <jdunck @gmail.com
>> <jdunck@gmail.com>> wrote:
>>
>>> Hi, I am working on an a-star atreus, trying to upload from a Mac
>>> 10.10.4.  I searched github issues for similar things and found nothing.
>>> Here's my logs.  Any pointers?
>>>
>>> Thanks,
>>>    Jeremy
>>>
>>>
>>> $ diff /tmp/dev-off /tmp/dev-on
>>> 17a18
>>> > cu.usbmodem1411
>>> 194a196
>>> > tty.usbmodem1411
>>>
>>>
>>> $ ls -l /dev/cu.usbmodem1411
>>> crw-rw-rw-  1 root  wheel   18,   9 Jul 22 16:15 /dev/cu.usbmodem1411
>>>
>>> $ make upload USB=/dev/cu.usbmodem1411
>>> cp -n layout_qwerty.h layout.h
>>> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o
>>> atreus.o atreus.c
>>> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu= atmega32u4 -c -o
>>> usb_keyboard.o usb_keyboard.c
>>> avr-gcc -mmcu=atmega32u4 usb_keyboard.o atreus.o -o atreus
>>> avr-size atre us
>>>    text   data    bss    dec    hex filename
>>>    2886    346    199   3431    d67 atreus
>>> avr-objcopy -O ihex -R .eeprom atreus atreus.hex
>>> while [ ! -r /dev/cu.usbmodem1411 ]; do sleep 1; done; \
>>> avrdude -p atmega32u4 -c avr109 -U flash:w:atreus.hex -P
>>> /dev/cu.usbmodem1411
>>>
>>> Connecting to programmer: .avrdude: butterfly_recv(): programmer is not
>>> responding
>>> make: *** [upload] Er ror 1
>>>
>>
>>
>

Re: [atreus] Problem uploading firmware

From:
Joe Schonbok
Date:
2015-07-23 @ 03:37
You need to do the reset to put the a-star in boot loader mode - the first
time you need to do that by shorting the two pins as described in the
instructions.  The LED on the a-star should "breathe" not just blink on and
off, it will "breathe" - dimming and brightening.  When it is doing that,
then you do the make upload.  After you have your first layout uploaded,
then you should be able to use the keyboard to initiate the boot loader
mode.  It only lasts a few seconds, so get the command prepped, get the LED
breathing, then hit return and do the upload.


On Wed, 22 Jul 2015 at 16:59 Jeremy Dunck <jdunck@gmail.com> wrote:

> It's the first load.
>
> Do you mean a hard reset is needed *before* upload?
>
> The instructions on the firmware repo say "Run make upload with the
> keyboard plugged in, and then activate the bootloader with reset (see
> below).", which made me think it was needed *after* upload.
>
>
> On Wed, Jul 22, 2015 at 4:47 PM, Andrew Griffith <andrewg@griffithind.com>
> wrote:
>
>> I guess I should say that is just the keyboard prep.  You still have to
>> run make upload.
>>
>> If you need instructions on the manual reset I can explain. You have to
>> have physical access to the controller.
>>
>> On Wed, Jul 22, 2015 at 4:42 PM, Andrew Griffith <andrewg@griffithind.com
>> > wrote:
>>
>>> Are you uploading for the first time or is this an update?  You have to
>>> reset the controller manually the first time and then after that you can do
>>> it by typing Fn+ESC and then Enter.
>>>
>>> On Wed, Jul 22, 2015 at 4:27 PM, Jeremy Dunck <jdunck @gmail.com
>>> <jdunck@gmail.com>> wrote:
>>>
>>>> Hi, I am working on an a-star atreus, trying to upload from a Mac
>>>> 10.10.4.  I searched github issues for similar things and found nothing.
>>>> Here's my logs.  Any pointers?
>>>>
>>>> Thanks,
>>>>    Jeremy
>>>>
>>>>
>>>> $ diff /tmp/dev-off /tmp/dev-on
>>>> 17a18
>>>> > cu.usbmodem1411
>>>> 194a196
>>>> > tty.usbmodem1411
>>>>
>>>>
>>>> $ ls -l /dev/cu.usbmodem1411
>>>> crw-rw-rw-  1 root  wheel   18,   9 Jul 22 16:15 /dev/cu.usbmodem1411
>>>>
>>>> $ make upload USB=/dev/cu.usbmodem1411
>>>> cp -n layout_qwerty.h layout.h
>>>> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o
>>>> atreus.o at reus.c
>>>> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu= atmega32u4 -c -o
>>>> usb_keyboard.o usb_keyboard.c
>>>> avr-gcc -mmcu=atmega32u4 usb_keyboard.o atreus.o -o atreus
>>>> avr-size atre us
>>>>    text   data    bss    dec    hex filename
>>>>    2886    346    199   3431    d67 atreus
>>>> avr-objcopy -O ihex -R .eeprom atreus atreus.hex
>>>> while [ ! -r /dev/cu.usbmodem1411 ]; do sleep 1; done; \
>>>> avrdude -p atmega32u4 -c avr109 -U flash:w:atreus.hex -P
>>>> /dev/cu.usbmodem1411
>>>>
>>>> Connecting to programmer: .avrdude: butterfly_recv(): programmer is not
>>>> responding
>>>> make: *** [upload] Er ror 1
>>>>
>>>
>>>
>>
>

Re: [atreus] Problem uploading firmware

From:
Andrew Griffith
Date:
2015-07-23 @ 03:46
Good explanation Joe.

The pins are marked RST and GND I believe. It is only the first time where
this is required.  It is a pain if you have put everything together 
already. Shamefully it took me more than one attempt. Three or four at 
least. 

> On Jul 22, 2015, at 8:37 PM, Joe Schonbok <joebok@gmail.com> wrote:
> 
> You need to do the reset to put the a-star in boot loader mode - the 
first time you need to do that by shorting the two pins as described in 
the instructions.  The LED on the a-star should "breathe" not just blink 
on and off, it will "breathe" - dimming and brightening.  When it is doing
that, then you do the make upload.  After you have your first layout 
uploaded, then you should be able to use the keyboard to initiate the boot
loader mode.  It only lasts a few seconds, so get the command prepped, get
the LED breathing, then hit return and do the upload.
> 
> 
>> On Wed, 22 Jul 2015 at 16:59 Jeremy Dunck <jdunck@gmail.com> wrote:
>> It's the first load.
>> 
>> Do you mean a hard reset is needed *before* upload?
>> 
>> The instructions on the firmware repo say "Run make upload with the 
keyboard plugged in, and then activate the bootloader with reset (see 
below).", which made me think it was needed *after* upload.
>> 
>> 
>>> On Wed, Jul 22, 2015 at 4:47 PM, Andrew Griffith 
<andrewg@griffithind.com> wrote:
>>> I guess I should say that is just the keyboard prep.  You still have 
to run make upload.  
>>> 
>>> If you need instructions on the manual reset I can explain. You have 
to have physical access to the controller.
>>> 
>>>> On Wed, Jul 22, 2015 at 4:42 PM, Andrew Griffith 
<andrewg@griffithind.com> wrote:
>>>> Are you uploading for the first time or is this an update?  You have 
to reset the controller manually the first time and then after that you 
can do it by typing Fn+ESC and then Enter.
>>>> 
>>>>> On Wed, Jul 22, 2015 at 4:27 PM, Jeremy Dunck <jdunck @gmail.com> wrote:
>>>>> Hi, I am working on an a-star atreus, trying to upload from a Mac 
10.10.4.  I searched github issues for similar things and found nothing.  
Here's my logs.  Any pointers?
>>>>> 
>>>>> Thanks,
>>>>>    Jeremy
>>>>> 
>>>>> 
>>>>> $ diff /tmp/dev-off /tmp/dev-on
>>>>> 17a18
>>>>> > cu.usbmodem1411
>>>>> 194a196
>>>>> > tty.usbmodem1411
>>>>> 
>>>>> 
>>>>> $ ls -l /dev/cu.usbmodem1411
>>>>> crw-rw-rw-  1 root  wheel   18,   9 Jul 22 16:15 /dev/cu.usbmodem1411
>>>>> 
>>>>> $ make upload USB=/dev/cu.usbmodem1411
>>>>> cp -n layout_qwerty.h layout.h
>>>>> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu=atmega32u4 -c -o 
atreus.o at reus.c
>>>>> avr-gcc -std=gnu99 -Os -D F_CPU=16000000UL -mmcu= atmega32u4 -c -o 
usb_keyboard.o usb_keyboard.c
>>>>> avr-gcc -mmcu=atmega32u4 usb_keyboard.o atreus.o -o atreus
>>>>> avr-size atre us
>>>>>    text	   data	    bss	    dec	    hex	filename
>>>>>    2886	    346	    199	   3431	    d67	atreus
>>>>> avr-objcopy -O ihex -R .eeprom atreus atreus.hex
>>>>> while [ ! -r /dev/cu.usbmodem1411 ]; do sleep 1; done; \
>>>>> 	avrdude -p atmega32u4 -c avr109 -U flash:w:atreus.hex -P 
/dev/cu.usbmodem1411
>>>>> 
>>>>> Connecting to programmer: .avrdude: butterfly_recv(): programmer is 
not responding
>>>>> make: *** [upload] Er ror 1

Re: [atreus] Problem uploading firmware

From:
Phil Hagelberg
Date:
2015-07-23 @ 04:45
Jeremy Dunck <jdunck@gmail.com> writes:

> It's the first load.
>
> Do you mean a hard reset is needed *before* upload?
>
> The instructions on the firmware repo say "Run make upload with the
> keyboard plugged in, and then activate the bootloader with reset (see
> below).", which made me think it was needed *after* upload.

The `make upload` process will wait until the device it's pointed at
becomes visible, so you can run that command first. If you do the reset
first it can work, but you need to make sure that the compilation
completes before the board exits the bootloader, 8 seconds after the
reset.

There is a bug in the USB stack of Ubuntu 14.10 that causes an error
like the one you're seeing, but I haven't heard of it happening on Mac
OS X. It is common for it to take a few tries for `avrdude` to
successfully connect to the board for some reason though.

-Phil

Re: [atreus] Problem uploading firmware

From:
Jeremy Dunck
Date:
2015-07-24 @ 03:52
I've attempted the hard reset to get it to "breathe" before running `make
upload`, and I'm unable to get it out of the default blinking mode.

I'm *pretty sure* I'm hitting the ground and reset pins, but not certain
because it's soldered in with the face plate blocking the printed pins.
I've counted the offsets and compared to this image from the assembly guide
- looks right to me?

https://i.imgur.com/ldITKGg.png

Here's a video of me trying with the wire + pins, and normal blinking.

https://www.youtube.com/watch?v=KwwNlPrG6bY

Any ideas?  I'm really hoping I don't have to pull the board apart - I
already messed up one key's lead and delaminated one of the traces (on
switch 11:3, after realizing the key needed to be inserted from the top of
the face rather than the bottom) -- probably a dead board if I pull it
apart again. :-(

I'm regretting not taking more pictures as I went.  Oops.


On Wed, Jul 22, 2015 at 9:45 PM, Phil Hagelberg <phil@hagelb.org> wrote:

> Jeremy Dunck <jdunck@gmail.com> writes:
>
> > It's the first load.
> >
> > Do you mean a hard reset is needed *before* upload?
> >
> > The instructions on the firmware repo say "Run make upload with the
> > keyboard plugged in, and then activate the bootloader with reset (see
> > below).", which made me think it was needed *after* upload.
>
> The `make upload` process will wait until the device it's pointed at
> becomes visible, so you can run that command first. If you do the reset
> first it can work, but you need to make sure that the compilation
> completes before the board exits the bootloader, 8 seconds after the
> reset.
>
> There is a bug in the USB stack of Ubuntu 14.10 that causes an error
> like the one you're seeing, but I haven't heard of it happening on Mac
> OS X. It is common for it to take a few tries for `avrdude` to
> successfully connect to the board for some reason though.
>
> -Phil
>

Re: [atreus] Problem uploading firmware

From:
Phil Hagelberg
Date:
2015-07-28 @ 06:05
Sorry for the late reply here.

Jeremy Dunck <jdunck@gmail.com> writes:

> Here's a video of me trying with the wire + pins, and normal blinking.
>
> https://www.youtube.com/watch?v=KwwNlPrG6bY

You're definitely hitting the right pins, but it's possible that you're
also connected to some other pins, which could prevent the reset pin
From actually going low. If you have a multimeter, check for continuity
between the ground pin and the other nearby pins.

The other possibility is that the connection between the PCB and the
controller daughterboard (through the diode leg) is not solid.

> Any ideas? I'm really hoping I don't have to pull the board apart - I
> already messed up one key's lead and delaminated one of the traces (on
> sw itch 11: 3, after realizing the key needed to be inserted from the
> top of the face rather than the bottom) -- probably a dead board if I
> pull it apart again. :-(

Just remember that the circuit board is there as a convenience, not as a
strict requirement. The worst case scenario for when it gets damaged is
that you end up routing around the damage with a bit of hookup
wire. In fact, it's totally possible to build the whole keyboard without
any circuit board at all, it's just a lot more work:

  https://www.flickr.com/photos/technomancy/14577661067

If you've only placed a handful of keys so far, I think removing them
would be the way to go to debug this. Using a desoldering pump would
make it much easier to do without damaging the board.

Hope that helps.

-Phil

Re: [atreus] Problem uploading firmware

From:
Jeremy Dunck
Date:
2015-08-16 @ 01:18
Just reporting back here -- I couldn't see any short connections between
the visible a-star pins, but couldn't rule it out.

I got a solder pump and desoldered the keys I'd attached, then the a-star.
With the bare a-star, after verifying no shorts between the pins, I still
couldn't get it to reset ("breathe") by shorting reset and ground.  I think
I must have killed the a-star somehow, or received a defective one.  I'll
order a replacement and report back when it arrives.  Bummer. :-/



On Mon, Jul 27, 2015 at 11:05 PM, Phil Hagelberg <phil@hagelb.org> wrote:

> Sorry for the late reply here.
>
> Jeremy Dunck <jdunck@gmail.com> writes:
>
> > Here's a video of me trying with the wire + pins, and normal blinking.
> >
> > https://www.youtube.com/watch?v=KwwNlPrG6bY
>
> You're definitely hitting the right pins, but it's possible that you're
> also connected to some other pins, which could prevent the reset pin
> >From actually going low. If you have a multimeter, check for continuity
> between the ground pin and the other nearby pins.
>
> The other possibility is that the connection between the PCB and the
> controller daughterboard (through the diode leg) is not solid.
>
> > Any ideas? I'm really hoping I don't have to pull the board apart - I
> > already messed up one key's lead and delaminated one of the traces (on
> > sw itch 11: 3, after realizing the key needed to be inserted from the
> > top of the face rather than the bottom) -- probably a dead board if I
> > pull it apart again. :-(
>
> Just remember that the circuit board is there as a convenience, not as a
> strict requirement. The worst case scenario for when it gets damaged is
> that you end up routing around the damage with a bit of hookup
> wire. In fact, it's totally possible to build the whole keyboard without
> any circuit board at all, it's just a lot more work:
>
>   https://www.flickr.com/photos/technomancy/14577661067
>
> If you've only placed a handful of keys so far, I think removing them
> would be the way to go to debug this. Using a desoldering pump would
> make it much easier to do without damaging the board.
>
> Hope that helps.
>
> -Phil
>

Re: [atreus] Problem uploading firmware

From:
Andrew Griffith
Date:
2015-07-24 @ 05:07
It looks like you are hitting the correct pins. But you are not getting the
same blinking I got.  It was noticeably different.  I am wondering if your
microcontroller is shorting out somewhere, maybe some of the solder points
are crossing over.  I would take a very good look at everything you can
see, maybe between the microcontroller and the PCB.  I am just guessing. I
don't know for sure, but a short somewhere else on the PCB could cause an
issue with the reset too.

Maybe Phil can save us.

On Thu, Jul 23, 2015 at 8:52 PM, Jeremy Dunck <jdunck@gmail.com> wrote:

> I've attempted the hard reset to get it to "breathe" before running `make
> upload`, and I'm unable to get it out of the default blinking mode.
>
> I'm *pretty sure* I'm hitting the ground and reset pins, but not certain
> because it's soldered in with the face plate blocking the printed pins.
> I've counted the offsets and compared to this image from the assembly guide
> - looks right to me?
>
> https://i.imgur.com/ldITKGg.png
>
> Here's a video of me trying with the wire + pins, and normal blinking.
>
> https://www.youtube.com/watch?v=KwwNlPrG6bY
>
> Any ideas?  I'm really hoping I don't have to pull the board apart - I
> already messed up one key's lead and delaminated one of the traces (on
> switch 11: 3, after realizing the key needed to be inserted from the top of
> the face rather than the bottom) -- probably a dead board if I pull it
> apart again. :-(
>
> I'm regretting not taking more pictures as I went.  Oops.
>
>
> On Wed, Jul 22, 2015 at 9:45 PM, Phil Hagelberg <phil@hagelb.org> wrote:
>
>> Jeremy Dunck <jdunck@gmail.com> writes:
>>
>> > It's the first load.
>> >
>> > Do you mean a hard reset is needed *before* upload?
>> >
>> > The instructions on the firmware repo say "Run make upload with the
>> > keyboard plugged in, and then activate the bootloader with reset (see
>> > below).", which made me think it was needed *after* upload.
>>
>> The `make upload` process will wait until the device it's pointed at
>> becomes visible, so you can run that command first. If you do the reset
>> first it can work, but you need to make sure that the compilation
>> completes before the board exits the bootloader, 8 seconds after the
>> reset.
>>
>> There is a bug in the USB stack of Ubuntu 14.10 that causes an error
>> like the one you're seeing, but I haven't heard of it happening on Mac
>> OS X. It is common for it to take a few tries for `avrdude` to
>> successfully connect to the board for some reason though.
>>
>> -Phil
>>
>
>

Re: [atreus] Problem uploading firmware

From:
Andrew Griffith
Date:
2015-07-23 @ 05:08
It only took about 2 seconds to compile on my MacBook Pro. I guess that is
why it worked for me. Sounds like I could have done the steps in the 
correct order and not had to rush. 

Sent from my iPhone

> On Jul 22, 2015, at 9:45 PM, Phil Hagelberg <phil@hagelb.org> wrote:
> 
> Jeremy Dunck <jdunck@gmail.com> writes:
> 
>> It's the first load.
>> 
>> Do you mean a hard reset is needed *before* upload?
>> 
>> The instructions on the firmware repo say "Run make upload with the
>> keyboard plugged in, and then activate the bootloader with reset (see
>> below).", which made me think it was needed *after* upload.
> 
> The `make upload` process will wait until the device it's pointed at
> becomes visible, so you can run that command first. If you do the reset
> first it can work, but you need to make sure that the compilation
> completes before the board exits the bootloader, 8 seconds after the
> reset.
> 
> There is a bug in the USB stack of Ubuntu 14.10 that causes an error
> like the one you're seeing, but I haven't heard of it happening on Mac
> OS X. It is common for it to take a few tries for `avrdude` to
> successfully connect to the board for some reason though.
> 
> -Phil

Re: [atreus] Problem uploading firmware

From:
Kyle Isom
Date:
2015-07-22 @ 23:40
Hello Jeremy,

I had to run `make upload` with `sudo` on some machines where the
permissions on the device didn't allow the user to access it. Does that
work for you?

Cheers,
Kyle

Re: [atreus] Problem uploading firmware

From:
Jeremy Dunck
Date:
2015-07-22 @ 23:57
The device is world-writable (as shown in the `ls -l ` line), but I ran it
with sudo just to double-check.  Same error.  :-/


On Wed, Jul 22, 2015 at 4:40 PM, Kyle Isom <isomk@kyleisom.net> wrote:

> Hello Jeremy,
>
> I had to run `make upload` with `sudo` on some machines where the
> permissions on the device didn't allow the user to access it. Does that
> work for you?
>
> Cheers,
> Kyle
>