conflicting Nordic Dk with Texas programmer ?

Our product consists of a Texas MSP430 and a Nordic nRF52832 Chip, with serial/UART between

for MSP programming, debug and development : I'm using the official TI MSP-FET Flash Emulation Tool (USB device)
for Nordic : I have a nRF52DK-52832 (PCA10040), several 52840 dongles (PCA10059) and the final hardware with 52832

When the Texas MSP is connected via USB most of the Nordic stuff is not properly working:
- It seems I can download code with Segger Studio into the PCA10040, but it crashes right after start
- I wonder why nRF Conenct for desktop lists the Texas MSP programmer as valid device
- I cannot use the 52840 dongle for Bluetooth with nrf connect for desktop, is just brings an error=-1

The MSP programmer works without problems, it can download code and debug - and when I pull it off my computer USB, all the Nordic things work again. Just plug it in - no need to start any session with Texas' code composer - Nordic tools are not working right.

Anyone experiencing a similar issue ? This is most annoying since I need to develop and work with both controllers

thanks for any advice, Matthias

  • Hi,
    Just want to clarify that I understand you issue correctly. 

    The issue persists regardless of what Nordic device you have connected to the computer as long as the Texas MSP is connected to the same computer via USB?

    So if you have the nRF52DK connected via to you computer and want to flash or debug on that device at the same time you have the Texas MSP is connected, then you are not able to successfully work with the Nordic devices?

    Regards,
    Jonathan

  • ..yes, it's exactly like this. It affects the PCA10040 nRF52DK, my 52840 dongles, and also the Segger J-Link plus I'm using for development. Regarding the 52840 dongles (I use them for sniffing and test) I really thought these were defective, even Nordic Germany sent me replacement modules, but now I guess its the same issue with the MSP programmer.

    The Texas software never shows the Nordic USB/programmer, but eg the nRF Connect for Desktop (BLE tool) lists the Texas programmer as valid hardware and I assume that some of the programming tools are using the wrong USB device path.

    I'm also using a simple (non-powered) 4-port USB hub but it seems to not matter which devices are connected to the hub and which are connected right to the PC USB ports.

    If you need some log files let me know..

  • Thanks for the clarification. 

    What OS do you run on you computer?

    And have you tested this on a different computer to see if it issue is happening on more than one setup? 

    Regards,
    Jonathan

  • I'm using Win10 - and it happens on both, my work and my home computer. A colleague of mine reports similar issues, he also uses MSP-Programmer and Nordic equipment.

  • Thanks, good to know. 

    I will try to replicate the issue, but might take some time, don't currently have a TI debugger at hand. Will update with any news or further questions. And feel free to share anything you might think is relevant. Not a issue we have seen before.  

    Regards,
    Jonathan

Related