Debugging errors

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Mon May 14 02:07:45 MST 2012
In the last time, it happens that i get errors while entering or leaving debug mode.

Here is one, that i just encountered. Others concern flash write operations. Did i treat my mcu wrong? Is it possible, that i damaged it anyhow?

EDIT:
They seem to appear randomly, so sometimes it works just fine and smooth...(for example at the moment... :D)

Unable to parse register descriptor: not matched:Lg: Reply: +$OK
Unable to parse register descriptor: not matched:Lg: Reply: +$OK
  {r0}R0=0x0000ED10
  {r1}R1=0x00000001
  {r2}R2=0x00080000
  {r3}R3=0x0007FFFF
  {r4}R4=0x40048000
  {r5}R5=0xEFFFDCB1
  {r6}R6=0x00000005
  {r7}R7=0x10001FE0
  {r8}R8=0xD3C65B70
  {r9}R9=0x2458AE55
  {r10}R10=0xBC9D9344
  {r11}R11=0x32437290
  {r12}R12=0x10000284
  {sp}SP=0x10001FE0
  {lr}LR=0x0000051D
  {pc}PC=0x0000051C
  {cpsr}PSR=0x21000000
  !Flags=0x21000000:nzCvq
  !EPSR=0x21000000:none
  !IPSR=0x21000000:0  (Base)
  !PSP=0xFA94E2B0
  !CONTROL=0x0:Privileged/MSP (Now)
  [+IntMask]
  BasePri=0x00
  PriMask=disabled
  FaultMask=disabled
  []
  
  Lg: Reply: +$OK

EDIT2:
Ah and there goes the error:

15: Target error from Commit Flash write
  15: Target error from Commit Flash write
  Flash erase or write operation aborted.

What happens here?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed May 16 03:08:58 MST 2012

Quote: Caradhras

the only advantage of cmsis 3 ist rtos support?

See http://knowledgebase.nxp.com/showpost.php?p=15250&postcount=2

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Wed May 16 03:04:16 MST 2012
i think i got it done fine :)

up to now: no warnings, no debugging errors yet. thanks for the help!

the only advantage of cmsis 3 ist rtos support?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Tue May 15 04:20:48 MST 2012
If you are using on chip drivers, then make sure you read the "Reserved Memory Regions" section in the following FAQ...

http://support.code-red-tech.com/CodeRedWiki/EnhancedManagedLinkScripts

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Tue May 15 03:12:58 MST 2012
I'm using IAP :eek:

http://support.code-red-tech.com/CodeRedWiki/ReserveIAPRam?highlight=%28iap%29

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Tue May 15 03:07:30 MST 2012
Is this post by code red still valid concerning your advise to increase stack size?
http://support.code-red-tech.com/CodeRedWiki/StackSize

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Tue May 15 02:59:33 MST 2012
...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Tue May 15 01:49:28 MST 2012

Quote:

I see that the samples used are somewhat 'dated'. What would you recommend to start with? I mean, it would be a rather stupid idea trying to port an old sample to cmsis v2?

As mentioned above, I use to start with Project wizard and create a new project (CMSIS2.0 and CRP enabled).

Quote:

Yes, the LPCXpresso-versions are 'mixed' but how should I handle projects as there are frequently new releases? Do I really need to rebuild everything from scratch for every new release of LPCXpresso?

This new releases doesn't bother a solid working project.

Quote:

Concerning the CAN-code: Yes, its based on the sample. Is it wrong, has anything significantly changed? What should be changed, what is "bad style"?

Bad style is everything what's making this project difficult to read. I've hundreds of projects on my PC, Laptop,... and so an important thing is to keep projects easy and readable.
I've to understand my own projects in 1, 5 or 10 years again :eek:

This CAN sample is using CAN ROM driver, so I just need rom_driver_CAN.h and a few lines for CAN_RX... in main. So I don't need thousands of directories, configs, headers.... :)

As simple Debug and Release version, 2 or 3 options for UART and CAN self test that's all I need. With all my files in src folder there's nothing confusing any more :rolleyes:

After a few month of testing I create libs of larger files (like TFT stuff), that's making working and compiling faster.

You have to decide yourself what's bad or good, but my experience is that easy, readable projects are a very important part of working successful with this stuff.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Tue May 15 01:05:35 MST 2012
Ok,

I see that the samples used are somewhat 'dated'. What would you recommend to start with? I mean, it would be a rather stupid idea trying to port an old sample to cmsis v2?

Yes, the LPCXpresso-versions are 'mixed' but how should I handle projects as there are frequently new releases? Do I really need to rebuild everything from scratch for every new release of LPCXpresso? :eek:

Concerning the CAN-code: Yes, its based on the sample. Is it wrong, has anything significantly changed? What should be changed, what is "bad style"?

Thank you! :)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Tue May 15 00:50:44 MST 2012
Your project is a nice confusion of old CAN-sample, 2 changed projects, different LPCXpresso versions and CMSISV1p30 :rolleyes:

I don't know if this is a test or a serious project, but I would strongly recommend to:[INDENT] #1 Create a new clean LPC11C24 project with actual CMSIS2p00 and CRP

#2 Increase stack size to 32

#3 Throw out all unused files and directories and all this 'own linker script' stuff

#4 Test your code again (with disabled sleep)
[/INDENT]If you spend a few hours to create a new standard sample it will pay off in future :)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Mon May 14 13:59:29 MST 2012
hey,

after upgrading to 4.2.2 i didnt get unexplainable errors anymore while debugging. :cool:

but the strange warnings persist. you can find my project attached to the post. :)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Mon May 14 09:40:25 MST 2012

Quote: Caradhras
Builtlog first:

Except including WDT your log is inconspicuous :eek:

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Mon May 14 09:24:53 MST 2012
Builtlog first:

**** Build of configuration Debug for project IRTe_Dashboard ****

make all 
Building file: ../startup/cr_startup_lpc11.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"startup/cr_startup_lpc11.d" -MT"startup/cr_startup_lpc11.d" -o"startup/cr_startup_lpc11.o" "../startup/cr_startup_lpc11.c"
Finished building: ../startup/cr_startup_lpc11.c
 
Building file: ../src/main.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"src/main.d" -MT"src/main.d" -o"src/main.o" "../src/main.c"
Finished building: ../src/main.c
 
Building file: ../driver/A6282.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"driver/A6282.d" -MT"driver/A6282.d" -o"driver/A6282.o" "../driver/A6282.c"
Finished building: ../driver/A6282.c
 
Building file: ../driver/gpio.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"driver/gpio.d" -MT"driver/gpio.d" -o"driver/gpio.o" "../driver/gpio.c"
Finished building: ../driver/gpio.c
 
Building file: ../driver/ssp.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"driver/ssp.d" -MT"driver/ssp.d" -o"driver/ssp.o" "../driver/ssp.c"
Finished building: ../driver/ssp.c
 
Building file: ../driver/timer16.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"driver/timer16.d" -MT"driver/timer16.d" -o"driver/timer16.o" "../driver/timer16.c"
Finished building: ../driver/timer16.c
 
Building file: ../driver/timer32.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"driver/timer32.d" -MT"driver/timer32.d" -o"driver/timer32.o" "../driver/timer32.c"
Finished building: ../driver/timer32.c
 
Building file: ../driver/wdt.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"driver/wdt.d" -MT"driver/wdt.d" -o"driver/wdt.o" "../driver/wdt.c"
Finished building: ../driver/wdt.c
 
Building file: ../cmsis/core_cm0.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\cmsis" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\startup" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\config" -I"C:\Users\pcw\Documents\LPCXpresso_4.2.2_275\workspace_DB\IRTe_Dashboard\driver" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"cmsis/core_cm0.d" -MT"cmsis/core_cm0.d" -o"cmsis/core_cm0.o" "../cmsis/core_cm0.c"
Finished building: ../cmsis/core_cm0.c
 
Building file: ../cmsis/system_LPC11xx.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -D__USE_CMSIS -DDEBUG -D__CODE_RED -IC:/Users/pcw/Documents/LPCXpresso_4.1.5_219/workspace_i2c/IRTe_Dynamik_Box/cmsis -IC:/Users/pcw/Documents/LPCXpresso_4.1.5_219/workspace_i2c/IRTe_Dynamik_Box/config -IC:/Users/pcw/Documents/LPCXpresso_4.1.5_219/workspace_i2c/IRTe_Dynamik_Box/driver -O0 -Os -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"cmsis/system_LPC11xx.d" -MT"cmsis/system_LPC11xx.d" -o"cmsis/system_LPC11xx.o" "../cmsis/system_LPC11xx.c"
Finished building: ../cmsis/system_LPC11xx.c
 
Building target: IRTe_Dashboard.axf
Invoking: MCU Linker
arm-none-eabi-gcc -nostdlib -Xlinker -Map=IRTe_Dashboard.map -Xlinker --gc-sections -mcpu=cortex-m0 -mthumb -T "IRTe_Dashboard_Debug.ld" -o"IRTe_Dashboard.axf"  ./startup/cr_startup_lpc11.o  ./src/main.o  ./driver/A6282.o ./driver/gpio.o ./driver/ssp.o ./driver/timer16.o ./driver/timer32.o ./driver/wdt.o  ./cmsis/core_cm0.o ./cmsis/system_LPC11xx.o   
Finished building target: IRTe_Dashboard.axf
 
make --no-print-directory post-build
Performing post-build steps
arm-none-eabi-size IRTe_Dashboard.axf; arm-none-eabi-objcopy -O binary IRTe_Dashboard.axf IRTe_Dashboard.bin ; checksum -p LPC11C24_301 -d IRTe_Dashboard.bin;
   text       data        bss        dec        hex    filename
   5856         48        580       6484       1954    IRTe_Dashboard.axf
Created checksum 0xb1dcffef in IRTe_Dashboard.bin at offset 0x1c

If you need the project, tell me.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon May 14 09:00:19 MST 2012
The messagefrom the tools that you posted looks slightly different to the typical "invalid project path" warning - so I'm not convinced you are seeing the problem described in the FAQ.

Can you preferably zip up and post your project:

http://support.code-red-tech.com/CodeRedWiki/ImportExport

or if you are not willing to do so, then please post the build log:

http://support.code-red-tech.com/CodeRedWiki/BuildConsole

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Mon May 14 04:33:39 MST 2012
upgrading the IDE seem to have fixed the debug errors (entered debug mode three times without problems) but there is this eclipse plaque again:

Invalid project path: Missing project folder or file: \projectname\config\cr_startup_lpc11.c for Include path.

Last time i could fix it through fiddling with the automatic "ressource" management and deleting old paths.

This time it did not help and this neither:
http://support.code-red-tech.com/CodeRedWiki/InvalidProjPath

EDIT:
I should mention that in the workspace of the old IDE i exported the project without the debug/release folder and reimported it in the new v4.2.2 workspace. So like mentioned here, i should got rid of some of the old mess. But as stated above it didnt help.
http://knowledgebase.nxp.com/showthread.php?t=3192

HELP!

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Mon May 14 03:34:16 MST 2012
i will now upgrade to from 4.1.5 to v4.2.2 hoping these suddenly occuring errors vanish... :(

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Mon May 14 02:54:10 MST 2012
hmm, adding additional power didnt help:

Error reading null
unable to parse register descriptor: not matched: Lg: Reply: +$ok

Unable to parse register descriptor: not matched:Lg: Reply: +$OK
Unable to parse register descriptor: not matched:Lg: Reply: +$OK
  {r0}R0=0x00000000
  {r1}R1=0x100002B4
  {r2}R2=0x00000402
  {r3}R3=0x00000001
  {r4}R4=0x40048000
  {r5}R5=0xEFFFDCB1
  {r6}R6=0x00000005
  {r7}R7=0x10001FE0
  {r8}R8=0xC3C61B70
  {r9}R9=0x2458AC45
  {r10}R10=0x9C899344
  {r11}R11=0x12427210
  {r12}R12=0x10000284
  {sp}SP=0x10001FE0
  {lr}LR=0x00001015
  {pc}PC=0x00000488
  {cpsr}PSR=0x41000000
  !Flags=0x41000000:nZcvq
  !EPSR=0x41000000:none
  !IPSR=0x41000000:0  (Base)
  !PSP=0xE294E230
  !CONTROL=0x0:Privileged/MSP (Now)
  [+IntMask]
  BasePri=0x00
  PriMask=disabled
  FaultMask=disabled
  []
  
  Lg: Reply: +$OK

does this mean the program hit a null pointer?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Mon May 14 02:34:29 MST 2012

Quote: Caradhras

Quote:

[B]Warning about vector catch[/B]

Don't know which mcu and which board you are using, but I don't switch off Vector catch since years without problems :rolleyes:

I think this warning is old (= LPCXpresso V3.x) :eek:

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Caradhras on Mon May 14 02:24:17 MST 2012
Oh, i see, that there is much more information available than thought first:

Maybe of help for people running in similar situations:
http://support.code-red-tech.com/CodeRedWiki/CommitFlashWrite

[B][SIZE=3]15: Target error from Commit Flash write[/SIZE][/B]

 [SIZE=2]This error is reported when the debugger is attempting to write to the flash, and the verify fails. [/SIZE]
[SIZE=2]The  most common cause for this error is insufficient power being supplied  to the target while programming the flash. Flash programming increases  the power consumption of the chip dramatically, and if your supply is  not up to it, the flash programming will fail. [/SIZE]
[SIZE=2]A  common cause of insufficient power is PC USB ports, which are not  supplying the USB spec of 500mA. Try another USB port on the PC, or use  an external power supply to provide the power instead.  [/SIZE]

Also one should check if the "catch vector" option is enabled in the launch configuration as stated here:
http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip

[B]Warning about vector catch[/B]

 Note that  once you have recovered debug access to your MCU, then in most cases you  should then modify your Debug Configuration to turn vector catch off  again. If this is not done, then this can cause problems in some  circumstances with some versions of the Code Red IDE. For example with  NXP LPC13xx parts, connecting more than once to the MCU with vector  catch enabled can lead to the part ID being incorrectly read - which can  again cause debug connections to fail: