"Entries have to be submitted in the form of repositories on github.com with a clearly stated BSD-style license (the Apache 2.0 license is preferred)"
Ha. Ha. Ha. BSD-style. Apache 2.0 preferred. Why would they state that? Oh, I don't know... maybe because of this clause?
"[...] each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form."
Yes, this is standard for BSD-style licenses, and I like it, because this means I can use other designs as well in my commercial products. This is the concept of open source: give and take. Usually I release my stuff as open source, too, if it is my own project, or if my client allows it.
And no problem if they want to promote the RISC-V. It is a win-win deal: they get some PR and you get some money if you win. And you can still use and sell your core as well, even when they are selling it. Of course, there are already a few very good open source FPGA implementations of the RISC-V available, will be difficult.
Regarding the Verilog requirement: You could use something like
Chisel, or develop it in VHDL, then translate it to Verilog. I've tested a few products, free and commercial, and this was the best so far:
http://www.syncad.com/verilog_vhdl_translator.htmThe price is ridiculously high ($250 per day), but you can get a free one-day evaluation license. Sufficient to convert the project, once it is working in VHDL.
Meanwhile I finished writing a simple C emulator, optimized for the RV32I architecture, based on a more complex emulator, which passes all compliance tests:
https://gist.github.com/FrankBuss/c974e59826d33e21d7cad54491ab50e8Now I just need to convert this to Verilog (and setup the FPGA projects, add the boot-code, UART etc.). Or find a small core which has a C compiler and just compile it, which I think is allowed by the contest rules. They don't say it is forbidden that you use a 6502 core and CC65 to compile the C to microcode to emulate the RISC-V core
