Hi All,
I am using "FRDM-KW38" in project "adv_ext_peripheral_freertos",
I need to use normal advertising but not extension advertising when KW38 directly after finish init .
but I have a tricky issue, KW38 only advertising maybe 4 seconds and it will disable advertising by itself.
Is there any config I miss?
I enable advertising like below:
Solved! Go to Solution.
Hello Adam,
Hope you are doing well.
Could you please help us with more details about your application? Is your application intended to use only "normal" advertising? If so, please take a look at the Heart Rate Sensor (hrs) or Temperature Sensor (temp_sens) example projects inside the SDK, these examples could be used as a base to develop your application, they are highly configurable, allowing the user to set some relevant parameters and change the information being transmitted
Also, please consult the Bluetooth Low Energy Application Developer's Guide. You can find this file inside KW38 docs folder > wireless > Bluetooth.
KW38 documentation can be found in the MCUXpresso SDK Builder when downloading the corresponding SDK:
Regards,
Eduardo.
Hello Adam,
Hope you are doing well.
Could you please help us with more details about your application? Is your application intended to use only "normal" advertising? If so, please take a look at the Heart Rate Sensor (hrs) or Temperature Sensor (temp_sens) example projects inside the SDK, these examples could be used as a base to develop your application, they are highly configurable, allowing the user to set some relevant parameters and change the information being transmitted
Also, please consult the Bluetooth Low Energy Application Developer's Guide. You can find this file inside KW38 docs folder > wireless > Bluetooth.
KW38 documentation can be found in the MCUXpresso SDK Builder when downloading the corresponding SDK:
Regards,
Eduardo.
Hi @EduardoZamora ,
Thanks for yout suggestion.
I will taks a look HR and TMP project.
Regards,
Adam
Hi ,
I don't know why, but after I create a periodoc timer before enable adv this issue will not happen again.
Maybe it need delay?