spi_master vs spi_master_5w?

RE: spi_master vs spi_master_5w?

Mike Wirth — Fri, 07 Nov 2014 19:05:53 GMT

Thanks, Asbjorn and Maki. Answers my question. BTW, in the Doxygen-generated documentation for functions, it would be very useful if in describing parameters, the acceptable range of values is included, as well as an example. For enums I can trace back the definition and find the acceptable values, but for other types it's often not clear (e.g. when a return is specified as unint32_t and it's an error code). Mike

RE: spi_master vs spi_master_5w?

maki — Fri, 07 Nov 2014 14:38:57 GMT

For all cases, except serialization, usage of standard spi_master driver is recommended. SPI_master_5W has extended functionality to support so called spi-5-wire serialization protocol. And as such, was tested only with 'ser_phy_spi_5w' driver. SPI_5W protocol is rather specific, and uses nrf51 slave device features. For details, please refer to SDK html documentation. The protocol is described in SDK\Libraries\BLE Serialization\Serialization PHY\SPI_5W RAW Protocol.

RE: spi_master vs spi_master_5w?

Asbjørn — Fri, 07 Nov 2014 10:45:09 GMT

The 5W example is a SPI serialized version of the HRS example. The latest update about this can be found here, but it's pretty much the same as in SDK 6.1

The serialization examples are made to just send data to the nRF51 through UART/SPI and the nRF51 will handle all the BLE traffic and your co-processor doesn't need to handle anything. If you're looking for just a SPI example I would have a look at the non-serialized examples, but rather the spi_master_example.

Regarding your request, I can't say whether or not we will or when it then would be implemented, nevertheless, I've reported it internally to our SDK team.