Cool.  Works now.  The cause of my problem was VirtualBox mapping the
device into the VM used by docker.

On Thu, Jun 30, 2016 at 10:24 AM, [email protected] <[email protected]> wrote:

> The Edbg serial port build into the arduino zero debug is a cdc serial
> port (not FTDI). Linux and Mac should have support but Windows requires
> some additional drivers
>
> > On Jun 30, 2016, at 10:20 AM, marko kiiskila <[email protected]> wrote:
> >
> > Hi Todd,
> >
> > my MAC is using USB CDC driver for this, and it names the tty’s as
> > /dev/tty.usbmodemXXX.
> >
> >> On Jun 30, 2016, at 10:01 AM, todd mitton <[email protected]> wrote:
> >>
> >> 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 <[email protected]>
> 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 <[email protected]>
> 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 <[email protected]>
> >>>> wrote:
> >>>>
> >>>>> Cool! Thanks Brian.
> >>>>> -G
> >>>>>
> >>>>> On Wed, Jun 29, 2016 at 3:08 PM, Brian Giori <[email protected]>
> >>>> 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
> >
>

Reply via email to