[En-Nut-Discussion] RE: En-Nut-Discussion digest, Vol 1 #150 - 1 msg

[ptlinux]

Hi,

I have got through the burning error; I found that my parallel port
setting was causing the burning issue I had earlier. Now I went through
the erase chip alrite.. but when I am flashing the .hex file.. I got the
follow error?


Any thing wrong with what I am doing? 

I am using NutOS 3.0.1 under Windows XP Pro.


C:\ethernut\nut\app\timers>make burn
uisp -dprog=stk200 --erase --upload --verify if=timers.hex
Atmel AVR ATmega128 is found.
Erasing device ...
Reinitializing device
Atmel AVR ATmega128 is found.
Uploading: flash

flash error at address 0x257c: file=0xa2, mem=0xff
flash error at address 0x257d: file=0x0e, mem=0xff
flash error at address 0x257e: file=0xb3, mem=0xff
flash error at address 0x257f: file=0x1e, mem=0xff
flash error at address 0x2580: file=0x20, mem=0xff
flash error at address 0x2581: file=0x80, mem=0xff
flash error at address 0x2582: file=0x31, mem=0xff
flash error at address 0x2583: file=0x80, mem=0xff
flash error at address 0x2584: file=0x37, mem=0xff
flash error at address 0x2585: file=0xfe, mem=0xff
flash error at address 0x2586: file=0xcf, mem=0xff
flash error at address 0x2587: file=0xcf, mem=0xff
flash error at address 0x2588: file=0x34, mem=0xff
flash error at address 0x2589: file=0xe0, mem=0xff
flash error at address 0x258a: file=0x83, mem=0xff
flash error at address 0x258b: file=0x2a, mem=0xff
flash error at address 0x258c: file=0x30, mem=0xff
flash error at address 0x258d: file=0x94, mem=0xff
flash error at address 0x258e: file=0x21, mem=0xff
flash error at address 0x258f: file=0x94, mem=0xff
flash error at address 0x2590: file=0x31, mem=0xff

-----Original Message-----
From: en-nut-discussion-admin at egnite.de
[mailto:en-nut-discussion-admin at egnite.de] On Behalf Of
en-nut-discussion-request at egnite.de
Sent: Friday, March 21, 2003 10:00 PM
To: en-nut-discussion at egnite.de
Subject: En-Nut-Discussion digest, Vol 1 #150 - 1 msg

Send En-Nut-Discussion mailing list submissions to
	en-nut-discussion at egnite.de

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.egnite.de/mailman/listinfo/en-nut-discussion
or, via email, send a message with subject or body 'help' to
	en-nut-discussion-request at egnite.de

You can reach the person managing the list at
	en-nut-discussion-admin at egnite.de

When replying, please edit your Subject line so it is more specific
than "Re: Contents of En-Nut-Discussion digest..."


Today's Topics:

   1. Re: Weird "Make Burn" Problem (Theodore A. Roth)

--__--__--

Message: 1
Date: Thu, 20 Mar 2003 14:44:13 -0800 (PST)
From: "Theodore A. Roth" <troth at openavr.org>
To: en-nut-discussion at egnite.de
Subject: Re: [En-Nut-Discussion] Weird "Make Burn" Problem
Reply-To: en-nut-discussion at egnite.de



On Thu, 20 Mar 2003, Hideaki Shishido wrote:

:)
:) Hi Pat,
:)
:) I concern about 2 point.
:)
:) first:
:)   Pat> stk500 -dATmega128 -e -pf -vf -ifbasemon.hex
:)               ^^^^^^^^^^^
:) I'm using "-dpart=" to specify devices, such as "-dpart=atmega128"
:) You can use "dpart=auto", may be.

For uisp, use -dpart=<device> where <device> is case-insensitive.
-d<device> is most definitely wrong.

The stk500 can not do auto detection of the target device. This is
because you have to download a bunch of device config params to the
stk500 before you can read the signature bytes.

Ted Roth


--__--__--

_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo/en-nut-discussion


End of En-Nut-Discussion Digest