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

How to enable Jlink for custom board for nRF52832 DK

I am using nRF52832 DK. I have connected our custom board using Debug out and loading code is successful for custom board. I loaded radio_test code. Now I want to test the radio parameters. For that any settings required on the DK board to enable Jlink for custom board?????? In my system Jlink isi detected in com ports, but I am not getting Radio test in terminal. Please provide any settings required to enable Jlink for custom board.

Thanks in Advance.

Parents
  • Kristin, I've configured to other pins, whatever pins I can take out and configured those pins for UART. Now my UART is working. I am facing another problem. Please look into this query...

    Req: from the cap-sense board, different tap will be done by user (like 2 times tap, 3 three times tap etc). so the Bluetooth board (nrf52) will receive these taps as interrupt connected to a gpio configured from cap-sense board.

    Profile Used in Bluetooth board: Proximity .

    For the requirement stated,

    1. firstly, i have added the interrupt functionality (pin_change_int code) into Proximity profile for checking the no of tap received through the gpio as interrupt.

    2. secondly, when the tap is made from cap-sense side, the Bluetooth board will read the tap through the gpio assigned as interrupt.

    Bluetooth board will to do fast adv , slow adv and goes to sleep (separate function buttons_led_init is there in Proximity code), but when interrupt functionality is added to the proximity profile, Bluetooth device is not going to sleep. so what change in code should be done in order avoid this conflict.

Reply
  • Kristin, I've configured to other pins, whatever pins I can take out and configured those pins for UART. Now my UART is working. I am facing another problem. Please look into this query...

    Req: from the cap-sense board, different tap will be done by user (like 2 times tap, 3 three times tap etc). so the Bluetooth board (nrf52) will receive these taps as interrupt connected to a gpio configured from cap-sense board.

    Profile Used in Bluetooth board: Proximity .

    For the requirement stated,

    1. firstly, i have added the interrupt functionality (pin_change_int code) into Proximity profile for checking the no of tap received through the gpio as interrupt.

    2. secondly, when the tap is made from cap-sense side, the Bluetooth board will read the tap through the gpio assigned as interrupt.

    Bluetooth board will to do fast adv , slow adv and goes to sleep (separate function buttons_led_init is there in Proximity code), but when interrupt functionality is added to the proximity profile, Bluetooth device is not going to sleep. so what change in code should be done in order avoid this conflict.

Children
No Data
Related