Re: [atreus] Re: Updating A-star program from Atreus keyboard reset not working on Mac
- Nick Pascucci
- 2015-04-01 @ 19:09
The upload target in the makefile will wait for the designated interface to
become available before starting the programming process, so if you run
'make upload' and then reset it should work just fine as well. Once the
microcontroller exits the bootloader it won't appear in /dev/ anymore.
You already know the name of the interface you need, but for posterity's
sake here's how I found mine:
Run 'watch ls -C /dev/' and reset the keyboard. A new device should appear
for a few seconds and then disappear - that's the keyboard's
microcontroller while it's in the bootloader.
On Wed, Apr 1, 2015 at 2:59 PM, Dustin Brewer <email@example.com>
> I am a noob to the Atreus keyboard, but I have successfully programmed it
> a number of times on my mac.
> Since you have already programmed the keyboard, it will only appear as
> /dev/cu.usbmodemfd121 (for you) for about 8 seconds after you do the reset
> key-sequence (the yellow light should be flashing).
> What I do is add a sleep 5 command before the upload command, and reset
> the keyboard before 5 seconds elapses:
> sleep 5 && make upload USB=/dev/cu.usbmodemfd121
> Hope that helps!
> I successfully programmed my Atreus keyboard the first time w ith the
>> hardware reset, but I have not yet been able to program it using the
>> keyboard reset. I am pretty sure I am getting the Atreus to reset to the
>> bootloader properly, but any programming attempt just hangs. I used the
>> recommended homebrew tools on a cleanly restored MacBook Air 4,2 running
>> up-to-date Yosemite.
>> On the successful programming I had to specify the
>> USB=/dev/cu.usbmodemfd121 (found by the dev-on dev-off procedure). After
>> that, I used the OS to identify the keyboard and now /dev/cu.usbmodem no
>> longer appears and no other /dev/* toggles based on whether the keyboard
>> is connected.
>> When I try to program without specifying a USB device, it uses
>> dev/ttyACM0, but that does not appear in /dev.
>> I expect I am missing something simple, maybe related to how Apple reveals
>> USB devices.
>> Does anyone have any suggestions?
>> Thanks, (especially to Phil for putting together a great kit)