Wireless MCUのトピックRe: advertisement configuration at runtime using FRDMKW36

advertisement configuration at runtime using FRDMKW36

thailivenkatesh — Fri, 05 Nov 2021 12:24:05 GMT

trying to update the advertisement scanning at runtime it is working fine but when i try to update multiple time it is updating only few times not consistently updated . Can anyone please help me to solve this issue. Below is the code return in serial manager.c file. sending command as #ccdas_123 from iot tool box. This value i am storing in hardware parameters and when i reset updated value is stores in advertisement structure. But hardware structure is not updating sometimes.

serial_t *pSer = &mSerials[0];
uint16_t idx;
idx = pSer->txCurrent;
(void)NV_ReadHWParameters(&gHardwareParameters);//venk

//initially default value loaded if eeprom write new updated else condition
if (!gHardwareParameters.devidset)//default nonzero
advScanStruct[2].aData = (uint8_t*) "cdas-123";//default

else{
advScanStruct[2].aData=gHardwareParameters.device_id;}
//idx points to current txQueue buffer
if(idx==0)
idx=5;

else
idx = pSer->txCurrent;

//current buffer loaded to temp value
temp_id=pSer->txQueue[idx-1].pData;//venk
temp_id2=temp_id+9;
temp_id3=temp_id+9;

if(((*temp_id2==' ')&&(*++temp_id2=='#'))||((*temp_id3=='#')&&(*++temp_id3=='c')))
{
gHardwareParameters.temp_id1=temp_id2;
if(*gHardwareParameters.temp_id1=='c')
{
gHardwareParameters.temp_id1=gHardwareParameters.temp_id1+1;
}

else
{
gHardwareParameters.temp_id1=gHardwareParameters.temp_id1+2;
}

gHardwareParameters.device_id=(uint8_t*) (gHardwareParameters.temp_id1);//venk
advScanStruct[2].aData=gHardwareParameters.device_id;
gHardwareParameters.devidset =1;
(void)NV_WriteHWParameters(&gHardwareParameters);//venk

}

Re: advertisement configuration at runtime using FRDMKW36

nxf56274 — Mon, 08 Nov 2021 02:33:53 GMT

Hi,

When you try to update the scanning data, please firstly stop the scanning. After the data is written, start scanning. Don't modify the scanning data when your mcu is scanning.

Have a great day,

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 days after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: advertisement configuration at runtime using FRDMKW36

thailivenkatesh — Mon, 08 Nov 2021 05:26:38 GMT

Hi,
Thanks for your support and I followed your solution but still facing same problem.

Re: advertisement configuration at runtime using FRDMKW36

nxf56274 — Mon, 08 Nov 2021 05:52:27 GMT

Hi,

You want to use iot toolbox to send the new device name for mcu to scan? Am I correct? Where do you put the stop scanning function?

Re: advertisement configuration at runtime using FRDMKW36

thailivenkatesh — Mon, 08 Nov 2021 07:28:32 GMT

Hi ,

Yes I am sending device name from IOT tool box to update the advertisement structure and did not use any stop scanning functions. but i searched for Gap_StopAdvertising() only declaration is available in gap_interface.h file but no definition for it .Please suggest me any solution for it.

Re: advertisement configuration at runtime using FRDMKW36

nxf56274 — Mon, 08 Nov 2021 07:45:54 GMT

Hi,

When you send the new device name to mcu, you firstly write it into memory. And then make mcu disconnect from the phone using 'Gap_Disconnect'. Read the adv structure from the memory. Use 'Gap_SetAdvertisingData' to set the adv data. Use 'App_StartAdvertising' to start the adv again.

Re: advertisement configuration at runtime using FRDMKW36

thailivenkatesh — Mon, 08 Nov 2021 12:24:37 GMT

HI,

I followed your procedure it is working better than previous code but when I try to change device name it is updating ok for 4 times when I update 5th time it is not updating or even when I reset the mcu it is updating 2 times again showing previous updated value and I am not understanding why there is inconsistent in updating the value or problem with proper reading or writing to ghardware structure.

Re: advertisement configuration at runtime using FRDMKW36

nxf56274 — Tue, 09 Nov 2021 03:22:54 GMT

Hi,

There are too many points you need to notice. So I wrote this program. Input '#' and after this char, it is your device name. For example, '#asdf', the adv name will become 'asdf'. Pay attention that the device name should smaller than 6 byte. This is due the limit of adv packet length.

I do not write adv name into memory. You can add it by yourself. The code is added at 'BleApp_ReceivedUartStream'.

Re: advertisement configuration at runtime using FRDMKW36

thailivenkatesh — Tue, 09 Nov 2021 07:05:55 GMT

Hi,

Thank you very much for your support now it is working fine and it is updating multiple times consistently.