> On Jun 27, 2016, at 1:08 PM, Kevin Townsend <[email protected]> wrote: > > > On 27/06/16 19:05, David G. Simmons wrote: >> Will, >> >> Thanks! One issue was certainly that I was using the PDK instead of the DK, >> I’ll add that to the documentation as there was no mention of this. And >> while I have been known, in the past, to get TX and RX backwards, that is >> not the case here. >> >> That being said, I’m still getting nothing, even on the scope where, no >> matter what was hooked to what, I would still expect to see the Tx pin >> toggling as data is written to it. Still flat-lined. I did try hooking up >> DTS and CTS — even though they’re not mentioned in the tutorial — in hopes >> that I might get some signs of life out of it that way, but still no joy. > > CTS on one side goes to RTS on the other side, and similar for RTS which goes > to CTS. Try switching the two lines? You may also need to enable HW flow > control in your terminal emulator depending on what you are using. >
Yup, got that too. The interesting bit is that both the Tx and Rx pins coming off of the NRF52 are flat-lined on the scope, which indicates that the board is unable to, or unwilling to, properly use those pins for some reason. dg -- 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
