• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 62 subscribers
  • Views 2689 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 104529
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
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

MAC OS X error connecting PCA10028 and PCA10031 JLINK DISK.

cocoa

Hello Nordic guys, help requested !!!

Error while connecting to USB port the new development boards, DK and DONGLE.

Error is "OS X unable to repair JLINK disk". Action required : reformat disk.

Unable to write on this disk or copy a file (.bin .hex)

Is it safe to format the disk or there is a risk to damage the board ?

If you can not write to the disk, how do you copy the .bin file and change from mbed to JLINK and vice versa?

Jlinkexe from terminal runs.

SEGGER J-Link Commander V4.94c ('?' for help)
Compiled Oct 31 2014 20:08:55
DLL version V4.94c, compiled Oct 31 2014 20:08:48
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Sep 18 2014 11:53:15
Hardware: V1.00
S/N: *********** 
VTarget = 3.300V
Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
No devices found on JTAG chain. Trying to find device on SWD.
Info: Found SWD-DP with ID 0x*********
Info: Found Cortex-M0 r0p0, Little endian.
Info: FPUnit: 4 code (BP) slots and 0 literal slots
Cortex-M0 identified.
Target interface speed: 100 kHz

Thanks,

-c

  • 0

    There seems to be an issue with the Segger drivers on OS X Yosemite. You can try to install the latest Segger driver from Segger.com. Please let me know if the problem persists.

  • 0 in reply to Vidar Berg

    Hi Vidar, updated to last version but problem persists.

    JLINK disk is locked as Read-only file system.

    image description

  • 0

    This is a known issue with the MBED driver which is already being looked at (github.com/.../69). There's a workaround on that thread, but it's not awfully stable.

    I also reported it to Nordic last week and they're looking at it and so is Segger. It's going to need a new build of the firmwares (both MBED and Segger) when the patch is done.

    As for the rest of your questions - since the board comes with JLink OB on it and that works fine with JLink in the same way the previous eval and dev boards did, you can continue to work that way, just unmount the drive and ignore it. If you really want to use MBED then use a windows box to put the firmware on and use the workaround to remount the drive and copy your .bin file to it. I really wouldn't though, I'd stick with the JLink debugging, it's way better anyway.

    Update 26 November 2014

    The latest beta from Segger (V4.95c) contains new firmware. Just running JLinkExe with the usual arguments should update your board to it. The JLINK partition now mounts correctly, not that I've tried using it. Currently however if you boot with the BOOT/RESET key held down to get the BOOTLOADER partition, that still fails in the same way. I've reported that to the person at Nordic who's been helping me and hopefully that will get back to Segger.

    Still waiting on MBED to apply the patch and release, but at least with the latest from Segger you can JLink Debug (as you could before) but without OSX moaning and complaining every time you plug the board in. I assume dumping a .bin file on the JLINK partition will also flash the chip but I'm rather too scared to find out.

Related