AVR-Chat

From: "Honea" 
2. RE: at89C4051
From: "Dave Miller" 
3. Re: at89C4051
From: "Honea" 
4. Re: at89C4051
From: Zack Widup 
5. help
From: rajesh parwani 
6. Re: help
From: Ralph Hilton 
7. RE: Strcmp() problem stepping through AVR Studio
From: "wbounce" 
8. Re: Strcmp() problem stepping through AVR Studio
From: Brian Dean 
9. Re: Problem using MAKE - seems to be a path problem
From: "arhodes19044" 
10. Re: Re: Problem using MAKE - seems to be a path problem
From: David Kelly 
11. Jumpers !!
From: Ahmad El-Saied 
12. Re: Re: Problem using MAKE - seems to be a path problem
From: Dave Hylands 
13. Re: Jumpers !!
From: Dave VanHorn 
14. JTAG MK II and /RESET
From: "alwelch93021" 


________________________________________________________________________
________________________________________________________________________

Message: 1 
Date: Tue, 12 Apr 2005 18:05:48 -0400
From: "Honea" 
Subject: at89C4051

Hello, This at89C4051 chip is before my time (in my AVR lifespan ;) )
And I was wondering how you program it.. since it doesn't have jtag..

Here is the spec sheet:
http://www.atmel.com/atmel/acrobat/doc1001.pdf


So on the older chips, you have to have a programming board like the stk500?
No simple/single cable programming?


thanks
Lee

[This message contained attachments]



________________________________________________________________________
________________________________________________________________________

Message: 2 
Date: Tue, 12 Apr 2005 15:20:04 -0700
From: "Dave Miller" 
Subject: RE: at89C4051

Hello,



The AT89 series is actually an MCS51 family (8051) core not an AVR core.
This chip is NOT in circuit programmable and must be programmed using a
parallel programmer such as this: www.needhams.com
. It is a great chip that I still use today in a
few projects.



Thanks,

Dave Miller



_____ 

From: Honea [mailto:fredit@charter.net] 
Sent: Tuesday, April 12, 2005 3:06 PM
To: AVR-Chat@yahoogroups.com
Subject: [AVR-Chat] at89C4051



Hello, This at89C4051 chip is before my time (in my AVR lifespan ;) )

And I was wondering how you program it.. since it doesn't have jtag..



Here is the spec sheet:

http://www.atmel.com/atmel/acrobat/doc1001.pdf





So on the older chips, you have to have a programming board like the stk500?

No simple/single cable programming?





thanks

Lee



_____ 

Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/AVR-Chat/

* To unsubscribe from this group, send an email to:
AVR-Chat-unsubscribe@yahoogroups.com


* Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service. 



[This message contained attachments]



________________________________________________________________________
________________________________________________________________________

Message: 3 
Date: Tue, 12 Apr 2005 18:38:31 -0400
From: "Honea" 
Subject: Re: at89C4051

Oh :/ 

So in the last couple of years AVR has moved from using other people's cores (and adding some features) to now AVR developing their own core + peripherals?

thanks-Lee

----- Original Message ----- 
From: Dave Miller 
To: AVR-Chat@yahoogroups.com 
Sent: Tuesday, April 12, 2005 6:20 PM
Subject: RE: [AVR-Chat] at89C4051


Hello,



The AT89 series is actually an MCS51 family (8051) core not an AVR core. This chip is NOT in circuit programmable and must be programmed using a parallel programmer such as this: www.needhams.com. It is a great chip that I still use today in a few projects.



Thanks,

Dave Miller




------------------------------------------------------------------------------

From: Honea [mailto:fredit@charter.net] 
Sent: Tuesday, April 12, 2005 3:06 PM
To: AVR-Chat@yahoogroups.com
Subject: [AVR-Chat] at89C4051



Hello, This at89C4051 chip is before my time (in my AVR lifespan ;) )

And I was wondering how you program it.. since it doesn't have jtag..



Here is the spec sheet:

http://www.atmel.com/atmel/acrobat/doc1001.pdf





So on the older chips, you have to have a programming board like the stk500?

No simple/single cable programming?





thanks

Lee





------------------------------------------------------------------------------
Yahoo! Groups Links

a.. To visit your group on the web, go to:
http://groups.yahoo.com/group/AVR-Chat/

b.. To unsubscribe from this group, send an email to:
AVR-Chat-unsubscribe@yahoogroups.com

c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 



[This message contained attachments]



________________________________________________________________________
________________________________________________________________________

