Coder Social home page Coder Social logo

nordicsemiconductor / ios-nrf-toolbox Goto Github PK

View Code? Open in Web Editor NEW
578.0 81.0 204.0 54.64 MB

The nRF Toolbox is a container app that stores your Nordic Semiconductor apps for Bluetooth Low Energy in one location.

Home Page: https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Toolbox

License: BSD 3-Clause "New" or "Revised" License

Objective-C 15.87% C 0.47% Swift 83.66%

ios-nrf-toolbox's Introduction

IOS-nRF-Toolbox

The nRF Toolbox is a container app that stores your Nordic Semiconductor apps for Bluetooth Low Energy in one location.

It contains applications demonstrating the following Bluetooth LE profiles:

  • Cycling Speed and Cadence
  • Running Speed and Cadence
  • Heart Rate Monitor
  • Blood Pressure Monitor
  • Health Thermometer Monitor
  • Glucose Monitor
  • Continuous Glucose Monitor
  • Proximity Monitor
  • Nordic UART

Additionally, the HomeKit profile allows to switch a supported HomeKit device to DFU mode.

Device Firmware Update (DFU)

The Device Firmware Update (DFU) profile allows you to update the application, bootloader and/or the Soft Device image over-the-air (OTA). It is compatible with Nordic Semiconductor nRF5x devices that have the S-Series SoftDevice and bootloader enabled. From version 1.5 onward, the nRF Toolbox has allowed to send the required init packet. More information about the init packet may be found here: nrf util.

nRF Toolbox is using the iOSDFULibrary framework, available here: IOS-Pods-DFU-Library. The library is packaged with the project so no extra work is needed, if you would like to manually update it or modify it, it is bundled via cocoapods so a simple pod update will handle updating the library for you.

The DFU profile has the following features:

  • Scans for devices that are in DFU mode.
  • Connects to devices in DFU mode and uploads the selected firmware (Softdevice, Bootloader and/or application).
  • Allows ZIP, HEX or BIN file updates.
  • Allows to update a Softdevice and/or bootloader and application from a distribution ZIP file automatically.
  • Pause, resume, and cancel firmware updates.
  • Includes pre-installed examples that consist of the Bluetooth LE services and Doorlock firmware from Nordic HK SDK 6.1.

Secure Device Firmware Update (Secure DFU)

The Secure Device Firmware Update (Secure DFU) profile allows you to securely update your Nordic Semiconductor nRF5x S-Seriese devices. This works by verifying that your firmware files are signed by the vendor that released the code and has not been tampered with, also this means that the peripherals will only accept updates from the intended developers and reject any firmwares that are not properly signed with the matching key.

As an applications developer, the frontend for the DFU Library is agnostic of the DFU protocol in use, so there are no changes to be done on the mobile application's side to support Secure DFU.

Requirements

  • iOS 9.0 and above.
  • Compatible with nRF5x devices with S-Series Softdevice and DFU Bootloader flashed.

Resources

ios-nrf-toolbox's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ios-nrf-toolbox's Issues

nRF Toolbox DFU Operation failed

With the default demo code or download nRF Toolbox App from AppStore, it's fail.
Does anyone know what the problem might be? Thanks
devices :nRF52 demo board PCA10040 V 1.1.0
mobile :iPhone 5s, iOS 8.1.3 / iPhone 6Plus, iOS 9.3.3

step1:Enter bootloader DFU mode.

img_1230

step2:Select file "hrs_dfu_s130_2_0_0_7a_sdk_11_0_0_2a.zip", and upload.

img_1231

step3:Get the error message "DFU Operation failed", and log as following.

