> Why didn't it actually make it to the main branch?
Maybe the fork developers simply didn't upstream it (yet?)?
You'd need to ask them via their repo.
Hope this helps.
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
Hi,
The target in question seems to be a Cortex-M0-based MCU
with a DAP, accessible via SWD.
Nuvoton's OpenOCD forks from commit 674141e (very old, May 2016).
At first glance it seems to add support for the "Nu-Link Programmer"
aka. "Nuvoton ICE" and several Nuvoton MCUs/MCU families
including
Hi @Tommy Murphy,
Thank you very much for your quick reply.
This is certainly helpful. Unfortunately, I'm not a hero in these kind of
things (building OpenOCD from the sources). In fact, I use the following guide
to make my Windows build:
Doesn't look like that probe is supported in the master openocd project:
https://repo.or.cz/openocd.git/tree/HEAD:/src/jtag/drivers
However this fork seems to have support for it:
https://github.com/OpenNuvoton/OpenOCD-Nuvoton/blob/master/src/jtag/drivers/nulink_usb.c
Not sure why it was never
Dear OpenOCD developers,
I'm trying to get the Nuvoton board "NuMaker-M032SE V1.3" to work (see
https://www.nuvoton.com/hq/board/numaker-m032se).
This board has:
- Target chip: M032SE3AE
- On-board flash/debug probe: Nu-Link2-Me
I looked around in the "scripts/target" folder from my
This is an automated email from Gerrit.
Michael Jung (mij...@gmx.net) just uploaded a new patch set to Gerrit, which
you can find at http://openocd.zylin.com/5344
-- gerrit
commit b480bac4d0ee819f1dd1044e9fd4b95a77632d04
Author: Michael Jung
Date: Fri Nov 15 19:33:25 2019 +0100
