Hi Paul,
I'm curious, what nrf51 are you using exactly? \-- **Marco Ferreira** Founder / CTO [email protected] [www.altitude.co](https://link.nylas.com/link/d8alirm8yqo9t58fef8uienha/local- 1612f713-e9be/0?redirect=http%3A%2F%2Fwww.altitude.co%2F&r=ZGV2QG15bmV3dC5pbmN 1YmF0b3IuYXBhY2hlLm9yZw==) DISCLAIMER: The information contained in this e-mail is confidential and may be legally privileged. If the reader of this message is not the intended recipient you are hereby notified that any use, dissemination, distribution, or reproduction of this message is prohibited. If you have received this message in error please forward this message to [[email protected]](mailto:[email protected]) and delete all copies of this message.  On Aug 29 2016, at 7:51 pm, [email protected] wrote: > All, > > I have been adding split image to ble-nano. > > What I found what that there is something happening with MK20 USB daughter board. When I have the BLE module plugged into the daughter module, I am not able to use newtmgr commands with slinky. > > However, when I unplug the module and wire power/gnd/tx/rx to the board (with a remote serial port), I am able to use newtmgr. > > I am thinking there are two issues. > > 1\. It seems like there are some serial characters coming out the board that is messing with newtmgr: "$$$10950203ADB91E7D92DF9FD5" is an example. 2\. It would seem that when I make/break a serial connection to the MK20 via USB, it is resetting the nrf51 via the debug pins ( the device. Since newtmgr does this on every command, this may be causing it not to work. > > Anyone have any knowledge about this? > > Paul
