# Issues: Data communication on UART2

**URL:** <https://forum.sierrawireless.com/t/issues-data-communication-on-uart2/1483>\
**Category:** General\
**Created:** [July 31, 2007, 4:17pm UTC](https://forum.sierrawireless.com/t/issues-data-communication-on-uart2/1483 "2007-07-31T16:17:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![schadha](https://avatars.discourse-cdn.com/v4/letter/s/46a35a/32.png) [@schadha](https://forum.sierrawireless.com/u/schadha)\
**Post date:** [July 31, 2007, 4:17pm UTC](https://forum.sierrawireless.com/t/issues-data-communication-on-uart2/1483/1 "2007-07-31T16:17:12Z")

</div>

# Background:

We are using UART2 on WMP100 to communicate with a PC to exchange binary data.

Baudrate: 115200, set on Both the PC and WMP100  
Hardware flow control: Turned on PC, Default on WMP100  
8,N, 1 set on PC, Default used on WMP100

Here are two issues we are seeing:

1. The UART2 port spits out the following at startup:  
+WIND: 13  
OK

This is not ideal for data, since we need to parse these string before we start data exchange.  
Question: Is there anyway to turn these messages off on UART2.

1. For testing we are sending and receiving 8 bytes of data. After a random number of message exchanges  
(seen anywhere from 64 to 3977 exchanges) both the OpenAT/PC applications block.

I believe that the exchange gets stuck on the incoming messages from the PC to the OpenAT. A message is not being received.

Questions:   
Any reasons why this may be happening?  
Are there any AT commands or other tools to help debug this.

# Recv Handler (which also sends a message):

bool hnd\_fcmData\_U1 ( u16 DataSize, u8 \* Data )  
{  
static int numRecv;  
Message msg;  
char outStr[255];

```
sprintf(outStr, "\r\n>> NumRecv %d hnd_fcmData_U1 %d\r\n", numRecv++, 
                    DataSize);
adl_atSendResponse ( ADL_AT_UNS, outStr); 

msg.type = 96;
msg.value = 98; 
adl_fcmSendData(UART2_Handle, &msg, sizeof(Message));

```

return TRUE;  
}

---

<div class="post-metadata">

**Author:** ![jan](https://avatars.discourse-cdn.com/v4/letter/j/ce7236/32.png) [@jan](https://forum.sierrawireless.com/u/jan)\
**Post date:** [August 1, 2007, 8:42am UTC](https://forum.sierrawireless.com/t/issues-data-communication-on-uart2/1483/2 "2007-08-01T08:42:13Z")

</div>

see also: [http://www.wavecom.com/modules/movie/scenes/forums/viewtopic.php?t=1554](http://www.wavecom.com/modules/movie/scenes/forums/viewtopic.php?t=1554)

---

<div class="post-metadata">

**Author:** ![fft](https://avatars.discourse-cdn.com/v4/letter/f/e8c25b/32.png) [@fft](https://forum.sierrawireless.com/u/fft)\
**Post date:** [August 1, 2007, 9:31am UTC](https://forum.sierrawireless.com/t/issues-data-communication-on-uart2/1483/3 "2007-08-01T09:31:03Z")

</div>

> [@](#):
>
> After a random number of message exchanges […] both the OpenAT/PC applications block.

If by ‘block’ you mean freezing without rebooting, it’s most probably a hardware problem: software freezes are caught by the watchdog and cause a reboot, after something like 10 seconds IIRC.