LPC54S018-EVK can't debug freertos_hello

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPC54S018-EVK can't debug freertos_hello

1,429 Views
rf66
Contributor I

Hello

I'm new to using MCUXpresso(v11.9.0) and FreeRTOS, I'm looking at the examples attached with SDK (version 2.15.000). I can't debug the FreeRTOS examples, for example in the case of freertos_hello the Debugger Console reports this:

GNU gdb (Arm GNU Toolchain 12.3.Rel1 (Build arm-12.35)) 13.2.90.20230627-git

Copyright (C) 2023 Free Software Foundation, Inc.

.................................

 

 

Program stopped.

0x0000089a in vPortFree (pv=0x20000018 <s_debugConsoleState+12>) at ../freertos/freertos-kernel/portable/MemMang/heap_4.c:339

339 }

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: could not convert 'main' from the host encoding (CP1252) to UTF-32.

This normally should not happen, please file a bug report.

 

or

 

Program stopped.

warning: (Internal error: pc 0x0 in read in CU, but not in symtab.)

prvIdleTask (pvParameters=0x0 <DbgConsole_Getchar>) at ../freertos/freertos-kernel/tasks.c:3467

3467 if( listCURRENT_LIST_LENGTH( &( pxReadyTasksLists[ tskIDLE_PRIORITY ] ) ) > ( UBaseType_t ) 1 )

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: (Internal error: pc 0x214 in read in CU, but not in symtab.)

warning: could not convert 'main' from the host encoding (CP1252) to UTF-32.

This normally should not happen, please file a bug report.

 

How can I solve it?

 

0 Kudos
Reply
1 Reply

1,390 Views
Omar_Anguiano
NXP TechSupport
NXP TechSupport

Hello

Please clean the project and make sure that the build is on debug not the release.
Erase the launch file of the debug session so it opens another one and verify that the correct driver is selected on the project settings
Make sure that the cable is connected to the corresponding USB connector and verify that JP1 and JP5 jumpers are open. 

 

Omar_Anguiano_1-1714075434690.png

 

Best regards,
Omar

0 Kudos
Reply