3 years ago.

DISCO_L475VG_IOT01 ble not working!

Good day, I have two boards DISCO_L475VG_IOT01 and one is visible through bluetooth low energy scanners, while the other isn't. I did the same exact steps and used the same program so I cannot phantom what may be wrong - hoping it's not the board itself. The one who isn't ble-scannable is still working if for example I read the sensors values, so the problem may be related only to bluetooth low energy. Is there a way I can understand If there's something wrong? I'm working on Ubuntu 16.04 64 bit. Thanks in advance,


Hi Chiara,

It's not clear what program you are using for test, but please try running a few of our BLE canned examples available here (these support your board):

Each example has a Markdown file that explains what the program does and how to check that it's operating properly.

If you don't see the expected output from one of your two boards, please turn to ST Microelectronics for assistance in troubleshooting the board. It might be broken.

-Ralph, Team Mbed

posted by Ralph Fulchiero 03 Jul 2018

I indeed used the provided examples, but not sure why it doesn't always start working right at the beginning. Is there an "on/off" button or procedure for it to be working? I don't think so, but to be honest, I noticed that when I flash the device with the bin, it doesn't work right away - with the LED and the Battery Level examples. I'm unable to find the device with ble scanners. After I press the reset and user buttons the D6 led starts blinking and then everything works fine. But the other board I have - same model - starts blinking from the start after the flashing. In conclusion, I don't think it's broken, but I'd like to know what I'm doing wrong eventually. Thank you so much for the assistance. I hope I explained myself well, Regards

posted by Chiara Simoni 13 Jul 2018

1 Answer

3 years ago.

Hi Chiara,

Naturally if the boards are configured identically they should perform the same when programmed with the same software! It appears that one might not be observing the reset that would be issued after programming. Perhaps the two boards have different ST-LINK interface firmware? You can check the firmware version from the "details.txt" file when it mounts on your host system. You can get the latest firmware here:

If both boards have the same interface firmware, you will have to consult with ST as to what could be causing the difference in behavior.