This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Timer and Multirole for PCA20006

Hello, I have implemented the code below for my project based on switching central and peripheral role in S130. The code works fine on the Devkit PCA10028 but on porting it to PCA20006 I noticed some bugs in the final steps.

  • Without line 195 and 271 to 310 everything seems to work well on the Beacon, the LED is toggling in the right frequency. However after some time the frequency seems to roughly double. I cannot solidly quantify this observation.
  • Adding the above lines, the beacon does not switch on any LED at all. Only in debug mode the LEDs are switched on and the timer handler is entered. It seems there is a problem with my timer interrupt handling, but I dont know what.
  • I Am unsure if this code will be capable of handling 120 interacting nodes (well, mostly only up to 20 should be in close proximity)

Does anybody have an idea what could be my problem when porting to PCA20006? I am also grateful for any ideas to improve the code.

edit1: attached file instead of code: Corrected line numbers to reflect recent changes, as I corrected functionality. edit2: For completness I attached to whole (ecplise) project folder. Putting it into /central_and_peripheral/experimental/ should work. The makefile is currently set for PCA20006.

edit2: attached updated code

edit3: final code

Parents
  • Hello Terje. You are right, I still have a lot of safeguards to implement. I implemented a couple over the weekend and fixed some minor bugs in the functionality (updated atteachment). Now on the DK the code is behaving exactly as it should.

    On the beacon however something is wrong. I oberserve the following:

    • If I do not call scan_start() everything seems to work alright. The advertisment is correct and updates to show the right time counter for a long time. No LEDs are blinking (as intended).

    • If I switch on scanning by calling scan_start I oberserve different behaviour. If I do a cold start, i.e. the beacon was without power for several minutes (~30), at the start everything looks fine, i.e. same behaviour as before. After some time (varying, observed up to 350 s) the LEDs flash and the counter is reset. The counter increases again and is reset at shorter and shorter intervals.

Reply
  • Hello Terje. You are right, I still have a lot of safeguards to implement. I implemented a couple over the weekend and fixed some minor bugs in the functionality (updated atteachment). Now on the DK the code is behaving exactly as it should.

    On the beacon however something is wrong. I oberserve the following:

    • If I do not call scan_start() everything seems to work alright. The advertisment is correct and updates to show the right time counter for a long time. No LEDs are blinking (as intended).

    • If I switch on scanning by calling scan_start I oberserve different behaviour. If I do a cold start, i.e. the beacon was without power for several minutes (~30), at the start everything looks fine, i.e. same behaviour as before. After some time (varying, observed up to 350 s) the LEDs flash and the counter is reset. The counter increases again and is reset at shorter and shorter intervals.

Children
No Data
Related