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

UART1 support for msp430f1611 and SPI #5599

Closed
kYc0o opened this issue Jul 5, 2016 · 9 comments
Closed

UART1 support for msp430f1611 and SPI #5599

kYc0o opened this issue Jul 5, 2016 · 9 comments
Assignees
Labels
Platform: MSP Platform: This PR/issue effects MSP-based platforms State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT

Comments

@kYc0o
Copy link
Contributor

kYc0o commented Jul 5, 2016

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?

@kYc0o kYc0o added Platform: MSP Platform: This PR/issue effects MSP-based platforms Feature Request labels Jul 5, 2016
@kYc0o kYc0o added this to the Release 2016.07 milestone Jul 5, 2016
@thomaseichinger
Copy link
Member

@kYc0o @OlegHahm I don't know the wsn430 boards, the question is if USART1 is actually connected? Or do you use a UART adapter with the board?

@kYc0o
Copy link
Contributor Author

kYc0o commented Jul 5, 2016

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.

@thomaseichinger
Copy link
Member

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. 😞

@kYc0o
Copy link
Contributor Author

kYc0o commented Jul 5, 2016

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.

@thomaseichinger
Copy link
Member

I don't think it is possible to tell USART0 (configured as SPI module) to use USART1 buffers. :|

@kYc0o
Copy link
Contributor Author

kYc0o commented Jul 5, 2016

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...

@thomaseichinger
Copy link
Member

@kYc0o please see #5606.

@kYc0o
Copy link
Contributor Author

kYc0o commented Jul 26, 2016

Postponed as the PR solving this was postponed too.

@kYc0o kYc0o modified the milestones: Release 2016.10, Release 2016.07 Jul 26, 2016
@miri64 miri64 modified the milestones: Release 2017.01, Release 2016.10 Oct 31, 2016
@PeterKietzmann PeterKietzmann modified the milestones: Release 2017.01, Release 2017.04 Jan 26, 2017
@miri64 miri64 added Type: new feature The issue requests / The PR implemements a new feature for RIOT and removed Feature Request labels Sep 30, 2018
@stale
Copy link

stale bot commented Aug 10, 2019

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.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@stale stale bot closed this as completed Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Platform: MSP Platform: This PR/issue effects MSP-based platforms State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
None yet
Development

No branches or pull requests

6 participants