3 ms·
I wonder what the use cases of MicroBlaze V are vis a vi, say, SERV https://serv.readthedocs.io/en/latest/servant.html https://serv.readthedocs.io/en/latest/se
by GeorgeTirebiter 3y ago
I wonder what the use cases of MicroBlaze V are vis a vi, say, SERV https://serv.readthedocs.io/en/latest/servant.html https://serv.readthedocs.io/en/latest/servant.html
That is, the only advantage MicroBlaze V gives you, besides blessing from the chip manufacturer, is speed. Aren't FPGA CPUs usually used to do tasks that aren't especially time-sensitive? I mean, that's what the FPGA fabric is for, to get high-speed, time-sensitive tasks done (in conjunction with the on-chip I/O interfaces).
- crote 3y agoTooling and support. You don't really want to mess around with a RISC-V softcore, you just want it to work and interface with the stuff you actually care about already. MicroBlaze allows you to literally construct your own softcore via drag-and-drop, selecting from a wide variety of configuration options and peripherals. It includes SDKs for your custom applications, and debugging tools to figure out what's going wrong. I would not be surprised if development using SERV would take several orders of magnitude longer, solely due to immature tooling.