Joel,
please add the following options to the CFLAGS and recompile it:
CFLAGS += -Wa,-adhlns=$(<:%.c=$(OBJDIR)/%.lst)
This will add the high-level source and assembler to the listing and than come
back. Which gcc version are you using?
In the mean time I still thinking...
Joel Sherrill wrote
9 2:12 PM
> To: Schwichtenberg, Knut
> Cc: simulavr-devel@nongnu.org
> Subject: Re: [Simulavr-devel] anacomp getting reserved access messages
>
> I captured a trace and deleted all of the stuff below the error.
> It appears to be happening very early in main.c.
>
> Look fo
> > here you find a usage for "-W 0x20,-". 0x20 in the
> RAM-Area of the AVR is identicall to 0x00 in the IO-Space
> which is forbidden by most AVR's. This loop puts normally
> 10.000 "*" on you terminal. Maybe it's in there to delay or
> only to confuse the maintainer ;-).
> I thought of tha
Joel,
here you find a usage for "-W 0x20,-". 0x20 in the RAM-Area of the AVR is
identicall to 0x00 in the IO-Space which is forbidden by most AVR's. This loop
puts normally 10.000 "*" on you terminal. Maybe it's in there to delay or only
to confuse the maintainer ;-). BTW: The comment block at
As Joel Sherrill wrote:
> >My only other idea would be to have a RWSphFake class instead, which
> >by default behaves like RWSph but could throw a warning when being
> >told to be really picky.
> Implemented as described.
Cool, thanks!
--
cheers, J"org .-.-. --... ...-- -.. .
Joerg Wunsch wrote:
As Joel Sherrill wrote:
rw[0x5f]= new RWSreg(this, status);
- rw[0x5e]= new RWReserved(this, 0x5e);
+ rw[0x5e]= new RWSph(this, stack); // not really but benign
My only other idea would be to have a RWSphFake class instead, which
by default behaves like RWSph but c
As Joel Sherrill wrote:
> rw[0x5f]= new RWSreg(this, status);
> - rw[0x5e]= new RWReserved(this, 0x5e);
> + rw[0x5e]= new RWSph(this, stack); // not really but benign
My only other idea would be to have a RWSphFake class instead, which
by default behaves like RWSph but could throw a warning when
Joerg Wunsch wrote:
As Joel Sherrill wrote:
0x3d - 0x3e should allow writes but a read does not
have to return the value previously written?
0x3d is SPL, and is always implemented, accept on devices with a
hardware stack which we can ignore as they are all obsolete now (like
the vener
As Joel Sherrill wrote:
> 0x3d - 0x3e should allow writes but a read does not
> have to return the value previously written?
0x3d is SPL, and is always implemented, accept on devices with a
hardware stack which we can ignore as they are all obsolete now (like
the venerable AT90S1200, but there ha
Joerg Wunsch wrote:
As Joel Sherrill wrote:
FYI the avr .h file has this:
io4433.h:/* 0x3D..0x3E SP */
Is this by convention?
Yes, that's GCC's frame pointer management. We know this is slightly
incorrect, but GCC classifies AVRs into a few rather coarse CPU models
for its code gen
As Joel Sherrill wrote:
> FYI the avr .h file has this:
>
> io4433.h:/* 0x3D..0x3E SP */
>
> Is this by convention?
Yes, that's GCC's frame pointer management. We know this is slightly
incorrect, but GCC classifies AVRs into a few rather coarse CPU models
for its code generation, and the actua
rsday, March 26, 2009 2:12 PM
To: Schwichtenberg, Knut
Cc: simulavr-devel@nongnu.org
Subject: Re: [Simulavr-devel] anacomp getting reserved access messages
I captured a trace and deleted all of the stuff below the error.
It appears to be happening very early in main.c.
Look for RESERVED.
--joel
Joel
: Joel Sherrill [mailto:joel.sherr...@oarcorp.com]
Sent: Thursday, March 26, 2009 2:12 PM
To: Schwichtenberg, Knut
Cc: simulavr-devel@nongnu.org
Subject: Re: [Simulavr-devel] anacomp getting reserved access messages
I captured a trace and deleted all of the stuff below the error.
It appears to be
I captured a trace and deleted all of the stuff below the error.
It appears to be happening very early in main.c.
Look for RESERVED.
--joel
Joel Sherrill wrote:
Schwichtenberg, Knut wrote:
Joel,
here you find a usage for "-W 0x20,-". 0x20 in the RAM-Area of the AVR is identicall to 0x00
Schwichtenberg, Knut wrote:
Joel,
here you find a usage for "-W 0x20,-". 0x20 in the RAM-Area of the AVR is identicall to 0x00 in the IO-Space which is forbidden by most AVR's. This loop puts normally 10.000 "*" on you terminal. Maybe it's in there to delay or only to confuse the maintainer ;-)
Hi,
Now that I have turned on messages for accessing
reserved locations, anacomp, using the at90s4433,
has generated messages about two reserved accesses:
The first was accessing 0x20 at the beginning main.c:
for( i=0; i<1; ++i )
*( (volatile char*) 0x20)='*';
The other is acces
16 matches
Mail list logo
