On using your DFU code in iOS-nRF-Toolbox, We were only able to reset the BLE device It same happen on use iOS-nRF-Toolbox to update firmware.
On using your DFU code in iOS-nRF-Toolbox, We were only able to reset the BLE device It same happen on use iOS-nRF-Toolbox to update firmware.
HI CGS,
which iOS version did it work on and which iOS version did you update to?
Is the BLE device bonded to the iOS device?
Can you provide the debug output logs from both the nRF device as well as the DFU library on the iOS device?
Best regards
Bjørn
Hi Bjorn,
it's possible to download nrfConnect source code for iOS because in this app we able to update firmware
Thanks,
CGS
Hi CGS,
we do not distribute the source code for our nRF Connect apps for iOS or Android.
In both cases, i.e. IOS-Pods-DFU-Library and the IOS-nRF-Toolbox the debug log outputs look normal, i.e. the correct characteristics and descriptors are written to and the nRF device is disconnecting and resetting to enter bootloader mode. So in the case of the iOS Pods DFU library it would seem that the iOS device is not able to connect to the nRF Device after it enters bootloader mode.
I will need to see the log output from the nRF Device to see if the IOS is issuing a connection request or not. It would also be useful if you could capture a sniffer trace using our nRF Sniffer v2, see https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Sniffer.
You did not answer these questions in my previous comment:
Which iOS version did it work on and which iOS version did you update to?
Is the BLE device bonded to the iOS device?
Which iOS version did it work on and which iOS version did you update to?
- I am asking for BLE device update
Is the BLE device bonded to the iOS device?
- YES
Ok, my bad I though the title of the question,"Device is not updated after update for iOS", meant that the DFU failed after updating the iOS version.
And you did answer the question related to bonding. Again sorry.
If the nRF Device is bonded then the nRF device should send a Service Changed indication to inform the Central( iOS device) that the GATT table has changed as the iOS device will cache the GATT table of bonded peers. So the Service Changed Characteristic must be present on the nRF device, but as the DFU is successful when using nRF Connect, it indicates that this is OK.
I will need to look at a sniffer trace to see if the nrf device is advertising correctly after being put into bootloader and if the iOS device is issuing the connection request.
I will need to look at a sniffer trace to see if the nrf device is advertising correctly after being put into bootloader and if the iOS device is issuing the connection request.
-- how to sniffer trace work
I will need to look at a sniffer trace to see if the nrf device is advertising correctly after being put into bootloader and if the iOS device is issuing the connection request.
-- how to sniffer trace work
Please see the nRF Sniffer User Guide v2.2
Hello Bjorn,
I have checked above User Guide but not getting exact idea.
In nrf ToolBox source code, Why my BLE device disconnect when I select device it will connected but once BLE device reset it will be automatically BLE disconnect
Hello Bjorn ,
Are you checked ?
Can you elaborate? What is it that you are not getting? The idea is to capture a trace of the on air packets between the iOS device and the nRF Device?
CGS said:I have checked above User Guide but not getting exact idea.
I do not quite understand what you mean when you state the following:
CGS said:In nrf ToolBox source code, Why my BLE device disconnect when I select device it will connected but once BLE device reset it will be automatically BLE disconnect
I would recommend using the nRF Connect app over the nRF Toolbox as it will generate a log output that you can attach to this question.
I would recommend using the nRF Connect app over the nRF Toolbox as it will generate a log output that you can attach to this question.
