topic Re: Clev663 board Breaking problem in LPC Microcontrollers

Clev663 board Breaking problem

lim — Fri, 16 Jul 2021 08:30:35 GMT

Hi NXP

i just debugged with a SDK example Basic discovery loop

i can building a project but when i debug to the board that make a problem

Break at address "0xdeadbeee" with no debug information available, or outside of program code.

Failed to execute MI command:
-data-disassemble -s 3735928558 -e 3735928698 -- 3
Error message from debugger back end:
Cannot access memory at address 0xdeadbeee

like that... do you have any idea about that problem?

Re: Clev663 board Breaking problem

frank_m — Fri, 16 Jul 2021 08:45:24 GMT

> Break at address "0xdeadbeee" with no debug information available, or outside of program code.

The value looks suspiciously like a preset value for a stack check. Which would point to a stack overflow at runtime.

If this happens in the debugger before it stops on a breakpoint, try to disable "run to main", and start debugging at the reset vector.

Re: Clev663 board Breaking problem

lim — Mon, 19 Jul 2021 06:31:10 GMT

Thank you for your replying .

i changed a debug information and it made other breaking point

i used a SDK example i think project doesn't have problem...

Thread #1 57005 (Suspended : Signal : SIGTRAP:Trace/breakpoint trap)

HardFault_Handler() at semihost_hardfault.c:61 0xf092
<signal handler called>() at 0xfffffff9

Re: Clev663 board Breaking problem

frank_m — Mon, 19 Jul 2021 07:38:06 GMT

> HardFault_Handler() at semihost_hardfault.c:61 0xf092
<signal handler called>() at 0xfffffff9

Now at least you got somewhere.

You can check the SCB fault registers to decode the reason, and/or single step through the preceeding assembler instructions to see where and why it faults.

Re: Clev663 board Breaking problem

lim — Tue, 20 Jul 2021 05:43:48 GMT

Thank you for your helping

i just running the example project and displayed Basic Discovery Example

but when i detected card ,board doesn't working...

Re: Clev663 board Breaking problem

frank_m — Tue, 20 Jul 2021 05:58:21 GMT

I think you would need to debug into the SDK code, down to instruction level if necessary.

I do not have a CLRC663 board. But even SDK examples might contain bugs occasionally.