|
osdir.com mailing list archive |
|
Subject: avrdude and AT89S8253 (how can I change reset polarity via file) - msg#00064List: hardware.avr.avrdude.develtoday I tested my USBprog (based on AVR069) with an AT89S8253. And it works. But I missed a parameter in the configuration file for parts which tells avrdude that the command SET_PARAMETER PARAM_RESET_POLARITY must be called. Is there a parameter which can cause this? http://www.embedded-projects.net/index.php?page_id=241 (here is a german page with the configuration). Also there is a bug, or i miss understood this. The AT89S8253 has got only 2 signature bytes. But if I configure memory "signature" size = 2; avrdude ignore this. It's no problem I can use this at the moment with the configuration memory "signature" size = 2; and as compare signature signature = 0x1e 0x73 0x1e; (because he get the first signature byte at third read call) But how can I force a RESET_POLARITY call via the configuration file? Regards Benedikt Thread at a glance:
Previous Message by Date: click to view message previewRE: Avrdude Gui problem>> Remember, it was EW that said "factory floor" is a >> justification for a gui. But so far, EW has rejected >> the input that came from people with actual factory >> floor experience (and I don't mean me by that.) > > What I reject is two things: > - Something that is clearly outside the scope of the > avrdude project, which is an all encompassing .zip file to contain > everything and the kitchen sink. > - More talk. Is there any reason that bell and whistles couldn't be implemented via some sort of scripting or plugins? Seems to me that having a set of dll's that one could use would be a good idea. Mr Foo Next Message by Date: click to view message preview[bug #22699] Errors in AVR910 Device CodesURL: <http://savannah.nongnu.org/bugs/?22699> Summary: Errors in AVR910 Device Codes Project: AVR Downloader/UploaDEr Submitted by: None Submitted on: Sunday 03/23/2008 at 03:32 UTC Category: None Severity: 3 - Normal Priority: 5 - Normal Item Group: None Status: None Privacy: Public Assigned to: None Originator Name: Mike Perks Originator Email: mikep@xxxxxxxxxxxxx Open/Closed: Open Discussion Lock: Any _______________________________________________________ Details: It is important to maintain support for AVR910 programmers and therefore a few corrections to the AVR910 devices codes is required (looking at AVRDude 5.5): 1. The following devices do not have AVR910 device code in the conf file: mega48, mega88, mega168. These should be added so a AVR910 can be used for these devices. 2. The following devices use device code 0x75 although that is already allocated to the mega16 bootloader. I suggest that device code 0x73 might be better: mega329, mega329p, mega3290, mega3290p, mega649, mega6490. 3. The device code for mega162 is listed as 0x63 but this should be 0x62 because device code 0x63 is for the mega162 bootloader. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?22699> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/ Previous Message by Thread: click to view message previewHelloHi, I just started appending to this list so I thought it would be a good idea to introduce myself. I am a professional software engineer/architect at a large software/hardware company. I actually got interested in first electronics and then software as a teenager. That was 30 years ago. I have a wealth of experience in C, C++ and Java and have used all 3 to build large software applications for both my company products and for customers with custom applications. I got back into electronics a few years ago and AVRs in particular. I have several websites including: * http://home.austin.rr.com/perks/micros/ * http://oakmicros.com I started Oak Micros to first create ZBasic devices (based on AVRs) and then AVR devices such as the om128. I like the functionality of AVRDude but have always found it hard to use. Recently I started working on updating my 3 year old AVR910 programmer and hit some device code problems (documented on avrfreaks but needs to be copied here to be hopefully fixed in the next release). So rather than just simply complain about problems I thought I would get involved. Regards Mike Perks Next Message by Thread: click to view message preview[bug #22699] Errors in AVR910 Device CodesURL: <http://savannah.nongnu.org/bugs/?22699> Summary: Errors in AVR910 Device Codes Project: AVR Downloader/UploaDEr Submitted by: None Submitted on: Sunday 03/23/2008 at 03:32 UTC Category: None Severity: 3 - Normal Priority: 5 - Normal Item Group: None Status: None Privacy: Public Assigned to: None Originator Name: Mike Perks Originator Email: mikep@xxxxxxxxxxxxx Open/Closed: Open Discussion Lock: Any _______________________________________________________ Details: It is important to maintain support for AVR910 programmers and therefore a few corrections to the AVR910 devices codes is required (looking at AVRDude 5.5): 1. The following devices do not have AVR910 device code in the conf file: mega48, mega88, mega168. These should be added so a AVR910 can be used for these devices. 2. The following devices use device code 0x75 although that is already allocated to the mega16 bootloader. I suggest that device code 0x73 might be better: mega329, mega329p, mega3290, mega3290p, mega649, mega6490. 3. The device code for mega162 is listed as 0x63 but this should be 0x62 because device code 0x63 is for the mega162 bootloader. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?22699> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/ Loading Comments...
|
|
