Dear Dialog,
We are having a custom bluetooth tags, to which, we are flashing the software through OTA. But, one of the tags is advertising with two "USER_DEVICE_NAME"s. Suppose, if the tag names are TAG_NAME_1 and TAG_NAME_2. This specific tag is advertising with TAG_NAME_1 for 10 seconds and TAG_NAME_2 for 10 secs. but "CFG_NVDS_TAG_BD_ADDRESS"s are same for this tag, when it is advertising with two different names. We are unable to find root cause for this issue. Please let me know the possible reasons for this behavior. Please let me know, if you need more information.
Thanks & Regards,
BleBot.
Device:
Hi BleBot,
Could you please rephrase your question and try to describe what you are trying to accomplish? I am not able to understand you question, please try to clarify it.
Thanks, PM_Dialog
Hi PM_Dialog,
We have ten BLE tags with us. We are flashing the code into these ten tags through Over The Air (OTA) update. We are flashing each tag with its own binary file. The code, which we are flashing to these tags, have the same functionality. Only difference is, each tag has its own "MAC ID", which is hard-coded. When we flashed these ten binary files to ten tags, nine tags are working as expected. But, one of these tags is advertising with two device names.
Before, we flashed these tags by using OTA, all of the tags are flashed with a single binary file and through JTAG. At this stage, all of the tags are having MAC_ID as "DE:AD:BE:EF:00:01" and all of the tags are having the name "TEST_TAG". After this, we flashed all the tags by using OTA as mentioned in the first paragraph. At this stage, all of the tags are having different MAC IDs and they start from "DE:AD:BE:EF:00:01" and end at ""DE:AD:BE:EF:00:10" and all of the tags are having the name as "PROTO_TAG". After this, all of the tags are advertising with name "PROTO_TAG" and their respective MAC IDs. But tag with MAC_ID "DE:AD:BE:EF:00:01" is advertising with name "TEST_TAG" for ten seconds and "PROTO_TAG" for ten seconds. Can you help me in finding the root cause for this behavior?
Thanks & Regards,
Giri Prasad N.
Hi blebot,
The most possible reason is that the DE:AD:BE:EF:00:01 is cached from the SUOTA mobile application, so it takes a little bit time to update this binary image. Could you please use a sniffer in order to check if you are sending the “PROTO_TAG" and not the "TEST_TAG" device name in the first 10 seconds? If you are sending the correct device name, this means that the corresponding mac address is cached from the application, so the binary image is updated in the next application scan.
Thanks, PM_Dialog