Monday, October 23rd 2017, 8:51pm UTC+2

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.

Avenue33

Beginner

Date of registration: Aug 9th 2016

Posts: 10

1

Monday, May 1st 2017, 6:02pm

nRF52832: Ozone fails when JLinkGDBServer succeeds

I manage to debug against the nRF52832_xxAA with JLinkGDBServer and arm-none-eabi-gdb.

When I try with Ozone, it fails with the following message:

Source code

1
2
3
Debug.Start();
J-Link: connected to target device
Instruction trace could not be started: hardware does not support instruction trace"


What's going wrong?

Configuration
  • J-Link Edu
  • Firmware: J-Link V9 compiled Apr 21 2017 11:08:06
  • Hardware: V9.40
  • JLinkARM.dll V6.14e (DLL compiled Apr 27 2017 18:29:07)
  • Ozone 2.32 on macOS 10.12.4
  • GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20151217-cvs


Thank you!

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,684

2

Tuesday, May 2nd 2017, 4:23pm

Hi,


Does it fail?
The output just says that the trace view of Ozone is currently open, but the debugger hardware (J-Link V9) does not support trace.
This warning can be omitted by closing the Trace View before connecting to the target.

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