Add support for PUYA PY32F0xx about edbg

[ataradov]

I will look into supporting them. They are very similar to STM32 parts, so overall support should not be too hard. But there are a number of annoying differences between the devices. PY32F002B does not seem to have any documented flash read protection, for example. And 004 devices have option bytes located at a different address.

I only have PY32F002A, so this is the only device I can test, so I will be targeting that.

[ataradov]

I have added PY32F002A support. It should also work for PY32F002B, but I can't find device IDs for any of the devices, so I just added the one I have for tests. If you have any other devices, I can work with you on figuring out those IDs and adding them to the program.

Other devices are similar, but different enough that adding them is not as easy as adding device ID line. But it still should be possible to do remotely.

[ShmulikKraus]

Wow that was quick! Many thanks Alex! I only have PY32F002A right now, but I ordered some PY32F002BW15S6TU and just yesterday the package was shipped. Should be here in about 3 weeks or so.
When it does arrive, will using OpenOCD to program it and thus giving me the Chip ID be enough or should I do anything else?

[ataradov]

When you have the device, you can just run edbg with "py32f0" target and it will give you the ID code, since it will not recognize it. Just provide it to me and I will add it to the program.

[ShmulikKraus]

No problem, and thanks again.

[ShmulikKraus]

My package finally arrived. As promised here is the code for the PY32F002BW15S6TU:
0x20220064

You can close this issue now, if you want to.

[ataradov]

This code was already added, the most recent version should recognize this device. It was reported on EEVBlog forum.

[ataradov]

Closing the issue.