Cannot run a precompiled example hex file

[junma]

Hi all,
I have one PCA10040 board, and want to start to download and run some examples while reading the on-line documentations.
In section "Running precompiled examples ", I see the description of copy and drag an existing hex file to the standard USB drive. I've tried several times to copy and drag hex files to the USB drive, however, each time after I dragged to the drive, seems the USB drive will reset and delete my dragged hex files. Attached is the capture of the USB drive.

Is there any procedures that I missed? Hope someone can help me about this issue. Thank you in advance!

Best regards.
junma

[RK]

the drive doesn't delete the file, it uploads it to the chip for you, after it's uploaded you will no-longer see it on the drive. The drive is just for transport.

[junma]

Hi RK,
Thank you for your reply! But the problem was that I didn't see the effect out from the board, even I pressed the "Reset" button or power-off then power-on the board.
So I thought that the hex file was not flashed to the chip.

[Scott]

I am suffering the same miserable out-of-the-box experience here with 2 brand new nrf52-dk boards: PCA10040 V1.1.1 2016 37 682770908 & 682488524

Please help me at least get something that should be so basic working, as this is only the tip of the iceberg (attempting to download and debug from the example IAR projects doesn't work either, but that is of course a separate thread).

Note that the JLINK removable drive enumerates, I drag and drop a sample .hex, progress show incrementing to 100%, drive momentarily disappears and then reappears, but nothing - no BLE advertisements, no LEDs, etc.

Plugging in the dev board enumerates this COM port on Windows10 Pro: JLink CDC UART Port

[Scott]

I found the issue: windows10 pro account type.

I use a windows 10 pro standard account for myself and this is where I have worked and developed, using all kinds of tools, compilers, ide's, and so forth. As usual, I installed all of the new Nordic stuff from this account, entering the Admin password when necessary. And below you see the problems encountered - bizarrely, things enumerated and pretended to work with no errors or warnings or issues with device manager, etc. Actually, it was worse than bizarre ... crazy making, really.

I wish I could attach screen shots where you can clearly see that for the standard account, the nRF52-DK enumerates just fine and pretends to act ok (including the drag and drop of a precompiled hex, but no action), yet nRFgo studio never sees it (I did not know what to look for in nRFgo studio, so I didn't notice what was missing).