# Upgrade to Firmware 7.4a and UART2

**URL:** <https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136>\
**Category:** Documentation feedback\
**Created:** [January 26, 2010, 8:37am UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136 "2010-01-26T08:37:01Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![dsanchez](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@dsanchez](https://forum.sierrawireless.com/u/dsanchez)\
**Post date:** [January 26, 2010, 8:37am UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/1 "2010-01-26T08:37:01Z")

</div>

Hi,

I connect a device to the UART2 at 38400 baud:

Using the adl\_atCmdCreate function, I do:

// Check if already open  
AT+WMFM=0,2,2 [OK]  
// Open it (if not)  
AT+WMFM=0,1,2 [OK]  
// Set baudrate  
AT+IPR=38400 [OK]  
// Set character framing (8 data 1 stop)  
AT+ICF=3 [OK]  
// Set flow control (DCE\_by\_DTE=none DTE\_by\_DCE=none)  
AT+IFC=0,0 [OK]

And then switch to data mode ( adl\_fcmSwitchV24State (myUartHandle, ADL\_FCM\_V24\_STATE\_DATA); ) to start communication.

All work fine !

But since I upgrade the firmware from R74 to R74a the device does NOT answer ! If I downgrade to R74 all re work fine.

NOTE: The connected device works ONLY if CTS signal is kept high all the time. But according to the doc “When \<DTE\_by\_DCE\> parameter is set to 0 (none), the CTS is kept high all the time”.

Is any reason that R7.4a does no more do that ?

Does anybody have an idea of a such behavior ?

Thanks’

---

<div class="post-metadata">

**Author:** ![dsanchez](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@dsanchez](https://forum.sierrawireless.com/u/dsanchez)\
**Post date:** [January 26, 2010, 9:11am UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/2 "2010-01-26T09:11:35Z")

</div>

Hi,

I confirm that the R7.4a does NO more keept the CTS signal high with AT+IFC=0,0 !

Why ?

---

<div class="post-metadata">

**Author:** ![dsanchez](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@dsanchez](https://forum.sierrawireless.com/u/dsanchez)\
**Post date:** [January 28, 2010, 8:25am UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/3 "2010-01-28T08:25:53Z")

</div>

Hi,

Is the right place for this post ?

Moderator can you move it please in the correct section ?

Thanks’

---

<div class="post-metadata">

**Author:** ![Madouc](https://avatars.discourse-cdn.com/v4/letter/m/b782af/32.png) [@Madouc](https://forum.sierrawireless.com/u/Madouc)\
**Post date:** [January 28, 2010, 10:36am UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/4 "2010-01-28T10:36:02Z")

</div>

did you raise an issue with your distributor?  
they can get wavecom to notice this.

this forum (except fot the M2M studio part) does nos seem to be monitored regularly. ❗

---

<div class="post-metadata">

**Author:** ![dsanchez](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@dsanchez](https://forum.sierrawireless.com/u/dsanchez)\
**Post date:** [January 28, 2010, 10:56am UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/5 "2010-01-28T10:56:54Z")

</div>

> [@Madouc](#):
>
> did you raise an issue with your distributor?  
> they can get wavecom to notice this.
> 
> this forum (except fot the M2M studio part) does nos seem to be monitored regularly. ❗

Yes but no answer after two mails… I will phone to my distributor…

---

<div class="post-metadata">

**Author:** ![Jeroen1](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@Jeroen1](https://forum.sierrawireless.com/u/Jeroen1)\
**Post date:** [January 28, 2010, 12:36pm UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/6 "2010-01-28T12:36:12Z")

</div>

We encountered the same issue and already reported it. It is confirmed by wavecom and should be corrected in Oasis 2.33, the release after the upcomming one.

---

<div class="post-metadata">

**Author:** ![dsanchez](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@dsanchez](https://forum.sierrawireless.com/u/dsanchez)\
**Post date:** [January 28, 2010, 1:06pm UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/7 "2010-01-28T13:06:08Z")

</div>

> [@Jeroen](#):
>
> We encountered the same issue and already reported it. It is confirmed by wavecom and should be corrected in Oasis 2.33, the release after the upcomming one.

Thanks.

Do you known when Wavecom plans to release it ?

Or do you known if Wavecom can release a patch to correct this ?

---

<div class="post-metadata">

**Author:** ![Jeroen1](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@Jeroen1](https://forum.sierrawireless.com/u/Jeroen1)\
**Post date:** [January 28, 2010, 2:30pm UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/8 "2010-01-28T14:30:56Z")

</div>

The response mentioned that the release date is yet unknown. Wavecom proposed to use r73a for the time being. No mention of patches or workarounds.

---

<div class="post-metadata">

**Author:** ![dsanchez](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@dsanchez](https://forum.sierrawireless.com/u/dsanchez)\
**Post date:** [January 28, 2010, 3:09pm UTC](https://forum.sierrawireless.com/t/upgrade-to-firmware-7-4a-and-uart2/4136/9 "2010-01-28T15:09:38Z")

</div>

> [@Jeroen](#):
>
> The response mentioned that the release date is yet unknown. Wavecom proposed to use r73a for the time being. No mention of patches or workarounds.

Ok. Thanks !
