Microchip patches (was: RC1 and open changes/pull request)

[Tomas V. <to...@us...>]

Liam,

I'm aware of the series of Microchip patches and believe me the slow (or 
almost no) progress makes me sad.

The idea of the new patch with just the target configuration file is 
good, actually the same was requested
in Antonio's review 
https://review.openocd.org/c/openocd/+/8561/comment/56c7814e_16ac017c/
half year ago.

Please do not abandon other patches, you may rebase them on top of the 
new patch (now or later).

I do not agree with you that microchip_riscv.cfg is ready. Although it 
may work somehow, I noticed
couple of suspicious things and some evident errors. This config is also 
very complicated as it serves for
several different devices and setups. I doubt anybody of OpenOCD team 
could seriously review it without
having access to the hardware.

You may try to submit the config first to the RISC-V specialised OpenOCD 
fork repository
https://github.com/riscv-collab/riscv-openocd

Tomas

On 23/05/2025 15:43, Lia...@mi... wrote:
> Hello,
>
> we see that an RC1 is coming soon. We have some pull requests open for 
> drivers that will probably not make it in on time, however the 
> configuration files for the target is ready and can be used with 
> already upstreamed drivers such as Olimex, etc for software debug.
> What we would like to do is to try get the target configuration file 
> in and drop the patches for driver support. What would be the best way 
> to do this? Currently Conor Paxton has patches for all the drivers/ 
> configuration files (8563 
> <https://review.openocd.org/c/openocd/+/8563> and 8561 
> <https://review.openocd.org/c/openocd/+/8561>). Should we abandon 
> these and create a new patch with just the target configuration file?
>
> Thank you in advance for any advice offered.
>
> Best regards,
>
> Liam.
>
>
> (apologies if this is a duplication, issue with mail client)
>
>
>