Change MOSI/MISO to COPI/CIPO to follow OSHWA guidance

tigard-tools / tigard

An FTDI FT2232H-based multi-protocol tool for hardware hacking

Other

592 stars 72 forks source link

Change MOSI/MISO to COPI/CIPO to follow OSHWA guidance #12

Closed securelyfitz closed 4 years ago

securelyfitz commented 4 years ago

https://www.oshwa.org/a-resolution-to-redefine-spi-signal-names

I have used Main and Subordinate whenever spelling out the acronyms, but happy to jump on this bandwagon since it's the first formal, collective statement on the matter. Will update my class materials to match.

Primary change would be silkscreen and documentation, but probably worth renaming nets to match too.

securelyfitz commented 4 years ago

Hmm. On re-reading, it seems they'd recommend using SDI and SDO labels on those pins, but waffles on which is which. (are we naming it from the controller's perspective or the peripherals?)

The only way to eliminate that ambiguity is to use 4-letter acronyms, so i still think COPI/CIPO is best.

fharding1 commented 4 years ago

:+1: fixed net names, silk, and README. Agreed COPI/CIPO is best.

fharding1 commented 4 years ago

After we test the v0.1 boards we should increment the version number to v1. Then I will render and clean up the board image so it'll not have MISO/MOSI anymore.