[NUCLEO_F411RE]: Some BLE examples doesn't work with the X-NUCLEO BLE shield

[pan-]

• Description: The following BLE examples doesn't work on the NUCLEO_F411RE with the ST shield:
  • BLE_BatteryLevel
  • BLE_Button
  • BLE_EddystoneObserver
  • BLE_EddystoneService
  • BLE_GapButton
  • BLE_HeartRate
  • BLE_LED
  • BLE_LEDBlinker
  • BLE_Thermometer
    The cause of the failure is the use of an LED and the SPI1 in the same application. Even if the board define 4 LED, only 1 LED is actually accessible to the programmer and the LED line is shared with the clock line of the SPI1. Using both at the same time will cause failure regarding SPI communication and in this case prevent the application to actually work.
• Workaround: Remove the code related to the LED (including the declaration!), it is only use to show that the board is alive.

[apalmieriGH]

@pan- the X_NUCLEO_IDB0XA1 library page on mbed.developer.org warns about Arduino connector compatibility and describes the workaround. Should be added also on github ?

[pan-]

@apalmieriGH While the X_NUCLEO_IDB0XA1 warn about the Arduino connector, the F411RE page doesn't indicate that the LED can't be used if SPI1 is used at the same time.

I've found another issue regarding pin mapping of F411 and F401. In the datasheet, they are identical but they are declared differently in mbed.

[liuxinbai]

Any update for this issue? we test the BLE_HeartRate_IDB0XA1, generate the bin by compiling with online compiler, found it work well. no LED1 and SPI1 conflict issue be found as your description. But faild when use the mbed-os-example-ble-xxx.
So, would like to know if it is really HW issue or it belong to SW issues since mbed-os 2 work well?

Actually we got a project by using X_NUCLEO_IDB0XA1 + STM32F401RE + mbed os 5.4, hope you guys can help to find the root cause, and fix it then.

Best Regards,
Xinbai

[jmjobin]

How do you test your mbed-os-example-ble-xxx? And what mbed-os-example-ble-xxx?
I had problem too using the mbed-os-ble-Thermometer. The Nordic app in Android expect to receive a "Indication" but the mbed-os-.... send a"Notification" it work making some changes in the HealthThermometerService.h.
I am using the same device as yours X_NUCLEO_IDB0XA1 + STM32F401RE.
Do not know if this could help.
jean-marc

[liuxinbai]

Hi Jean-marc Thanks alot for your kindly information. I tested the Battery and HeartRate, none of them work will(the Device can not be found when adverting ) with mbed-os-5.4.0. May I know which OS version in your Thermometer example. And I use STM32 BLE Profiles as a test tool. Best Regards, Xinbai

[jmjobin]

Hello :-)
I use mbed on-line compiler.
Excellent Xinbai........ Great stuff.
The mbed-os on revision says tag:mbed-os-5.4.2 since I updated it recently... But never tried to compile and flash again.
You are right this revision does not work...
I revert back to 5.3 and it works.
Thank you Xinbai :+1

[jmjobin]

Post Scriptum: If this does help others as well. The revision 5.4.2 works on Nordic nRF52DK.
jean-marc

[liuxinbai]

@jmjobin Thanks a lot for your confirmation, the issue more like a SW bug in mbed-os-5.4. it's very helpful. Best Regards, Xinbai

[pan-]

@liuxinbai The bug described here is specific to the NUCLEO_F411RE and it's IO mapping in mbed OS. I would be surprised if the mbed OS 2 example work. On the other hand, the NUCLEO_F401RE is not impacted by this shared I/O issue.

@liuxinbai @jmjobin I've found two bugs affecting the X_NUCLEO_IDB0XA1 under mbed OS 5.4:

• The link to the ST library is outdated, I'm not sure of how it happens, I've merged an update of this reference one month ago (Update reference to the ST shield library #54) and somehow it was reverted.
• Mbed OS 5.4 has improved I/O throughput on STM boards. The side effect is an incorrect reset sequence of the X_NUCLEO_IDB0XA1 module (it is happening too fast).

We're working to deliver a fix to both of these issues in a timely manner.

[liuxinbai]

@pan Thank you very much, waiting for your good news.

[jmjobin]

Ready to test it :-)

[pan-]

@liuxinbai @jmjobin the problem encountered should be fixed now.

[jmjobin]

I tested now and still not OK... But strangely the OS rev. is still 5.4.2
What did you fix? Maybe I am not making the correct update!

[pan-]

@jmjobin Could you detail your setup: compiler used, example tested, sniffer used and revision of the example, mbed OS and at shield library ?

The reference to mbed OS has been updated to 5.4.2, previously these examples were using mbed os 5.4.1 and a bug has been fixed in the ST BLUENRG library. This library has been updated as well.