Bypassing the thread message to SPI bus instead of Multiprotocol on NRF52840

Hey Nordic team , 

We are trying to work on use-case where we want NRF52840 to generate  thread Stack message but instead of using multi-protocol features it can transmit the message to SPI bus .

Is that possible and other chip can totally work as transmitter or receiver.

If we can run same case with 52832 

Just in short context: is that possible to disable the multiprotocol layer and we can run thread stack on two differ chips .Where on board can process the thread stack and share an spi message and other board will act as 802.15.4 handler  

Parents
  • Hi,

    We are trying to work on use-case where we want NRF52840 to generate  thread Stack message but instead of using multi-protocol features it can transmit the message to SPI bus .

    Is that possible and other chip can totally work as transmitter or receiver.

    From what I understand, you want the upper parts of the thread stack to run on one SoC, and the lower parts (RF parts) to run on another SoC? I.e. similar to for Bluetooth LE, where you can have host (upper layers) run on a different unit than the controller (upper layers) and use the Host Controller Interface (HCI) for the communication.

    This is not possible with our Thread stack, no.

    If we can run same case with 52832

    The nRF52832 does not have support for 802.15.4, so it cannot run Thread.

    Just in short context: is that possible to disable the multiprotocol layer and we can run thread stack on two differ chips .Where on board can process the thread stack and share an spi message and other board will act as 802.15.4 handler  

    I wonder, what would be the reason for doing that? Are you planning on running two different RF protocols in parallel, for instance Thread and BLE? Or Thread and another protocol? Then it would be much easier to run both protocols on the same device, then to run them on two different devices. In order for two protocols to run concurrently, they must cooperate. Otherwise, if one sends when the other listens, or both sends, you will get effects such as packet collisions, interference, etc. and worst-case damage the device.

    Regards,
    Terje

Reply
  • Hi,

    We are trying to work on use-case where we want NRF52840 to generate  thread Stack message but instead of using multi-protocol features it can transmit the message to SPI bus .

    Is that possible and other chip can totally work as transmitter or receiver.

    From what I understand, you want the upper parts of the thread stack to run on one SoC, and the lower parts (RF parts) to run on another SoC? I.e. similar to for Bluetooth LE, where you can have host (upper layers) run on a different unit than the controller (upper layers) and use the Host Controller Interface (HCI) for the communication.

    This is not possible with our Thread stack, no.

    If we can run same case with 52832

    The nRF52832 does not have support for 802.15.4, so it cannot run Thread.

    Just in short context: is that possible to disable the multiprotocol layer and we can run thread stack on two differ chips .Where on board can process the thread stack and share an spi message and other board will act as 802.15.4 handler  

    I wonder, what would be the reason for doing that? Are you planning on running two different RF protocols in parallel, for instance Thread and BLE? Or Thread and another protocol? Then it would be much easier to run both protocols on the same device, then to run them on two different devices. In order for two protocols to run concurrently, they must cooperate. Otherwise, if one sends when the other listens, or both sends, you will get effects such as packet collisions, interference, etc. and worst-case damage the device.

    Regards,
    Terje

Children
No Data
Related