Monday, December 11th 2017, 2:22pm UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

1

Monday, February 15th 2016, 3:51pm

[SOLVED] DEBUGGING doesn't work in external RAM, but in internal RAM

Hello,

I just start with SEEGER probe.

I 've configured a EClipse project which works on Internal RAM (set a beakpoint, step into functions, etc.. everything is fine).
So now I load my code in the external RAM.

- when I run my application without setting any breakpoints, everything works.
- when i set a breakpoint, application stops but "counter program" seems freeze after that.




here is my JILINK script for cortexM4 : iMX6SoloX_Connect_CortexM4.JLinkScript.txt

Is there specials commands to make DEBUG in external RAM of M4 ?

Thanks a lot for your replies.

This post has been edited 1 times, last edit by "pca" (Mar 7th 2016, 3:01pm)


SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

2

Tuesday, February 16th 2016, 11:23am

Hi,


sorry for the delay in response.
Are you using an evaluation board or custom hardware?
If you are using an evaluation board, which one do you use?
Could you provide us with your project (or a stripped down version) for reproduction purposes?

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

3

Tuesday, February 16th 2016, 5:49pm

DEBUGGING doesn't work in external RAM, but in internal RAM

Hello Niklas,

Thanks a lot for your reply.

I'm busy too, so I just can reply now.

Yes I use an evaluation board , it is the Imx6 Solox SABRE SD.

You can find attached a ZIP file which contains my project (EClipse based). test_mqx.zip

I also attached the files "ram.ld" I use to run on "internal ram" or "external ram" (this case doesn't work), respectively "ram_int.ld" and "ram_ext.ld".

ram_ext.ld.txt ram_int.ld.txt

Before building my project I copy this file to

C:\Freescale\Freescale_MQX_4_1_IMX6SX\lib\imx6sx_sdb_m4.gcc_arm\debug\bsp\ram.ld according to the build (internal or external RAM).


I hope it can help you ...

Thank you very much for your help

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

4

Thursday, February 18th 2016, 11:51am

Hi,

Quoted

Is there specials commands to make DEBUG in external RAM of M4 ?

I just checked with my colleagues, it should work without any further configuration.

Could you please provide us with an "out of the box" project, that we can use to reproduce the issue using J-Link Commander / J-Link Debugger?

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

5

Friday, February 19th 2016, 9:24am

Hi,


please abstain from sending me personal messages, as other SEGGER employees are also monitoring this forum but not my PMs.
If I get ill / go on vacation etc you still want to get answers to your question i suppose :)

With the term "out of the box project" I was referring to a project (or maybe a binary is sufficient) that I can use with J-Link Commander / J-Link Debugger without using Eclipse and downloading and compiling the NXP SDK(I could not find the version you are using either).


Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

6

Friday, February 19th 2016, 11:41am

Hello Niklas,

OK I attached a BIN file and also the corresponding MAP file which can help you for the memory mapping.

And sorry for the private email ;)

test_imx6sx_sdb_m4.bin

test_imx6sx_sdb_m4.map.txt

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

7

Monday, February 22nd 2016, 9:56am

Hi,


sorry for the delay in response.
Embedded World 2016 is starting tomorrow and some preparation had to be finished last week.

You sent us a binary for the Cortex-M4 core, but afaik the M4 cannot run on its own, instead, the A-9 needs to be running an unlock the M4, then the M4 can be used.
Am i wrong about that?
If so, can you give me instructions on how to get your application running, starting with an erased device?


Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

8

Wednesday, February 24th 2016, 3:52pm

Hi,

Yes, excuse me...

I attached a file imx6sx_sdb_m4_ram_int.bin which runs on internal RAM.

I suppose UBoot is on the board, here is the commands to start M4 with this app :


Source code

1
2
3
=> tftpboot 0x00900000 192.168.64.111:imx6sx_sdb_m4_ram_int.bin
=> dcache off
=> bootaux 0x00900000


where :


  • 0x00900000 is the internal start RAM adress
  • 192.168.64.111 is the TFTPBOOT server
  • imx6sx_sdb_m4_ram_int.bin is the file to load

I hope this can help you.

Thanks.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

9

Thursday, February 25th 2016, 2:32pm

Hi,

sorry again for the delay in response.
I was finally able to reproduce your setup, but I did not encounter any issues during the debug session.
Breakpoint example:


Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

10

Monday, March 7th 2016, 2:56pm

Hello Niklas,

Excuse me for delay...

I was in holidays... :)


Now i can respond to your email :

I see in the picture that you can set a breakpoint and be halted on it.

Yes me too.... ;)

But are you able to make a single step ? that is the problem. When I want to do a step, the PC register don't move ...

Thanks a lot for your reply.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

11

Monday, March 7th 2016, 6:22pm

Hi,

I hope you had a great holiday.
Stepping worked for me, I will add a screenshot tomorrow with additional information.

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

12

Wednesday, March 9th 2016, 11:23am

Hi,


This is what i did in Yocto:


And here is a screenshot of stepping from 0x81000000


Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

13

