This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP432P401R: Changed NPI in project_zero from UART to SPI

Part Number: MSP432P401R

Hello.

First of all, the Hardware is as follows.
MSP-EXP432P401R (MSP432 LaunchPad)
LAUNCHXL-CC2650 (SimpleLink CC2650 BoosterPack)

We want to change the NPI in project_zero from UART to SPI and check the BLE operation.
Then, we are proceeding with the next step and have completed Step 3.

Step 1:
Import project_zero in CCS, build and run it, and BLE is working. (The NPI is still UART)
Step 2:
Changed the NPI on the CC2650 side to SPI.
(Based on the simple_np project, select FlashROM_SPI in the build configuration and run the build.)
Step 3:
I wrote the above Firmware (simple_np_cc2650bp_app.hex) to the CC2650. (Use Flash Programmer2).
Step 4:
In CCS, import project_zero and change the NPI on the MSP432 side from UART to SPI.

Q1:
Is there any mistake in the above procedure?

I have a problem in this Step 4, please tell me how to solve it.

Q2:
In CCS, when you import Project Zero, you will see the following source files.
Board.h
main_tirtos.c
MSP_EXP432P401R.h
MSP_EXP432P401R.c
platform.h
platform_msp432p401r.c
project_zero.c
project_zero.h
If you have made any changes to the above File, those changes will take effect when you build it.
However, changes made to source files other than those listed above will not be reflected.
For example, defining "NPI_USE_SPI" in C:\ti\simplelink_sdk_ble_plugin_3_20_00_24\source\ti\npi\npi_data.h does not take effect.

What steps do I need to take in CCS to make my changes take effect?

Q3:
I cannot find npi_tl_spi.h and npi_tl_spi_m_simplelink.c under C:\ti\simplelink_sdk_ble_plugin_3_20_00_24\source\ti\npi.
Can I download these from somewhere?(Is there a sample code?)

Best Regards.

  • Hey Hitoshi,

    The SDK plugin is based on an old version of the BLE stack. For this reason, we no longer recommend using this for new designs. I would take a look at using the CC2640R2 or the CC26x2.

  • Hi.
    Thanks for the reply.

    Does this mean that using project_zero (CC2650 BoosterPack - MSP432 LaunchPad) with SPI communication is unsupported and not recommended?

    We want to use SPI communication instead of UART to verify BLE operation.
    I thought that using project_zero as a base would be the quickest way to check, but it's not?

    Is there any sample software that can work with SPI and verify BLE operation?
    If not, what is the best procedure to follow?

    Best Regards.

  • Hey Hitoshi,

    If using a CC2640R2 or CC26x2, you can download the full SDK and start from there (where you will find project_zero and simple_peripheral). To be clear, I would not recommend using the ble_plugin SDK and would recommend using the full SDK for these devices.

    Here's the link to the SDKs:

    CC2640R2 SDK

    CC26x2 SDK

    Are these valid options for you? If not, we can discuss further.

  • Hi.
    Thanks for the reply.

    According to the customer's intentions, the hardware is decided as follows.
    ・MSP-EXP432P401R(MSP432 LaunchPad)
    ・LAUNCHXL-CC2650(SimpleLink CC2650 BoosterPack)
    Then we need to change the NPI from UART to SPI.
    How should I proceed in this case?

    Also, I found the following information in the support forum.
    e2e.ti.com/.../msp432e401y-ble-plugin-using-spi-between-msp432e401y-and-cc2640r2f
    If the above measures are implemented for the current hardware and software, will it be possible to do what we want to do?

    Best Regards.

  • Hey Hitoshi,

    It is certainly possible. However we don't have an example out of the box. Essentially, I would recommend the customer download BLE-STACK-2-X (rather than the BLE SDK plugin). The customer can start by using the simple_np (network processor) example and define NPI_USE_SPI after configuring the pins correctly.

    Since we're essentially rebuilding the ble_plugin example, there may be some modifications and firmware required on the MSP side to talk to the CC2650 example as that will not be available out of the box.