2006-04-09 by scmikes03
Hello All, I downloaded 4.12 and applied service pack 2. I created a winavr project I snagged some sample butterfly code from http://www.siwawi.arubi.uni-kl.de/avr_projects/#bf_app I set the device type to simulator, 169. How do I set the simulator to use the 4 meg flash memory.
Thread view
Attachments: 0
2006-04-09 by David VanHorn
Shortly after I sent the email I thought about the possibility of a pin seeing a negative voltage. Anybody know what the effect, if any, would be on the processor? How tolerant is the ATmega16 of this condition? That IS one of those "don't go there" conditions with any part. EE o
Thread view
Attachments: 0
2006-04-09 by Zack Widup
On Sun, 9 Apr 2006, John Samperi wrote: > At 05:31 AM 9/04/2006, you wrote: > >I think most of us used Dave's site as a kick off in the AVR, I know I > >did :) > > hmmm I think he deserves a few photocopies of $100.00 bills > don't you? :-) > Would a scan be OK? ;-)
Thread view
Attachments: 0
2006-04-08 by Gary J. Melvin
Thanks to all that have responded. Shortly after I sent the email I thought about the possibility of a pin seeing a negative voltage. Anybody know what the effect, if any, would be on the processor? How tolerant is the ATmega16 of this condition? I'd gladly submit the code to the
Thread view
Attachments: 0
2006-04-08 by John Samperi
At 05:31 AM 9/04/2006, you wrote: >I think most of us used Dave's site as a kick off in the AVR, I know I >did :) hmmm I think he deserves a few photocopies of $100.00 bills don't you? :-) Regards John Samperi ******************************************************** Ampertronics
Thread view
Attachments: 0
2006-04-08 by Alex Shepherd
Hi Ned, Looks like avr-nm will do the job nicely - thanks. Alex
Thread view
Attachments: 0
2006-04-08 by Kathy Quinlan
Hi John and Dave :) John Samperi wrote: > I know, back in the olden days when I was trying > to learn about the AVR I came across your website > and copied :-) the way you save and restore the SREG > (I use r15), don't have any other registers preserved > unless I need them. I th
Thread view
Attachments: 0
2006-04-08 by Ned Konz
On Apr 7, 2006, at 2:15 PM, Alex Shepherd wrote: > Hi Guys, > > Is there a utility in the WinAVR bundle that can display a sorted > list of > function sizes? Have you tried # sort by size, but mix up ROM and RAM avr-nm --size-sort --print-size -r myprog.elf # Sort first by type o
Thread view
Attachments: 0
2006-04-08 by David VanHorn
On 4/7/06, John Samperi samperi@ampertronics.com.au > wrote: At 12:30 PM 8/04/2006, you wrote: >Atmel data sheets have been known to be less than completely accurate. :) NO!!! =-O =-O Then there's Vittoz mode and CKOPT. :-P I know, back in the olden days when I was trying to lear
Thread view
Attachments: 0
2006-04-08 by John Samperi
At 12:30 PM 8/04/2006, you wrote: >Atmel data sheets have been known to be less than completely accurate. :) NO!!! =-O =-O >I do reserve a pair of registers for the ISRs, and one to store SREG >in, so that a typical ISR has no pushes or pops. I know, back in the olden days when I
Thread view
Attachments: 0
2006-04-08 by David VanHorn
however the recommendation is: From the Data sheet: --------------- It is recommended to have the Global Interrupt Flag cleared during the four last steps to avoid these problems. -------------- Well.. There's no reason to do it until you need to.. Atmel data sheets have been kno
Thread view
Attachments: 0
2006-04-07 by John Samperi
At 12:42 AM 8/04/2006, you wrote: >But you don't really need to CLI till just before the SBI EECR. >That's the only part that has to be atomic. From the Data sheet: ------------ The examples assume that interrupts are controlled (e.g., by disabling interrupts globally) so that no
Thread view
Attachments: 0
2006-04-07 by Alex Shepherd
Hi Guys, Is there a utility in the WinAVR bundle that can display a sorted list of function sizes? I had been using the avr-sizex utility to produce a sorted list of functions and their size which is shown below. However the avr-sizex utility isn't supplied in the newer WinAVR ve
Thread view
Attachments: 0
2006-04-07 by David VanHorn
The fist one (by Vittoz et. al.) is a little bit on the theoretical side, but the "Fox files" counterweight this with short practical application notes. That is good, I'd been looking for Vittoz's paper outside the walls of the IEEE. :) Unfortunately, none of this gives us specif
Thread view
Attachments: 0
2006-04-07 by David VanHorn
;Put 1 byte in temp to address pointed by Z. put_ieep_byte: sbic EECR,EEWE ;Wait for completion of previous write rjmp put_ieep_byte cli out EEARH,zh ;Set up address (in Z ) in address register out EEARL,zl out EEDR,temp ;Write data (temp) to data register sbi EECR,EEMWE ;Write l
Thread view
Attachments: 0
2006-04-07 by Larry Barello
I recently experienced severe eeprom problems when switching from a mega32 to a mega128. The solution, it turned out, was to lengthen the start up time for the external resonator. This was surprising, to me; Ever since the BOD has been available I have had zero eeprom problems (I
Thread view
Attachments: 0
2006-04-07 by Stefan Wimmer
Hi you Quartz and CKOPT tamers out there ;-) I came across a nice set of documents about Crystal oscillator design located at: http://gaia.ecs.csus.edu/~bist/pll_team_docs/papers.html The fist one (by Vittoz et. al.) is a little bit on the theoretical side, but the "Fox files" co
Thread view
Attachments: 0
2006-04-07 by John Samperi
At 12:10 PM 7/04/2006, you wrote: > Would you please post the routine you used to write to the EEPROM? All your precautions will come to nothing unless you remember to turn off interrupts whilst writing to the EEPROM. It will work most of the time / sometimes but you are likely t
Thread view
Attachments: 0
2006-04-07 by Robert Adsett
At 10:39 AM 4/6/2006 -0500, Gary J. Melvin wrote: >My client has another product in a similar application which has been >causing them a lot of grief with random EEPROM write errors, presumably >due to noise glitches. (They use the built-in Brown Out feature - >both trigger setti
Thread view
Attachments: 0
2006-04-07 by Mark Jordan
On 6 Apr 2006 at 10:39, Gary J. Melvin wrote: > > I'm open to suggestions. If you have a better approach or a > bullet-proof algorithm, please enlighten me. > Would you please post the routine you used to write to the EEPROM? Thanks.
Thread view
Attachments: 0
2006-04-07 by Ned Konz
You probably already know this, but I just figured it out and thought that maybe there's someone else out there who hadn't yet... If you're using gcc, the way that register names are defined means that the compiler doesn't know about them. That is, the preprocessor rewrites the c
Thread view
Attachments: 0
2006-04-06 by James Hatley
Hello Gary, Well ... an interesting problem ... my opinions follow ... If it was me the first thing would be to find the source of the EEPROM write errors in the similar application. Check the read/write code ... check the grounds ... the bypassing ... the filtering ... etc. Find
Thread view
Attachments: 0
2006-04-06 by Gary J. Melvin
Hello, "Long time listener, first time caller." I've taken on an ATmega16-based project. One of the requirements is that I need to write up to 3 bytes of data to EEPROM in a potentially electrically noisy environment. I've never used its EEPROM before, but it looks relatively unc
Thread view
Attachments: 0
2006-04-06 by Don AE5K
I now have an "official" answer from avr@atmel.com as follows: > On new devices is the stack pointer initialized to REMEND at reset, and you don't need to do that in your code. > Please see the datasheet of the device you're using. > I'll update the FAQ. > > Best regards > Jan Hå
Thread view
Attachments: 0
2006-04-06 by Don Kinzer
--- In AVR-Chat@yahoogroups.com, Henry Carl Ott wrote: > The newer avr parts init the stack at ramend. I just checked the mega644 via the JTAG Mk II. SP is 0x10ff prior to executing any instructions. In the mega32, on the other hand, SP comes up as 0x0000. Don ZBasic Microcontrol
Thread view
Attachments: 0
2006-04-05 by Henry Carl Ott
At 06:03 PM 4/5/2006, you wrote: >The newer avr parts init the stack at ramend. Atmel has a tendency to copy >and paste their data sheets, and these kind of conflicts creep in. > The 0x60 is a bit of a giveaway, I'm pretty sure ram STARTS at 0x100 on >most of the newer chips with
Thread view
Attachments: 0
2006-04-05 by David VanHorn
The newer avr parts init the stack at ramend. Atmel has a tendency to copy and paste their data sheets, and these kind of conflicts creep in. The 0x60 is a bit of a giveaway, I'm pretty sure ram STARTS at 0x100 on most of the newer chips with an expanded i/o space. Hmm.. Do we kn
Thread view
Attachments: 0
2006-04-05 by Henry Carl Ott
At 03:43 PM 4/5/2006, you wrote: >However, some of the most recent Atmel datasheets (for example >doc2586.pdf, 2586F dated 4/06 on the tiny 25/45/85) lead me to believe >that Atmel has gone the way of initializing the stack pointer to the top >of SRAM at reset/powerup time. In th
Thread view
Attachments: 0
2006-04-05 by David VanHorn
Normally, I'd agree with you ... but in this particular instance I have exactly 2 words left in some real tight code that I rewrote from a AVRFreaks contribution -- the original author didn't init stack and uses a rcall ;-) The code works, but I started wondering if I was playing
Thread view
Attachments: 0
2006-04-05 by Don AE5K
David VanHorn wrote: > If they've started preloading SP to the end of ram in the larger > devices, that's news. > It's no big deal either way, four instructions that execute once isn't > anything to worry about. Normally, I'd agree with you ... but in this particular instance I h
Thread view
Attachments: 0
2006-04-05 by David VanHorn
On 4/5/06, Don AE5K don@ae5k.us > wrote: As a longtime user of micros (since the Intel 4004), I know about the necessity of initializing the stack pointer in those devices which have it. :) I used to work on 4004 systems. However, some of the most recent Atmel datasheets (for exa
Thread view
Attachments: 0
2006-04-05 by Don AE5K
As a longtime user of micros (since the Intel 4004), I know about the necessity of initializing the stack pointer in those devices which have it. However, some of the most recent Atmel datasheets (for example doc2586.pdf, 2586F dated 4/06 on the tiny 25/45/85) lead me to believe
Thread view
Attachments: 0
2006-04-05 by David VanHorn
On 4/5/06, dlc dlc@frii.com > wrote: Not uncommon with AVR's in my experience. I have yet to get a board designed that didn't have problems with resets on an AVR or MEGAAVR part. What's the state of your CKOPT fuse?
Thread view
Attachments: 0
2006-04-05 by Kathy Quinlan
John Samperi wrote: > At 02:22 PM 5/04/2006, you wrote: >> If you want to first check your CKOPT fuse (the default is UNCHECKED, >> CHECK IT!!!!) that will fix a lot of problems. > > The data sheet is VERY clear that the CKOPT fuse must be set ( i.e. 0) > for clock speeds higher
Thread view
Attachments: 0
2006-04-05 by John Samperi
At 02:22 PM 5/04/2006, you wrote: >If you want to first check your CKOPT fuse (the default is UNCHECKED, >CHECK IT!!!!) that will fix a lot of problems. The data sheet is VERY clear that the CKOPT fuse must be set ( i.e. 0) for clock speeds higher than 8 MHz. I must say that I ha
Thread view
Attachments: 0
2006-04-05 by Kathy Quinlan
DLC wrote: > Indeed, I'll have to check that one out. Hmm, limited frequency, > increased noise susceptability when unchecked, additional amp, rail to > rail operation when checked. D@M! that sure sounds like the pill! I > never saw that one, that is some really hefty fine print
Thread view
Attachments: 0
2006-04-05 by DLC
Indeed, I'll have to check that one out. Hmm, limited frequency, increased noise susceptability when unchecked, additional amp, rail to rail operation when checked. D@M! that sure sounds like the pill! I never saw that one, that is some really hefty fine print hidden in there. It
Thread view
Attachments: 0
2006-04-05 by dlc
Not uncommon with AVR's in my experience. I have yet to get a board designed that didn't have problems with resets on an AVR or MEGAAVR part. I've found that if I run the part at its maximum rated frequency, I get flaky boards, if I derate by 20% or so then the board gets more re
Thread view
Attachments: 0
2006-04-05 by Kathy Quinlan
dlc wrote: > Not uncommon with AVR's in my experience. I have yet to get a board > designed that didn't have problems with resets on an AVR or MEGAAVR > part. I've found that if I run the part at its maximum rated frequency, > I get flaky boards, if I derate by 20% or so then the
Thread view
Attachments: 0
2006-04-05 by Larrie Carr
> ----- Original Message ----- > From: "kernels_nz" > To: > Sent: Monday, April 03, 2006 1:41 PM > Subject: [AVR-Chat] Re: Connecting AVRs directly to inputs of 74HC and LS > logic chips. > > > Hmmhm, discussion seems to have strayed a bit, but just in case > anyone ever runs acr
Thread view
Attachments: 0
2006-04-05 by Timothy D. Lenz
Sounds like a flaky batch of chips. ----- Original Message ----- From: "kernels_nz" To: Sent: Monday, April 03, 2006 9:37 PM Subject: [AVR-Chat] Re: Connecting AVRs directly to inputs of 74HC and LS logic chips. > hi Jim, > > Yeah, ive almost given up, sounds a bit like a beginne
Thread view
Attachments: 0
2006-04-04 by Kishore Diggavi
Hi, Thanks John & David for ur response .. can u kindly suggest me the lock bits & fuse settings .. i've placed a 20 Mhz crystal on the STK500 board. My VCC is within tolerence .. I think david is probably right .. may be the serial programming is disabled .. but i hav doubt .. a
Thread view
Attachments: 0
2006-04-04 by Tzif
Hi Les I have the MAX485EESA which is almost the same as the MAX487 but the problem is that the EESA is a SO8 I did some projects that i made an adapter to switch between the two. If it is ok with you just let me know..... I am leving in Israel so you will have to think if you ha
Thread view
Attachments: 0
2006-04-04 by Les Grant
I know this is a bit off topic but... I have a client in Adelaide who needs a MAX487CPA (DIL8) ASAP. Is there anyone on the list who may be able to assist please. Reply off list to info@grantronics.com.au. Thanks. Regards, Les Grant. ----------------------------------------------
Thread view
Attachments: 0
2006-04-04 by Leon Heller
----- Original Message ----- From: David VanHorn To: AVR-Chat@yahoogroups.com Sent: Tuesday, April 04, 2006 4:23 AM Subject: Re: [AVR-Chat] Re: Connecting AVRs directly to inputs of 74HC and LS logic chips. Very strange seeing that the typical HC chip has an input load of several
Thread view
Attachments: 0
2006-04-04 by Russell Shaw
Peter Gargano wrote: > Russell Shaw wrote: > >>If you look at fig.182 of the ATmega16 data sheet, you'll find that VIHmin=1.9V, >>so the 3V spec must be at some 3-5 sigma distribution point. > > > Russell, thanks for that. Also fig. 192 and 193 of the M64 datasheet > say the same
Thread view
Attachments: 0
2006-04-04 by Peter Gargano
Russell Shaw wrote: > If you look at fig.182 of the ATmega16 data sheet, you'll find that VIHmin=1.9V, > so the 3V spec must be at some 3-5 sigma distribution point. Russell, thanks for that. Also fig. 192 and 193 of the M64 datasheet say the same thing. Again, on the M64 data sh
Thread view
Attachments: 0
2006-04-04 by Kathy Quinlan
John Samperi wrote: > At 02:34 PM 4/04/2006, you wrote: >> You are looking at worst case, typical case is that it will work well. > > ...at room temperature of about 25 deg. :-) I would not use that > method for, say, automotive application like Peter would use it for > and defin
Thread view
Attachments: 0
2006-04-04 by John Samperi
At 02:37 PM 4/04/2006, you wrote: >The DDR was set such that the 4 pins >connecting to the inputs of the logic chip (74ls138 and 74hc138) were 1's. hmmm you are not using the JTAG pins of the Mega 16 for your output are you? If so is the JTAG disabled? Regards John Samperi ******
Thread view
Attachments: 0
2006-04-04 by David VanHorn
On 4/3/06, Peter Gargano peter@techedge.com.au > wrote: I have the reverse concern - Driving AVRs from parts designed to be used with TTL. Most AVRs (eg Mega-168) have a 0.6VCC spec. on VIHmin meaning 3.0 Volts when run at 5.0 Volts (well, actually worse case is 0.6 x VCCmax whic
Thread view
Attachments: 0