Skip to content

Conversation

@ArcaneNibble
Copy link
Collaborator

This is dependent on pybricks/pybricks-pru#1 , and it needs to be modified to download the PRU binary rather than checking it into git (see related: pybricks/support#2262 ), but I am opening the PR for now as the rest of the code is ready.

@coveralls
Copy link

coveralls commented Jul 15, 2025

Coverage Status

coverage: 57.239%. remained the same
when pulling cc34c7f on ArcaneNibble:pru-pwm
into 49f716f on pybricks:master.

@ArcaneNibble
Copy link
Collaborator Author

PR has been updated to download a released PRU binary (which is no worse than what currently happens for U-boot).

This is now ready for review.

@ArcaneNibble
Copy link
Collaborator Author

Updated based on feedback.

Using the linker script incidentally means that overflowing the shared memory region will be caught. However, this PR doesn't yet migrate PRU0 to use it.

$(BUILD)/pru_ledpwm.bin:
$(ECHO) "Downloading pru_ledpwm.bin"
$(Q)mkdir -p $(dir $@)
$(Q)curl -sL -o $@ https://github.com/pybricks/pybricks-pru/releases/download/v0.0.1/pru_ledpwm.bin
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would already call it v1.0.0. (I no longer believe in https://0ver.org/) 😆

@dlech
Copy link
Member

dlech commented Jul 16, 2025

This one looks good to go.

@dlech dlech merged commit 4484552 into pybricks:master Jul 16, 2025
17 checks passed
@dlech
Copy link
Member

dlech commented Jul 16, 2025

Although I just noticed too late that none of the commits have a description beyond the subject. We don't want to make a habit of this and instead would like at least one sentence explaining why the change is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants