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
UART1 support for msp430f1611 and SPI #5599
Comments
Oh, I assigned you because it seems that you committed the current configuration of the SPI on this board. USART1 is not used AFAIK, the issue here is that we need to add it because it shares buffers and some configurations with the SPI port. I don't have access to the actual boards but using IoT-Lab ones on the testbed. |
Changing the serial module isn't much effort, I'd just need to know if USART1 is actually connected. (Also on the IoT-Lab) Else I guess serial output and radio are not useable at the same time. 😞 |
UART1 in the wsn430-v1_4 board is not connected, I think, as you said it shouldn't be much effort, maybe only to tell the SPI to use the buffer of UART1 would be enough. |
I don't think it is possible to tell USART0 (configured as SPI module) to use USART1 buffers. :| |
And what about configuring the USART1 as SPI? I think it should work since in the IoT-Lab repositories there is a port for contiki which uses UART1 for STDIO and SPI for radio... |
Postponed as the PR solving this was postponed too. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions. |
The SPI peripheral on msp430f1611 is configured to be used with the UART0 peripheral, so we can't have the shell output and the SPI working at the same time.
Therefore, we need to add support for UART1, in order to share it with the SPI and enable the use of UART0 and SPI together.
Anyone having the same issue or willing to add support to this?
The text was updated successfully, but these errors were encountered: