avrdude-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avrdude-dev] ERE EMBMega32 board and avrdude.conf


From: Nathan Smith
Subject: Re: [avrdude-dev] ERE EMBMega32 board and avrdude.conf
Date: Sat, 15 Jan 2005 09:30:44 +1000
User-agent: Mozilla Thunderbird 0.8 (Windows/20040913)

Rune Christensen wrote:

-----Original Message-----
From: Nathan Smith [mailto:address@hidden Sent: Friday, January 14, 2005 12:26 PM
To: address@hidden
Subject: Re: [avrdude-dev] ERE EMBMega32 board and avrdude.conf


Rune Christensen wrote:

-----Original Message-----
From:
address@hidden
[mailto:address@hidden
u.org] On Behalf Of Nathan Smith
Sent: Friday, January 14, 2005 10:10 AM
To: Nathan Smith
Cc: avrdude-dev
Subject: Re: [avrdude-dev] ERE EMBMega32 board and avrdude.conf


Nathan Smith wrote:

Ok, I'm using the standard download cable (ISP-AVR) for the
ERE Mega32
board (www.ere.co.th).

I emailed them and got the lpt pin out.

I've tried (1) setting up my own, new, programmer in
avrdude.conf and
(2) modifying another entry to suit the ERE ISP-AVR cable.

Unfortunately nothing I've done works.

The download cable uses a 7407 buffer and the pinout has a
pin out for
the parallel port has a pin labelled "CONT" along with
"MOSI, SCK, RES
etc". Within the download cable, "CONT" is tied high.  Could this
"CONT" pin need to be pulsed to get it to download? And if so what should I try within avrdude to get it is pulse or whatever anyone suggests here.

Thanks


Having now checked to 7407 datasheet I can't see why it is
there. In the actual header pin out to the board it doesn't actually seem to connect to anything. I'm stumped why the extra pin called "CONT" is there.

Anyway, any thoughts what I should do next? I've told avr dude which
parallel port pins end up connecting to MOSI, MISO, SCK and
RESET and
avrdude says "device not responding"


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.11 - Release Date:
12/01/2005

_______________________________________________
avrdude-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/avrdude-dev

Hello

Please send the email from ERE and also what you have done in the avrdude.conf file.

Is the CONT input or output?

/Rune
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0502-2, 11-01-2005
Tested on: 14-01-2005 11:03:33
avast! - copyright (c) 1988-2004 ALWIL Software. http://www.avast.com








Thanks.
This is the what I've done in avrdude.conf (obviously without the #). I've attached the file as well.

#programmer
# ATTEMPT TO USE ERE PROGRAMMER
#  id    = "futurlec";
#  desc  = "Futurlec.com programming cable.";
#  type  = par;
#  reset = 4;
#  sck   = 3;
#  mosi  = 2;
#  miso  = 10;
#;

Hello
First of all each programmer must have an ID that is not used before.

programmer
 id    = "ere-avrisp";
 desc  = "ERE AVR ISP"
 type  = par;
 reset = 4;
 sck   = 3;
 mosi  = 2;
 miso  = 10;
;

Have you used AVRDude before with success on the same computer?
What operating system are you using?

As far as I can see you can just ignore CONT.

/Rune
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0502-2, 11-01-2005
Tested on: 14-01-2005 13:43:13
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com






Yes, I've used avrdude on the same PC happily to program the at90s2313 before. I am using Win2k but I have givoio all set up and working and I've verified that it is operating. I do realise each programmer needs its own ID, Like I said I first tried a separate entry, when that didn't work I tried modifying a "known good" entry. That is why I had played around with the entries for the "futurlec" programmer. I had tried it previously as a separate entry.

I agree, it looks like "CONT" doesn't require avrdude to use it.

I will try Joerg's suggestion and post the -vvvv output.


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 12/01/2005





reply via email to

[Prev in Thread] Current Thread [Next in Thread]