hrs malfunction when switch to sdk9.0

RE: hrs malfunction when switch to sdk9.0

halive — Sat, 15 Oct 2016 08:13:12 GMT

Thanks to Stefan! the problem is fixed when the ic is changed to rev 3.0.

RE: hrs malfunction when switch to sdk9.0

Stefan Birnir Sverrisson — Mon, 29 Aug 2016 15:56:19 GMT

Perhaps you can realize more what needs to be done with looking at this thread.

I usually have found it easiest when moving an application from one SDK version to another, to copy my custom code into a code template which is a part of the new SDK.

RE: hrs malfunction when switch to sdk9.0

halive — Fri, 26 Aug 2016 18:03:07 GMT

I I know that my IC is rev 1, but I used s110 6.0 for sdk 5, which is for rev 2 , and nothing bad happened. So I think , s110 8.0 will be ok for rev 1, only bad when some softdevice API specially for rev 3.

RE: hrs malfunction when switch to sdk9.0

halive — Fri, 26 Aug 2016 17:56:14 GMT

I repeat my problem as the following: It's a custom board, with sdk 5.0, I modified SDK_v5.1.0.36092\Nordic\nrf51822\Board\pca10001\s110\ble_app_hrs , modifications include: ble_stack_init->SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION, false); and IO pins are reconfigured. The projet's hex runs well in my board, I can connect and receive data with NRF TOOLBOX. Then I changed to sdk 9,\nRF51_SDK_9.0.0_2e23562\examples\ble_peripheral\ble_app_hrs\pca10028 , the same change was made and memory map was modified accordingly. I have no button on the board.I just see advertising led toggling rightly, but no device could be found on the phone.I donnot know how to get the bug. It has been two weeks, and I am really upset now. Pls give me just some advice, thanks!!

RE: hrs malfunction when switch to sdk9.0

halive — Thu, 25 Aug 2016 17:05:31 GMT

thanks.I tried what u said,i got no err loop. I compared the code between the two projs. The ble bond manage files show a lot of diferrences. In sdk 5.0, it is called ble_bondmngr.c, while in sdk 9, it is called device_manager_peripheral.c. Is there something I have to do to make it adapt to 51822? I tried to clear bond info in sdk 5 hrs proj, and I can connect 51822 normally, but in sdk 9, if I tried device_manager_init(true), the code will halt at some place, with no advertising led toggling. What can I get from the my try?

RE: hrs malfunction when switch to sdk9.0

Stefan Birnir Sverrisson — Mon, 22 Aug 2016 10:30:05 GMT

On the phone, use nRF Connect, if you aren't already.

Make sure you use compatible softdevice compatible with SDK 9 applications, i.e. S110 8.0.0, or S130 1.0.0, see the nRF51 compatibility matrix.

What if you debug through it [1] [2], do you see any errors returned in the main function?

See the correct RAM and ROM settings in any of the SDK 9 example projects for the seftdevice that you are using. IROM1 0x18000 0x28000, IRAM1:0x20002000 0x2000 looks like correct for S110 8.0.0 softdevice and nRF51 QFAA IC. Anyway, nRF51822 QFAAC0 is revision 1. You should replace that with nRF51822 revision 3.

RE: hrs malfunction when switch to sdk9.0

halive — Fri, 19 Aug 2016 23:51:54 GMT

I am not sure what you mean to say, in nrfgo studio, I see: nrf51822 QFAAC0(0X001d) Is that what u want?

RE: hrs malfunction when switch to sdk9.0

Wojtek — Fri, 19 Aug 2016 14:22:54 GMT

What chip revision you have onboard?