MSDK OpenOCD vs Latest OpenOCD - which commit is the current AD version From

[rhempel]

I have verified that he MSDK builds, flashes, and debugs using VSCode on my Linux machine. So far so good - the vendor supplied toolchain works and was a pleasantly easy install.

@Jake-Carter please extend my thanks to the team that works on MSDK. The tooling, install, and especially the documentation is actually quite good. Isn't it nice when tools like Sphinx are available and are really suited to the task :-)

As nice as MSDK is, I have a toolchain and build process that uses Docker containers for both development (on Linux/Windows/Mac) and CI/CD via GitHub or GitLab automation.

I am trying to sort out why the latest OpenOCD xpack fails to program the 32690 device FLASH - its version is:

xPack Open On-Chip Debugger 0.12.0+dev-01685-gb9224c0c0-dirty (2024-08-02-19:50)

The ADI OpenOCD works fine, but I can't tell exactly which commit it is built from because the version string is:

Open On-Chip Debugger (Analog Devices 0.12.0-1.0.0-7) OpenOCD 0.12.0 (2023-09-27-07:53)

There's no commit number and no tag so I can't see which version of the original OpenOCD I should be comparing against for differences.

Has ADI made a merge request for changes to support the MAX32xxx devices better been made more recently than 2021? Here is the search for commits with 32xxx in the official OpenOCD repo:

https://repo.or.cz/openocd.git?a=search&h=HEAD&st=commit&s=32xxx&.cgifields=sr

[ttmut]

Hi @rhempel,

Have you checked ADI's fork of openocd https://github.com/analogdevicesinc/openocd for MAX32xxx related commits?

[rhempel]

@ttmut yes I have checked that repo for max32xxx commits. It looks like there was some work done to separate the adi-5 and adi-6 debug interfaces, but the latest OpenOCD already has support for those interfaces within the adi-5 files.

I'll have another look to see if the AD/MAX support can be brought into the current openOCD as a smaller set of changes.

Is the current AD OpenOCD tool built from main, or some other branch. If I'm going to do this I want to be sure I'm starting from the right branch :-)

[ttmut]

I am not much involved in OpenOCD development and I might be completely misunderstanding your query. However, looking at https://github.com/analogdevicesinc/openocd/commits/0.12.0-1.0.0/ suggests that it is https://github.com/openocd-org/openocd/commits/v0.12.0/ plus changes introduced in analogdevicesinc/openocd@3a0e71b

[sihyung-maxim]

Hi!

Although I'm not directly involved with the OpenOCD development either, all OpenOCD development for ADI is done within an internal ADI repo (not on GitHub) from which a release is created and subsequently pushed to analogdevicesinc/openocd. The OpenOCD binaries that come with the MSDK installer are pulled from the internal repo and, as Tahsin mentioned, match this release here: https://github.com/analogdevicesinc/openocd/releases/tag/0.12.0-1.0.0

I don't know when ADI plans to merge its changes with the official OpenOCD repo, but the links, that Tahsin linked above, are a good place to start!

Let me know if you have any other questions.