FTDI bug with Yosemite

[PatLOGre]

Hello

I have a moetino R4 + FTDI adapter.
I use Arduin IDE in iBook and Yosemite (OS version).
I can upload my script once onto the moteino, having it running correctly.

But, I can't reload a new version of the script. I made many tries, I can confirm. It works only one time.

The error message is :

avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding

If I reset the board, then it works once for one time.
The FTDI driver installed on my Mac is the last one you made available on your site.

Thanks for help.
Regards

Patrick

[Felix]

Ok, can we try a different OS/computer?
Also a shorter, ideally shielded USB cable?

[LaneF]

Was there ever a solution to this post?

I have a R5-USB - Plugged it in once and uploaded "Blinky" to test it, it ran great for 20min, I unplugged it, plugged it back into the exact same cable and port a day or so later, nothing, and nothing ever since.

I've tried to re-upload "Blinky" again, one of the super small LEDs (green) on the R5 blinks a few times then the errors start rolling in.

Thanks for your help.

Lane

[kobuki]

I don't have a Mac, but are you using the latest drivers from here?

EDIT: I think this should worth a try, too.

[Felix]

This plug-it-again-and-it's-dead makes no sense, hardware doesn't die unless the FTDI chips are disabled by a bad driver, that's a crazy guess though. Another possibility is the OS remembers the signature of that chip and somehow doesn't enumerate the port again or keeps it in DTR state which would assert RST and prevent the atmega from ever jumping past the bootloader, another sci-fi guess.
My suggestion: divide and conquer method, try another computer or a PC, it's the simplest possible test.

[LaneF]

Thanks for the tips.

Kobuki - I had to load the FTDI drivers when I loaded IDE and Codebender so I think I'm up to date on that.

Felix - It doesn't make sense.  I'll try a PC I have, if it's dead, I'll order a replacement.


Thanks again

[kobuki]

Kobuki - I had to load the FTDI drivers when I loaded IDE and Codebender so I think I'm up to date on that.

Sorry for being persistent on this, but please verify you do have the latest version on that page, and please also check the sparkfun link too, it's specifically about Yosemite. You might end up with a perfectly working replacement from Felix that behaves the same way.

[HeneryH]

I had a ton of frustration getting started but the root cause of my problems were the bug in the original design for the new FTDI chips where you have to add resistors.  If I used the external FTDI adapter all went well.

To the recent poster, which device are you trying to connect via?  For instance, a GarageMote or MotionMote with internal USB or a basic Mot with an external FTDI adapter?