On Wed, Apr 14, 2010 at 4:19 PM, Maarten Brock wrote:
> Are you sure it doesn't write to DPTR1 when you set DPS to 1 and then
> perform MOV DPTR,#0 ? B.t.w. SDCC only uses dual datapointers in the
I'll have to test that. The Nordic documentation is not very clear. =(
> alternative crtxinit.asm
Scott,
Are you sure it doesn't write to DPTR1 when you set DPS
to 1 and then perform MOV DPTR,#0 ? B.t.w. SDCC only
uses dual datapointers in the alternative crtxinit.asm
and not in any other (generated) file IIRC.
To use the multiply unit you could adapt the _div*,
Scott,
That should do fine. You can also keep an eye on the
generated .mem file because pdata access does not set
_XPAGE every time. I usually let make echo it to the
terminal.
Modifying crtpagesfr.asm may be overkill. The other two
are required.
OTOH for real paranoia you can use an extra pe
Has anyone worked on making sdcc play nicely with the Nordic
Semiconductor nRF24 series of 8051 microcontrollers? In particular,
they have a dual DPTR mechanism which isn't quite the same as the one
SDCC uses (setting DPS seems to change the location used for @DPTR
instructions, but it doesn't cha
I'm compiling for a target (Nordic nRF24LU1) which doesn't support
pdata access -- no equivalent to an XPAGE SFR. What's the best way to
disable this feature in SDCC and ensure that my code doesn't
accidentally get an XPAGE reference?
Currently my plan is to replace crtpagesfr.asm with an empty
s
Anthony,
I don't really see how SDCC could help here. Is this debug status register
an SFR? If so you could read it anywhere in your code. But the question is
of course if you still get to that code when it is set. An interrupt might
help here. When detected you can light an LED or something or pe
