stnolting
stnolting
> I found that the version is manually bumped in several places. Right. I know it is bad practice. This whole "versioning concept" emerged in a very early stage of...
> While reviewing the latest changes, I found that the version is manually bumped in several places. SemVer seems to be the way to go! -> #37 > On the...
> The language (VHDL) provides features for solving those problems (both initialising mems from files or defining a version in some file/package). The point is whether the tools you want...
> Hi. I created pyVersioning to be called e.g. in Vivado (synthesis) and Vivado SDK as pre-build steps. I will have a closer look. > In Vivado (synthesis), it's called...
:smile: I completely forget that **stale** is watching this repository... > Hmmm, @stnolting, I'm not sure it is good to have issues automatically marked as stale/wontfix and then closed. There...
> So, why are you using your pre-built GCC toolchain? Do you need to customise it so that it understands NEORV32 as the target architecture? Or is it because of...
@umarcor > Those are riscv64. However, I used RISCV_TOOLCHAIN=riscv64-unknown-elf-gcc make install in sw/example/demo_pwm, and that produced exactly the same output as using an Ubuntu container and extracting your custom GCC...
> So, we should update the docs (user guide) to let Windows users know that they can install pacman -S mingw-w64-x86_64-riscv64-unknown-elf-gcc mingw-w64-x86_64-yosys mingw-w64-x86_64-nextpnr 🚀 Absolutely! And there should also be...
This is not urgent at all. I was just amazed by the documenter's features. :heart: So I agree with @umarcor: > I was not criticising the lack of Action, but...
So we have two options right now to support a FPGA-USB interface: 1. https://github.com/no2fpga/no2muacm 2. https://github.com/davidthings/tinyfpga_bx_usbserial I would prefer porting option 1 as a **new peripheral for the processor** since...