This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SPI working in mesh SDK, not in normal SDK

Dear Devzone,

When working with the nRF52840 I had implemented an ethernet connection using the W5100 chip. I used some examples and libraries from this blogpost I had a mesh network running and was posting information to a mock back-end using the W5100 connected with SPI.

Right now I started with working with combining Mesh and BLE SDK, and the same libraries and SPI code is not working anymore. I used the guide " Coexistence with other Nordic SDK's " and this Question/post to get the Mesh working in my BLE SDK project.

Both guides explain about : " Customize the simple_hal.c to not use GPIOTE_IRQHandler() as it conflicts with the gpiote driver in the SDK " so I just commented the code in simple_hal.c, and later I tried commenting it in nrf_drv_gpiote.c.

To verify:

  • using the same *.h & *.c files for all the W5100, Ethernet libraries as in the other project
  • Using a logic analyzer I can verify that GPIO signals are send by the nRF52840 in the new project but that I get no response (again using the exact same code).

I compared the sdk_config.h files and the all the relevant settings for SPI are identical. Althought there are some differences in the file.

sdk_config.h for the BLE new project (SPI not working ) sdk_config.h for the old MESH project (SPI working)

Does any one have an idea where I can start looking?

To me it is weird that using the same way of calling the SPI libraries and Ethernet libraries will work in one project, but not in another. Other then some settings in the sdk_config.h I can't think of anything else.

Thanks in advance.

Parents Reply Children
No Data
Related