Message: 4 
Date: Tue, 12 Apr 2005 17:36:50 -0700
From: Zack Widup 
Subject: Re: at89C4051

That is an MCS-51 family chip. You'd need a programmer to program it.

I think my Needhams EMP-30 will do it. But there are many programmers 
on the market. You might find one cheap on eBay.

Zack


Honea wrote:

> Hello, This at89C4051 chip is before my time (in my AVR lifespan ;) )
> And I was wondering how you program it.. since it doesn't have jtag..
> 
> Here is the spec sheet:
> http://www.atmel.com/atmel/acrobat/doc1001.pdf
> 
> 
> So on the older chips, you have to have a programming board like the 
> stk500?
> No simple/single cable programming?
> 
> 
> thanks
> Lee
>
> ------------------------------------------------------------------------
> Yahoo! Groups Links
>
> * To visit your group on the web, go to:
> http://groups.yahoo.com/group/AVR-Chat/
> 
> * To unsubscribe from this group, send an email to:
> AVR-Chat-unsubscribe@yahoogroups.com
> 
> 
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service .
>
>



________________________________________________________________________
________________________________________________________________________

Message: 5 
Date: Tue, 12 Apr 2005 23:43:42 +0100 (BST)
From: rajesh parwani 
Subject: help

can any one give me good links or documents for biometric security system like finger scanning system. 



Yahoo! India Matrimony: Find your life partneronline.

[This message contained attachments]



________________________________________________________________________
________________________________________________________________________

Message: 6 
Date: Wed, 13 Apr 2005 02:19:57 +0200
From: Ralph Hilton 
Subject: Re: help

On Tue, 12 Apr 2005 23:43:42 +0100 (BST) you wrote:

>can any one give me good links or documents for biometric security system like finger scanning system. 
>
>
>
>Yahoo! India Matrimony: Find your life partneronline.

Try google. www.google.com 


--
Ralph Hilton
http://www.ralphhilton.org
C-Meter: http://www.cmeter.org
FZAOINT http://www.fzaoint.net


________________________________________________________________________
________________________________________________________________________

Message: 7 
Date: Tue, 12 Apr 2005 21:30:18 -0400
From: "wbounce" 
Subject: RE: Strcmp() problem stepping through AVR Studio

Thanks Brain for the suggestion. I did that and AVR Studio is still
messed up. 


-----Original Message-----
From: Brian Dean [mailto:bsd@bdmicro.com] 
Sent: Tuesday, April 12, 2005 1:18 AM
To: AVR-Chat@yahoogroups.com
Subject: Re: [AVR-Chat] Strcmp() problem stepping through AVR Studio



On Sun, Apr 10, 2005 at 10:51:01PM -0400, wbounce wrote:

> If have serveral strcmp statements
> 
> Originally I had them all like this.
> 
> if (strcmp("GPGGA",gcBuffer) == 0)
> {
> gpFieldPtr=(PGM_P) GGA;
> } 
> 
> It would execute the pointer assignment on each of the 8 statements
> 
> I changed them to
> 
> lnResult = strcmp("GPGLL",gcBuffer);
> if (lnResult == 0)
> {
> gpFieldPtr=GLL;
> }
> 
> So I could see the result code of strcmp. This time it skipped the 1st

> 3 ok but then started doing the assignments. And when it got to the 
> strcmp that should have matched, lnResult was not 0 and yet it did the

> assignment anyhow.
> 
> Anyone have any idea why?

I'm not sure about the problem, but just a quick observation. With
AVR-GCC, string references like above consume both Flash as well as
precious RAM. It can add up quickly, too. To rewrite those to save RAM
space, try:

strcmp_P(PSTR("GPGLL"),gcBuffer);

This references the string data directly from Flash and saves making a
copy of it to RAM.

-Brian
-- 
Brian Dean
BDMICRO - ATmega128 Based MAVRIC Controllers http://www.bdmicro.com/



Yahoo! Groups Links










________________________________________________________________________
________________________________________________________________________

Message: 8 
Date: Tue, 12 Apr 2005 21:51:34 -0400
From: Brian Dean 
Subject: Re: Strcmp() problem stepping through AVR Studio

Woops - looks like I told you the order wrong for strcmp_P(), should
be:

strcmp_P(gcBuffer, PSTR("GPGLL"));

Sorry about that.

Also, I wasn't really suggusting this as a fix to the problem you are
seeing, though there was an off chance that it could help if you were
running out of RAM. Strange things happing when your stack grows down
into your variable space.

It was more the case that it can save you lots of RAM if you have many
strcmp()'s using constant strings.

-Brian

On Tue, Apr 12, 2005 at 09:30:18PM -0400, wbounce wrote:
> DomainKey-Signature: 
> To: 
> From: "wbounce" 
> Date: Tue, 12 Apr 2005 21:30:18 -0400
> Subject: RE: [AVR-Chat] Strcmp() problem stepping through AVR Studio
> 
> Thanks Brain for the suggestion. I did that and AVR Studio is still
> messed up.


________________________________________________________________________
________________________________________________________________________

Message: 9 
Date: Wed, 13 Apr 2005 03:05:19 -0000
From: "arhodes19044" 
Subject: Re: Problem using MAKE - seems to be a path problem


Here is the error report from make:

----------------------------------------
> "make.exe" all
make.exe: *** No rule to make target `all'. Stop.

> Process Exit Code: 2
---------------------------------------------------

My path is:

%SYSTEMROOT%\system32;%SYSTEMROOT%;%SYSTEMROOT%\system32
\WBEM;F:\winavr\bin;F:\winavr\utils\bin;C:\PROGRA~1\ATITEC~1
\ATICON~1;C:\Program Files\ATI Technologies\ATI Control Panel


---------------------------------------------------------

I even modified the path to only point to the winavr directories in 
case some of the other entries screwed it up. No change in its 
actions. Maybe it is related to being on the F drive and something 
in make expects the C drive.

When I put a copy of the make utility directly in the current 
directory (demo), then make worked fine.

There are no other instances of make elsewhere on my computer, so 
some other make is not interfering with the correct one. I have not 
yet moved the winavr directory to the C drive, and I will not be 
doing that any time soon. That drive is getting flaky and needs to 
be replaced.

So, I have worked-around the issue by putting a copy of the make 
utility in each project directory. Not pretty but it works.

Any ideas from anyone now? I am fresh out of ideas of what is wrong.

-Tony


--- In AVR-Chat@yahoogroups.com, Dave Hylands wrote:
> Hi Tony,
> 
> > Any ideas why the path would not work right?
> 
> What's the exact output when it fails?
> 
> What path are you using?
> 
> How are you setting the PATH?
> 
> If you're using cmd.exe, you can click on the icon in the top left 
and
> choose properties, and then under options make sure QuickEdit is
> selected.
> 
> Then you can drag your mouse over the window to select text and 
press
> Enter. This will copy the selected text into the clipboard. You can
> paste text into the window using a right-click.
> 
> Just be careful using QuickEdit though. If you click in the window 
and
> the title bar changes to "Select ..." then all output to the window
> stops under you press ENTER or ESC.
> 
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/





________________________________________________________________________
________________________________________________________________________

Message: 10 
Date: Tue, 12 Apr 2005 22:55:56 -0500
From: David Kelly 
Subject: Re: Re: Problem using MAKE - seems to be a path problem


On Apr 12, 2005, at 10:05 PM, arhodes19044 wrote:

> Here is the error report from make:
>
> ----------------------------------------
>> "make.exe" all
> make.exe: *** No rule to make target `all'. Stop.
>
>> Process Exit Code: 2
> ---------------------------------------------------

[...]

> Any ideas from anyone now? I am fresh out of ideas of what is wrong.

Your error message makes perfect sense. The rule tree for the target 
"all" is incomplete. From the make.info document:

