LM3S8962 serial input output

[shraken]

Hello,

I've been using the LM3S8962 for about 5 months now.  Both in the LabVIEW ARM embedded experience and I also did some projects in the Kiel4 environment with C projects.  I'm having trouble getting serial input/output working in LabVIEW however.

In the Keil development I used serial communication rather easily to communicate with my Bluetooth bluesmirf serial modem.  I was able to use UART0 and UART to transmit to the modem.  I'm trying to replicate this behavior in Labview enviorment.

I've been trying to get Serial Comm.lvproj to work (it's in the Examples for LM3S8962) and simply cannot get it to work.  This data that is sent should be ASCII text, correct?  I ran the software for the ARM microcontroller and tried using UART1 then logged in under my Serial terminal looking for the output text.  It's a lot of data that is garbled. UART0 just doesn't work at all.  Is Labview internally using uart0 and uart1 to transmit data back to host PC for debugging?

Any help would be much appreciated.  This the last piece of my puzzle than I can make a great project. 

[Will_S.]

Hi Shraken,

Are you turning off debugging when deploying the Serial Comm.vi to the ARM? You cannot use both the USB JTAG and COM0 at the same time, so this could be the cause of the issue. Turning off debugging in the build spec and just downloading the program to the ARM should resolve the issue if that is its cause.

[shraken]

Hi Will,

I turned off debugging and ran it.  I also built it in a Kiel and downloaded it onto the device manually.  I tried both uart ports (1/2) and looked at the output on my putty terminal and saw garbage.  Serial comm.lvproj requires a debug build though because it has front panel interaction so I had make a new .vi to test this.  I think this should open uart0/1 and send "1234.'abc" 20 times with 100 ms delay.   

The configuration I have right now is:

Computer <-> Bluesmirf Bluetooth module <-> MCU.

Thank you for help.

[Will_S.]

Hi Shraken,

I'm in the process of getting the hardware necessary to test this, so I should hopefully have more informatino soon. But typically garbled data is due to mismatched baud rates. Have you confirmed that they are identical between the host and ARM? Same with the data bits, stop bits, and parity. I would recommend setting them to 9600 to see how that works.

[Will_S.]

Hi Shraken,

Did adjusting the baud rate fix the issue? If you directly connect the UART Transmit to the UART Receive and run that as a loopback test do you get the correct values? This will let us know if it is a PUTTY issue or a transmit issue.

When connected to the PC using USB, the board should not be using UART0 or UART1.

[shraken]

Hi Will,

My apologies for not responding till yet.  I'm away from the lab for a week so I'll have to get back to you.  I will try

1. Adjusting the baud rate of the modem back to 9600, which is default for the LV vi.

2. Loopback

Thank you for assistance,

Nicholas