On Mon, Dec 30, 2019 at 5:45 PM Roman Elshin <[email protected]> wrote:
>
> Hi Antonio,
>
> 29.12.2019 19:34, Antonio Borneo пишет:
> > Hi Roman,
> >
> > can you please submit your patch in OpenOCD's gerrit?
> done

Thanks. I will test and review it.

> ...
> > On Fri, Dec 27, 2019 at 9:16 AM Roman Elshin via OpenOCD-devel
> > <[email protected]> wrote:
> >> It is with keil ulink2, attached patch make it functional  but RUN and
> >> CONNECT leds works similary (i don't know how to make it properly).
> > I'm not sure I understand what you say. What do you mean for "...leds
> > works similary"?
> > If you mean you have to call cmsis_dap_cmd_DAP_LED() two times, that's
> > correct, accordingly to ARM code.
> I was mean, that in a current implementation RUN led say nothing about
> target
> mcu's state (is it running or halted at break point) and it only repli
> CONNECT led.
> Is there are easy way inside a cmsis_dap_usb.c of proper control for RUN
> led ?

Today OpenOCD does not propagate the status of the target to the JTAG adapter.
You could extend the API in struct jtag_interface (file
src/jtag/interface.h) and add (for example) an optional
target_status_changed() method that can be used by some adapters to
display the new status, e.g on cmsis-dap it would change the RUN LED.
Then the new API should be called from poll() at each status change.
But, how to deal with multiple targets? Today I'm working on a SoC
that has two Cortex-A and one Cortex-M. I control them independently
and I can run/halt/step-by-step each of them. What should be displayed
by the LED as RUN status?

Another possibility is to use the RUN LED to display that there is
some activity on the JTAG (I mean show that the JTAG is running,
independently on target status). But this is not really useful since
at every call to poll() there is JTAG activity; if OpenOCD is running
and poll is on, the LED would be blinking...

Antonio


_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to