> On Jun 24, 2016, at 12:35 PM, Christopher Collins <[email protected]> wrote: > > On Fri, Jun 24, 2016 at 11:59:49AM -0400, David G. Simmons wrote: >> The trouble arises at this point. No device is ever registered for >> the USB port, so using minicom (or screen, etc.) isn’t an option as >> there is not device. I’ve tried everything I can think of, from >> removing the STLINK jumpers to plugging in both USB (STLINK and USER), >> etc. but still no joy. > > Hi David, > > You'll need to make sure the FTDI virtual COM port driver is installed > on your machine (http://www.ftdichip.com/Drivers/VCP.htm). With the > driver present, plugging a USB cable into your computer should cause a > tty device to be added to /dev.
Thanks for the reply. The VCP is certainly installed on my computer. I’ve been working with FTDI stuff for a long time (I ported the FTDI SPI Library to Mac OS X a while back). I can see the usb com port for the NRF52, and for the STM32091C, but nothing shows up for the Discovery board. > > You have two options with the nRF52dk: 1) the virtual COM port, or 2) > the UART pins. You get the virtual COM port "for free" when you power > your board via USB. On OS X, this interface has a name beginning with > /dev/tty.usbmodem. Alternatively, to use the UART pins, you need to > connect a three-wire serial cable to the RX, TX, and ground pins on the > board. > > The virtual COM port is easier to set up, but the UART pins seem more > reliable. In my experience, the virtual COM port sometimes gets "locked > up"; it won't send or receive data. I should add that I don't know if > this is a problem with my computer, Mynewt, or the nRF52dk, so take it > with a grain of salt. > > Chris -- David G. Simmons (919) 534-5099 Web • Blog • Linkedin • Twitter • GitHub /** Message digitally signed for security and authenticity. * If you cannot read the PGP.sig attachment, please go to * http://www.gnupg.com/ Secure your email!!! * Public key available at keyserver.pgp.com **/ ♺ This email uses 100% recycled electrons. Don't blow it by printing! There are only 2 hard things in computer science: Cache invalidation, naming things, and off-by-one errors.
signature.asc
Description: Message signed with OpenPGP using GPGMail
