Is anybody working on ch32v317?
Good luck with that. I'm not and haven't personally heard or read anything about it apart from you. Your posts may trigger an interest in it though.
I admit I'm not that interested myself for reasons already exposed, but that's just me.
Found a couple of issues, would be good to share them to avoid others running into the same debug loops and workaround finding tracks as me because there are no errata documents.
Might start a seperate thread otherwise.
IMO you should definitely start a new thread about it. This thread is starting to be a bit old and its title suggests a not-yet-available MCU, so that may not attract much interest by now.
Wch stopped somehow replying to my mails after me reporting that their factory bootloader allows readout of read protected flash if utilized in a certain way... Which I showed to them to stimulate them to share how to enable exchange of the factory bootloader.
The bootloader can be reflashed with an own one, but only during an active debug session and not when run standalone which is what I'd need: https://github.com/robots/wch-ch32v20x-flash
I'm not too surprised here. They are not keen to share anything related to the bootloader and even to the debug interface. I had also asked specifically about the debug protocol. They replied it wasn't open and that was it. (Note: the protocol for the lower-end CH32V00x is documented OTOH, but this isn't the same at all. The CH32V00x use a one-wire debug interface, the CH32V2/3xx use a 2-wire interface which is completely different.)