-
Notifications
You must be signed in to change notification settings - Fork 10
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
[SL-UP] 917ncp init failure fix #133
[SL-UP] 917ncp init failure fix #133
Conversation
Why does the efx32_ncp_host update cause errors? Did we root cause the the seen errors? |
The error is seen during SPI transfer, sl_si91x_host_spi_transfer() - This API is throwing SPI_BUSY error. I've tried to debug, but couldn't root cause it. |
Let me know when we have a better idea with what is happening with the latest efx32 ncp host file and the sl_net APIs. It might be worth while to open a Wiseconnect issue for this to get them involved. |
3bf866b
to
2792275
Compare
Wiseconnect ticket - https://jira.silabs.com/browse/WIFISDK-1109 |
00775a3
into
SiliconLabsSoftware:release_2.5-1.4
This PR fixes the init failure in 917NCP boards.
After integrating the matter_sdk code with the sl_net APIs, the init is failing because LWIP init is called twice for 917NCP.
To resolve this, we have removed the LWIP init from PlatformManager and modified the init sequence to avoid errors while booting. But, with the recent SPI related changes, we are facing SPI_BUSY error. So, reverted the recent changes made in efx32_ncp_host.c file. With these changes, the init for 917NCP is passing.