Hey Paul, you seem like a very busy guy here. My cable arrived from you today (thanks very much) and I've finally had time to play a bit with the Teensy-3.1.
After the usual blinky test, I then immediately wanted to try out the usb serial library support, since this is a convenient way to get debugging feedback from the arm side. Documentation that exists for that, seems to be out of date WRT the Teensy-3.1. For example, the documentation suggests that you should call usb_init(). Well... after an hour+ of trying to figure out why my example usb serial program wouldn't work (I was getting "Resource Busy" on the Mac OSX /dev/cu.usbmodem-XXXXX side), I discovered that if I left out the usb_init() call, things suddenly worked. Hmmmm... it turns out this now happens as part of the Teensy initialization (from the ResetHandler -> _init_Teensyduino_internal_). Yet the documentation I saw, suggested this was necessary.
I don't want to pick on the documentation, but rather suggest perhaps that a wiki.prjc.com might help in documentation maintenance/contributions. This is always a struggle as software and hardware goes through continual change. However, if members were able to contribute wiki-style, this may help the community at large. I am willing to contribute, as I am sure, many others would also (judging by their own contributions).
Thanks, Warren
After the usual blinky test, I then immediately wanted to try out the usb serial library support, since this is a convenient way to get debugging feedback from the arm side. Documentation that exists for that, seems to be out of date WRT the Teensy-3.1. For example, the documentation suggests that you should call usb_init(). Well... after an hour+ of trying to figure out why my example usb serial program wouldn't work (I was getting "Resource Busy" on the Mac OSX /dev/cu.usbmodem-XXXXX side), I discovered that if I left out the usb_init() call, things suddenly worked. Hmmmm... it turns out this now happens as part of the Teensy initialization (from the ResetHandler -> _init_Teensyduino_internal_). Yet the documentation I saw, suggested this was necessary.
I don't want to pick on the documentation, but rather suggest perhaps that a wiki.prjc.com might help in documentation maintenance/contributions. This is always a struggle as software and hardware goes through continual change. However, if members were able to contribute wiki-style, this may help the community at large. I am willing to contribute, as I am sure, many others would also (judging by their own contributions).
Thanks, Warren