img_1232
objc[860]: Class BluetoothManager is implemented in both /System/Library/PrivateFrameworks/BluetoothManager.framework/BluetoothManager and /private/var/mobile/Containers/Bundle/Application/81EEFFC7-2F0D-4212-8BA6-365D8407B50E/nRF Toolbox.app/nRF Toolbox. One of the two will be used. Which one is undefined.
2016-08-18 16:09:20.112 nRF Toolbox[860:79822] getFilesFromDirectory
2016-08-18 16:09:20.115 nRF Toolbox[860:79822] app resource path: /private/var/mobile/Containers/Bundle/Application/81EEFFC7-2F0D-4212-8BA6-365D8407B50E/nRF Toolbox.app
2016-08-18 16:09:20.116 nRF Toolbox[860:79822] firmware folder path: /private/var/mobile/Containers/Bundle/Application/81EEFFC7-2F0D-4212-8BA6-365D8407B50E/nRF Toolbox.app/firmwares
2016-08-18 16:09:20.116 nRF Toolbox[860:79822] getFilesFromDirectory
2016-08-18 16:09:20.117 nRF Toolbox[860:79822] app resource path: /private/var/mobile/Containers/Bundle/Application/81EEFFC7-2F0D-4212-8BA6-365D8407B50E/nRF Toolbox.app
2016-08-18 16:09:20.117 nRF Toolbox[860:79822] firmware folder path: /private/var/mobile/Containers/Bundle/Application/81EEFFC7-2F0D-4212-8BA6-365D8407B50E/nRF Toolbox.app/firmwares
2016-08-18 16:09:23.431 nRF Toolbox[860:79822]
WARNING: The class 'Manifest' is not key value coding-compliant for the key 'dfu_version'
There is no support for optional type, array of optionals or enum properties.
As a workaround you can implement the function 'setValue forUndefinedKey' for this. See the unit tests for more information
2016-08-18 16:09:29.934 nRF Toolbox[860:79822] 1: Connecting to DfuTarg...
2016-08-18 16:09:29.935 nRF Toolbox[860:79822] 0: centralManager.connectPeripheral(peripheral, options:nil)
2016-08-18 16:09:30.107 nRF Toolbox[860:79893] 0: [Callback] Central Manager did connect peripheral
2016-08-18 16:09:30.108 nRF Toolbox[860:79893] 5: Connected to DfuTarg
2016-08-18 16:09:30.109 nRF Toolbox[860:79893] 1: Discovering services...
2016-08-18 16:09:30.109 nRF Toolbox[860:79893] 0: periphera.discoverServices(nil)
2016-08-18 16:09:30.531 nRF Toolbox[860:79903] 5: Services discovered
2016-08-18 16:09:30.532 nRF Toolbox[860:79903] 1: DFU Service found
2016-08-18 16:09:30.534 nRF Toolbox[860:79903] 1: Discovering characteristics in DFU Service...
2016-08-18 16:09:30.535 nRF Toolbox[860:79903] 0: peripheral.discoverCharacteristics(nil, forService:DFUService)
2016-08-18 16:09:30.804 nRF Toolbox[860:79893] 5: DFU characteristics discovered
2016-08-18 16:09:30.807 nRF Toolbox[860:79893] 1: Reading DFU Version number...
2016-08-18 16:09:30.808 nRF Toolbox[860:79893] 0: peripheral.readValueForCharacteristic(00001534-1212-EFDE-1523-785FEABCD123)
2016-08-18 16:09:30.863 nRF Toolbox[860:79903] 5: Read Response received from 00001534-1212-EFDE-1523-785FEABCD123, value (0x):0800
2016-08-18 16:09:30.864 nRF Toolbox[860:79903] 10: Version number read: 0.8
2016-08-18 16:09:30.865 nRF Toolbox[860:79903] 1: Enabling notifiactions for 00001531-1212-EFDE-1523-785FEABCD123...
2016-08-18 16:09:30.865 nRF Toolbox[860:79903] 0: peripheral.setNotifyValue(true, forCharacteristic: 00001531-1212-EFDE-1523-785FEABCD123)
2016-08-18 16:09:30.981 nRF Toolbox[860:79893] 1: Notifications enabled for 00001534-1212-EFDE-1523-785FEABCD123
2016-08-18 16:09:30.982 nRF Toolbox[860:79893] 10: DFU Control Point notifications enabled
2016-08-18 16:09:30.983 nRF Toolbox[860:79893] 1: Writing to characteristic 00001531-1212-EFDE-1523-785FEABCD123...
2016-08-18 16:09:30.986 nRF Toolbox[860:79893] 0: peripheral.writeValue(0x0103, forCharacteristic: 00001531-1212-EFDE-1523-785FEABCD123, type: WithResponse)
2016-08-18 16:09:30.988 nRF Toolbox[860:79893] 1: Writing image sizes (104164b, 12996b, 0b) to characteristic 00001532-1212-EFDE-1523-785FEABCD123...
2016-08-18 16:09:30.990 nRF Toolbox[860:79893] 0: peripheral.writeValue(0xe4960100c432000000000000, forCharacteristic: 00001534-1212-EFDE-1523-785FEABCD123, type: WithoutResponse)
2016-08-18 16:09:31.041 nRF Toolbox[860:79903] 5: Data written to 00001531-1212-EFDE-1523-785FEABCD123
2016-08-18 16:09:31.042 nRF Toolbox[860:79903] 10: Start DFU (Op Code = 1, Upload Mode = 3) request sent
2016-08-18 16:09:31.582 nRF Toolbox[860:79893] 5: Notification received from 00001534-1212-EFDE-1523-785FEABCD123, value (0x):100101
2016-08-18 16:09:31.583 nRF Toolbox[860:79893] 10: Response (Op Code = 1, Status = 1) received
2016-08-18 16:09:31.584 nRF Toolbox[860:79893] 10: Writing Initialize DFU Parameters...
2016-08-18 16:09:31.584 nRF Toolbox[860:79893] 1: Writing to characteristic 00001531-1212-EFDE-1523-785FEABCD123...
2016-08-18 16:09:31.585 nRF Toolbox[860:79893] 0: peripheral.writeValue(0x0200, forCharacteristic: 00001531-1212-EFDE-1523-785FEABCD123, type: WithResponse)
2016-08-18 16:09:31.586 nRF Toolbox[860:79893] 1: Writing to characteristic 00001532-1212-EFDE-1523-785FEABCD123...
2016-08-18 16:09:31.588 nRF Toolbox[860:79893] 0: peripheral.writeValue(0xffffffffffffffff0100feff7630, forCharacteristic: 00001534-1212-EFDE-1523-785FEABCD123, type: WithoutResponse)
2016-08-18 16:09:31.590 nRF Toolbox[860:79893] 1: Writing to characteristic 00001531-1212-EFDE-1523-785FEABCD123...
2016-08-18 16:09:31.591 nRF Toolbox[860:79893] 0: peripheral.writeValue(0x0201, forCharacteristic: 00001531-1212-EFDE-1523-785FEABCD123, type: WithResponse)
2016-08-18 16:09:31.640 nRF Toolbox[860:79903] 5: Data written to 00001531-1212-EFDE-1523-785FEABCD123
2016-08-18 16:09:31.700 nRF Toolbox[860:79893] 5: Data written to 00001531-1212-EFDE-1523-785FEABCD123
2016-08-18 16:09:31.701 nRF Toolbox[860:79903] 5: Notification received from 00001534-1212-EFDE-1523-785FEABCD123, value (0x):100201
2016-08-18 16:09:31.701 nRF Toolbox[860:79903] 10: Response (Op Code = 2, Status = 1) received
2016-08-18 16:09:31.701 nRF Toolbox[860:79903] 10: Initialize DFU Parameters completed
2016-08-18 16:09:31.702 nRF Toolbox[860:79903] 1: Writing to characteristic 00001531-1212-EFDE-1523-785FEABCD123...
2016-08-18 16:09:31.703 nRF Toolbox[860:79903] 0: peripheral.writeValue(0x080c00, forCharacteristic: 00001531-1212-EFDE-1523-785FEABCD123, type: WithResponse)
2016-08-18 16:09:31.760 nRF Toolbox[860:79893] 5: Data written to 00001531-1212-EFDE-1523-785FEABCD123
2016-08-18 16:09:31.761 nRF Toolbox[860:79893] 10: Packet Receipt Notif Req (Op Code = 8, Value = 12) request sent
2016-08-18 16:09:31.761 nRF Toolbox[860:79893] 1: Writing to characteristic 00001531-1212-EFDE-1523-785FEABCD123...
2016-08-18 16:09:31.762 nRF Toolbox[860:79893] 0: peripheral.writeValue(0x03, forCharacteristic: 00001531-1212-EFDE-1523-785FEABCD123, type: WithResponse)
2016-08-18 16:09:31.821 nRF Toolbox[860:79903] 5: Data written to 00001531-1212-EFDE-1523-785FEABCD123
2016-08-18 16:09:31.821 nRF Toolbox[860:79903] 10: Receive Firmware Image (Op Code = 3) request sent
2016-08-18 16:09:31.822 nRF Toolbox[860:79903] 10: Uploading firmware...
2016-08-18 16:09:31.822 nRF Toolbox[860:79903] 1: Sending firmware DFU Packet characteristic...
2016-08-18 16:09:31.881 nRF Toolbox[860:79893] 5: Notification received from 00001534-1212-EFDE-1523-785FEABCD123, value (0x):100306
2016-08-18 16:09:31.882 nRF Toolbox[860:79893] 10: Response (Op Code = 3, Status = 6) received
2016-08-18 16:09:31.883 nRF Toolbox[860:79893] 20: Error 6: Operation failed
2016-08-18 16:09:31.883 nRF Toolbox[860:79893] 1: Disconnecting...
2016-08-18 16:09:31.884 nRF Toolbox[860:79893] 0: centralManager.cancelPeripheralConnection(peripheral)
2016-08-18 16:09:31.887 nRF Toolbox[860:79903] 0: [Callback] Central Manager did disconnect peripheral without error
2016-08-18 16:09:31.887 nRF Toolbox[860:79903] 5: Disconnected
2016-08-18 16:09:31.888 nRF Toolbox[860:79822] Error 6: Operation failed

