Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Messages

Browse messages

Page 216 of 307 · 15341 messages matched

call progress detection

2005-05-04 by Farzlina Ab.Hadi

hello..do you guys think that my approach for call progress detection by sampling (using a port as input) at certain intervals (using timers) is wise? is there any other way of doing it? thanks! elin

Thread view Attachments: 0

Graphic LCD - Looking for metal frame

2005-05-02 by acemailone

Maybe you will ask why I'm sending this email to this list. I'm an AVR user myself and recently I got some graphic LCDs from a computer recycle store. Unfortunately they don't have the metal frame to hold the display and the PCB together. These are T6963C based, DG071Z-1 made in

Thread view Attachments: 0

Migrating from Mega8 to Mega168

2005-05-02 by Peter Gargano

I didn't see any specific information on migrating from Mega8 to Mega168 here http://atmel.com/dyn/products/product_card.asp?part_id=3303 Anyone have any Atmel specific info? Peter.

Thread view Attachments: 0

Re: [AVR-Chat] Testing Timers In the AVR Studio Simulator ???

2005-05-02 by David Kelly

On May 1, 2005, at 9:54 AM, n4ij wrote: > I am a newby to AVR's. In fact I used to program old 8085's asajob, > but have been awayfrom programming for a while. I am playing with > at90s2313 code with timers. I have written somelong delaysand > amtrying to figure out how to simula

Thread view Attachments: 0

Testing Timers In the AVR Studio Simulator ???

2005-05-01 by n4ij

I am a newby to AVR's. In fact I used to program old 8085's asajob, but have been awayfrom programming for a while. I am playing with at90s2313 code with timers. I have written somelong delaysand amtrying to figure out how to simulate them. Can the simulator do this? If so, how?

Thread view Attachments: 0

Re: [AVR-Chat] lcd power up issues

2005-04-30 by David Kelly

On Apr 30, 2005, at 2:50 AM, Farzlina Ab.Hadi wrote: > hi..when i power up the lcd, it will display the two rows of blocks. > it only > display correctly if i power cycle or i reset my circuit. > does it mean that i need to increase the delay after i power up the > lcd or > some

Thread view Attachments: 0

Re: [AVR-Chat] lcd power up issues

2005-04-30 by Ralph Hilton

On Sat, 30 Apr 2005 15:50:11 +0800 you wrote: >hi..when i power up the lcd, it will display the two rows of blocks. it only >display correctly if i power cycle or i reset my circuit. >does it mean that i need to increase the delay after i power up the lcd or >some init problems?

Thread view Attachments: 0

lcd power up issues

2005-04-30 by Farzlina Ab.Hadi

hi..when i power up the lcd, it will display the two rows of blocks. it only display correctly if i power cycle or i reset my circuit. does it mean that i need to increase the delay after i power up the lcd or some init problems? fyi, i use ksu0069 lcd and i followed the init pro

Thread view Attachments: 0

Re: [AVR-Chat] TCP/IP over GPRS

2005-04-29 by Javier Fiasche

Piwi, tengo un amigo q labura con UDP en ARM sobre GPRS para rastreo satelital, quixzas despues te pueda ayudar, dejame ver q hago. No es un poco tarde para empezar com eso?? Saludos ----- Original Message ----- From: dan_avr To: AVR-Chat@yahoogroups.com Sent: Friday, April 29, 2

Thread view Attachments: 0

Re: [AVR-Chat] TCP/IP over GPRS

2005-04-29 by Cosmin Buhu

----- Original Message ----- From: "dan_avr" Sent: Friday, April 29, 2005 5:34 PM Subject: [AVR-Chat] TCP/IP over GPRS > People, has anybody worked with GPRS modems? I need to implement a PPP > protocol over a GPRS modem whit an AVR > Thanks! > Daniel Ethernut has PPP driver, che

Thread view Attachments: 0

TCP/IP over GPRS

2005-04-29 by dan_avr

People, has anybody worked with GPRS modems? I need to implement a PPP protocol over a GPRS modem whit an AVR Thanks! Daniel

Thread view Attachments: 0

AVRstudio simulator bug feedback & software interrupts

2005-04-28 by arhodes19044

I sent a sample code of the ATmega128 TC1 timer bug I had mentioned here a week ago. They got back to me confirming that they reproduced the error. It will not be able to be fixed in the upcoming update, but will be addressed in the future. It is odd that the bug is there because

