5 ms·
This sounds great! But as long as there's no GCC support it's usefulness is limited. These kind of controllers are more than sufficient for most simple control
by UltraViolence 4y ago
This sounds great! But as long as there's no GCC support it's usefulness is limited.
These kind of controllers are more than sufficient for most simple control tasks. ARM is simply too expensive here, since the licensing itself probably costs more than the MCU itself.
- eqvinox 4y agoIt's a RISC-V core… so it's supported by GCC, unless they f*cked up something quite badly (which I doubt.) [Ed.: Chinese datasheet says "RV32EC", in case anyone is wondering.]
- FullyFunctional 4y agoThe whole point of RISC-V is that there _is_ GCC support, since a decade, already. Even assuming they have proprietary extensions, it's pretty unlikely you need them in application code. At worst it's just in setup code. However I didn't see any of the usual "bragging" about extensions, so I doubt it. Usually the biggest issue is lack of [good] documentation, but I suspect this will work itself out over time.
- flaviut 4y agoGCC works fine. Following along the thread here, https://mobile.twitter.com/kprasadvnsi/status/1496012713423691786 https://mobile.twitter.com/kprasadvnsi/status/14960127134236... Looks like they have a semi-custom debug protocol, and there's a reverse-engineered OpenOCD here: https://github.com/fxsheep/openocd_wchlink-rv https://github.com/fxsheep/openocd_wchlink-rv As well as a copy of the source code for the vendor's version of OpenOCD here: https://github.com/kprasadvnsi/riscv-openocd-wch https://github.com/kprasadvnsi/riscv-openocd-wch Probably about good enough to get started with this device with a FOSS toolchain.