BLE-UART String Send

Hi,

Tested using iOS 10.1

Connecting to my device on UART-BLE, and then sending a string 'ACK' or any arbitrary characters would send up with a random hexstring sent. Sending the same character string 'ACK' twice shows on the log 2 different hexstrings are sent: for example "0x000abc" and "0x000abd".

I've tested my hardware and firmware against the Android version of the nRF Toolbox, and is proven to be working normally.

Crashes when copying DFU file from Email

Version 4.0.4, iPad Air 2, iOS 9.3.5

I longclick the DFU attachment in the Email app, and select "Copy to nRF Toolbox". The splash screen appears and then nRF Toolbox crashes. No files can be found in the "Inbox" folder under "User Files" after restarting the nRF Toolbox.

I have experienced the same problem on two devices, and this seems to be the exact same problem that user "develooop" describes here: #23

UART: Allow typing end lines \r and \n

I have a BLE peripheral running Nordic's 14.2.0 SDK and using their BLE CLI. CLI Commands coming from NRF Toolbox (BLE) UART 4.4.4 on iOS 12 do not appear to be processed by the peripheral. I have tried all combinations of \r and \n using an iOS keyboard utility "Unicode Keyboard" (the icon for this app is U+ against a gold background).

My peripheral is "known good" in so far as any CLI Commands coming from Adafruit Bluefruit LE Connect (from the iOS App Store) are processed by my peripheral and the results show up on the iPhone. This only required configuring \r to be the EOL in the Adafruit App.

