Sunday, November 19th 2017, 8:57pm UTC+1

You are not logged in.

  • Login
  • Register

Reply

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.

Message information
Message
Settings
Automatically converts internet addresses into links by adding [url] and [/url] around them.
Smiley code in your message such as :) is automatically displayed as image.
You can use BBCode to format your message, if this option is enabled.
Security measure

Please enter the letters that are shown in the picture below (without spaces, and upper or lower case can be used).

The last 5 posts

Tuesday, November 14th 2017, 4:17pm

by SEGGER - Nino

Hi Douglas,

Quoted

I set a data breakpoint by using Debug - Breakpoints - New Data Breakpoint.

Ok, that way i was able to reproduce the issue.
This is definitely not how it should be and we will be fixing it as soon as possible.

Quoted

So maybe the real issue is that the Data Breakpoint is not being setup as configured on the first (initial) try.
I have to manually go in and correct it afterwards...?


Yes, that would be the current workaround.

Sorry for any inconveniences caused.

Best regards,
Nino

Monday, November 13th 2017, 4:52pm

by DTurnbow

Hold on.
After I set the Data Breakpoint if I go into the Breakpoints window, right click on one of the data breakpoints I set and select "Edit Breakpoint" it shows the Breakpoint Trigger Type as "Default".
If I manually change it to "Write" again then it seems to start working.

So maybe the real issue is that the Data Breakpoint is not being setup as configured on the first (initial) try.
I have to manually go in and correct it afterwards...?

Is this a bug in SES? In the J-link? On the processor?

Monday, November 13th 2017, 4:08pm

by DTurnbow

I set a data breakpoint by using Debug - Breakpoints - New Data Breakpoint.
Expression: m_log_data.timestamp_func (or 0x20006034 which is the address of m_log_data.timestamp_func)
Breakpoint trigger type: Write
When breakpoint is hit: Stop
Check the "Use hardware Breakpoint" box


I actually setup both expressions (m_log_data.timestamp_func and 0x20006034) then restart my application.
Execution does not break at the point in the init code where m_log_data.timestamp_func is set.

Monday, November 13th 2017, 2:07pm

by SEGGER - Nino

Hello Douglas,

Thank you for your inquiry.

How exactly are you setting the data breakpoint?
Are you using the breakpoint window?
What exactly are your settings for the breakpoint?
What is its trigger type?

Generally it should work.
Keep in mind that for some target devices do not support all trigger types for all memory. Check the target device reference manual for more information.

Best regards,
Nino

Friday, November 10th 2017, 5:42pm

by DTurnbow

Data breakpoints

I'm troubleshooting a hard fault issue.
I can tell that a function pointer in a structure is getting corrupted and that's what's sending execution off "into the weeds".
So I tried to set a data breakpoint on the function pointer in the structure, but it doesn't seem to be working.
At least it doesn't trip in the initialization code when the function pointer is initialized.

Should data breakpoints work in my setup?

I have a Segger J-Link ULTRA+ debugger.
I'm using Segger Embedded Studio
I'm using a Nordic nRF52840 processor
I'm using the SWD interface (SWDIO/SWCLK)