What is the location of the PYBADGEBOOT directory? You can get it with the mount command. On Debian it's usually /home/<username>/PYBADGEBOOT.

As a temporary workaround, you can write it manually to the device. For example:

tinygo build -o /media/$USER/PYBADGEBOOT/firmware.uf2 -target=pybadge main.go

The location of this drive on Fedora is not the same as Debians. We ran into this exact problem recently at our workshop at SCaLE.

I think someone was going to submit a PR that added the correct path.

What is the location of the PYBADGEBOOT directory? You can get it with the mount command. On Debian it's usually /home/<username>/PYBADGEBOOT.

According to the Files app, the directory is:
/run/media/(my_username)/PYBADGEBOOT

Thanks @aykevl !

As a temporary workaround, you can write it manually to the device. For example:

tinygo build -o /media/$USER/PYBADGEBOOT/firmware.uf2 -target=pybadge main.go

This workaround appears to work (note the path below):
tinygo build -o /run/media/$USER/PYBADGEBOOT/firmware.uf2 -target=pybadge main.go

The location of this drive on Fedora is not the same as Debians. We ran into this exact problem recently at our workshop at SCaLE.

I think someone was going to submit a PR that added the correct path.

@deadprogram : Does the PR need to be submitted here or somewhere at Fedora? This looks like a tinygo building / flash issue. Does issue 954 serve as notice? :)

Not sure if this related, but I get this new error trying to flash the name badge code:
$ tinygo build -o /run/media/$USER/PYBADGEBOOT/firmware.uf2 -target=pybadge main.go

main.go

main.go:25:22: SPI1_MISO_PIN not declared by package machine

Changing the code from MISO to MIS0 doesn't appear to help....

EDIT: I'm finding commenting that line by prepending a "//" (no quotes) appears to get the ball rolling. Yay!

Regarding the path to the badge for flashing, that would be a PR here, please.

Regarding the SPI1 compile error, which program are you trying to build?

The relevant code is here if you want to make a PR: https://github.com/tinygo-org/tinygo/blob/master/main.go#L483
It locates the correct path simply by globbing at a well-known location (that unfortunately varies between distros).

Experiencing the same issue on Arch. The path for drives on Arch is /run/media/<user>/<drive name>.

Another workaround is creating a symlink, like so: sudo ln -s /run/media/$USER /media/$USER. After this, tinygo flash should just work.

Is there someone who would make a PR to fix this? The relevant code is here:

It doesn't need any special knowledge, but is much easier done when you're actually running Fedora or Arch (which I don't).

I will try to make a PR. Should be ready soon if I don't encounter any issues.

I've just created a PR that seems to fix it. Only tested on Arch, not Fedora or Debian.

I accidentally made my previous PR against release. Sorry about that. Anyway, I've created a new PR and changed it to work with pre-1.16 versions. If someone could look at it, and test it on Debian and Fedora, that would be much appreciated. Thank you.