• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 67 subscribers
  • Views 1500 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 103923
Options
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

Quick help required ble_uart_app nrf51822 rx issue

Aashish Patel

Hi All

I am trying to verify UART on one of our custom boards having nrf51822. We have only one uart which we are using to forward the data received over BLE.

I am using ble_app_uart example to test UART functionality and Nordic MCP and UART app on phone.

We have physically shorted uart tx and rx pins (disabled flow control)

So theorotically whatever data is sent to tx should come to rx and we should be able to see it as notification on phone app.

But we are not able to see any value for Rx characteristic. I tested with writing more than 20 bytes to Tx characteristic

Parents
  • 0

    After digging deeper we found out that Interrupt register of nRF51822 was not getting set even though we are enabling it in code.

    Also the values of CTS RTS were 0xFFFFFFFF

    So we moved the CTS and RTS pin config setting outside of if(hwfc) {} block (Even though we are not going to use it we just assigned them to some idle GPIO)

    Now the interrupt register was getting setting set and we got the rx working.

Reply
  • 0

    After digging deeper we found out that Interrupt register of nRF51822 was not getting set even though we are enabling it in code.

    Also the values of CTS RTS were 0xFFFFFFFF

    So we moved the CTS and RTS pin config setting outside of if(hwfc) {} block (Even though we are not going to use it we just assigned them to some idle GPIO)

    Now the interrupt register was getting setting set and we got the rx working.

Children
Related