Note: using the same peripheral but doing CLI from MacOS instead I was also able to CLI with bleterm2 from PunchThrough... until I updated to Mojave.

New version of app

I understand there is a new version of this app in the app store. Are there plans to update this git repository with the updated code?

DFU does not work on iOS 10

Hi
I'm having the same issue with this
#32

When I click on Upload after choosing packet zip file and nordic device, it seems not connect to the device
From the link above, he seems to have solved the problem, and I 'd like to solve that issue

It would be very great if you can help me

readSFloatValue Bug for BGM

FYI in case anyone else runs into this problem...

Testing a True Metrix Air Blood Glucose Meter with this code does not work. The meter is transferring per the profile standard, but the glucose concentration is not being calculated properly inside CharacteristicReader.m. See correct implementation here...

https://github.com/signove/antidote/blob/master/src/util/bytelib.c

Also, GlucoseReading.m updateFromBytes: is not checking the glucoseConcentrationUnit. So multiplying by 1000 is not necessarily correct (not sure it ever makes sense??). Should check whether unit is kg/L or mol/L before converting.

DFU. Operation not permitted

HI
When I upload the Zip file, remind Operation not permitted . what's the reason?
Do anyone have the same problem 。

nrf iOSDFU library. Operation Failed error

Hi, I want to use nrf iOSDFULibrary(4.4.2) to do DFU from S132 SDK12.3 to S132 SDK15.3. But it always shows Operation Failed error. log is attached below. Is anyone have advice on it?