Thread view Attachments: 0

timer_prescaler_reset

2005-04-28 by aswinefy2003

Friends I want to know more about timer prescaler reset option in ATmega32.Kindly suggest me What is the use of such a reset

Thread view Attachments: 0

Re: [AVR-Chat] Re: was eeprom ? Now about disasm

2005-04-27 by David Kelly

On Wed, Apr 27, 2005 at 05:31:13PM -0000, arhodes19044 wrote: > > In the Disasm, I can see that the interrupts are cleared. I could > not see where they were set again, but in the original source you > include, I see that a register is used to store SREG, and then to > restore it

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-27 by arhodes19044

I did like your C version of the eeprom routines. When I found out how to see the asm source of the library routine, it was hard to see what was happening without a listing of all the registers. Even then it was inconvenient. I also saw that the library routines had CLI just befo

Thread view Attachments: 0

Re: was eeprom ? Now about disasm

2005-04-27 by arhodes19044

AHA! That sourfce does it. I see that the interrupts are ALREADY cleared in the source you gave me. I also get the disasm version of my code and I see that the libc looks to be identical. In the Disasm, I can see that the interrupts are cleared. I could not see where they were se

Thread view Attachments: 0

Re: [AVR-Chat] Decode Servo PWM Signals

2005-04-27 by Brian Dean

On Tue, Apr 26, 2005 at 12:25:58AM +0300, Joel Haasnoot wrote: > I would like to decode PWM signals, for servos, such as those on > model pr rc airplanes. Does anybody have any experience, hints, > tips, code, google keywords or anything of the like? For high resolution pulse wid

Thread view Attachments: 0

Re: [AVR-Chat] was eeprom ? Now about disasm

2005-04-27 by David Kelly

On Apr 26, 2005, at 11:04 AM, arhodes19044 wrote: > I can not find the source files for the eeprom routines in libc. I > want to disable interrupts for the minimum necessary period while > writing to EEPROM. I bet that the clear/set should occur in the > write_byte function, sinc

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-27 by David Kelly

On Apr 26, 2005, at 8:33 PM, arhodes19044 wrote: > This makes sense. Did you truncate off the high bits down to (2048- > 1)because the CPU you were using had only 2k bytes of EERPROM? > Since the 128 has 4K, I guess then the address would be truncated to > (4096-1)? The target is

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-26 by arhodes19044

--- In AVR-Chat@yahoogroups.com, David Kelly wrote: > I don't quite follow your problem. Does this answer your question? > > #include > > typedef struct { > int a, > b, > c; > char s[32]; > } EEDATA; > > EEDATA eedata __attribute__ ((section (".eeprom"))); > EEDATA data; > > void

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-26 by arhodes19044

This makes sense. Did you truncate off the high bits down to (2048- 1)because the CPU you were using had only 2k bytes of EERPROM? Since the 128 has 4K, I guess then the address would be truncated to (4096-1)? -Tony --- In AVR-Chat@yahoogroups.com, David Kelly wrote: > On Tue, Ap

Thread view Attachments: 0

Re: [AVR-Chat] clocked interfaced drivers for LEDs

2005-04-26 by Russell Shaw

Robert Adsett wrote: > At 12:30 AM 4/27/05 +1000, Peter Gargano wrote: > > >>Paul Maddox wrote: >> >>>how about the good old 74HC595? serial->parallel latch? >>> >>>http://www.semiconductors.philips.com/pip/74HC595.html >> >>Paul, >> >> From the on-line datasheet for the 74HC595B

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-26 by David Kelly

On Tue, Apr 26, 2005 at 06:10:12PM -0000, arhodes19044 wrote: > > OK, I like this technique because _I_ do not have to keep track of > the address of variables in EEPROM. But.... > > Always a but. How do I use this command. I tried it in the C > source inside main(). This gave er

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-26 by David Kelly

On Tue, Apr 26, 2005 at 03:33:07PM -0000, arhodes19044 wrote: > > OOOOPS. That last part, 4 clock cyles, is pretty critical timing. > I COULD disable interrupts for just step 4 and 5. > > I can modify the code for the Libc eeprom code to suit that. This > is a very brief suspensi

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-26 by Dennis Clark

