Trying to use Microchip SoftConsole 2022 on PolarFire SoC Icicle Kit to debug example application, but OpenOCD failing with message: OpenOCD failed with code (-1073741819). We tried to Google but nothing comes up. Could you tell us what that error code means?
It is a new DELL laptop running Windows 11. We use SoftConsole on other 4 PCs and no problems. The interesting part that OpenOCD detects two Embedded FlashPro6 as shown on attached image and we did not see that before.
Thank you
Looks like you are using a fork of OpenOCD from MicroChip.
I don't expect we could help you on that code. I even cannot find the code published anywhere.
Yes - Microchip use a custom(ised) version of OpenOCD, I can't see that the sources/changes were ever published, and you will probably have to contact Microchip support for help with problems like this. Good luck!
(Disclaimer: I used to work for Microchip on the SoftConsole tools).
Edit: you should probably try to get OpenOCD working on the command line separate from SoftConsole/Eclipse first. And maybe use
-d3to get verbose logging in case that sheds any light on the failure.Last edit: Tommy Murphy 2024-10-11
On Fri, Oct 11, 2024 at 07:44:16PM -0000, Tommy Murphy wrote:
Also Microchip seems to be violating GPL which is illegal and
offensive. I suggest you request full corresponding source code for
their OpenOCD fork from them, there's a legal obligation to provide
it. Linking with proprietary DLLs is prohibited by GPL too.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
Thought I posted about this last week but I don't know what happened.
FWIW it looks like Microchip are upstreaming their changes now and the latest version seems to no longer require the use of the closed source
fpServercomponent.Thank you for your reply. I created a case on Microchip community forum but no response. It is very hard to get any support from them.
I am trying to do the same with Artery as I want to talk to their AT32F4xx chips and they have posted copies of their versions of OpenOCD, both 0.10.0 and 0.11.0 within some of their Application Notes (AN0033, AN0130, AN0186, AN0191 and AN0193 to name a few) without access to the varying sources they were built with. I have used their contact form to request the required sources as per the terms of the GPL but as I am not a copyright holder of any of the code my options are limited. Is there a copyright holder who could give them a gentle push/probe?
Does this repo contain anything of relevance?
It appears to be some sources but nothing in it ties in with the
dates/times of the builds they released in their app notes.
There are two totally different builds (one does appear in their App Note
AN0186) with what appears to be only 1 set of sources. Nice.
Having been through similar issues with Inventel, Sagem and Thomson/BT I'd
like to be able to build a matching executable to theirs before starting to
see what changes need porting.
Andy
On Mon, 18 Nov 2024 at 22:47, Tommy Murphy tm1234@users.sourceforge.net
wrote:
Related
Tickets: #439
Hi Marc,
Ready, willing and able. I have a couple of 415 and 435 Goteks I can try it
with.
Regards
Andy
On Tue, 19 Nov 2024 at 08:48, Marc Schink dev@zapb.de wrote:
Related
Tickets: #439
HI Marc,
I've just seen it. Will give it a try as soon as I can.
Thanks
Andy
On Sat, 21 Dec 2024 at 12:18, Marc Schink dev@zapb.de wrote:
Related
Tickets: #439
Hi,
I have same issue with "Arduino" one.
This is, how arduino see the problem:
I can try to run manually, with -d3 option, but no better result:
Looks totally unrelated to me. You're using debug adapter which is not supported in upstream OpenOCD at all and it's unclear what "sdi" transport is. I suggest you ask whomever provides that "Open On-Chip Debugger 0.11.0+dev-02415-gfad123a16-dirty (2023-05-05-13:43)" fork (WCH?), I doubt anyone here in upstream has any idea about it.
Yes - SDI is a WCH (proprietary?) 2-wire debug interface so presumably this OpenOCD (which is also old) is a custom/modified version from WCH or somebody else doing work with WCH RISC-V MCUs and questions about it should be directed to them. Not really sure why this was posted in an issue thread originally about Microchip SoftConsole OpenOCD? Seems completely off topic?
Hi, I can answer 2nd part. I posted it to this thread as I have same exit code and similar symptoms (vendor packed version etc).
What do you mean by "vendor packed version etc"?
Finally get it solved!
The problem is missing driver for WCH-Link SERIAL.
Default CDC driver from windows is not correct one. Additional driver from WCH is necessary in my case:
https://pio-ch32v.readthedocs.io/en/latest/installation.html#install-drivers-rules