> What's wrong with having "print('hello world')" run on a micropython running on a risc V core on an FPGA?
Because it betrays a misunderstanding of WHY you are using an FPGA in the first place.
If you want to program a microcontroller, go get a microcontroller.
You generally use an FPGA for a reason. And that reason almost always relates to speed (either latency or throughput). VERY occasionally it has to do with simply translating logic standards (changing from something like LVDS differential to standard CMOS, for example).
If you don't need speed, you should go back to the microcontroller. And, even if you need speed, you should still go back to a microcontroller and see if you can bend it to your needs somehow.
Programming an FPGA isn't just "throw some HDL around". Why do you need a clock? What are synchronizers and why do you need them? Why does my FPGA suddenly not have enough resources when I design a numerical divider and ask it to be fast?
Digital design != programming. And vice versa.
Programmers complain all the time "Git is easy. You just have to learn its mental model." and bitch about people that won't. So, why do you believe that wouldn't also hold for digital design?
> And why is it not simple?
How would you answer to someone complaining that "Why isn't programming simple? Dogma? Industry standards? Drinking the IDE vendor kool-aid?"
As a reminder, remember, "Hello, world." is a very difficult hurdle for most non-programmers.
> What's wrong with having "print('hello world')" run on a micropython running on a risc V core on an FPGA?
RISC-V is slightly odd in that actual microcontroller hardware is a bit thin on the ground. However, wanting to play with RISC-V via an FPGA development board that isn't explicitly set up for that purpose is kind of like learning Rust by programming an STM32F7 development kit.
You can, but boy are you making your life miserable.