arhodes19044 wrote: > > --- In AVR-Chat@yahoogroups.com, Dennis Clark wrote: > >>Tony, >>1. Wait until EEWE becomes zero. >>2. Write new EEPROM address to EEAR (optional). >>3. Write new EEPROM data to EEDR (optional). >>4. Write a logical one to the EEMWE bit in EECR. >>5. Withi

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-26 by arhodes19044

--- In AVR-Chat@yahoogroups.com, David Kelly wrote: > It was simpler than I remembered. This puts ee_serial_number in EEPROM: > > uint32_t ee_serial_number __attribute__ ((section (".eeprom"))); > > -- > David Kelly N4HHE, dkelly@H... > ===========================================

Thread view Attachments: 0

Re: [AVR-Chat] clocked interfaced drivers for LEDs

2005-04-26 by Dennis Clark

Have you considered something like the Phillips PCA9531/2/3 chips? They are I2C based LED drivers where you can control the brightness via PWM, or, slow the clock down and control the blink rate. I've seen units with 4, 8 and 16 LEDs supported. Check them out. DLC Peter Gargano w

Thread view Attachments: 0

Re: [AVR-Chat] clocked interfaced drivers for LEDs

2005-04-26 by Robert Adsett

At 12:30 AM 4/27/05 +1000, Peter Gargano wrote: >Paul Maddox wrote: > > how about the good old 74HC595? serial->parallel latch? > > > > http://www.semiconductors.philips.com/pip/74HC595.html > >Paul, > > From the on-line datasheet for the 74HC595BQ (above) we find > > Output Driv

Thread view Attachments: 0

Re: [AVR-Chat] clocked interfaced drivers for LEDs

2005-04-26 by Peter Gargano

Paul Maddox wrote: > how about the good old 74HC595? serial->parallel latch? > > http://www.semiconductors.philips.com/pip/74HC595.html Paul, From the on-line datasheet for the 74HC595BQ (above) we find Output Drive Capability: +/- 7.8 mA on parallel output That's OK for a low br

Thread view Attachments: 0

was eeprom ? Now about disasm

2005-04-26 by arhodes19044

I can not find the source files for the eeprom routines in libc. I want to disable interrupts for the minimum necessary period while writing to EEPROM. I bet that the clear/set should occur in the write_byte function, since that is probably called by all the larger size write fun

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-26 by arhodes19044

--- In AVR-Chat@yahoogroups.com, Dennis Clark wrote: > > Tony, > 1. Wait until EEWE becomes zero. > 2. Write new EEPROM address to EEAR (optional). > 3. Write new EEPROM data to EEDR (optional). > 4. Write a logical one to the EEMWE bit in EECR. > 5. Within four clock cycles afte

Thread view Attachments: 0

Re: [AVR-Chat] clocked interfaced drivers for LEDs

2005-04-26 by Paul Maddox

Peter, > I'm after a high side (source) low impedance driver for driving > multiplexed LEDs. I'm after something like this (Allegro 6810) > > http://www.allegromicro.com/sf/6810/ > > .. but, a lower cost lower voltage source driver for 8 or more bits. how about the good old 74HC5

Thread view Attachments: 0

clocked interfaced drivers for LEDs

2005-04-26 by Peter Gargano

I'm after a high side (source) low impedance driver for driving multiplexed LEDs. I'm after something like this (Allegro 6810) http://www.allegromicro.com/sf/6810/ .. but, a lower cost lower voltage source driver for 8 or more bits. I'm planning on using someone's source driver w

Thread view Attachments: 0

Re: [AVR-Chat] Decode Servo PWM Signals

2005-04-26 by Dave Hylands

Hi Joel, > Hi > I would like to decode PWM signals, for servos, such as those on model > pr rc airplanes. Does anybody have any experience, hints, tips, code, > google keywords or anything of the like? I have some code that works for an ATMega8. I modified it from some code from

Thread view Attachments: 0

Re: [AVR-Chat] Decode Servo PWM Signals

2005-04-26 by Dennis Clark

I handled it as an interrupt based on a 10us timer rollover. At 10us tics a 1ms to 2ms (+ or - a bit) can be handled as an 8 bit number from 100 to 200. Perhaps not that greatest resolution, but adequate to my needs. You could set the timer to give you a 5us interrupt for twice t

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-26 by arhodes19044

