ios nrf loader timeout during upload

RE: ios nrf loader timeout during upload

Ole Morten — Mon, 16 Dec 2013 12:57:10 GMT

I believe that the bootloader should compile out of the box, but I suspect that disabling optimizations might make it not fit anymore. Anyway, great that you've gotten further!

RE: ios nrf loader timeout during upload

Frank Zhao — Tue, 10 Dec 2013 19:28:02 GMT

I was compiling using MicroLib, because the original project configuration did not seem to fit, it threw a bunch of linker errors that were similar to some previous not-enough-RAM problems I faced. Enabling MicroLib allowed the project to compile, but I suspect it made it run slower.

I just tested bootloading my own application and it works. I added the command

fromelf --bin --output "$L@L.bin" "#L"

to my post build execution steps to generate the bin

RE: ios nrf loader timeout during upload

Ole Morten — Tue, 10 Dec 2013 16:40:17 GMT

That's interesting indeed. I saw NO_MEMORY errors once in a while when developing the app, but that was only when having long printf-s several places in the bootloader. I would not at all expect it to happen with the bootloader directly from the SDK. Do you still see errors when not doing any debug output?

There isn't any magic about creating a bin file to be used with nRF Loader, you can for example do like this to do such conversion: https://devzone.nordicsemi.com/index.php/how-to-use-the-nrf-loader-to-do-ota#reply-3155

RE: ios nrf loader timeout during upload

Frank Zhao — Mon, 09 Dec 2013 20:12:21 GMT

I am just trying out ble_app_rscs, 17260 bytes

changing notificationPacketInterval to 1 worked! it seems to transfer 20 (which is max packet size) bytes per notification now.

should I just increase it until it stops working?

Also although it seems to detect a valid application because it attempts to launch it, the application itself seems to be self-resetting... How do I go about generating a .bin file from my own .hex file?

I realize the above question is actually very simple to answer myself, but hex files specify addresses, bin files do not, I need to know the proper way of doing the conversion because of the address offset.

RE: ios nrf loader timeout during upload

Ole Morten — Mon, 09 Dec 2013 15:34:50 GMT

Thanks for the logs. I've posted a separate answer showing how the number of packets transmitted per notification can be changed, since it doesn't seem to have anything to do with what I thought was the initial problem.

RE: ios nrf loader timeout during upload

Ole Morten — Mon, 09 Dec 2013 15:34:03 GMT

You can change how many packets the iOS app sends between receiving a confirmation, which may help NO_MEMORY issues, by tuning the setting of the notificationPacketInterval in setFirmwareURL of the DFUController.

The algorithm to set this number was chosen based on getting a reasonable amount of updates over an application upload, but doesn't check the size it ends up at. May I ask how large the binary you're trying to upload is? It could be that this number simply becomes too big for the buffers on the nRF51822 side if the binary itself is big.

RE: ios nrf loader timeout during upload

Frank Zhao — Sun, 08 Dec 2013 22:06:01 GMT

I've identified that hci_mem_pool_rx_produce is failing due to NRF_ERROR_NO_MEM

Is it because iOS is sending faster than the nRF can process? How do we slow down iOS?

RE: ios nrf loader timeout during upload

Frank Zhao — Sun, 08 Dec 2013 21:43:32 GMT

I added some UART debug statements to the nRF DFU code.

It seems like the nRF51 chip itself is resetting periodically after the dfu timer times out.

Once upload starts, it hits "receive fw" and runs "app_data_process" a few times, then it freezes for a few seconds before the entire microcontroller resets

Also I am forced to use MicroLIB to compile, because without MicroLIB, it doesn't fit into the IRAM. I wonder if that makes a difference

the iOS NSLog is shown below

