[v_krishnan]

I’ve some DDF files which define the registers of the target device. One example file is below.

NOTE: file extension changed as .ddf is not allowed in attachments.

• This reply was modified 2 years, 6 months ago by v_krishnan.

Attachments:

You must be logged in to view attached files.

[v_krishnan]

I checked it up with Segger. Here’s there response –
<div>SMP debugging is not support by J-Link or J-Link GDB Server at the moment.</div>
<div>SMP debugging is planned for the future but without fixed schedule.

I guess I then have to use OpenOCD compatible debugger to do the SMP debugging, correct? Is IAR ijet supported by VisualGDB?</div>

[v_krishnan]

I get the following output from “info threads” command. The “Threads” window also shows a single thread only.

info threads
&"info threads\n"
Id Target Id Frame 
* 1 Thread 57005 cstartup () at startup.s:74
OK

Note: I get three options to choose the target device from, in the debug settings – R9A06G032, R9A06G032_CPU0, R9A06G032_CPU1. I’ve selected the first option.

[v_krishnan]

In an earlier reply to my original question, it was suggested that Segger J-Link should present each core of a multi-core target as a separate thread under VisualGDB. I’m seeing only a single thread. Is there any specific setting or configuration process to enable this?

My target is having two identical A7 cores. So, I want to run my application wherein my RTOS threads can be scheduled on any core, and I should be able to debug them. Is it possible using a single instance of Visual Studio, or do I require to open the same project in separate instances and debug each core separately?
I would ideally prefer a single instance to debug both the cores.

[v_krishnan]

Thanks, will give the new build a try.

[Author]

Posts