`No rule to make target `XXX'.'
`No rule to make target `XXX', needed by `YYY'.'
This means that `make' decided it needed to build a target, but
then couldn't find any instructions in the makefile on how to do
that, either explicit or implicit (including in the default rules
database).

I *know* the following Makefile works. Save it as "Makefile", 
capital-M. Also either create an empty file named ".depend" (dot 
depend) or comment out the last line. If you "make depend" then a new 
.depend will be created including all the #include dependancies it 
found in your sources. Make sure the indented lines are indented with 
tabs. Some makes are sensitive, some are not. I forgot which way GNU 
make permits/requires.

Very little editing would be needed to convert this to your project. 
Just the MCU line, SRCS, and change "object.elf", "object.bin", and 
"object.list" if you don't like that name for the final product.

#
#$Id: Makefile,v 1.27 2005/03/22 22:31:36 dkelly Exp $
#
CC= avr-gcc
#MCU=atmega8
#MCU=atmega16
#MCU=atmega32
#MCU=atmega163
#MCU=atmega323
#MCU=atmega64
MCU=atmega128

CFLAGS= -O -gdwarf-2 -Wall -ffreestanding -mmcu=$(MCU)
LDFLAGS= -Wl,-Map,$@.map

.SUFFIXES:
.SUFFIXES: .c .o .bin .elf .hex .srec .list

.c.o:
$(CC) $(CFLAGS) -c $<

.elf.bin:
avr-objcopy -R .eeprom -O binary $< $@

.elf.hex:
avr-objcopy -O ihex $< $@

.elf.srec:
avr-objcopy -O srec $< $@

#
# This is a fun conversion, creates an assembly dump
# including C source lines interspersed as comments.
#
.elf.list:
avr-objdump -DS $< > $@

# one per line makes CVS diffs easier to read
SRCS = \
main.c \
uarts.c \
timers.c \
cmm.c \
cmm_cmd.c \
misc.c \
it.c \
eeprom.c

OBJS = $(SRCS:.c=.o)

all: object.elf object.bin object.list

object.elf: $(OBJS)
$(CC) -o $@ $(CFLAGS) $(LDFLAGS) $(OBJS) $(LDLIBS)
avr-size $@

clean:
rm -f *~ *.elf *.cof *.bin *.hex *.srec *.s *.o *.pdf *core *.list 
*.map

# BSD make automatically reads .depend if it exists
depend: $(SRCS)
$(CC) -E -M $(SRCS) > .depend

# GNU make apparently must be told to include .depend
include .depend


--
David Kelly N4HHE, dkelly@HiWAAY.net
========================================================================
Whom computers would destroy, they must first drive mad.



________________________________________________________________________
________________________________________________________________________

Message: 11 
Date: Wed, 13 Apr 2005 05:16:42 +0100 (BST)
From: Ahmad El-Saied 
Subject: Jumpers !!

Hi All,
In some circuits, specially burners, i find
something called Jumper ... what is it's function ??
-- & what is the ICSP too ??
Thanks in Advance
Ahmad El-Saied 

Send instant messages to your online friends http://uk.messenger.yahoo.com 


________________________________________________________________________
________________________________________________________________________

Message: 12 
Date: Tue, 12 Apr 2005 22:33:45 -0700
From: Dave Hylands 
Subject: Re: Re: Problem using MAKE - seems to be a path problem

Hi Tony,

> My path is:
> 
> %SYSTEMROOT%\system32;%SYSTEMROOT%;%SYSTEMROOT%\system32
> \WBEM;F:\winavr\bin;F:\winavr\utils\bin;C:\PROGRA~1\ATITEC~1
> \ATICON~1;C:\Program Files\ATI Technologies\ATI Control Panel

It sounds like there's a make.exe that's in one of these directories:
%SYSTEMROOT%\system32
%SYSTEMROOT%;%SYSTEMROOT%\system32\WBEM
F:\winavr\bin

and it's not compatible with the make that comes with WinAVR.

Putting the make.exe into the "current" directory causes the correct
one to be executed.

Try removing the make.exe and try this instead:

f:\winavr\utils\bin\make

iIf that works and typing make by itself doesn't, then there's almost
certainly another make earlier in your path.

-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/


________________________________________________________________________
________________________________________________________________________

Message: 13 
Date: Wed, 13 Apr 2005 01:06:19 -0500
From: Dave VanHorn 
Subject: Re: Jumpers !!

At 11:16 PM 4/12/2005, Ahmad El-Saied wrote:

>Hi All,
> In some circuits, specially burners, i find
>something called Jumper ... what is it's function ??
>-- & what is the ICSP too ??
> Thanks in Advance
> Ahmad El-Saied

A jumper is sort of like a switch, but on a semi-permanent basis.

ICSP = In Circuit Serial Programming, like an AVRISP does.




________________________________________________________________________
________________________________________________________________________

Message: 14 
Date: Wed, 13 Apr 2005 13:29:28 -0000
From: "alwelch93021" 
Subject: JTAG MK II and /RESET


Having my JTAG work for hours and then refuse to go into debug I looked 
over all the signals and only thing I found suspect was the /reset 
line. Data sheet shows it should pull up to .85 X VCC and I run +5 VCC. 
My reset was showing a high level of around 3.2vdc with a 10k pull up 
on the line. I plan to reduce that to 5k today and see what i get.

Any one else seen problems with JTAG refusing to start debugging when 
the /reset was not pulled up enough?

Al Welch





________________________________________________________________________
________________________________________________________________________



------------------------------------------------------------------------
Yahoo! Groups Links




------------------------------------------------------------------------







---------------------------------
Post your free ad now! Yahoo! Canada Personals

At 05:50 PM 4/13/2005, Dave Hylands wrote:

>Hi Ma,
>
>It wou.

Indeed.