BlueNRG-M2SP – Unable to detect firmware or device via BlueNRG-GUI after flashing DTM project

[KoroshSF]

Hello,

I am using a BlueNRG-M2SP module mounted on my own custom PCB. I programmed it using the STSW-BLUENRG1-DK package and flashed the DTM / UART project to check basic functionality and enable advertising.

The project runs correctly in Debug mode, reaches while(1), and no HardFault occurs. I configured the Symbols as follows:

• HS_SPEED_XTAL = HS_SPEED_XTAL_32MHZ
• LS_SOURCE = LS_SOURCE_INTERNAL_RO
• SMPS_INDUCTOR = SMPS_INDUCTOR_NONE

UART is connected via DIO8 (TX) and DIO11 (RX) to a USB-to-TTL converter. However, when I open the COM port in BlueNRG-GUI, I get:

• No device detected
• No firmware detected on the motherboard

Because this is a custom PCB and not an ST evaluation board, the “motherboard firmware” message is unclear to me.

Could this issue be related to:

• The type of firmware (DTM project)
• UART configuration
• Clock / power / hardware setup
• Or BlueNRG-GUI limitations with custom boards?

I have also attached some photos and a short video of the setup and programming steps, which I believe may help clarify the issue.

Any guidance on how to at least verify that the BlueNRG-M2SP module is working properly would be highly appreciated.

Thank you.

[JW_it]

I will take a shot since BlueNRG responses (at least for the BlueNRG-LP) tend to get sparse responses.

• the “motherboard firmware” message is unclear to me.

My assumption is: This message is because BlueNRG-GUI is expecting an evaluation board with the ST-Link bridge MCU firmware (which I am assuming you do not have on your custom board).  So *I believe* this message is not referring to your custom firmware, rather the firmware associated with ST Link bridge MCU.    

[JW_it]

I retract my earlier response, which I believe was utter rubbish (I am sorry). 

Here is why:

I tried the following basic experiments using BlueNRG-LP EVAL board and my Nordic nRF5340-DK (as I do not have a BlueNRG-MS2 chip)

• The nRF5340-DK board loaded with firmware that does not understand HCI commands using BlueNRG GUI  (fails as expected with No firmware detected on the Motherboard etc.)  
• The BlueNRG-LP eval board loaded with **DTM_basic** firmware using BlueNRG GUI loaded (no error message)
• The BlueNRG-LP eval board loaded with **Beacon** firmware using BlueNRG GUI loaded (fails with No firmware detected on the Motherboard etc.)

This tells me the "No firmware detected...." message (at least) appears when the loaded firmware is not the expected firmware.  I might suggest, if you haven't tried already, to use the DTM_Basic example firmware instead (which responds for me on my BlueNRG-LP.    I think the ST Link MCU firmware is a red herring.

[JW_it]

I will end my spamfest with a suggestion you have likely already tried:

On BlueNRG GUI Menu: Settings->FW Stack Version->BlueNRG-MS Fw vX.X (whatever version you are using on your BlueNRG chip)

-eom-

[Dominique FOLLEZOUR]

Hello

 

As your custom PCB use same UART pinning than default FW, could you perform basic tests, have you try to flash the DTM_UART.hex from BlueNRG-1_2 DK 3.2.2\Firmware\BLE_Examples\DTM\STEVAL-IDB008V1M ?

If still not functionnal could you try the BLE_Chat_Server.hex from BlueNRG-1_2 DK 3.2.2\Firmware\BLE_Examples\BLE_SerialPort\STEVAL-IDB008V1M and check if device is visible for BLE debug App and logs visbile (tera term)

Br

Dominique