9 years, 5 months ago.

Can not write binaries into 'NUCLEO' disk in Mac OS X 10.10(Yosemite)

I already upgrade firmware to 'V2.J23.M6', but disk can not be written. When I connect f411re into my mac, it said that 'OS X can't repair the disk "NUCLEO."' and the disk was read only. What's wrong or missing?

Question relating to:

ST
A world leader in providing the semiconductor solutions that make a positive contribution to people’s lives, both today and in the future.

I have seen in the last days reports that the same is for other boards which are using mbed cmsis dap interface. We will fix it and report here once done. Thanks for reporting

posted by Martin Kojtal 23 Oct 2014

7 Answers

8 years, 12 months ago.

Here is the link to the V2.J23.M10 firmware of the Nucleo board to support Yosemite. I have updated it with a windows computer and from my Mac (both solutions work).

Regards

9 years, 4 months ago.

I have the same issue on my just-arrived brand-new Nordic nRF51 dev board and nRF51 Dongle.

Is the same patch for the other boards going to be a fix for this too or should I report it separately here or to nordic or to whom?

Come to that, when there is a patch, how am I going to apply it (new to MBED, these are the first nordic boards I have which support it).

9 years, 2 months ago.

This issue is 2mo old, is there still no solution?

9 years, 1 month ago.

Same issue here. What is the status? Is there a workaround?

9 years, 3 months ago.

I have same issue on my NUCLEO-F103RB, system message "can not be written" when I plug in USB cable, after I upgraded to Yosemite (10.10.1).

by the way, In OSX 10.9.4 everything is ok.

Tedd Okano has come up with a workaround which you can find documented here while you wait for the final fix.

I hope that helps,

Adam

posted by Adam Green 09 Dec 2014
9 years, 5 months ago.

Me too. After I upgraded OSX to Yosemite, I cannot write binaries to Nucleo. The serial port is working though.

9 years, 5 months ago.

The issue has been recognized and raised here https://github.com/mbedmicro/CMSIS-DAP/issues/69 . We are in the process of fixing it. Please sit tight and we should have a fix out soon.

-Austin Team mbed

Are you guys working on this for the Nucleo line, or is ST responsible for making the changes to the ST-LINK/V2-1 debugger/programmer? I don't see any ST-LINK related code in the repo https://github.com/toyowata/CMSIS-DAP/tree/refactor and was curious if there was any work being done to fix this issue on the Nucleo boards.

posted by Christopher Wilson 22 Jan 2015