I know I'm using the correct port and cable because I'm able to load new images using newt. I bet my problem is the USB device is mapped into the virtual machine that's used to run docker containers.
On Wed, Jun 29, 2016 at 10:00 PM, Brian Giori <briangi...@gmail.com> wrote: > First make sure you're connected to the programming microusb port and not > the native one. If you can't see a new tty look for a cu. I have heard of > some microusb cables providing power only so if all else fails try a new > cable. > > On Wed, Jun 29, 2016 at 8:39 PM, todd mitton <mit...@runtime.io> wrote: > > > What /dev device do I use? I don't seem to get any new tty to talk to. > > > > Thanks, > > -Todd > > > > On Wed, Jun 29, 2016 at 3:15 PM, Gavin Jefferies <ga...@vmbed.com> > wrote: > > > > > Cool! Thanks Brian. > > > -G > > > > > > On Wed, Jun 29, 2016 at 3:08 PM, Brian Giori <briangi...@gmail.com> > > wrote: > > > > Hey everyone, > > > > > > > > I recently changed the Arduino Zero/M0 Pro's default serial > connection > > to > > > > use the micro USB debugging port rather than the RX-0 and TX-1 pins. > > > > > > > > Here's the change: > > > > https://github.com/runtimeinc/mynewt_arduino_zero/pull/2 > > > > > > > > Now you can ditch that FTDI cable :) > > > > > > > > Brian > > > > > >
