This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF51822 mbed bug with Mac OSX Yosemite

Mac OS X 10.10 Yosemite rejects the format of the file system and puts it in a read only mode.

This issue was raised last October 24, 2014 at https://github.com/mbedmicro/CMSIS-DAP/issues/69 and is still open.

Work-arounds are available at https://developer.mbed.org/users/okano/notebook/mbed-on-yosemite/ but are not 100% reliable.

All mbed boards are affected, including Nucleo, Freedom, RedBearLab.

This is a tricky and potentially endless issue, as both the boards manufacturers and the OS developers can blame each other.

Any official answer from Nordic for the mbed-enabled boards?

Parents
  • Thank you for your answer. As you fully understood the question, my purpose was to raise awareness about the lack of a quick official answer from ARM, mbed and the vendors.

    IMHO, mbed developers are focused on the next big thing, mbed OS 3, and no longer on the mbed SDK available today.

    Copying an executable on the mass storage device of the board is a key feature of mbed. So let's hope next version of Mac OS X 10.10.3 fixes this issue for good.

Reply
  • Thank you for your answer. As you fully understood the question, my purpose was to raise awareness about the lack of a quick official answer from ARM, mbed and the vendors.

    IMHO, mbed developers are focused on the next big thing, mbed OS 3, and no longer on the mbed SDK available today.

    Copying an executable on the mass storage device of the board is a key feature of mbed. So let's hope next version of Mac OS X 10.10.3 fixes this issue for good.

Children
No Data
Related