Thursday, March 10th 2016, 11:38am

Hello Niklas,

Thank you for your reply.

I've made exactly the same things than you, and I obtain exactly the same result ...

But when I make test with a program running in "internal RAM", I can set a breakpoint, stop on it, make steps and GO. THe program stops correctly.

I make the test with "JLINK commander" and also "JLINK debugger, here is some pictures :






But when I make the testwith a program running in "external RAM", I can set a breakpoint but never stop on it. I can make a HALT, then steps correctly, but when I make a GO, the program never stop ... here are some pictures :


It seems that the breakpoint is correctly saw when its implementation is "HARD", but never saw when its implementation is "RAM" ...

Have you got an idea ?

I've also seen this URL https://www.segger.com/jlink-unlimited-f…reakpoints.html

this link discuss about external FLASH, is it also the case in external RAM ??

I understand that we have to purchase a probe with the "Unlimited Flash Breakpoint" license, ....

here is the log for our probe features: RDI, FlashBP, FlashDL, JFlash, GDB

Is it in uff ??


Thanks a lot...

This post has been edited 1 times, last edit by "pca" (Mar 10th 2016, 3:34pm)


SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

14

Thursday, March 10th 2016, 3:52pm

Hi ,


your J-Link already includes an unlimited Flash Breakpoints License. ("FlashBP")
Breakpoints in RAM are not limited.

It appears to me, that you never halt on this breakpoint because this instruction is not reached during execution.

You could try the following:
  • Step some time, note an instruction address that is executed
  • Reset to the beginning ("r" and "setpc" if necessary
  • Set a BP to the noted address
  • g
  • h
Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

15

Thursday, March 10th 2016, 4:01pm

Niklas,

I have set the breakpoint exactly at the same place (both in internal or external RAM) ...

So I'm sure the program pass on this.

My conclusion is the following :

- Breakpoints are not seen in external RAM.

But Why ??? ?(

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

16

Thursday, March 10th 2016, 4:07pm

Hi,


I cannot confirm this.
Could you please give it a try?
As an alternative :
  • setbp on any valid address
  • g (important in order to let J-Link set the breakpoint)
  • setpc on the address with the BP
  • s
In case this fails, could you do a ReadMEM (mem32) on the breakpoint address?

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

17

Thursday, March 10th 2016, 4:25pm

Niklas,

I 've again make a test.

1) run the program
2) connect with JLINK commander
3) halt program
4) do some steps and set a breakpoint at 0x81004FF6
5) make a GO
6) the program STOP and unbelievable it stop on the good address !!!
7) then i make some steps again
8) and the PC regsiter don't move :cursing: :cursing:

here is a log of my JLINK commander

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
SEGGER J-Link Commander V5.10r (Compiled Mar  8 2016 17:35:19)
DLL version V5.10r, compiled Mar  8 2016 17:34:46

Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Mar  8 2016 11:13:10
Hardware version: V10.00
S/N: 600001141
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
Emulator has Trace capability
VTref = 3.309V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: CORTEX-M4
Type '?' for selection dialog
Device>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "CORTEX-M4" selected.


TotalIRLen = 17, IRPrint = 0x001011

**************************
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1
149.1, 7.1.1.d, IR-cells). (NumDevices = 4, NumBitsSet = 3)

**************************

Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl 0 @ E00FF000
ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB00C SCS
ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl 0 [5]: FFF42000, CID: B105900D, PID: 000BB925 ETM
ROMTbl 0 [6]: FFF43000, CID: B105900D, PID: 003BB907 ETB
ROMTbl 0 [7]: FFF44000, CID: B105900D, PID: 001BB908 CSTF
Found 4 JTAG devices, Total IRLen = 17:
 #0 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
 #1 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
 #2 Id: 0x00000001
 #3 Id: 0x0891C01D
Cortex-M4 identified.
J-Link>h
PC = 81007A2C, CycleCnt = 89036EDE
R0 = 00000000, R1 = 00000328, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 20002828
R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
R12= 00000000
SP(R13)= 20002828, MSP= 20001820, PSP= 20002828, R14(LR) = 8100D4AB
XPSR = 81000000: APSR = Nzcvq, EPSR = 01000000, IPSR = 000 (NoException)
CFBP = 02000000, CONTROL = 02, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00

FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= 00000000
FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= 00000000
FPSCR= 00000000
J-Link>s
81007A2C:  11 E0              B       #+0x22
J-Link>s
81007A52:  80 BD              POP     {R7,PC}
J-Link>s
8100504A:  D4 E7              B       #-0x58
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>s
81004FF8:  D3 F8 30 23        LDR     R2, [R3, #+0x330]
J-Link>s
81004FFC:  01 32              ADD     R2, #1
J-Link>setBP 0x81004FF6
Breakpoint set @ addr 0x81004FF6 (Handle = 1)
J-Link>s
81004FFE:  C3 F8 30 23        STR     R2, [R3, #+0x330]
J-Link>s
81005002:  D3 F8 30 33        LDR     R3, [R3, #+0x330]
J-Link>s
81005006:  00 2B              CMP     R3, #0
J-Link>s
81005008:  19 D1              BNE     #+0x32
J-Link>s
8100503E:  7B 68              LDR     R3, [R7, #+0x04]
J-Link>s
81005040:  00 2B              CMP     R3, #0
J-Link>s
81005042:  00 D0              BEQ     #+0x00
J-Link>s
81005046:  02 F0 E9 FC        BL      #+0x29D2
J-Link>s
81007A1C:  80 B5              PUSH    {R7,LR}
J-Link>s
81007A1E:  00 AF              ADD     R7, SP, #0
J-Link>s
81007A20:  02 F0 12 F9        BL      #+0x2224
J-Link>s
81009C48:  80 B5              PUSH    {R7,LR}
J-Link>s
81009C4A:  00 AF              ADD     R7, SP, #0
J-Link>s
81009C4C:  00 F0 78 FE        BL      #+0xCF0
J-Link>s
8100A940:  80 B5              PUSH    {R7,LR}
J-Link>s
8100A942:  00 AF              ADD     R7, SP, #0
J-Link>s
8100A944:  02 F0 02 FE        BL      #+0x2C04
J-Link>s
8100D54C:  80 B5              PUSH    {R7,LR}
J-Link>s
8100D54E:  00 AF              ADD     R7, SP, #0
J-Link>s
8100D550:  0C 4B              LDR     R3, [PC, #+0x30]
J-Link>s
8100D552:  1B 68              LDR     R3, [R3]
J-Link>s
8100D554:  01 2B              CMP     R3, #1
J-Link>s
8100D556:  11 D0              BEQ     #+0x22
J-Link>s
8100D558:  FF F7 88 FF        BL      #-0xF0
J-Link>s
8100D46C:  80 B5              PUSH    {R7,LR}
J-Link>s
8100D46E:  00 AF              ADD     R7, SP, #0
J-Link>s
8100D470:  F3 F7 EC FE        BL      #-0xC228
J-Link>s
8100124C:  80 B4              PUSH    {R7}
J-Link>s
8100124E:  83 B0              SUB     SP, SP, #12
J-Link>s
81001250:  00 AF              ADD     R7, SP, #0
J-Link>s
81001252:  0B 4B              LDR     R3, [PC, #+0x2C]
J-Link>s
81001254:  1B 68              LDR     R3, [R3]
J-Link>g
J-Link>h
PC = 81004FF6, CycleCnt = 98AB33B4
R0 = 00000000, R1 = 00000328, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 20002830
R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
R12= 00000000
SP(R13)= 20002830, MSP= 20001820, PSP= 20002830, R14(LR) = 8100D4AB
XPSR = 81000000: APSR = Nzcvq, EPSR = 01000000, IPSR = 000 (NoException)
CFBP = 02000000, CONTROL = 02, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00

FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= 00000000
FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= 00000000
FPSCR= 00000000
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>s

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

18

Thursday, March 10th 2016, 4:35pm

Niklas,

here the test result :

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
J-Link>h
PC = 81007A2C, CycleCnt = 85FB4130
R0 = 00000000, R1 = 00000328, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 20002828
R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
R12= 00000000
SP(R13)= 20002828, MSP= 20001820, PSP= 20002828, R14(LR) = 8100D4AB
XPSR = 81000000: APSR = Nzcvq, EPSR = 01000000, IPSR = 000 (NoException)
CFBP = 02000000, CONTROL = 02, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00

FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= 00000000
FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= 00000000
FPSCR= 00000000
J-Link>setBP 0x81004FF6
Breakpoint set @ addr 0x81004FF6 (Handle = 1)
J-Link>g
J-Link>setPC 0x81004FF6
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>s
81004FF6:  FB 68              LDR     R3, [R7, #+0x0C]
J-Link>ReadMEM 0x81004FF6
Unknown command. '?' for help.
J-Link>mem32 0x81004FF6
Syntax: mem32 <Addr>, <NumItems>
J-Link>mem32 0x81004FF6, 16

**************************
WARNING: Mis-aligned memory read: Address: 0x81004FF6, NumBytes: 88, Alignment:
4 (Word-aligned)
**************************

81004FF6 = F8D368FB 32012330 2330F8C3 3330F8D3
81005006 = D1192B00 F8D368FB 32012334 2334F8C3
81005016 = 3334F8D3 D10F2B00 F8D368FB 32012338
81005026 = 2338F8C3 3338F8D3 D1052B00 F8D368FB
81005036 = 3201233C 233CF8C3 2B00687B BF30D000
81005046 = FCE9F002 0000E7D4
J-Link>

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

19

Thursday, March 17th 2016, 2:31pm

Hello Niklas,

Have you seen my last email ?

Could you reproduce the problem on your sabre board ?

pca

Beginner

Date of registration: Feb 15th 2016

Posts: 14

20

Friday, March 25th 2016, 10:07am

Hello Niklas,

What about my problem ?

did you be able to reproduce it on your board ?

The internal RAM is too small now and I can't debug my application in external RAM. So I'm really interested by your response.

Regards