[En-Nut-Discussion] Debugging external SRAM with AVRStudio/ICC

[Joe Doubek]

Michael Fischer found the problem. On 2.00 rev-a boards the PLD TCK and
TMS lines are tied to the ATMega128 JTAG lines which was causing my PLD
to have issues latching addresses when JTAG debugging. I lifted those
pins on the PLD and now everything works like a charm! -Joe

-----Original Message-----
From: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Harald Kipp
Sent: Wednesday, July 07, 2004 11:24 AM
To: Ethernut User Chat (English)
Subject: Re: [En-Nut-Discussion] Debugging external SRAM with
AVRStudio/ICC

Joe,

did you link with crtnutram.o? Further information is here
http://www.ethernut.de/en/iccavr/index.html

Harald

At 10:09 06.07.2004 -0600, you wrote:

>Hello all, Just out of curiosity& Is it normal to have issues seeing 
>external SRAM within AVRStudio 4 (v4.09) when compiling
>
>with ICC pro? I m finding that if I have variables declared within a 
>thread, I can t see them correctly unless I make them
>
>static. Attempting to use the download memory option produces the same 
>incorrect values I see in the debugger (the external
>
>SRAM just appears as 00, 01, &, FE, FF over and over). These variables
are 
>still being read correctly in the application however
>
>because I can printf them. Is there a configuration I might be missing
for 
>debugging or is this just the state of the debugger?


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