[riot-devel] iotlab-m3 and recent OS X update

Thomas Eichinger thomas.eichinger at fu-berlin.de
Fri Oct 2 14:39:34 CEST 2015

Dear list,

I wanted to share my findings regarding flashing an iotlab-m3 board from
OS X 10.11.

The good thing, the 3rd party FTDI driver is not needed anymore. Apple 
a FTDI kernel extension for some releases already but I didn't find them 
until this release. So, when connecting an iotlab-m3 board to your Mac 
having the old FTDI driver loaded you should already be able to connect 
to the
/dev/tty.usbserial-xxxxxB device with by executing

`BOARD=iotlab-m3 PORT=/dev/tty.usbserial-xxxxxB make term`

The bad thing, flashing fails as the Apple driver also assigns 
to the first serial device on the board and openocd can't claim it. I 
successfully prevent it from doing so by these steps:

DISCLAIMER: backup first and you do this on your own reliability.

1. `sudo nvram boot-args=kext-dev-mode=1`
We will change the kext's Info.plist so the signature will not be valid 

2. Boot into recovery mode by holding cmd + r during start up

3. In recovery mode open a terminal and execute
     `csrutil disable`
to turn off System Integrity Protection.

4. Restart into normal mode an use your editor of choice to edit the 
and comment out the <key> and <dict> entries for "AppleUSBEFTDI-6010-0" 
with <!-- ... -->
See the snip below.

5. Restart into recovery mode again and enable System Integrity 
Protection again by
	`csrutil enable`

6. Restart into normal mode and you should only see one remaining 
device. Flashing the board should work now.

If somebody found an easier approach, please let me know, else, good 

Best, Thomas

The snip:

More information about the devel mailing list