Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aleph libavr32 #18

Merged
merged 8 commits into from Nov 16, 2016
Merged

aleph libavr32 #18

merged 8 commits into from Nov 16, 2016

Conversation

@catfact
Copy link
Contributor

@catfact catfact commented Oct 31, 2016

BREAKING: changes to allow libavr32 to be used in the aleph codebase.

the breaking changes are pretty minor. as far as i can tell, they consist only of the changed pin definitions. so spi_write(SPI, DAC_SPI) becomes spi_write(DAC_SPI, DAC_SPI_NPCS), which is more consistent with usage across the ASF.

this is not just cosmetic; aleph uses UC3A and has multiple SPI ports, so it's necessary to explicitly define them.

for ansible, this doesn't break anything because all SPI access is through the ADC and DAC drivers in the library (as it should be.)

for teletype and trilogy, SPI pin and register defines are used directly in main.c, so those must be updated or frozen.

also, some minor changes to the ASF have been made, removing some unused board configuration headers and including conf_board.h more directly. this was necessary to get some of the drivers working. these changes should be reflected in yet another PR on the diet_asf repo.

@catfact catfact changed the title Aleph libavr32 aleph libavr32 Oct 31, 2016
@samdoshi samdoshi merged commit b82efd8 into monome:master Nov 16, 2016
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@catfact catfact deleted the catfact:aleph-libavr32 branch Nov 28, 2016
@catfact catfact mentioned this pull request Apr 14, 2017
1 of 2 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants