Hello. We are an OEM design company that is in immediate need for a BLE solution that will be compatible across the assorted phones in the market. Very new to BLE and only started this review on Friday so please excuse the generic questions.
We have the nrf52 kit to evaluate the nRF52832. nRF6827 Rev 1.1.1 2017.04 We have the nRF52840 Preview kit to evaluate the nRF52840. nRF6828 Rev 0.9.0 2017.08 Huawei P8 Lite (ALE-L21). Android 6.0.
-
We have downloaded the nRF5_SDK_14.2.0_17b948a toolchain with examples for testing. The examples are supplied with source code and compiled .hex files for drag & drop into the mbed style drive letter (E: for us).
-
For testing the compiled .hex file against the nRF52832 - should we drag & drop the file with the S132 in the filename? Read about the softdevice and this appears to be correct.
Respectively, S140 in the filename is for use with the nRF52840?
- Are the compiled examples inclusive of these softdevices? We also installed nrfGO tool which is reporting that some code is present in Region 1 so we cannot program our Proximity application unless we erase the chip. Then the tool does not complain.
Believe the compilex hex file is complete.
Why does the nrfGO tool not properly report the details of the softdevice?
Firmware: Unknown (ID: 0x0096) ?
We have attempted to drag & drop only the softdevice for the 840 IC and still the same Unknown status.
- After programming of the Proximity hex file -> our P8 Lite phone can see the ID in the settings.
Should we be able to PAIR to this board? We fail to pair using the P8 Lite.
The nrf Toolbox -> Proximity -> Add Device -> can see the ID fine and we can add this to the Proximity demo. Believe it is working ok as we walk around my home and at very remote distances, complains about the board getting away. However, also saw this message while being less than 12" away from the kit. Perhaps a fluke on the error.
- Similar issues with the HRM demo. However, onetime on Friday, believe the phone and kit paired up so not sure if we have now erased too much on the kit that has led to these non-working demo status.
HRM demo returns an error code (133) - using Google is raising some concern about Android issues, etc.
While too early to halt our review, we faced similar issues with the PSOC6 and another developer noted it is the phone that is at fault. Believe that Huawei is a player although their lack of support is not nice. We are reviewing some volume widgets and must have a reliable means to perform OTA and/or configuration of our products. It is not practical to request for the end user to switch phones till the tool works. If required, we will consider to build both sides of the wireless link but cost is a factor.
We used the same phone with the Samsung Artik 053 for which Samsung is reviewing their firmware (wifi) and as to why onboarding is failing to operate correctly. Asus phone went further with the wifi demo.
We are fine to bring in some related BLE sniffer tools, etc. to debug but we appear to be going down another rabbit hole.
Is it possible to reliably create a wireless link with only 2 of the Nordic devices (BLE is preferred). Using an embedded USB enabled BLE master, we can then perform the same OTA upgrade of our devices. Hoping these are just IP issues that will be resolved with firmware so we can migrate into Homekit, Mesh, Thread support over time.
Thanks !!
Kumar
PS: Saw another developer on this forum using the P8 Lite - may we ask if the phone works for you with the nRF kits and tools? If yes, can you recommend a simple demo so we can raise our confidence with this phone? We are ok to source a different phone to move forward but that is not a practical resolution for our end products.
