-
Notifications
You must be signed in to change notification settings - Fork 15
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
MAX2769 SPI interface not connected to GPIO with access to SPI module on STM32f4xx #4
Comments
We very carefully thought about this. As far as I remember:
I'll go take a look at your proposals. |
AARRRGHHH K is annoyingly correct. SPI2 is available and we should thus use it. How did we miss this? I approve of the mod wires for SPI2_MOSI and SPI2_SCLK. K, I think there's no reason to use SPI2_NSS because that's really just a GPIO pin, and we can continue to just use PE12. I don't believe the NSS does anything when the SPI peripheral is in master mode. Can you please confirm this? |
I recommend not bothering with the NSS pin. On RTx, I happen to be using the pin designated NSS (external ADCs on SPI1), but I'm neither configuring it in its SPI Alternate Function, nor am I calling the SPISelect() or SPIUnselect() functions, but rather just setting/clearing this pin.Rob On Fri, Jun 13, 2014 at 9:38 AM, Andrew Greenberg
|
The SPI peripheral has some trivial master mode NSS management (see ref. man. p860), but ChibiOS opts not to use this feature and instead manage NSS through it's GPIO driver. The implementation of SPISelect is literally palClearPad(). Furthermore the SPIConfig struct lets you set any pin to be managed by the SPISelect function. I too think it's fine to leave it alone. |
I have removed the modwire proposal from the v2 schematic for SPI2_NSS. We can use the chip select connection (PE12) in GPIO mode. |
This is a duplicate of avionics-cad repo. Issue 2.
(Perhaps it should only have been entered here.)
I have added mod wire proposals to the schematic for the v2 board.
The text was updated successfully, but these errors were encountered: