Another Workaround for the "Yosemite Problem"
Mac OS X 10.10 (Yosemite) currently does not properly handle HDK-based mbed devices. When we connect such an mbed (e.g., FRDM-KL25) to a Mac running Yosemite, a dialog saying "OS X can't repair the disk ..." appears and the device is mounted in read-only mode. Fortunately for us, Okano-san already brought out an easy-to-use droplet that helps copying files into such devices.
Here is another workaround inspired by Okano-san's droplet; a launchd daemon version. The daemon continuously watches the file system of your Mac and automatically fixes the mode of an mbed to be writable when the device is connected. This also enables direct drag & drop copying of files into the mbed drive.
You need to be able to execute
sudo for setting up this daemon.
sudo operations may cause serious damage to your system.
The author tested this with only a limited number of mbeds and Macs.
Please use this at your own risk.
- Download the package
- Unzip the package and execute install.sh as root
sudo sh install.sh
- Execute uninstall.sh as root
sudo sh uninstall.sh
- Connect your (HDK-based) mbed devices. You can ignore the warning dialog by pressing "OK".
- Now your mbed drives are writable and you are ready to copy your executables to them. Drag-and-drop copying is also possible.
I've briefly tested that this daemon works with the following mbed platforms.
- NXP mbed LPC1768 (this device works well without the daemon)
- NXP LPC00-MAX
- Freescale FRDM-KL25Z
- Freescale FRDM-KL46Z
- Freescale FRDM-K46F
- ST Nucleo F401RE
- Nordic nRF51822
- Switch Science mbed HRM1017
I'm thankful to Okano-san who reported that this works with the following platforms.
- Switch Science mbed LPC824
- Switch Science mbed LPC1114FN28
The daemon continuously watches the file system of your Mac and start the following Python script every time a disk is mounted. If the disk is mounted on /Volumes/MBED* (or /Volumes/NUCLEO*) and is read-only, the script re-mount it with appropriate settings.
import re, subprocess p = re.compile(r'(/dev/\S+) on (\S*(MBED|NUCLEO).*) \(msdos.*read-only.*\)') for r in p.finditer(subprocess.check_output('mount')): (d, m) = r.group(1,2) subprocess.check_call(['umount', d]) subprocess.check_call(['mkdir', m]) subprocess.check_call(['mount', '-w', '-o', 'sync', '-t', 'msdos', d, m])
The code is also available at https://github.com/wtakuo/mbedremounter.
6 comments on Another Workaround for the "Yosemite Problem":
Please log in to post comments.
The mount point for mbed drives is fixed to /Volumes/MBED. This means that you cannot connect two or more mbeds at once.
Here is an improved version of the script:
A ruby script that will remount all read-only MBEDs
And the corresponding plist