MCUmgr Error: ATT request failed: input channel closed: io: read/write on closed pipe

Greetings!

We have been using an nRF52840 Development Kit for a while now and have been performing FW updates OTA (between the same 3 FW images, cycling and updating between them many times) by using the CLI commands of MCUMgr such as:

mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Feel Gen 2 - 53615210' image list

These updates were performed smoothly with no issues and the nRF52840 was always responsive (always between the same three images).

This DK was stored away for two weeks and was revisited today to perform an update once again ( no one had access to it or changed its FW, I am the only person who worked on this and found it intact as expected )

Now after trying to perform the same MCUmgr commands(for the same three images) as I had been doing in previous weeks where they worked without issues, I am getting the following error message:

Error: ATT request failed: input channel closed: io: read/write on closed pipe

However, when performing the updates using the nRF Connect Android app they are performed correctly.

Nothing changed in the FW, DK or the PC being used to run the mcumgr commands. What could cause this behavior? 

Nothing changed in the procedure, it was for a demo I had prepared a few weeks prior and now that its time to perform the demo its not working. I have confirmed that everything is exactly the same as two weeks prior. The only thing that changed was that two weeks passed.

Thank you for your time and I look forward to hearing from you!

Best regards,

Stavros

  • Hi Stavros,

    I don't recall seeing this error before, but I suspect it's coming from the Bluetooth stack. Are you running Linux? Could BlueZ have been updated in the meantime? Either way, if you have a BT HCI dongle available (remember to pass the new hci interface the mcumgr command), I suggest trying it to see if you get the same error. Other things you might try is to reboot the PC, run the command as root, or ensure there are no other active BT connections on your system when attempting DFU.

    Best regards,

    Vidar

Related