Member | Action | Date |
---|---|---|
|
Replied
to
OTA functionality in MGM210PA32JIA time duration for DMP example
Hi YK, Ok. And we are using the Z3GatewayHost server only. Please find the log details below: "T00000000:RX len 80, ep 01, clus 0x0019 (Over the Air Bootloading) FC 19 seq 3C cmd 05 payload[00 02 10 06 00 02 00 00 00 95 0A 00 00 3F F0 72 FB 00 20 76 BD 10 B5 00 23 01 E0 00 1D 5B 1C 9C B2 8C 42 04 D2 04 88 94 42 F7 D1 40 88 10 BD 00 20 10 BD DF F8 20 18 40 1A 0C 22 90 FB F2 F2 00 21 DF F8 18 08 10 E0 02 88 B2 F5 7C 4F ] The above is the log of the Z3GAtewayHost. Thanks and Regards, Sai Teja |
17 days ago |
|
Replied
to
OTA functionality in MGM210PA32JIA time duration for DMP example
Hi YK, Thank you for the response. I had arranged a debug and when tested, I am getting the following error, "Image block response error: Expected offset 0x0000961E, but got 0x000095A0. Ignoring". Due to this error, my OTA is taking a lot of time. So could you suggest any solution to the error? So that the OTA update will become at a higher speed. Thanks and Regards, Sai Teja
|
17 days ago |
|
Replied
to
OTA functionality in MGM210PA32JIA time duration for DMP example
Hi YK, Thank you for your reply. As you suggested I had checked both the examples are configured as the router devices itself. But I have a query that the DMP example, the stack works on a priority basis i.e., it shifts priority for Zigbee and BLE right, so I think that is causing a problem when I am trying to do OTA. Thanks and Regards, Sai Teja |
23 days ago |
|
Posted
OTA functionality in MGM210PA32JIA time duration for DMP example on
Zigbee Forum - Thread Network Forum
Hi , When I take a basic Zigbee Miniminal example for OTA it is taking around 5 minutes for 400KB, but the same when I try taking a Dynamic Multi-Protocol Light example it is taking me than 1 hour for 400KB. Can I know what is the reason for this. And is there any solution or method to make it speed. Here I am using simplicity studio V4 for Zigbee Miniminal with GNU ARM v7.2.1 with the latest EmberZnet 6.7.8.0 whereas for Dynamic Multi-Protocol I am using IAR ARM 8.30.1. Thanks and Regards, Sai Teja. |
23 days ago |
|
Replied
to
Zigbee(MGM210P022JIA) OTA Server/Client 0x96 Error
Hi YK, Thank you for your response. As you suggested I had referred to the above link but still I am facing the same issue of errors with the DMP example which has the inclusion of Zigbee+BLE. But if try updating only Zigbee example i.e, Z3Switch example its is working fine. But for DMP example it is throwing the following error: T0000053D:RX len 19, ep 01, clus 0x0019 (Over the Air Bootloading) FC 01 seq 0B cmd 03 payload[02 02 10 0A 00 02 00 00 00 B6 19 06 00 3F 00 00 ] T0000053E:RX len 19, ep 01, clus 0x0019 (Over the Air Bootloading) FC 01 seq 0C cmd 03 payload[02 02 10 0A 00 02 00 00 00 F5 19 06 00 3F 00 00 ] T0000053E:RX len 12, ep 01, clus 0x0019 (Over the Air Bootloading) FC 01 seq 0D cmd 06 payload[96 02 10 0A 00 02 00 00 00 ] Thanks and Regards, Sai Teja.
|
37 days ago |
|
Replied
to
Zigbee(MGM210P022JIA) OTA Server/Client 0x96 Error
Hi YK, Thank you for your response. As you had mentioned I tried the thread provided by you. But if am changing the slot 0 start address to 0 the device is not at all responding. Instead, when I am trying to update the OTA i.e., when OTA is starting at the first step the client is shutting off and I am getting error 66. The OTA is not at all starting itself. So could you suggest to me any other solution for OTA for the DMP example? Thanks and Regards, Sai Teja. |
42 days ago |
|
Posted
Zigbee(MGM210P022JIA) OTA Server/Client 0x96 Error on
Zigbee Forum - Thread Network Forum
Hi I am also facing an OTA Client update issue, i.e., s it is throwing me a 0x96 error from EmberZNet 6.7.8 SDK and GNU ARM v7.2.1 toolchain. I had followed all the steps mentioned in the "AN728: Over-the-Air Bootload Server and Client Setup" Guide. Gateway or Server-side Output Log: T000004C7:RX lens 12, ep 01, clus 0x0019 (Over the Air Bootloading) FC 01 seq 51 cmd 06 payload[96 02 10 0A 00 02 00 00 00 ] RX Upgrade sEndReq status:96 Client 0x3F3D indicated upgrade status: 0x96 I am using Local Storage Bootloader Type for my application. In my application, I have selected the Use slot in the OTA EEPROM plugin. And I selected it as Use First slot 0. I had even enabled the SOC Bootloader Support checkbox too. The OTA Start offset and End offset addresses are 524288 and 1048576 respectively. So in my internal storage bootloader, I have set slot 0 address as 524288 as start address and size(bytes) as 499712. In the map file of the client application, I found the address as 0x00082000 as internal storage and size as 0x7c000. I am attaching the error image for reference. Regards, Sai Teja.
|
43 days ago |
|
Replied
to
Toolchain issue for compiling dynamic multiprotocol application(ZIGBEE+BLE)
Hi YK, It means it is unable to open the PLATFORM_HEADER while using this version, So DEFINETOKENS is showing as undefined.It is showing PLATFORM_HEADER as error. Thanks and Regards, Sai Teja. |
Feb 17 2021, 2:49 PM |
|
Replied
to
Toolchain issue for compiling dynamic multiprotocol application(ZIGBEE+BLE)
Hi YK, As you suggested I installed the latest EmberZnet 6.9.1.0 version, but again I am facing the same issue. It is not redirecting me to the PLATFORM_HEADER. Thanks and regards, Sai Teja. |
Feb 17 2021, 2:31 PM |
|
Replied
to
Toolchain issue for compiling dynamic multiprotocol application(ZIGBEE+BLE)
Hi YK, Again I tried from the scratch by building default DynamicMultiProtocolLight example with EbmerZnet 6.7.7.0,Bluetooth 2.13.7.0, Micro Kernel OS v2.7.7 and IAR ARM v8.50.9.278 and I am having the problem using halCommonSetToken() and halCommonGetToken() functions. It is not only redirecting me to the PLATFORM_HEADER, for reference I am attaching you the photo. Please go through it once. Thanks and regards, Sai Teja. |
Feb 17 2021, 8:05 AM |