Edit - this post may be obsolete, see first reply.
---
I am getting a variety of "programmer not responding" errors as I try to program the Gateway program onto the USB-Moteino or the Motion program into a MotionMote.
Which programmer should I select? I have these available:
- AVR ISP
- AVRISP mkii
- USB tinyISP
- ArduinoISP
- USBasp
- Parallel Programmer
- Arduino as ISP
Here are a sample of the errors I get on the Moteino-USB and the Gateway program
Arduino ISP
QuoteArduino: 1.5.8 (Mac OS X), Board: "Arduino Uno"
Sketch uses 10,300 bytes (31%) of program storage space. Maximum is 32,256 bytes.
Global variables use 598 bytes (29%) of dynamic memory, leaving 1,450 bytes for local variables. Maximum is 2,048 bytes.
avrdude: stk500_recv(): programmer is not responding
Problem uploading to board. See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.
This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
AVR ISP
QuoteArduino: 1.5.8 (Mac OS X), Board: "Arduino Uno"
Sketch uses 10,300 bytes (31%) of program storage space. Maximum is 32,256 bytes.
Global variables use 598 bytes (29%) of dynamic memory, leaving 1,450 bytes for local variables. Maximum is 2,048 bytes.
avrdude: stk500_paged_write(): (a) protocol error, expect=0x14, resp=0x10
avrdude: stk500_cmd(): programmer is out of sync
Problem uploading to board. See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.
This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
AVRISP mkii
QuoteArduino: 1.5.8 (Mac OS X), Board: "Arduino Uno"
Sketch uses 10,300 bytes (31%) of program storage space. Maximum is 32,256 bytes.
Global variables use 598 bytes (29%) of dynamic memory, leaving 1,450 bytes for local variables. Maximum is 2,048 bytes.
avrdude: stk500_paged_write(): (a) protocol error, expect=0x14, resp=0x10
avrdude: stk500_cmd(): programmer is out of sync
Problem uploading to board. See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.
This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
After poking around some more, it seems like the "Programmer" selection may not be even read if the main arduino app is set to program over USB via bootloader.
So, back to square-one, I cannot connect from my Mac to the moteinos.
I have installed the Arduino 1.5.8 beta app (I think I need this beta on OSX Yosemite due to java versioning issues).
I've installed the VCO drivers (FTDIUSBSerialDriver_v2_2_18.dmg).
When I connect either the Motion Mot or the USB Moteino, the Arduino App recognized both a /dev/tty.usbserialxxx and a /dev/cu.usbserialxxx.
Sketch files compile fine.
When trying to upload, they always timeout.
Ideas??
There is Arduino IDE v 1.6 available now.
Also FTDI driver v 2.2 seems out of date unless they are numbered differently on mac. I have 2.12 on windows.
Check this post also, has some good insights: http://tomblanch.wordpress.com/2014/10/17/ftdi-woes/
Any way to try a windows machine?
Trying on windows now, but running into the arduino drivers install challenges on 64bit W7. I'll research more and let you know.
I dowloaded apps and drivers from the source web pages directly.
I'm running W7x64 and had no such installation or driver issues.
Something about unsigned drivers.
As I somewhat expected, the Arduino forum blamed it on the hardware board because it wasn't an official board. http://forum.arduino.cc/index.php?topic=281287.0
By the way, it's not a FT232RL, it's a FT231XS. Only a small number of first MoteinoUSBs had FT232RL, and that's what your picture in the Arduino forum was showing.
OK, I got that info from the github schematics and other docs. I don't think it really matters anyway.
I'm about to give up. I made some progress by uninstalling both the FTDI and Arduino Apps & Drivers and starting over.
After clearing everything, I can install the 64bit FTDI VCOM driver. At that point, I see a new generic serial port device.
I can right click that generic serial device and try to install the pre-packaged arduino uno driver staged by the installer. As soon as I hit 'ok' or whatever on the arduino uno driver I get a BSOD. MF!!
Of some note, if you look at the installer details of the Arduino app, the very end of the log I see messages about installing the amd64 drivers. What?? amd64 drivers? I have an intel cpu!
They probably install all the drivers for all CPU types. I don't think I used the Arduino bundled drivers, but the original FTDI drivers, but it's been a long time ago and I believe windows updates the drivers during windows updates.
You should check the following setting to allow windows to use a driver from Windows Update if it doesn't find the right driver on your machine:
Computer Properties > Advanced System Settings > Hardware tab > click Device Installation Settings > choose "Install driver software from Windows Update if not found on my computer"
At least that's the setting I have on my computer. Once that is working and you have the right driver you can choose "Never install driver software from Windows Update" to skip waiting every time you plug in the FTDI device.
Gave up on Win7 and went back to OSX. After some random steps I got it working. In addition to the Moteino kits I bought, I bought some spare base boards and an FTDI i/f. That board loads fine with sample programs. (note, I suppose the LED isn't wired like an Uno since blinky loads but doesn't blink)
Unfortunately, my motion-moteino board and usb-moteino seem bricked. Can I send these back to you Felix for an attempt at reflashing the bootloader?
Please contact me privately via lowpowerlab.com/contact