Group Actions
Engagement
  • Author Author: jkutzsch
  • Date Created: Date Created
  • Views 682 views
  • Likes 3 likes
  • Comments 12 comments
Related
Recommended

Safe & Sound @ E14-CLEWE @#9_GPS Stalled

jkutzsch


E14-C.L.E.W.E. INDEX:

#1_”The word.”

#6_Energia!

#2_”The Science.”

#7_Blog7

#3_"GPS decisions."

#8_GPS_Issues

#4_"GPS arrives!"

#9_GPS_Stalled

#5_"The box, the box!"

                                                                             image

 

I have to apologize that this project has came to such a sad state of stalling.

 

I have continued to research and see if there are other ways that I can get this working but so far no luck.

 

I have completely ripped the project back down, retested the gps with arduino Uno and then re-assembled and retried code provided as good to go for serial/gps testing.

Code is same as in Blog 8.

 

I did find some hints that others have had the same issue:  https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/586961/2165670

 

"Please help somehow the serial monitor is not displaying any readings when I connect the GPS to P3.2 and P3.3 ..."

 

and

 

"Well I have been working in arduino for sometime now and the first part was implemented correctly..No problem at all...But when I am going to implement the same in msp432  nothing is happening..."

 

This sounds mighty similar to what I am running into.

 

Later he references success from information he found at 43oh.com but never details what was done.  :-(

 

"Thanks at least I can now get the location in my serial monitor...Forum 43oh was of great help"

 

and

 

"Thanks for all your help...I was finally able to successfully complete the whole project"

 

No links, so I have been checking the forum myself but keep getting:

 

image

 

Sigh...

  • in reply to jc2048

    The only thing he has to do (It took me some time to check this) is replace every occurrence in his code of Serial with Serial1.

    The Serial1 object reads and writes to P3.2 and P3.3

     

     

    If he reads or writes to Serial(), traffic is exchanged with the host PC

    If he reads or writes to Serial1() traffic goes to P3.2 and P3.3.

    Both can be used at the same time in the same sketch.

  • in reply to Jan Cumps

    Isn't it better for John to use the regular Boosterpack standard pins rather than breaking out the ones intended for the USB? It shouldn't take much to adapt any examples to work with UART2.

  • in reply to jc2048

    I've put a reply in the blog # 10

     

    https://www.element14.com/community/community/design-challenges/texas-instruments-safe-sound-wearables-design-challenge/…

     

    The Serial isn't broken out to 3.2 and 3.3, but via the bridge jumpers in the middle of the board to the USB.

  • in reply to jc2048

    image

     

    I see what they've done [I cheated and read the documentation on their website]. The 'direct' mode bypasses the Arduino's processor (the circuit above is for the Arduino Uno) and sends the data directly to the PC via the USB. So it just looks like there are two TX outputs connected together; as long as the Arduino processor has its serial disabled, then it would work. And that's the reason for the switch on the GPS shield - if it wasn't there, you couldn't isolate the TX and you then wouldn't then be able to download sketches to the Arduino if the shield were attached [because the two TXs would collide].

  • in reply to jkutzsch

    "I can't remember off the top of my head..."

     

    Which is why you write everything down in a log book...

     

    If I were trying to get this to go, I'd use a scope to look at the serial coming out (but then, being a hardware engineer, I do all my debugging with a scope). If you don't have a scope, how about using what you do have? You've already had the Arduino receiving data, so why not wire up the Arduino AND the MSP432 at the same time? The Arduino can confirm that the NEMA messages are being transmitted and are there for the MSP board to read, and then you just need to fiddle around with the 432 software until you're reading them.

     

    Put the shield on the Uno, wire the TX from the Adafruit shield to the RX input on the TI board (P3.2) and link the GNDs together. Keep the connections short and, if you want to avoid the possibility of one powering the other through the signal connection when one has power and the other doesn't, include a resistor between the two [a 470 ohm resistor would limit the current to something that wouldn't do much harm whilst not affecting the signal too much].