OK, I got EEPROM writes and reads working with a minimum of fuss. The macro offsetof() worked beautifully. I even understood how it was working!!!! Amazing. I found that I had to cast it as a (void*) when I went to use it in an eeprom_write_block() function. I even made that long

Thread view Attachments: 0

Decode Servo PWM Signals

2005-04-25 by Joel Haasnoot

Hi I would like to decode PWM signals, for servos, such as those on model pr rc airplanes. Does anybody have any experience, hints, tips, code, google keywords or anything of the like? Joel

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-25 by David Kelly

On Mon, Apr 25, 2005 at 07:16:15PM -0000, arhodes19044 wrote: > > Yes, I can see that the structure will provide a convenient > technique to read & write the entire block. > > It has been a long time since I worked with structures. Is there a > way to get the offset of the elemen

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-25 by Robert Adsett

At 08:18 PM 4/25/05 +0000, arhodes19044 wrote: >Oh yeah. I remember the pain of figuring when to use the > vs . >operators. pointer references or whatever. OUCH!!! Well, I will >go through it again. name->item is a pointer dereference (it's a two character operator) name.item is

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-25 by Robert Adsett

At 07:16 PM 4/25/05 +0000, arhodes19044 wrote: >It has been a long time since I worked with structures. Is there a >way to get the offset of the element within the structure? >Something like "&structure.element". This way, I can start with the >location of the structure in SRAM o

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-25 by David Kelly

On Mon, Apr 25, 2005 at 01:38:57PM -0500, David Kelly wrote: > > As for the syntax of compiling EEPROM variables all I can say is, "I've > done it" but don't have an example under my fingertips or in CVS. IIRC > the variables were defined in a .c source file reserved specifically

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-25 by arhodes19044

Thanks! That jump starts my usage of the structures. You have been a geat help! -Tony --- In AVR-Chat@yahoogroups.com, Robert Adsett wrote: > At 08:18 PM 4/25/05 +0000, arhodes19044 wrote: > >Oh yeah. I remember the pain of figuring when to use the > vs . > >operators. pointer re

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-25 by David Kelly

On Mon, Apr 25, 2005 at 05:12:13PM -0000, arhodes19044 wrote: > > > Actually, that struct idea is just perfect. > > I definitely was planning on keeping an SRAM version of the > variables, then only save the requesite info when necessary. > > One of these will be a "first-run" fl

Thread view Attachments: 0

Re: [AVR-Chat] Re: need variables to be stored in EEPROM

2005-04-25 by Dennis Clark

Tony, About disabling interrupts during EEPROM writes, see below: arhodes19044 wrote: > > Actually, that struct idea is just perfect. > > I definitely was planning on keeping an SRAM version of the > variables, then only save the requesite info when necessary. > > One of these wi

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-25 by arhodes19044

Oh yeah. I remember the pain of figuring when to use the > vs . operators. pointer references or whatever. OUCH!!! Well, I will go through it again. 2 reasons. The structure needed for the initializer variables, then the data log which is a PERFECT structure application. so as I

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-25 by arhodes19044

Great! I do not remember the "offsetof()" function. I will look it up right now. THANKS -Tony --- In AVR-Chat@yahoogroups.com, Robert Adsett wrote: > At 07:16 PM 4/25/05 +0000, arhodes19044 wrote: > >It has been a long time since I worked with structures. Is there a > >way to get

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-25 by arhodes19044

Yes, I can see that the structure will provide a convenient technique to read & write the entire block. It has been a long time since I worked with structures. Is there a way to get the offset of the element within the structure? Something like "&structure.element". This way, I c

Thread view Attachments: 0

Re: [AVR-Chat] need variables to be stored in EEPROM

2005-04-25 by Philipp Adelt

Hi Tony, arhodes19044 schrieb: > I see in the docs how to use the registers to access the EEPROM on > my ATmega128. > > However, Which part of it is allowed to be used? Is there nothing > in it unless I use it myself? This is correct, you can use each and every byte. There have b

Thread view Attachments: 0

Re: need variables to be stored in EEPROM

2005-04-25 by arhodes19044

Actually, that struct idea is just perfect. I definitely was planning on keeping an SRAM version of the variables, then only save the requesite info when necessary. One of these will be a "first-run" flag which will allow initialization of the EEPROM, then there are some setting

Thread view Attachments: 0

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.