Originally developed on SDK3.10, basic functions, update to SDK3.20,
SDK3.20 exist the following bug
1, the TC Link Key after more than 112, the coordinator will collapse, cause the reason was that the SDK3.20 NV FLASH RAM can only use two sectors
2, if the target device is based on the silabs, CC2652 command, to the hair band APS Ack request silabs zigbee node first reply Response or other application layer packet, then reply ASP Ack, CC2652 may misjudge the APS Ack timeout, and this misjudgment is only in the case of multilevel routing,
3, the Group table in NV RAM cannot save correctly, this bug TI has given official patches,
SDK3.30 solved bug1 and bug2, but out of the new bug again,
1, the SDK version before 3.20, the Associate List and TC Link Key Table in NV in RAM address, separate accounts for a NV RAM block, that is to say, each record is exclusive a NV record entries, but may be a protocol stack of TI team was too careless, the two tables in the store and restore the moth, I in E2E solution are given,
2, the Group can not save NV RAM table, is in their SDK 3.30 has hair version of the case, I found them, so SDK3.30 continue to use egg pain patch,
3, parsing ZCL Config Report command, bool type 0 bytes of data fields, but TI a byte code when jumping, TI all versions of the protocol stack has this bug, there have been N years, TI let developers to repair itself in the code, the key is TMD this error for many years, haven't was found,
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
About our universal gateway, the first to support 3.0 protocol zigbee, TI's native protocol stack, send and receive commands incredibly don't support manufacture code command, before docking Cetus and millet peripherals, found myself changed ZCL code, can perfect support with manufacture code command,
Followed by zigbee 3.0 net management, according to my own understanding, zigbee 3.0 there are three APS layer encryption Key, respectively is the Default Key, TC Link Key (or Verified Key), and install code Key,
Equipment into the net, the coordinator (also called trust center) to access devices send NWK Key, in the zigbee HA, received the NWK Key, even if the net, in 3.0, the zigbee added Verify this process, the Key in Verify the Key to obtain a unique TC Link Key, in order to be truly, TC Link Key can be classified as zigbee 3.0 soul,
TC Link Key has several useful: 1, if after NWK Key change again, the coordinator will use the TC Link Key to encrypt NWK Key, to the target device, 2, TC Link Key can be used for APS layer encryption, unlike NWK Key, TC Link Key only the coordinator and the target node know, used to encrypt some private information, such as OTA upgrade of packets,
CodePudding user response:
Cc2530F256 excuse me whether also supports zigbee 3.0?CodePudding user response:
The