Why do I use the reference design DA14580_DialogBeacon_3.40.6, try to discover a problem according to UM-B-019_DA14580_Beacon_Reference_Application_v1.2 this document to debug. My method of operation according to the document in the tenth chapter of Dynamic advertising data, it was found not to achieve dynamic advertising data. I look at the program behind this discovery APP_RESTART_ADV_TIMER app_timer_set (APP_RESTART_ADV_TIMER, TASK_APP, timer_ticks) unused. Further analysis app_adv_undirect_complete (uint8_t status); has not been called. Actual use does not implement Dynamic advertising data.
I probably did not notice where I hope Dialog technical support can help analyze, thank you！
Keywords:
Device:
Hi sam,
The document indicates that in order to update the data dynamically you should set one of the two following definitions, either the CFG_CONNECTABLE_ADV_MODE or the CFG_DYNAMIC_BEACON_DATA, have you define the latest ? In order to update dynamically the advertising string the device will read the channel 1 on the adc and populate the minor and major values with that data, the reference code provides just the infastructure to read the adc.
Thanks MT_dialog
Hi MT_dialog,
Two places you mentioned, I have before in document UM-B-019 to do inside, CFG_DYNAMIC_BEACON_DATA and CFG_CONNECTABLE_ADV_MODE defined, and in this function app_adv_func there adc_read_P01_channel () assumes a parameter: 0xa569. The problem is that I actually see is not updated, and I did not test the simulation.
Hi sam,
You mean that if you define the CFG_DYNAMIC_BEACON_DATA and you put some dummy values instead of reading the adc you dont get the values on your phone ? I just tried it out with a couple of variables increasing everytime the string is updated and seemed to be working ok. Can you please remove the sleep configuration and place some breakepoints to line 610 where the major and minor values are populated and at the app_restart_adv_timer_handler() function and check if they hit. Also the beacon has various configurations regarding the dev kit or reference design it runs so please check the configuration of the fw for the device. You can find the configuration in the da14580_config, at the moment i am executing the firmware with HW_CONFIG_BEACON_REF selection in order for the other defines (CFG_DYNAMIC_BEACON_DATA) to apply.
Thanks MT_dialog
Thank MT_dialog,
finally able to achieve normal Dynamic advertising data, and recommendations based on your reference, I noticed that my two problems,
1.CFG_EXT_SLEEP before me this definition, cause my simulation time, app_dialog_beacon_proj.c function only of app_adv_func call time; later modified to be able to after #undef been updated.
2. I define variables and did not achieve the changes pbeacon-> major value, followed by defining a global variable plus property __attribute __ ((section ( "retention_mem_area0"), zero_init)) you can normally see on your phone data changes.
Hi sam,
Regarding the CFG_EXT_SLEEP this definitions sets the default sleep mode of the beacon, as all of our reference designs you wont be able to debug while being in sleep mode, you will have to either remove the sleep by #undef CFG_EXT_SLEEP or stop the debugging in order to see your device advertising.
Thanks MT_dialog