0 Members and 1 Guest are viewing this topic.
Your client does not respond. Check that you have specified the correct address and other network parameters.
Well, somehow the client does not respond to the OTA request. Debug that.No, the server does not need a bootloader. The server is working as designed here, but your client does not respond to the OTA Start request. So check the client.
What will be the reason?
Quote from: Peili on March 31, 2019, 07:13:55 amWhat will be the reason? Client does not respond. There may be 1000 reasons. Get a sniffer. I don't even understand how you can do any wireless development without a sniffer.
Does that device ever send anything? Is it in the right PAN? Does it have OTA enabled and configured?
Destination PAN in the sniffer is 0x3124, in the config 0x1234.
Capitalize the sentences.Show the frame log (just a list, no decode) when you start OTA. See what exactly happens at that moment.
The sniffer log. It is useless to look at a single frame, you need to look at everything that is going all. All the frame that are being exchanged. There are many stages to this whole process, and failure at any of them may result in that status code.
In this log the PAN is still 0x3124. And the device 0x8555 (OTA server) sends a route request for device 0x0. Device does not respond. Figure out your PAN ID confusion.
In that case your target device is not responding. Check that it is actually running some firmware. You said that it sends frames, but there is no evidence of that in the log.
Have it send frames so that you know that network stuff works too. May be build some other configuration, not a coordinator (address > 0).
Actually, if I remember correctly you had NWK_ENABLE_ROUTE_DISCOVERY disabled in your projects, but update server attempts to do the route discovery, which means it must be enabled there. Your network configurations must be the same on all devices.