2019-07-02 12:28:05.406464+0800 Flyplay[5715:1741134] 0: peripheral.writeValue(0x04, for: 8EC90001-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
2019-07-02 12:28:05.463114+0800 Flyplay[5715:1741134] 5: Data written to 8EC90001-F315-4F60-9FB8-838830DAEA50
2019-07-02 12:28:05.463916+0800 Flyplay[5715:1741134] 5: Notification received from 8EC90001-F315-4F60-9FB8-838830DAEA50, value (0x): 60040a
2019-07-02 12:28:05.464571+0800 Flyplay[5715:1741134] 20: Error 10: Operation failed
2019-07-02 12:28:05.465358+0800 Flyplay[5715:1741134] 1: Disconnecting...
2019-07-02 12:28:05.465751+0800 Flyplay[5715:1741134] 0: centralManager.cancelPeripheralConnection(peripheral)
2019-07-02 12:28:05.469522+0800 Flyplay[5715:1741134] 0: [Callback] Central Manager did disconnect peripheral
2019-07-02 12:28:05.469728+0800 Flyplay[5715:1741134] 5: Disconnected
2019-07-02 12:28:05.470021+0800 Flyplay[5715:1741134] Error 20: Operation failed

Single bank DFU upload

Seems like DFU upload doesn't support large files (even though they fit with single bank bootloader).

file not found

IOS-nRF-Toolbox-develop/nRF Toolbox/UART/BaseRevealViewController.h:23:9: 'SWRevealViewController.h' file not found

DFU file not support

With the default demo code about DFU, I got the message “Selected file is not supported.” after I selected hex file. Why?

BGM Module

Can I download the engineering connect my yuwell glucose meter can obtain after the first and last data, but can't get all the data, I saw the break point, method of adding data doesn't seem to go, can you help me to solve it for me? Thank you very much!

iOS DFU not working since update

Hi, it seems that after the ios 10 update and the swift code conversion, my DFU code is not longer working correctly. In code, I am able to get the module into the DFU mode (DFTTarg), after that I am able to connect to the module again under the new service UUID for the DFU. However, after this step I try and call the DFUServiceInitiator.start() method, and it seems to work, but the only update I get (didStateChangedTo) is a state change to "connecting" and that is it, it stays there. I am able to do the DFU with an android phone using Nordic NRF Connect just fine, so the module is ok. Has the implementation of the code changed? Am I missing something? Is there example code I can refer to? Thanks a bunch, and if there is anything else that I could provide that might help, please let me know. Thanks.

Unable to get UART connection on iOS 11

Could not connect to the nRF52840 preview DK eval kit running the ble_peripheral/ble_app_uart on iOS 11, tried on iPhone 7 and 8. Connection does not get established.
Tried the app on an Android - no issues.

Please advise

最新版的xcode10.2不兼容swift4.1

我们升级了xcode版本到xcode10.2,发现xcode10.2不支持swift4.1,只支持swift4.0、4.2和5.0,动态引用会和现有的pod导入的静态库冲突,不知道这个sdk能不能升级到swift5.0或者4.2版本?

nRFToolbox - HTS issue

Hi
In ble_app_hts sample code, the default setting

define MIN_CELCIUS_DEGREES 3688

define MAX_CELCIUS_DEGRESS 3972

define CELCIUS_DEGREES_INCREMENT 36

When nRFtoolBox - HTS connect with Device, it will shows 3688+36 = 3724. It means 37.24 degrees

Android will show 37.24 degress but iOS will show 176.00 degress.

When press button 1 on nRF51 DK. It will increse 36.

Android will show 37.60 degress but iOS will show 212.00 degrees.

Customer wants to demo their HTS device to their end customer in these days.

When will Nordic release new version to fix this issue?

Thanks.

invalid state error

when doing a DFU update with a single zip that contains an application, softdevice, and bootloader, I am sometimes getting an Invalid State Error, even if the device is on the charger.

screen shot 2016-04-21 at 1 27 28 pm

this is running the latest code out of master. i'm not able to consistently reproduce. any help with understanding when this error appears would be helpful. thanks.

Glucose measurement is in mmol/l but it is really in KG/L?

I used a glucometer with bluetooth to send the reading to the app. I compared my reading from the glucometer to the data that is shown by the app and found that the app converts the glucose measurement to KG/L and not to mmol/l? The reading on the glucometer is in mg/dl so when I multiplied the app reading by 100000 , that is when they are the same. Also the parsed time is late by an hour. Right now I don't have an idea why but I'm checking out the downloaded code. Just a heads up.

IOS TOOLBOX DFU upload failure

toolbox which version is newly on IOS,DFU can not work,I have found the reason...at upload start,toolbox does NOT write CCCD of DFU control point,so device think it is a failure,then RESET.
could you solve the problem of toolbox?

changes in version 2.5

Apologies, this isn't an issue. Area all the changes with the new version visual? Or are there changes to anything that involves firmware updates?

I abstracted the fw update code from the pervious version so when looking at the changes for this version, there are a lot of diffs.

DFU not working

On pressing upload, app crashes and the configurable settings (number of packets and External MCP DFU) are reset to 12 and OFF respectively. We require number of packets to be 1, and External MCP DFU to be ON. We did not have this issue in v3.0.1.

DFU does not work for nRF52

There is no way to change the MBR size from the default 4096 (0x1000) to 12288 (0x3000) , which is required to update the nRF52.

Crashing during DFU

Version 4.0.4(12). iPhone 5c, IOS 9.3.4
I choose DFU mode, then Select any zip-file, then push button "Select Device". The app crashes down.
It does not matter if I don't choose any file or choose hex-file
When I choose UART mode, I have the same behavior after "Connect" button pressed.

I tried it in app from official AppStore and in app built from master branch

UART Library

Where can I find libraries of methods for working with UART?

DFU max speed

Hi,
What's the max throughput we can achieve with iOS (4S) during DFU ? What are reliable connection interval, packet size ,...., parameters ?
And during downlink (iOS -> peripheral) ?
Cheers,
Alexis

BLE Scanning Disabled

Also posted in iOS nRF Connect GitHub: NordicSemiconductor/IOS-nRF-Connect#39

This has been a bug since first install of iOS 11, I believe. Now I'm on iOS 11.4.1 and both nRF Toolbox and nRF Connect are unusable. I am using iPhone 6S. Same device, no problems with nRF apps before this one.

The scanning list will only populate for a few seconds immediately after phone reboot.

Other BLE Scanning apps (i.e. Adafruit Bluefruit) seem to have problems too, but it is intermittent and can be reset by Bluetooth radio power cycle.

Force closing, re-opening does not fix. Force closing all apps does not fix.

I'm happy to share log files and help diagnose.

img_5468

App crashes at splash screen

Hi,
I upgraded the nRF-Toolbox app to version 3.0 on 2 devices: iPad Mini (iOS 9.3.1), iPhone 4S (iOS 8.4).
On both devices the app crashes on the splash screen, no messages are displayed, I'm not able to use the app anymore, please solve the bug or tell us how to solve.
We are beacon developers/manufacturers, we use the app to test the FW upgrade procedure on our beacons.

Application not starting

I am running the code on xcode 7.2 and it crashes straight away at the beginning. I am attaching the screenshot.

screen shot 2016-03-20 at 3 11 29 pm

Scanner Delegate is not working.

Hi,
when i m using only Proximity . when I use
- (void) centralManager:(CBCentralManager*) manager didPeripheralSelected:(CBPeripheral*) peripheral;
this method in ProximityViewController it not work. because when this method is calling from ScannerViewController it not redirect to me at ProximityViewController so i can't understand what should i do now.

DFU firmware update text string broken

DFU firmware update texts string broken in version 4.4.4

The text beneath the "DEVICE FIRMWARE UPDATE"
is broken, shows only "U...ad"
dfu-oops

PS "Firmware Update" title seems unnecessarily large (but hey that's just me.
especially since the gray text on the left article margin already says that.

Thanks for your support

Crashing during DFU

Version 4.1.0. iPhone 5c, IOS 9.3.4
I choose DFU mode, then push button "Select Device". The app crashes down.
I choose UART mode, I have the same behavior after "Connect" button pressed.
I tried it in app from official AppStore

Buttonless DFU not working, Error 4: Operation Failed

I changed "alternativeAdvertisingNameEnabled" to false like I saw in another thread. But the operation is still failing.

Verbose: Enabling indications for 8EC90003-F315-4F60-9FB8-838830DAEA50...
Debug: peripheral.setNotifyValue(true, for: 8EC90003-F315-4F60-9FB8-838830DAEA50)
Verbose: Indications enabled for 8EC90003-F315-4F60-9FB8-838830DAEA50
Application: Buttonless DFU indications enabled
Warning: Application with buttonless update found
Verbose: Trying setting bootloader name to Dfu58664
Verbose: Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...
Debug: peripheral.writeValue(0x0a000000000000000208, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)
Info: Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50
Info: Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):030000
Error: Error 4: Operation failed
Verbose: Disconnecting...
Debug: centralManager.cancelPeripheralConnection(peripheral)
Debug: [Callback] Central Manager did disconnect peripheral
Info: Disconnected

nRF Toolbox doesn't work but nRF Connect does. Why would that be?

Cryptic error message

We wasted a valuable time trying to understand the reason of a issue we were having with OTA.

We were using NRF51 SDK 11 which support only legacy OTA.
Nordic documentation didn't specify anything about a specific version of nrfjprog, but we learn (via amazing Nordic Support) that we needed to use nrfutil <= 0.5.2 (https://github.com/NordicSemiconductor/pc-nrfutil/tree/v0.5.2) in order to generate a legacy compatible package.

I'm not sure if the error code return by the app match any other similar issue but we get "Operation failed. Ensure the firmware targets that device type and version." (i.e..:

report(error, "Operation failed. Ensure the firmware targets that device type and version.")
) which is pretty cryptic.

It would have been awesome to have something like: "This package version doesn't seem to be supported by your current boot loader SDK version. Please consider upgrading your SDK or use the correct firmware packaging format, see docs xxx for more help"

Thank you for your help and support, we know it's hard to maintain past documentation but I think legacy OTA (even if unsecure) is still pretty widely used for device which don't need this security.

Thanks and hope it helps others :)

IphoneX and iphone8 dfu

The app will stuck at enabling DFU Bootloader. After a while, it will return unknow error(code 0).
However, the same packet is used and it works on iphone 7 , iphone 6+, iphone 6.

Thank you for investigating this.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.