Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Receiving Garbage Over BLE UART When Using "SAADC UART Timer Driven Scan Mode"

I am working with the BL652 Module from Laird, and with Keil 5, using a ST Link SWD programmer clone.

I am using the ble_app_uart_timer_driven_scan_mode from the ADC examples on github: https://github.com/NordicPlayground/nRF52-ADC-examples

I can connect to the device using the nRF Uart v2.0 app, receive senseless data:

I am not sure what could be causing this. I did set the program to be scanning analog 0, 1, 2, 3, rather than what it was downloaded as. 

Could the baud rate be off? I believe the reference is correct, which is VDD (3.3 V). When I use a voltmeter, I am reading 0 volts on AIN1, 2, and 3, and ~ 1 V on AIN0.

Thank you for the help!

Parents Reply Children
  • Martin, thank you for the reply, and sorry for the delay.

    I get the same result when I use the nRF Toolbox app. 

    The "ble_app_uart_timer_driven_scan_mode"  example is unmodified EXCEPT for that I changed the four pins read in default to four different analog pins. (0-3)

    I can connect to the device normally when the "ble_app_uart" example is loaded, but I am not sure how monitor the com port -- no port is created by the ST Link programmer, that I can tell.

Related