I'm trying to port uIP to LPC2378 using Rowley Crossworks (surprising
that nobody seems to have done this, but I can't find it anywhere -
there's a few IAR versions but they use some very IAR-specific
features).
Anyway, I eventually got it to compile and partly run, but when the
board receives a packet it drops into the undef handler. What does this
mean - is it trying to execute an undefined instruction? It appears to
have originated from the tapdev_read routine (which I've converted from
the IAR version), but the strange thing is if I put a breakpoint in
there, then it never goes to undef handler - only if it's running at
full speed.
Anybody any idea?
--
Tim Mitchell
Undef handler
Started by ●October 8, 2008
Reply by ●October 8, 20082008-10-08
Hi Tim,
> I'm trying to port uIP to LPC2378 using Rowley Crossworks (surprising
> that nobody seems to have done this, but I can't find it anywhere -
> there's a few IAR versions but they use some very IAR-specific
> features).
>
> Anyway, I eventually got it to compile and partly run, but when the
> board receives a packet it drops into the undef handler. What does this
> mean - is it trying to execute an undefined instruction? It appears to
> have originated from the tapdev_read routine (which I've converted from
> the IAR version), but the strange thing is if I put a breakpoint in
> there, then it never goes to undef handler - only if it's running at
> full speed.
Read the extensive errata. If you have a Rev - device, weep. Run it at
48MHz with the MAM disabled. The MAM, PLL, and FLASH bugs all conspire to
screw any sense of reality.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
> I'm trying to port uIP to LPC2378 using Rowley Crossworks (surprising
> that nobody seems to have done this, but I can't find it anywhere -
> there's a few IAR versions but they use some very IAR-specific
> features).
>
> Anyway, I eventually got it to compile and partly run, but when the
> board receives a packet it drops into the undef handler. What does this
> mean - is it trying to execute an undefined instruction? It appears to
> have originated from the tapdev_read routine (which I've converted from
> the IAR version), but the strange thing is if I put a breakpoint in
> there, then it never goes to undef handler - only if it's running at
> full speed.
Read the extensive errata. If you have a Rev - device, weep. Run it at
48MHz with the MAM disabled. The MAM, PLL, and FLASH bugs all conspire to
screw any sense of reality.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors