MPC5644A RAM image Debug Issue

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

MPC5644A RAM image Debug Issue

653 Views
haowu
Contributor I

I have problem of  debugging RAM image with CW 10.6 and P&E USB multilink Universal. After RAM image is downloaded to ECU and start execution,  Program Counter(PC) is not able to move to start of main() function. It is stuck in Memory area of BAM.  

 

With same source codes built into ROM image, i have no problem of downloading and debugging it. everything acts normal.

 

I build a RAM image with  an empty project that only has a while loop, I could download and debugging it without any issue. After RAM image is downloaded, PC immediately stops at begin of main function and wait for debugging. 

 

 If i decrease size of my source codes by removing some modules and build it into a RAM image, I could  successfully debug it without any issue. 

 

Is there any size limit for RAM image debugging? like 32K?  I am using evaluation version of CW 10.6.

 

Thanks a lot for your help!

Labels (1)
0 Kudos
2 Replies

527 Views
haowu
Contributor I

Martin, thanks a lot for your reply. Excuse me for not able sharing my source code, since i am not the owner. I checked size of RAM image downloaded. It is 48k bytes. and there is an Error msg in debug log attached below for your reference. It seems like breakpoint has been placed at begin of Main() function, but it just cant get there.

Thanks again for your help!

GDI: CPU:0, DiMemoryRead(addr = 0x40008200, space = 1, mem_items = 256, size = 1)
GDI: => DI_OK
GDI: E2 F9 00 04 18 21 06 E0 23 F5 00 C4 24 03 D7 F1 E4 32 7C 60 18 F8 18 00 C8 03 E6 06 06 05 91 43
GDI: 26 00 20 03 E2 FD 74 87 40 2F 74 86 C0 0F 74 80 80 1F 74 BF D9 7F 44 47 44 60 18 24 A8 00 44 70
GDI: 2A 0F 7C 84 01 9E 24 23 E6 0C D1 43 26 0F D2 43 D3 43 D4 43 D5 43 D6 43 D7 43 D8 43 21 F3 E2 F6
GDI: 74 A0 F7 7F 2A 00 E6 05 D1 43 26 00 20 33 E2 FD 20 23 2E 35 2A 05 E6 05 91 43 26 05 20 03 E2 FD
GDI: C7 F1 21 F1 00 04 18 21 06 E0 00 80 D9 01 D7 F1 01 3F E9 B9 01 F3 C7 F1 C9 01 00 90 21 F1 00 04
GDI: 18 21 06 E0 71 08 E0 01 1C 68 FC F0 C0 43 C1 03 D4 41 D5 01 C2 03 D6 01 21 F1 00 04 18 21 06 F0
GDI: 00 80 D5 01 E9 EE C5 01 00 90 20 F1 00 04 00 00 18 21 06 F0 00 80 D5 01 78 00 0B F5 78 00 13 9B
GDI: 78 00 1A 77 78 00 04 EF 78 00 10 A1 78 00 3A 85 54 6D 80 78 78 00 09 19 48 00 71 3F E7 F5 51 09
GDI: CPU:0, DiBreakpointSet(brkpt = (type = DI_BPT_EXECUTE, addr = (lin_addr = 0x400082D0, space = 0), bp_method = SW))
GDI: => DI_OK
GDI: CPU:0, brkpt_id:0x400082d0 -> 0x400082D0
GDI: CPU:0, DiExecContinue()
INF: Error : Error in ONCE status register during instruction execution.
INF: Error : Error in ONCE status register during instruction execution.
ERR: Could not write breakpoint to hardware.
INF: Error : Error in ONCE status register during instruction execution.
INF: Error : Error in ONCE status register during instruction execution.
GDI: => DI_OK
GDI: CPU:0, DiExecGetStatus(cpu_status = (cause = GDI_WAIT_RUNNING, brkpt_id = 0))

0 Kudos

527 Views
martin_kovar
NXP Employee
NXP Employee

Hi,

from your description it seems, you do not have enough RAM memory to execute RAM target. Please realize that MPC5644A has 4MB flash memory, but it has 192KB RAM memory only and in case you use RAM target, code and data has to be placed to this RAM memory. 

While compiling, do you have any warnings from linker?

C source-level debugger/programmer C-code and data size is restricted to 512 KB for Qorivva microcontrollers. You can check on the following URL:

CodeWarrior for Microcontrollers-Eclipse IDE|NXP 

Is possible for you to share the project you are not able to debug?

Regards,

Martin

0 Kudos