hartmannathan commented on issue #14690: URL: https://github.com/apache/nuttx/issues/14690#issuecomment-2464926181
> @hartmannathan Thank you for your suggestion. However, after adding the lines you recommended, I am still encountering the same issue. I have spent several hours debugging, but the problem persists, and I can't seem to identify the root cause. Any further guidance or insights would be greatly appreciated. **In your board's include/board.h file**, you need to define `GPIO_SSI1_CLK`, `GPIO_SSI1_RX`, and `GPIO_SSI1_TX`. `GPIO_SSI1_CLK` can be defined in one of the following two ways: If your board has the SSI1 CLK routed to pin PD0: ``` #define GPIO_SSI1_CLK GPIO_SSI1_CLK_1 ``` or, if your board has SSI1 CLK routed to pin PF2: ``` #define GPIO_SSI1_CLK GPIO_SSI1_CLK_2 ``` The same goes for `GPIO_SSI1_RX`, and `GPIO_SSI1_TX`, with `GPIO_SSI1_RX` defined either to `GPIO_SSI1_RX_1 ` (PD2) or `GPIO_SSI1_RX_2 ` (PF0), and with `GPIO_SSI1_TX` defined either to `GPIO_SSI1_TX_1 ` (PD3) or `GPIO_SSI1_TX_2 ` (PF1). How do you know which pin the _1 suffix or _2 suffix will use? These definitions are in [nuttx/arch/arm/src/tiva/hardware/tm4c/tm4c_pinmap.h, around line 245](https://github.com/apache/nuttx/blob/db31e569579c7ec9753d5fb69d07e8f997c7eae1/arch/arm/src/tiva/hardware/tm4c/tm4c_pinmap.h#L245) ``` # define GPIO_SSI1_CLK_1 (GPIO_FUNC_PFIO | GPIO_ALT_2 | GPIO_PORTD | GPIO_PIN_0) # define GPIO_SSI1_CLK_2 (GPIO_FUNC_PFIO | GPIO_ALT_2 | GPIO_PORTF | GPIO_PIN_2) # define GPIO_SSI1_FSS_1 (GPIO_FUNC_PFIO | GPIO_ALT_2 | GPIO_PORTD | GPIO_PIN_1) # define GPIO_SSI1_FSS_2 (GPIO_FUNC_PFIO | GPIO_ALT_2 | GPIO_PORTF | GPIO_PIN_3) # define GPIO_SSI1_RX_1 (GPIO_FUNC_PFIO | GPIO_ALT_2 | GPIO_PORTD | GPIO_PIN_2) # define GPIO_SSI1_RX_2 (GPIO_FUNC_PFIO | GPIO_ALT_2 | GPIO_PORTF | GPIO_PIN_0) # define GPIO_SSI1_TX_1 (GPIO_FUNC_PFIO | GPIO_ALT_2 | GPIO_PORTD | GPIO_PIN_3) # define GPIO_SSI1_TX_2 (GPIO_FUNC_PFIO | GPIO_ALT_2 | GPIO_PORTF | GPIO_PIN_1) ``` Hope this helps. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
