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. dg > On Jun 27, 2016, at 12:43 PM, will sanfilippo <[email protected]> wrote: > > David: > > I am not sure if this is the issue but it could be you are using the nrf52pdk > bsp as opposed to the nrf52dk bsp. The PCA version on top of the board will > tell you which one you should be using. The pdk is 10036 and the dk is 10040. > If you turn the board over you will see that pins 5,6,7,8 and RTS, TXD, CTS > and RXD (respectively). Of course, you gotta flip ‘em when you connect your > serial cable to them but I am sure you know that… > > Anyway, let me know if that solves your problem (or not). > > >> On Jun 27, 2016, at 9:34 AM, David G. Simmons <[email protected]> wrote: >> >> Me again … >> >> So I gave up on serial to the STM32F3Discovery board (for now) and moved on >> to the NRF52 board that I just got. >> >> Started working through the tutorial >> http://mynewt.apache.org/os/tutorials/bletiny_project/ >> <http://mynewt.apache.org/os/tutorials/bletiny_project/> and, of course, >> found some issues. :-) I can load the image on the board, and it appears to >> be running (can’t see the BLE device using a BLE stumbler, but that’s >> another issue I guess) and … still no serial access. >> >> From what I know from the board specs, pin PA.08 is RX and pin PA.06 is TX, >> so I hooked those up to my AdaFruit FT232H board, which should give me >> USB-Serial interface and … once again, nothing. Hmmm … could it be the >> FT232H itself? Hooked the PA.08 and PA.06 pins to my scope and I would >> expect to see activity on the PA.06 pin but nope! Flat-lined. >> >> So I’d love to be told the error of my ways here … >> >> dg >> -- >> David G. Simmons >> (919) 534-5099 >> Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • >> Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter >> <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs> >> /** Message digitally signed for security and authenticity. >> * If you cannot read the PGP.sig attachment, please go to >> * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!! >> * Public key available at keyserver.pgp.com <http://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. >> >> > -- 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
