ubuntu - Cannot program Atmega1284p with arduino on linux, works on mac -


this issue driving me nuts. working on project other guys built electronics. have custom boards atmega 1284p. usb cummunication 1284p use ftdi ft230x usb bridge. doesn't have dtr; rts used reset board using capacitor (pretty off shelf arduinos).

the arduino bootloader used, , use mighty-1284p upload. board selected "original mighty 1284p 8mhz". after installing right ftdi drivers http://www.ftdichip.com/drivers/vcp.htm can upload board mac. linux has these drivers built kernel. however, cannot upload board. avr gives following error:

avrdude: ser_recv(): programmer not responding avrdude: stk500_recv(): programmer not responding avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x00 avrdude: send: 0 [30]   [20] 

dmesg gives following:

... [   51.299964] usbcore: registered new interface driver ftdi_sio [   51.300088] ftdi_sio 1-1.2:1.0: ftdi usb serial device converter detected ... 

and lspci:

... bus 001 device 006: id 0403:6015 future technology devices international, ltd bridge(i2c/spi/uart/fifo) ... 

the settings mac , linux machine identical. on both use arduino 1.0.5. both see correct serial port.

i've seen many posts in forum similar problems, have yet find 1 solution works me. holding reset, or clicking before uploading not work. suggested in forums have tried removing brltty no avail. have tried uploading arduino ide, eclipse avr plugin , avr via command-line. none work. i've tried on different machines different versions of ubuntu, , uploading works in none of them. adding -c arduino avrdude command doesn't trick either. ideas on how fix this?

my user part of dialout group, , can upload other arduino boards (like duemilanove) without problems.

this question asked here: http://forum.arduino.cc/index.php?topic=244363

you mentioned ubuntu; doing normal user?

if so, may need add account correct group, serial port device belongs to.

you can this:

sudo usermod -a -g dialout 

then (easiest) logout , log in again.

however, possible called other dialout in latest ubuntu, haven't checked. can confirm still dialout here on debian wheezy.

(this little odd, though, if works; permission error instead...)


Comments

Popular posts from this blog

commonjs - How to write a typescript definition file for a node module that exports a function? -

openid - Okta: Failed to get authorization code through API call -

thorough guide for profiling racket code -