Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: Philip Aps. - Stack Issue

2005-07-05 by lp2000c

WOW!!

Has anyone else reproduced this?

keithgw_strider:

Have you found out anything more?



--- In lpc2000@yahoogroups.com, "dsidlauskas1" <dsidlauskas@w...> 
wrote:
> Martin and All,
> 
> Sorry for the wrong message number. Message 7898 fully describes the
> problem.
> 
> In brief:
> "
> It appears anytime the PC and SP are equal except for the high byte 
of
> the address, and you run a POP {R4} instruction, the chip will pop 
two
> times off the stack thus loading R4 with the wrong value and messing
> up your stack.
> 
> for example:
> 
> 0x000001F4 POP {R4} With SP = 0x400001F4.
> 
> R4 will be loaded with the contents of 0x400001F8.
> "
> 
> Dave
> 
> --- In lpc2000@yahoogroups.com, "Martin Maurer" <mailingliste@c...> 
wrote:
> > Can you add a short summary of the problem, what the problem is ?
> > 
> > Regards,
> > 
> >          Martin
> > 
> > ----- Original Message ----- 
> > From: "lpc2100_fan" <lpc2100_fan@y...>
> > To: <lpc2000@yahoogroups.com>
> > Sent: Monday, July 04, 2005 8:12 AM
> > Subject: [lpc2000] Re: Philip Aps. - Stack Issue
> > 
> > 
> > > Dave,
> > > 
> > > Your pointer was a little misleading (7923) but I found the 
issue
> > > described in 7898.
> > > 
> > > My question to the original poster (I guess Keith) is whether 
the MAM
> > > was enabled? If not please do so.  
> > > 
> > > Did enabling the MAM change anything?
> > > 
> > > 
> > > 
> > > --- In lpc2000@yahoogroups.com, "dsidlauskas1" 
<dsidlauskas@w...>
> wrote:
> > >> Message 7923 describes a bizarre stack problem on the 213x. If
> this is
> > >> correct, it would seem to seriously limit the usefulness of 
this
> part.
> > >> 
> > >> What say you Philips Ap's?
> > >> 
> > >> Dave
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Yahoo! Groups Links
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >

Attachments

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.