Read on serial COM Port ColdFire

fabianwork wrote on Tuesday, December 01, 2009:

Hello,

I’ve just updated freeRTOS from v3 to v6.0.1. Everything was working fine on v3 and I’m trying to do it on v6. I’ve met the first problem : when I tried to read a serial port and to fill data in a tab, It lose some packets.

Here’s my code that used to work fine on v.3 :


*xPortRF  = xSerialPortInit( serCOM1, ser57600,  serNO_PARITY, serBITS_8, serSTOP_1, 40 );

for(i=0;i<22;i++)
{

while(!xSerialGetChar(xPortRF, &rxchar,portTICK_RATE_MS));
trameCMD_=rxchar;

}

And when I send on serial port for example 01 - 02 - 03 - 04 - 05 - 06

In my tab I have : 01 - 02 - 04 - 01 - 02 - 04 - 01 - 02 - 04 …

Thank you for the help you may provide to me ! _

edwards3 wrote on Tuesday, December 01, 2009:

Search for “Changes between V4.8.0 and V5.0.0 released April 15, 2008” on http://www.freertos.org/History.txt

Have you taken into account the upgrade instructions given there?

fabianwork wrote on Wednesday, December 02, 2009:

Yes I’ve taken this instructions.

I forgot to update some files. I’ve find a new serial.c file v6.0.1 but there’s no more xSerialPortInit function.

Where could I found the serial.c file where xSerialPortInit is implemented ?

Thank you

fabianwork wrote on Thursday, February 18, 2010:

Hello,

I come back still with the same problem !

This time, I’m using a COM port to communicate with a GPS and to read GPGGA and GPRMS data.

3 month ago, I met a problem with my ColdFire 5213 because it was reading only half of the data, so I’ve changed the serial buffer size from 64 to 128, and this resolved the problem.
Yesterday, the problem came again, but instead of increasing the size of the buffer to resolve it, it was necessary to reduce it to 64 but I don’t know why…
Does anyone has an idea of this problem origin? How can I work with the latest FreeRTOS without the xSerialPortInit function?

Thank you very much if you can help me.