Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

Smart Bluetooth Forum Discussions

MiTo_1583836
Level 5
50 likes received 25 likes received 10 likes received
Level 5

Is there any technical limitations that would prevent the OTA update to happen between two BCM20737 modules?  I don't see an issue as long as the BLE application is small enough to shelter a copy of the firmware used for the OTA in RAM and the OTA protocol is implemented properly in the module (GATT etc...).

I may have a BCM20737 module in the field that receives over PUART a firmware that would be used to do an OTA update of sensors (peripheral BCM20737 modules). The central would behave in the same manner as the smartphone application that initiate OTA update.

Let me know if you think there are limitations,

Thank you!

0 Likes
1 Solution
MichaelF_56
Moderator
Moderator 250 sign-ins 25 comments on blog 10 comments on blog
Moderator

mickael.toumi_1583836​ and user_462265863

I spoke with the developers and they feel that what you've described should work just fine.

View solution in original post

0 Likes
2 Replies
Anonymous
Not applicable

I have a similar task. I am using BCM20736 modules. I would program module A (first BCM20736 module) with firmware via the uart. I would then like to have it (module A) replicate its firmware OTA to a second Module B (also a BCM20736). Module A would only update a second device when instructed. Is there any limitation in "replicating" firmware OTA  between BCM20736 modules? All of this would initially not be using the secure process.

Thanks

0 Likes
MichaelF_56
Moderator
Moderator 250 sign-ins 25 comments on blog 10 comments on blog
Moderator

mickael.toumi_1583836​ and user_462265863

I spoke with the developers and they feel that what you've described should work just fine.

0 Likes