Friday, May 25th 2018, 1:06pm UTC+2

You are not logged in.

  • Login
  • Register

Ushan

Beginner

Date of registration: Aug 12th 2014

Posts: 8

1

Tuesday, September 23rd 2014, 10:26am

JLink feed back upon reaching a breakpoint

Hi,

SetBP is used to set a break point in my program.

I want to know whether the PC reaches the break point without polling using a command like 'moe'.

At the moment i use 'moe' to check whether the target is halted.

I want to get rid of the polling method and I am wondering whether there is a method to know the break point is hit asynchronously.

Thanks,
Ushan

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,516

2

Wednesday, September 24th 2014, 9:17pm

Hi Ushan,

No, currently not.
The J-Link DLL only performs a minimum of communication with the target during a debug session and usually only requests the IsHalted() state when the debugger tells it to do so.
Where is the problem with polling via IsHalted()?


- Alex

Ushan

Beginner

Date of registration: Aug 12th 2014

Posts: 8

3

Thursday, September 25th 2014, 1:25am

Hi Alex,

In fact, I am using JLinkExe in a Ubuntu machine with a command script.

A QSPI flash is used in my hardware and the processor manufacturer does not provide a config file that is capable of flashing the QSPIflash via JTAG.
what I am doing is that I load a small program long with the target binary to the RAM using JLinkExe. Then the RAM program downloads the binaries to the QSPI flash. Once the programming is completed, it stops at a break point.

In order to know whether it reaches the break point I use 'moe' (mode of entry).

If there is command like WaitHalt, that waits until the break point is reached, I would be able use it to know whether the flashing is completed. This is necessary to automate the process.

Thanks,
Ushan

This post has been edited 1 times, last edit by "Ushan" (Sep 25th 2014, 3:47am)


Mike Luebke

Beginner

Date of registration: Jun 25th 2012

Posts: 8

4

Thursday, October 2nd 2014, 7:44am

Hi Ushan,

I agree, there should be a command like "WaitHalt", ideally with optional timeout.
Also J-Link Commander should in non-batch mode instead of just waiting for the key press
wait for either key-press or halt event.
This would make it possible/easier to use it as a command line debugger.

It would be a great addition of value to an otherwise great product.

Does not sound like a big change, so maybe Alex & team can add this to the next Beta ...?

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,516

5

Thursday, October 2nd 2014, 9:17pm

Hi,

We will add a "WaitHalt" command in one of the next versions.

Quoted

Also J-Link Commander should in non-batch mode instead of just waiting for the key press wait for either key-press or halt event.

I would not say *should*... a matter of taste.
But there is a larger re-design of the J-Link Commander planned anyhow, so I will add this to the discussion.


- Alex