Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I went through the steps in this post (WICED Smart Bluetooth Forums ) to change my BLE Mac address to a custom value on production programming. However I am trying to discover if there is a way I can read the flash memory across the UART programmer pins so I can check if it has already been programmed with an expected mac address, and if so, to use the same one. So far out of the Zipped tools in that post, it doesn't appear to have any resources to do that. I also wasn't able to find a way to read flash memory through the WICED ide. Any suggestions?
When you call that function, the blecm evt handler will be triggered and the device address will be reported in the event handler. If you enable the print logs, you can see the device address being printed.
Have a question on BD Address, during production if we assign a static MAC ID (programmed through tool or using HCI command 10 FC ') will the address persisted if we upgrade the application using minidriver ? Do we need to write the MAC ID again after upgrading the application (CYBLE-013025-00)