Faulty DK-52?

RE: Faulty DK-52?

fab — Wed, 27 Jul 2016 17:56:44 GMT

Hey Keyton, You are right. The iOS app takes some time read the new service. Killing the App and restarting Bluetooth helps.

RE: Faulty DK-52?

Keton — Sun, 17 Jul 2016 18:23:43 GMT

It looks like a caching issue. I don't know iOS much but on Android if you are reconnecting to bonded peripheral device OS assumes that service map doesn't change and you must do a manual refresh by deleting bond and redoing service discovery. I also vaguely remember discussion on stackoverflow where people complained that iOS really likes bonding to BLE devices and something has to be done manually to do a refresh. But it was in iOS 8 era when I've done last BLE development for that platform.

If you by any chance have access to android device I'd try recent version of Nordic nRF connect. After uploading new program to the DK select 'delete bond information' and 'refresh services' in 3 dots menu. I use this all the time during firmware development.

RE: Faulty DK-52?

fab — Sun, 17 Jul 2016 15:44:26 GMT

Hey Keton,

Thank you for your prompt answer.

Ok, I'll try to upgrade the J-link firmware from a real Windows machine or a linux one as soon as I have one available. I suspected that this was the issue and I tried to switch off and then on the board without success.

I am uploading the programs directly from Keil, but I have tried to upload also using nRFgo. Erasing the device or not. Always the same result.

What I expect is that different examples generate different services and characteristics, instead I see different peripheral's names but services and characteristics are always the same. This makes no much sense. In fact, the only part of nRF Toolbox that works is HRM.

RE: Faulty DK-52?

Keton — Sun, 17 Jul 2016 15:23:11 GMT

You will have problems updating J-link firmware where updater runs on virtual machine. During update process J-Link reboots and has to be manually attached to VM that's why upgrade fails at Waiting for emulator to attach... It's easiest to use real host with windows or linux to do this.

As for your other problems please describe in detail how you are uploading programs to your board and what expected result in your opinion should be.