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

nRFToobox on Android not recognizing changes in application type running on Nordic pcb

Today nRF Toolbox App on my Android 5.0 phone is only recognizing HRM code running on my nRF5182-mkit, not other examples.

  • Today nRFToobox and nRFUART2.0 Apps both report "The Device Does not have the required services" when I try anything other than HRM code yesterday and today.

  • Two days ago it was allowing me to easily switch between code on the mkit, but then something changed. It was about same time as the latest nRFToolbox update on playstore. Funnily enough it was just after the previous Nordic updates on playstore that this all started working, as two weeks ago it wasn't working with similar issue. Did a fix get undone?

  • nRF-MCP App is shows changes in Device Name when I run other sample code on my mkit (Thermometer, UART Loopback, HRM, etc.)

  • I tried wiping the cache in the Android 5.0 phone, no effect

  • I can capture with nRF-MCP or Sniffer if that will help (just tell me what you need, I'm not very familiar with either of those)

Any help appreciated! Paul

Parents
  • Possibly:

    • If not properly disconnect then App data in Android may be confused.
    • This may be a bug in latest nRF-MCP/nRF-ToolBox for Android (Released ~20141209?)

    Try:

    • Open nRF-MCP in Android, select device, connect, disconnect (Ensure disconnect happens)

    Note:

    • UART device doesn't seem to offer disconnect (nRF51 sample code may need tweak)
    • May need to load a 3rd sample, disconnect from that, then try new sample.

    Still testing. This method of using nRF-MCP to disconnect between sample type changes (HTM, HTM, UART) does appear to be working, consider it a "work around" for now.

Reply
  • Possibly:

    • If not properly disconnect then App data in Android may be confused.
    • This may be a bug in latest nRF-MCP/nRF-ToolBox for Android (Released ~20141209?)

    Try:

    • Open nRF-MCP in Android, select device, connect, disconnect (Ensure disconnect happens)

    Note:

    • UART device doesn't seem to offer disconnect (nRF51 sample code may need tweak)
    • May need to load a 3rd sample, disconnect from that, then try new sample.

    Still testing. This method of using nRF-MCP to disconnect between sample type changes (HTM, HTM, UART) does appear to be working, consider it a "work around" for now.

Children
No Data
Related