Uploading code to ARM MCU's from OSX

[vishnubob]

Hi Paul (et al). Thanks for the Teensy project, the hardware combined with the libraries are an outstanding contribution to the maker community.

I would like to modify the command line tool to support uploading code to a Teensy3.0 on OSX. The documentation states this is only possible for Linux, and before I start digging through the code, I was wondering if you could explain why this is. Is there something special about the boot loader and/or the USB libraries on Linux?

[neonsoftware]

Hi vishnubob,

I can confirm you that it is possible to uploading code on Teensy3.0 on OSX as I do it. On the resources and in the code you see just Linux. Probably test support just for linux is because that is where the code is developed and tested and also maybe linux is where the share of cli users is higher. But this is just me guessing. I try to wrap up what you need more exactly.

[neonsoftware]

You probably do not need to modify the teensy_loader_cli repository. The code has a switch that divides the code depending on the operating system, and therefore it has a part of code for linux (using the library LIBUSB) and one part for OSX (using the native Apple API)

Now, IMHO, since Paul refers to use Linux, I think that the best thing to use the most maintained and updated code is to use the code that is meant for linux by using Libusb on your OSX.

[neonsoftware]

It is incredibly easy, if you do it with brew. Do you know brew ?

If yes

brew install libusb-compat

If no then you can check it out here http://brew.sh It installs packages on OSX. In particular with lubusb it is my experience that it does a great job, rather than having to download compile the libusb binaries manually.

(there are different libusb available, 0.1 and 1.0, but libusb-compat is exactly what you need as it gives you the interface of 0.1, which is used by the teensy loader code, but using the engine of the latest and more maintained and available 1.0 version. compat stands for compatibility in this case )

[neonsoftware]

Then in the Makefile you actually want to leave

OS ?= LINUX

and NOT OS ?= MACOSX

Because what OS ?= LINUX already does is setting for you:

• -DUSE_LIBUSB : which will make take the linux switch in the code that uses limbs
• -lusb : which will link to the limbs library that brew installed on your OSX

[neonsoftware]

If too verbose, here is a recap for you:

• clone the repo
• install brew and brew install libusb-compat
• make (leave OS ?= LINUX in the Makefile even if you are on Mac)

it should do give you the binary that you request, just tested on OSX Yosemite :D :+1:

[neonsoftware]

[the following is over the scope of your question question, please ignore if you are ok with the process above or other answers will solve your problem] If you do not want to handle the dependency of libusb your-self AND by chance you are a golang user (you have golang installed and set-up on your OSX) you can check https://github.com/neonsoftware/teeloader in that case by running

go get github.com/neonsoftware/teeloader

you get a compiled and created binary of the loader on linux, osx, and win (did not check on every every architecture) at $GOPATH/bin/teeloader-cli of your system

The project is just a quite bare golang wrapper around this repo that includes compilation and dependencies to provide cli binaries using the golang compilation system. Note :

• it is not constantly up to date with the state of this repo, it include some months ago for the last time, but it supports 3.0 and 3.1 for example
• I wrote it just for my self as I actually use all the three OS and never linked it anywhere, so prepare for feedback :smile:

[PaulStoffregen]

documentation states this is only possible for Linux, and before I start digging through the code, I was wondering if you could explain why this is.

Teensy 3.0, 3.1 and LC implement buffering, where a USB stall indicates not ready. Previously a stall indicated error. Now, an error needs to be treated as "not ready" and a retry-and-timeout approach needs to be used.

If you look at the 4 sets of code, you'll see the retry and timeout was added on the Linux libusb code. The Mac IOkit, Windows WIN32 and BSD versions simply abort on the first error, rather than implementing tries and a timeout.

[PaulStoffregen]

Hardly anyone uses this command line tool on platforms other than Linux, so reworking the other 3 sets of USB code is pretty much at the bottom of my priority list... meaning it'll probably never happen.