Friday, December 15th 2017, 8:47pm 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.

stefan

Beginner

Date of registration: Feb 24th 2017

Posts: 6

1

Friday, September 1st 2017, 11:30am

[SOLVED] Ozone tracing: No clock present

Hi,

I am trying to enable the ETM Tracing with Ozone on a TWR-K65 board.

But when starting a debugging session I get the following error:

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
Debug.Start();
Executed J-Link command "ScriptFile=D:/temp/Kinetis_Tracing.JLinkScript"
J-Link: Device "MK65FN2M0XXX18" selected.
J-Link: Executing InitTarget()
J-Link: Found SW-DP with ID 0x2BA01477
J-Link: Scanning AP map to find all available APs
J-Link: AP[2]: Stopped AP scan as end of AP map has been reached
J-Link: AP[0]: AHB-AP (IDR: 0x24770011)
J-Link: AP[1]: JTAG-AP (IDR: 0x001C0000)
J-Link: Iterating through AP map to find AHB-AP to use
J-Link: AP[0]: Core found
J-Link: AP[0]: AHB-AP ROM base: 0xE00FF000
J-Link: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
J-Link: Found Cortex-M4 r0p1, Little endian.
J-Link: FPUnit: 6 code (BP) slots and 2 literal slots
J-Link: CoreSight components:
J-Link: ROMTbl[0] @ E00FF000
J-Link: ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS
J-Link: ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
J-Link: ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
J-Link: ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
J-Link: ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
J-Link: ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
J-Link: ROMTbl[0][6]: E0042000, CID: B105900D, PID: 003BB907 ETB
J-Link: ROMTbl[0][7]: E0043000, CID: B105900D, PID: 001BB908 CSTF
J-Link: connected to target device
J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
J-Link: Reset: Reset device via AIRCR.SYSRESETREQ.
J-Link: Executing AfterResetTarget()
J-Link: J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match
Executed J-Link command "SelectTraceSource=1"
J-Link: Start: Initializing trace pins
J-Link: End: Initializing trace pins
J-Link: Using main connection for streaming trace. For max. trace throughput, please connect J-Trace via IP
J-Link: No trace clock present, trace may not work correctly.
If application enables trace clock during execution, start of trace data may be missing.


The JLinkScript I use is attached and my Ozone-COnfigurations looks like this:

Source code

1
2
3
4
void OnProjectLoad (void) {
	Project.SetDevice ("MK65FN2M0xxx18");	Project.SetHostIF ("USB",  "");	Project.SetTargetIF ("SWD");
	Project.SetTIFSpeed ("4 MHz");	Project.SetTraceSource ("Trace Pins");	Project.SetTracePortWidth (4);	Project.AddSvdFile ("Cortex-M4.svd");
	Project.SetJLinkScript("D:/temp/Kinetis_Tracing.JLinkScript");}



Any Ideas whats going wrong here?

Thanks!
stefan has attached the following file:

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 467

2

Friday, September 1st 2017, 1:45pm

Hello Stefan,

Thank you for your inquiry.
Did you make sure the Trace Pins are connected to the debug header?
Because according to the TWR-K65 schematics they are not connected by default.
You will need to populate resistors R54-58 with 0 Ohm resistors so the trace signals can reach the J-Trace PRO.

Also you are using a K64 JLinkscriptfile, make sure this script file is compatible to K65 devices.
Some devices require unlock sequences for register access for example.

Best regards,
Nino

stefan

Beginner

Date of registration: Feb 24th 2017

Posts: 6

3

Friday, September 1st 2017, 2:47pm

Thank you!

I added the missing resistors and now it works!

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 467

4

Friday, September 1st 2017, 2:50pm

Hello Stefan,

Great to hear that you are up and running again.
I will consider this case as solved then.

Best regards,
Nino