Skip to main content
kukushonok
kukushonok
Associate III
August 11, 2014
Question

Flash recovery

  • August 11, 2014
  • 14 replies
  • 2761 views
Posted on August 11, 2014 at 11:24

Hi,

I'm developing a device based on the BlueNRG. 

I worked on the support of flash BlueNRG from my firmware,  but during a flash error occurred (probably due to an incorrect program address). After flash failed BlueNRG does not respond, as in my firmware and through the RF MOTHERBOARD vers. 3.0 (BLUENRG_GUI.exe).

Is there a way to restore the firmware? 

Maybe can I download the firmware via JTAG?

Software engineer, Andrei Kukenov.

Regards. 

#recovery #flash #bluenrg #image
This topic has been closed for replies.

14 replies

Show previous replies
Scott Löhr
Scott Löhr
Senior III
January 23, 2015
Posted on January 23, 2015 at 19:46

I would love to try that experiment - may I please have a link to where to find the v6.3 images?

marchese.graziella
marchese.graziella
Visitor II
January 26, 2015
Posted on January 26, 2015 at 09:29

Hi,

Please, Can you any feedback about the questions:

which VCOM firmware have you loaded on the motherboard?

Assuming that the fw image ''bluenrg_6_4_Mode_2-16MHz-XO32K.im''g has been correctly loaded (as showed in the GUI), have you tried to run basic command as GATT_INIT, GAP_INIT with the GUI?

Are they run with success? (Check the HCI_COMMAND_COMPLETE Status =Success)?

If yes, the BlueNRG fw upgrade should be ok, so another test that you could to do is to set the TX power as follow:

ACI_HAL_SET_TX_POWER_LEVEL(0x01,0x04) and verify if the device is correctly advertising or not.

The Tx Power settings address an issue which is documented in the device errata (see section 1.3). You can download the document at the following link:

http://www.st.com/st-web-ui/static/active/en/resource/technical/document/errata_sheet/DM00133230.pdf

Regards,

Graziella

Scott Löhr
Scott Löhr
Senior III
April 3, 2015
Posted on April 03, 2015 at 02:01

Wow, what a long strange trip it is learning to use the BlueNRG.

I have finally realized why it seemed that upgrading from v6.3 to v6.4 ''looked'' to break the advertising (and thereby, the ability to be connectable at all). The hint came from following this post:

https://my.st.com/public/STe2ecommunities/interface/Lists/Low%20Power%20RF%20Solutions/Flat.aspx?RootFolder=/public/STe2ecommunities/interface/Lists/Low%20Power%20RF%20Solutions/How%20to%20set%20a%20specific%20channel%20for%20advertising&currentviews=24

So, as I was fast and furiously using ST sample apps to establish a proof-of-concept project running by BlueNRG, I (like most of the ST sample code) was not checking return values. Since ST chose to REMOVE the HCI set advertising from v6.4 (and ONLY support ACI set discoverable), my call to hci_le_set_advertising_parameters() began to fail after the f/w upgrade, but since I had not been checking return values, it ran, and the few places that I could verify BlueNRG was still alive, like read board address, I could tell that the f/w upgrade did not kill the BlueNRG, but just seemed to break its discoverability.

marchese.graziella
marchese.graziella
Visitor II
April 3, 2015
Posted on April 03, 2015 at 09:42

Hi Smith,

For a complete list of supported ACI & HCI APIs refer to

file:///C:/Program%20Files%20(x86)/STMicroelectronics/BlueNRG%20DK%201.6.0/Docs/bluenrg_fw_stack_release_notes_html/bluenrg_stack_apis_v6_4_vs_v6_3.html

 (under folder  ..\Docs\bluenrg_fw_stack_release_notes_html\bluenrg_stack_apis.html)

Regards,

GM

Terms & ConditionsAccessibility statement