Polling has stopped after upgrading NXP_SDK stack from sprint27 to sprint38

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Polling has stopped after upgrading NXP_SDK stack from sprint27 to sprint38

472件の閲覧回数
kaushalpatel
Contributor I

Hello All,
We are using "Zigbee_Smart_Energy_Hostprocessor_SDK".

Previously, we used the sprint27 release in our product and choose the "IPD NODE" on the NCP(Network Coprocessor) side. End Device is able to "poll" its parent for data. and it was working fine.

But after upgrading from sprint27 to sprint38. The End Device has stopped "polling".

In "APP_ZpsEventTask" API, flag "bIsPktPosted" turn to false. due to that polling has stopped.

"bIsPktPosted = ZQ_bQueueReceive(&sAPP_msgZpsEvents, &sStackEvent);  APP_ZpsEventTask".

Can you please suggest to me the required solution for the same?

Regards,
Kaushal Patel

0 件の賞賛
2 返答(返信)

467件の閲覧回数
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi @kaushalpatel,

I am assuming that you are working with the JN5169 Device.

Unfortunately, the ZSE is not currently supported, I recommend using the ZB3 stack instead.

Note: K32W061/41 or JN5189/88T are preferred for any new Zigbee®, Thread and Bluetooth® LE 5.0 design. No new software releases planned.

Regards,

Mario

0 件の賞賛

447件の閲覧回数
kaushalpatel
Contributor I

Hello @mario_castaneda 

Yes, you are right we are using the JN5169 Device and device is already in production. 

Can you please provide the guidance for the below queries?

Why Enddevice has stop polling after upgrading from sprint27 to sprint38?

 

Regards,

Kaushal Patel

 

 

 

0 件の賞賛