2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler

Hi,
I'm using LPC2378 and playing with uC/TCP-IP stack from Micrium.

I'm asking help for an annoying problem:
When starting to debug with IAR ew, the program crashes in EMAC_Init
while initializing MAC1 = 0 (which is "MAC Configuration Register 1",
comment of the line says "Deassert all prior resets").

After the crash J-Link says "Unable to halt ARM core" and I can't get
to debug mode anymore. After this I have to erase the flash to get
debugging, and the program does again the same thing as described above.

So wondering if it's about the program or something with the board?
None of the other programs I have tried does the same as this one.

Regards

Jukka
------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

>> After the crash J-Link says "Unable to halt ARM core" and I can't get to debug mode anymore

Typically when a debugger is unable to halt the CPU, it is due to a data fault where the memory manager is locked up. You have a problem with your code. Set breakpoints earlier until you reach the section that causes the lockup.

Chris.

[Non-text portions of this message have been removed]
------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

--- In l...@yahoogroups.com, "HM2" wrote:
>
> >> After the crash J-Link says "Unable to halt ARM core" and I can't
get to debug mode anymore
>
> Typically when a debugger is unable to halt the CPU, it is due to a
data fault where the memory manager is locked up. You have a problem
with your code. Set breakpoints earlier until you reach the section
that causes the lockup.
>
> Chris.
>

Thanks Chris for your response.

I also got e-mail from Micrium and now the problem is solved.

So if someone else is facing the same kind of issues with EMAC, my
answer was that I had defined a wrong silicon revision (should have
noticed it since have seen similar issues with other stacks :). At
least it matters the value of PINSEL2.

Regards
Jukka
------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )