This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

S130 Testing

I want to use the s130 softdevice because we need the broadcaster/observer mode at the same time. I bought the nRF51 Dongle and the beacon Device.I use the Keil IDE, debugging works until i hit a breakpoint. After that I think the programm doesn´t work correct.

  1. Is this a normal behavior?

For our project we don´t want to connect the BLE devices. We want to make the whole communication with abvertising messages. Example

Device A advertises Device B receives the advertising message Device B sends a advertising message Device A receives the advertising message

  1. Is it possible to do this with the Softdevice s130?
  2. Which of the example files for Programm Application will be the right choice?

Thanks in advance!

Parents
    1. Yes this is a normal behavior, after you hit the breakpoint, you halt the CPU but the internal timers in the nRF51 still are running and when they expire will have interrupts handling pending. When you continue from your breakpoint, the stack will notice the timers have strange values and behaves in a unpredicted way. So the point is once you hit your breakpoint we cannot expect the softdevice to work normally.

    here are few answers on this

    devzone.nordicsemi.com/.../ devzone.nordicsemi.com/.../

    1. In short you want devices A and B keeps swapping between central and peripheral roles. This should be possible. This is one of the main uses cases of S130. I think the closest app i can find is nRF51_SDK_8.0.0\nRF51_SDK_8.0.0_5fc2c3a\examples\ble_central_and_peripheral\experimental

    In this experiment you can atleast see how you can manage state machine for your roles on the device depending on incoming events.

    Update:

    S130_Sample_App.pdf

Reply
    1. Yes this is a normal behavior, after you hit the breakpoint, you halt the CPU but the internal timers in the nRF51 still are running and when they expire will have interrupts handling pending. When you continue from your breakpoint, the stack will notice the timers have strange values and behaves in a unpredicted way. So the point is once you hit your breakpoint we cannot expect the softdevice to work normally.

    here are few answers on this

    devzone.nordicsemi.com/.../ devzone.nordicsemi.com/.../

    1. In short you want devices A and B keeps swapping between central and peripheral roles. This should be possible. This is one of the main uses cases of S130. I think the closest app i can find is nRF51_SDK_8.0.0\nRF51_SDK_8.0.0_5fc2c3a\examples\ble_central_and_peripheral\experimental

    In this experiment you can atleast see how you can manage state machine for your roles on the device depending on incoming events.

    Update:

    S130_Sample_App.pdf

Children
No Data
Related