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

Soft device enable and disable - [DFU] disconnected by the remote device

AliMahmood123

Hello all

I am facing a very strange issue, already searched the forum but didnt find anything like it.

Okay so I can get DFU to work. For our custom application we have to disable the soft device for some time for sensor acquisitions and re enable it at a later time for OTA upgrades.

I simply use nrf_sdh_disable_request() to de initialize the soft device successfully, which it does.

I later re - enable soft device using the standard ble calls in example code:

ble_stack_init();
    peer_manager_init();
    gap_params_init();
    gatt_init();
    advertising_init();
    services_init_2();
    conn_params_init();   
     
    //Start execution.
    application_timers_start();
    advertising_start(erase_bonds);

BLE gets initialized successfully, device is advertised and connects to as well. The problem is in DFU. When I attempt DFU, it keeps getting stuck into trying to switch to bootloader, repeatedly giving
"[DFU] disconnected by the remote device"

The logs then try to open the firmware file again, re initiating the process but nothing happen. I have spend quite some time on this and hit a blocker. Any help is appreciated. There must be a step I am missing during re-enabling the soft device

  • 0

    Hello,

    "[DFU] disconnected by the remote device"

    Where is this message printed? Is it in the mobile app on iOS or Android? And have you tried to debug the FW app to see if it hangs or enters the app_error_fault_handler() function?

    Okay so I can get DFU to work. For our custom application we have to disable the soft device for some time for sensor acquisitions and re enable it at a later time for OTA upgrades.

    Sure you really need to disable the Softdevice for this? The only case I can think of where it makes sense to disable the Softdevice is when there is a need to stop the LF clock. 

    Best regards,

    Vidar

  • 0 in reply to Vidar Berg

    Hi Vidar.
    I read an article here which said that in order to disable a service and re-enable it later, I need to disable the whole soft device as the services at start up become part of the "stack"

    if there is another way, please let me know. Basically I just want to disable the DFU service and show that service at some other point

    Also, this message appeared on the android app

  • 0 in reply to AliMahmood123

    Hi,

    Yes, that is correct, you can't remove services that have already been added. So there isn't really any way around this if you need the Buttonless DFU service to be "hidden". Could you have used the same mechanism you use to enable the buttonless service to just jump directly to bootloader DFU mode instead?

  • 0 in reply to Vidar Berg

    Yes but I just need it again at a later stage. For that I need to disable and enable soft device. That's only going to happen once though. Can you please guide me on that instead?

  • 0 in reply to AliMahmood123

    Sure, but I need a bit more info to go on. Have you done any debugging of the app to see if it crashes, or if it successfully reaches the  ble_dfu_buttonless_bootloader_start_finalize() call where the program is reset into the bootloader?

Related