1 of 1 people found this helpful
Are you sure you programmed the correct OTA project?
OTA updates on windows requires patience and persistence. You probably have a broken connection and that's why nothing's happening. Try:
- Removing the device and re-adding it. Rebooting the dongle won't hurt.
- Double clicking on the device before starting the update so that windows begins to interrogate the device. If it's pulling in service info, it's connected and the OTA should start. I'm hitting about 75% success rates using this approach.
- Hitting refresh in the last dialog you posted before and during the update. Sometimes that kicks the ota into action if it appears to hang.
- Turning off bluetooth on any nearby devices (tablets, phones, etc).
- Turning off the 'allow windows to turn off this device' feature for the dongle. I have been told that the dongle (or hub it's sitting on) can be shut down by windows in the background... WHILE you're trying to use it.
I *HIGHLY* recommend you set up a linux box/VM and play hidtool and gatttool. It won't let you update but you can talk to the device directly and see if the services/chars that you expect to be there actually are. It can also help identify timeouts that you might not be aware of.
Thanks for the response. I'll give your suggestions a try, I hope I will have better luck with that. I should also forgot to mention that I'm using the Broadcom based IOGear dongle GBU521, not sure how big of a factor that maybe.
But from your experience, it sounds like the OTA isn't really reliable which is a worrisome. I do like the idea of using the hidtool and gattool, hopefully that can help me develop a linux based OTA.
I try also to play with OTA, signing an OTA image, to put to my Android project etc.
I have found here helpful command as:
But if I do this on Windows (Win 7, 64bit - BTW: the path to this exe is not set in %PATH% - hard to specify path to exe) - I get this error:
"Broadcom Bluetooth profile pack for Windows (BTW) has to be installed."
What does it mean?
What to do?
I want to convert the generated FW BIN into a singed OTA image so that I can take it to res/raw in Android project.
Please, could you provide a bit more info how to put FW BIN to Android project (as local OTA file - I see it is supported but how to use?). Thank you.
In regards to the "Broadcom Bluetooth profile pack for Windows (BTW) has to be installed.", I have seen that error trying to run the WsOtaUpgrade.exe on a laptop that is using a non-broadcom device adapter. From what I can tell, it looks like you need to install the BTW (BlueTooth for Windows) from the following link for a broadcom device.
Doing a bit more searching, I found this link Interested in using Broadcom’s Windows stack for Windows 7?
Great, very appreciated.
Uppps, I had to buy something????
I need a BRCM BLE dongle on my Windows 7 laptop?
It looks like I am forced to waste my money:
Installing the BRCM SW - it hangs endless on "Detect Bluetooth Device" and it does not proceed.
Does it mean, just to convert an OTA.BIN into a ".signed" I have to buy and connect a BRCM BLE dongle on my laptop.\?
Why do I need HW just to convert a file?????????
Sorry, what should I say?
(it is not a nice way to generate business ... sorry, I could drop more words here, too ...)
From my understanding you only need the BTW and Dongle in order to do the OTA upgrade from Win7 to the device. If you want to do the conversion, I believe there is a document somewhere in the SDK for that. Or you can check this link: WICED Smart BCM92073X OTA Firmware Upgrade (1) and WICED Smart BCM92073X OTA Firmware Upgrade (2)
Why it is so hard to get such docs, links ...?
How have you found these?
This is exactly what I was looking for. Thank you!
Where is is the "table of contents" to find next time without to bother all?
BTW: it does not talk about that I have to purchase anything.
Really a need to buy something for my Windows 7 laptop?
BTW: if I would use my office laptop - is there a guarantee that the expected HW is inside?
(also running Win 7).
For this 5 minute task to convert just a file I waste meanwhile so much time ... (and get frustrated ...).
Let me try to address some of the topics that were presented in this thread throughout the evening.
Yes, the free Windows based OTA Client software we provide within the SDK requires a Broadcom BCM20702 based dongle. The BCM20702 is used in many of the low cost dongles on the market today, many of which can be easily found both online and at brick and mortar type retailers throughout the world.
The Broadcom "Bluetooth for Windows" (BTW) software that supports these dongles can be found online at Broadcom.com (shows up as one of the top results on Google). These are also the drivers that many of the BCM20702 dongle providers ship with their product.
When installing these drivers it is VERY important to first disable any internal Bluetooth radio that already exist on your PC. The install simply will not work if a BCM20702 based chipset is not found.
Once installed, reboot and plug the dongle in, then pair it with your PC using the Bluetooth Control provided in Windows. Once this process is complete, the Windows client should work.
OTA cannot be used for first time programming. It has to be the HCU UART as noted in posts throughout the site.
hThere are several OTA enhancements/improvements coming in SDK 2.2
There is an excellent Appnote here on Secure OTA: WICED Secure Over-the-Air Firmware Upgrade Application Note (SDK 2.x and TAG3 Board)
Secure OTA Requires the BCM20737 as it is the only device that supports RSA (Polar SSL library included in ROM), which is leveraged for "Secure" OTA.
In addition, for non secure OTA (supported on the 20736 as well) documentation, there are simple explanations within the headers of the source files provided. In addition, there is a Readme in the ota_firmware_upgrade\peerapps\windows\wsotaupgrade directory you will find helpful.
Yes, unprecedented growth this year within the community has made some of this information difficult to find on the website. As we are assuming 100%+ growth again this year, my plan for 2015 is to create a much more scalable information architecture across all of the community websites (including of course BLE) which will make much of this information front and center.
As a quick patch for the OTA related information, I created a new category for OTA and updated all of the Tags attached to this content as to enable better searching: WICED Smart Forums
Hopefully many of you will find this helpful.
Thanks for the clarification.
1 of 1 people found this helpful
Settle down Beavis, it's only $14 for the dongle: Plugable USB-BT4LE Bluetooth 4.0 USB Adapter for Windows and Linux PCs | Plugable
You can also use the (FREE) android app to flash OTA if you have a supported device, btw.
Trying to figure out a way to like and mark this one helpful 3x :-)
Sorry, what does it mean?
There is an APP which can convert BIN to signed OTA file?
I do want to do an OTA update or flash of my device. Instead:
I want to get the signed OTA image to my (the WICEDSense) App. It should come with the App, as this (FREE) App you have mentioned.
App should come with signed OTA embedded, so that all users and do this, not me.