Thingy:91 X with external SPI Slave possible?

Hello, I just had a look at the Thingy:91 X with the nRF9151 and nRF5340 SoC's including nRF7002 Wifi support.

My understanding is that the nRF5340 is the main MCU running the main application, while the nRF9151 is used as a Cellular modem

(1) How is communication implemented between the nRF5340 and nRF9151? I noticed that the schematic defines two UART connections between the SoC's, VCOM0 and VCOM1. Are full Cellular modem features on the nRF5340 available through these communication channels? Further, are both channels needed or can one channel be used for a project-specific communication protocol?

(2) Is my assumption correct that even when using the Thingy:91 X with full features (Cellular, Wifi and Bluetooth active), the nRF5340's "GPIO" pins connected to P9 and the nRF9151's "TRACE" pins, are fully available for project-specific extensions? E.g. adding a MCP2515 CAN controller? In other words, these four pins are NOT needed for communication between the nRF5340 and the nRF9151?

Best regards,
Michael

  • (1) How is communication implemented between the nRF5340 and nRF9151? I noticed that the schematic defines two UART connections between the SoC's, VCOM0 and VCOM1. Are full Cellular modem features on the nRF5340 available through these communication channels? Further, are both channels needed or can one channel be used for a project-specific communication protocol?

    It should be using UART with the connectivity bridge application running on nRF5340. One of the channels is used for modem trace by default I think.

    (2) Is my assumption correct that even when using the Thingy:91 X with full features (Cellular, Wifi and Bluetooth active), the nRF5340's "GPIO" pins connected to P9 and the nRF9151's "TRACE" pins, are fully available for project-specific extensions? E.g. adding a MCP2515 CAN controller? In other words, these four pins are NOT needed for communication between the nRF5340 and the nRF9151?

    Are those the pins used for modem trace by default? Could you show me for example a screenshot?

    Best regards,

    Michal

  • It should be using UART with the connectivity bridge application running on nRF5340. One of the channels is used for modem trace by default I think.

    So, one channel is used for communication/operation, and the other is used for modem trace, which is some debug logging? Can the modem trace channel be deactivated, leaving the connection available for project-specific communication?

    Further, can the connectivity bridge be combined with project-specific code?

    These are the pins I would like to use for an external SPI device:

    And these are the VCOM / UART connections between the SoC's:

    Best regards,
    Michael

  • Hi Michael,

    Thank you for your patience with this. I have started to look for some answers to your questions but it is taking some time.

    I will try to get a proper reply to you on Monday.

    Best regards,

    Maria

  • Hi Michael,

    puz_md said:
    So, one channel is used for communication/operation, and the other is used for modem trace, which is some debug logging?

    If you're asking what the modem trace is, the answer is that it is the logs from the cellular modem. See this documentation for more info.

    My apologies if I misunderstood your question.

    puz_md said:
    Can the modem trace channel be deactivated, leaving the connection available for project-specific communication?

    I haven't found an answer to this yet.

    puz_md said:
    Further, can the connectivity bridge be combined with project-specific code?

    Yes.

    Best regards,

    Maria

  • Hi Maria,

    thanks for looking so deeply into my inquiry!

    And please don't forget my main question, which is whether the pins mentioned above are freely available (to connect a SPI CAN controller) in the intended nRF5340+nRF9151 setup.

    Best regards,
    Michael

Related