This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OtaServer Unsupported Attribute Status code = 0x86

Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: UNIFLASH

Hi,

I’m using the SimpleLink SDK 5.20.00.52 do develop a ZigBee sensor that should use OTA.

So as the first step, I downloaded the zr_sw_ota_client and zr_ota_server examples. I build and run the examples on 2 LAUNCHXL-CC1352P boards.
Then I connect to the zr_ota_server with the Windows App OtaServer and pressing the left button on the board to join the ZigBee network.
Now both devices are in the same network and I can see the Node 0xA9EE under Pan 0x3075 in the Device List.
When I open the Node in OtaServer, I see 8 attributes and every attribute has the same error message: Unsupported Attribute (Status code = 0x86).
If I right click on the Node and select "Image Notifiy", nothing happens.

Does anyone have in idea, what I'm doing wrong?

Regards,

Thomas

  • Hi Thomas,

    Are both devices joining a third-party ZC or are the routers creating a distributed network?  I recommend starting with the zc_ota_server and zr_sw_ota_client to verify operation.  Make sure to erase all device memory to delete any saved NV memory before re-programming.  Also confirm through the terminal UI that the ota client device is the correct short address node as listed on the ota server.  Please review the Zigbee Over-The-Air Firmware Upgrade section of the Z-Stack User's Guide.  Do you have a Packet Sniffer set up so that you can review over-the-air packets?  Please be aware that the latest SDK version is the SIMPLELINK-CC13XX-CC26XX-SDK

    Regards,
    Ryan

  • Hi Ryan,

    thanks for information, it was very helpfull.
    Its now working.
    The problem was, that I didn't erase the full memory.
    After erasing the full memory with UniFlash and flash it again with the bim_offchip and zr_sw_ota_client, everything is working now.

    Thanks!

    Regards,

    Thomas