Is it possible to prevent the nrf51dk to display as a mapped drive?

[Ricardo Rodrigues]

I am currently using one nrf51dk board that is automatically showing itself on my computer as a mapped storage device with the label "JLINK".

This is actually a board I borrowed from someone, after i bricked my own, so that I can continue working until a new board arrives.

But in the meantime, there is something that is bothering me: the nrf51dk board I inadvertently bricked was not doing this. It was NEVENR being mapped as "JLINK", but instead would only map itself as "BOOTLOADER" hen running the "START+RESET" routine.

Because of how the previous board behaved, I assume there is a way to have the new board also behave the same. Anyone knows how to achieve this?

I have been using linux (same computer with the 1st board and now with the borrowed one), but I don't think that that is relevant, as it looks like either some configuration on the board, or maybe a different bootloader or softdevice?

On the first board I actually was using mbed studio at start, before I figured out how to put SDK12 working with the nrf51dk board, so maybe there was something that mbed studio did to disable this JLINK storage device mapping?

[tesc]

Hi,

I see that you have a private case as well, where you mentioned with the old (malfunctioning) board you had been previously using mbed? Then you had probably at some point reprogrammed the interface MCU with other firmware than the J-Link firmware, and it would either appear as MBED or, depending on particular firmware and configuration, not appear at all. That might be one reason for not appearing as JLINK.

Another reason is, it is possible to configure the J-Link firmware to not register as a Mass Storage Device (MSD). Then it will not appear as anything. For that you use the program "J-Link Commander", which is part of the Segger J-Link Software and Documentation Pack.

To disable MSD, use the command "MSDDisable" (without the quotes) from J-Link Commander.

To reenable MSD, use the command "MSDEnable".

Since you are borrowing this board, I suggest that if you choose to change the configuration (e.g. disabling MSD), you let them know, and you make sure to reenable it before handing it back to them.

Regards,
Terje

[Ricardo Rodrigues]

TLDR: Thanks! Worked perfectly.

I am not sure what exactly happened with the old board when I used MBED with it, since it was already a long time ago. It is completely possible that MBED had at some point overwritten the J-Link firmware.

What I am sure about is that for the last 2 months I was using Segger Embedded Studio and the DK was not mapping itself at all when connecting to USB. It was only being mapped as BOOTLOADER when running the START+RESET procedure.

As an additional note, and regarding your recommendation to not make changes on the board I had borrowed,it ended up not being needed. I got a new board for myself yesterday issued the MSDDisable command on that one instead.

I wonder though, why are MSDEnable/MSDDisable not shown when running "?" for help command on the J-Link Commander. That would have avoided my post, and gets me thinking what other commands are also not displayed that could eventually be useful. In any case, please don't take this as criticism, but rather as constructive recommendation.

Many thanks for your help.