[Windows 11] No valid BOARD values for make command

[rasmuskurstein]

Hi!

Just got my eurorack-pmod and an icebreaker board, and I am trying to get started with some of the examples!

I followed the "Getting Started" section of this repo, and followed the oss-cad-suite-build installation as specified on the github page.

However, I appears that I have no board values for the make command. Is there some (maybe obvious) step I am missing for connecting the icebreaker board?

I am completely new to this world, would also appreciate any help on what to read up on to better understand the tools!

---

On windows 11. When running the make command from the gateware directory:

make HW_REV=HW_R33 BOARD=icebreaker CORE=mirror prog

I get the error:

mkdir -p build/icebreaker
The syntax of the command is incorrect.
make: *** [Makefile:36: prog] Error 1

When running just the make command, I get:

process_begin: CreateProcess(NULL, ls boards, ...) failed.
Makefile:12: pipe: No such file or directory
process_begin: CreateProcess(NULL, basename --suffix=.sv -- cores/*.sv, ...) failed.
Makefile:13: pipe: No such file or directory
process_begin: CreateProcess(NULL, ls boards, ...) failed.
Makefile:21: pipe: No such file or directory
"Valid HW_REV values are: "HW_R31 HW_R33"".
"Valid BOARD values are: ".
"Valid CORE values are: ".
"Valid TOUCH values are: "TOUCH_SENSE_DISABLED TOUCH_SENSE_ENABLED" (default disabled, valid for R3.3+ only, required for any examples that use touch)".
"For example:"
"  $ make clean"
"  $ # Build bitstream with specific core and program it"
"  $ make HW_REV=HW_R33 BOARD=icebreaker CORE=mirror prog"
make: *** [Makefile:19: all] Error 1

[vk2seb]

Hey there @rasmuskurstein!

I think the problem is that some unix-y dependencies are missing when running this straight from a Windows command prompt. Agree this could use some better docs.

The build system uses a unix-style Makefile system, which means you need to install some extra things on Windows compared to Linux or Mac. However, I have this job in CI where you can see exactly what I needed to install to get a successful Windows build (this is tested on every commit):

https://github.com/apfelaudio/eurorack-pmod/blob/master/.github/workflows/main.yml#L45-L67

I'd recommend going through the above CI job to see what is there, but in summary:

• Install MSYS2 and open an MSYS2 shell
• Install git and make with something like pacman -S git make
• git submodule update --init --recursive in the eurorack-pmod repository to clone the dependencies
• Extract the oss-cad-suite somewhere else
• Make sure the binaries are available in your PATH using (replace path_you_extracted)

export PATH=$PATH:/path_you_extracted/oss-cad-suite/bin
export PATH=$PATH:/path_you_extracted/oss-cad-suite/lib

• If you do a yosys --version from the eurorack-pmod git repo and it works, the above worked
• Then you can try a make

As a completely different alternative to the above, you could try using WSL2. However I think with WSL you might have issues with the iceprog tool being able to access the USB device. To be clear I don't use Windows myself but I did make sure that Windows builds are automatically tested.

let me know how you go!

[rasmuskurstein]

I did indeed try to run it from the windows terminal!

After running the command

<extracted_location>/oss-cad-suite/environment.bat

in the MSYS shell, the board values appear when running the make command.

---

I had a second issue as well though, I will leave the solution here for other people getting started with icebreaker->euorack-pmod on windows:

I was getting an error from the make command, that the icebreaker board wasn't found, even though lsusb shows it is connected and with the correct id.

To work with the ICEBreaker board on windows , the driver needs to be changed to WinUSB. This can be done with Zadig.

---

It's working now, I have the mirror core up and running! I will check out some more examples, and then get to programming!

Thanks for the help :)

[vk2seb]

Good to hear it's working now and thank you for the details on Zadig, I feared iceprog might need a trick like that. I'll migrate these notes over to the README at some point :)