2013-12-08 15:36:47.286 nRF Loader[1103:60b] Set firmware with size 17260, notificationPacketInterval: 43 2013-12-08 15:36:47.398 nRF Loader[1103:60b] CoreBluetooth[WARNING] <CBCentralManager: 0x15d24510> is disabling duplicate filtering, but is using the default queue (main thread) for delegate events 2013-12-08 15:36:47.401 nRF Loader[1103:60b] Started scan. 2013-12-08 15:36:47.405 nRF Loader[1103:60b] Central manager did update state: 5 2013-12-08 15:36:48.519 nRF Loader[1103:60b] Stopped scan. 2013-12-08 15:36:48.634 nRF Loader[1103:60b] didConnectPeripheral DfuTarg 2013-12-08 15:36:48.637 nRF Loader[1103:60b] didConnect 2013-12-08 15:36:48.640 nRF Loader[1103:60b] State changed from 0 to 1. 2013-12-08 15:36:49.196 nRF Loader[1103:60b] didDiscoverServices succeeded. 2013-12-08 15:36:49.199 nRF Loader[1103:60b] Discover characteristics... 2013-12-08 15:36:49.376 nRF Loader[1103:60b] didDiscoverCharacteristics succeeded. 2013-12-08 15:36:49.379 nRF Loader[1103:60b] Found packet characteristic. 2013-12-08 15:36:49.380 nRF Loader[1103:60b] Found control point characteristic. 2013-12-08 15:36:49.382 nRF Loader[1103:60b] didFinishDiscovery 2013-12-08 15:36:49.384 nRF Loader[1103:60b] State changed from 1 to 2. 2013-12-08 15:36:55.144 nRF Loader[1103:60b] startTransfer 2013-12-08 15:36:55.146 nRF Loader[1103:60b] State changed from 2 to 3. 2013-12-08 15:36:55.148 nRF Loader[1103:60b] sendNotificationRequest 2013-12-08 15:36:55.196 nRF Loader[1103:60b] didWriteControlPoint, state 3 2013-12-08 15:36:55.199 nRF Loader[1103:60b] State changed from 3 to 4. 2013-12-08 15:36:55.202 nRF Loader[1103:60b] sendStartCommand 2013-12-08 15:36:55.256 nRF Loader[1103:60b] didWriteControlPoint, state 4 2013-12-08 15:36:55.316 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100101>. 2013-12-08 15:36:55.319 nRF Loader[1103:60b] didReceiveResponse, 1, in state 4 2013-12-08 15:36:55.321 nRF Loader[1103:60b] State changed from 4 to 5. 2013-12-08 15:36:55.322 nRF Loader[1103:60b] sendReceiveCommand 2013-12-08 15:36:55.376 nRF Loader[1103:60b] didWriteControlPoint, state 5 2013-12-08 15:36:55.379 nRF Loader[1103:60b] State changed from 5 to 6. 2013-12-08 15:36:55.380 nRF Loader[1103:60b] sendFirmwareData 2013-12-08 15:36:55.392 nRF Loader[1103:60b] didWriteDataPacket 2013-12-08 15:36:55.394 nRF Loader[1103:60b] State changed from 6 to 9. 2013-12-08 15:36:55.395 nRF Loader[1103:60b] Sent 860 bytes, total 860. 2013-12-08 15:36:55.438 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.440 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.442 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.443 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.466 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.469 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.471 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.473 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.498 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.499 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.501 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.503 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.526 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.529 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.531 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.533 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.556 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.559 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.586 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.589 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.591 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.592 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.616 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.619 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:36:55.621 nRF Loader[1103:60b] Did update value for characteristic <CBCharacteristic: 0x15e56cf0>. Value: <100306>. 2013-12-08 15:36:55.622 nRF Loader[1103:60b] didReceiveResponse, 6, in state 9 2013-12-08 15:37:56.349 nRF Loader[1103:60b] didDisconnectPeripheral DfuTarg: Error Domain=CBErrorDomain Code=6 "The connection has timed out unexpectedly." UserInfo=0x15d49480 {NSLocalizedDescription=The connection has timed out unexpectedly.} 2013-12-08 15:37:56.351 nRF Loader[1103:60b] didDisconnect 2013-12-08 15:37:56.481 nRF Loader[1103:60b] State changed from 9 to 0. 2013-12-08 15:37:56.554 nRF Loader[1103:60b] cancelTransfer 2013-12-08 15:37:56.556 nRF Loader[1103:60b] CoreBluetooth[WARNING] <CBCentralManager: 0x15d24510> is disabling duplicate filtering, but is using the default queue (main thread) for delegate events 2013-12-08 15:37:56.560 nRF Loader[1103:60b] Started scan.

RE: ios nrf loader timeout during upload

Ole Morten — Fri, 06 Dec 2013 09:41:04 GMT

If you only see the device when it is connected, this is not the bonding issue after all. Which iOS version are you using? Do you have the possibility to run the app in a development environment?

RE: ios nrf loader timeout during upload

Frank Zhao — Thu, 05 Dec 2013 20:08:48 GMT

I can only see the device in the iOS settings when the nRF Loader application is in the connected state. I can't do anything with it, tapping on the name does nothing, tap and hold does nothing, I can't swipe it away... How do I make the bond disappear?

RE: ios nrf loader timeout during upload

Ole Morten — Wed, 04 Dec 2013 15:05:50 GMT

No, all bonding on iOS is completely transparent to an app, and you have no control over it. The only way to delete a bond on iOS is for the user to go into the Settings menu and manually "Forget this device".

RE: ios nrf loader timeout during upload

Frank Zhao — Wed, 04 Dec 2013 15:02:22 GMT

Is there an explicit un-bond function in iOS? I tried Google, no relevant results.

RE: ios nrf loader timeout during upload

Ole Morten — Wed, 04 Dec 2013 12:00:20 GMT

Could it be that you have a bond with your device? If so, the DFU solution as given in the SDK will need to be modified to work. Take a look at this question for details.

If this is not the problem, it would have been very useful if you could run the application directly from an iOS development environment, and posting the log output of it. This should make it more clear what happens.