chmousset

@Codetector1374 all done on my side. FYI the the ch32v305 examples fail to build on `nightly` on my machine too, but builds successfully on `nightly-2025-06-01` Maybe pinning the rust version...

@jsprog TBH I didn't want to open that can of worms. - if ch32-data is wrong, or lack chip-specific information, we should create a PR in ch32-data - I'm all...

@jsprog > As they're using in-package separate flash. What's making half-word erase value 0xe339 instead of 0xFFFF? Unfortunately I didn't find any clue in the documentation or online... like most...

@jsprog so does it work? if you can share a PoC, even rough, that could be useful.

@Snow-in-Dublin CH32V307 is Qingke V4F, which is RV32IMAC**F** The original code looks right to me. Did you witness illegal instruction or other issues when using floating-point ?