Messages

1

µTasker general / Re: Important Notice about Forum Holiday

« on: June 27, 2011, 07:53:53 PM »

Up to now registration has not been based on approval but this may be introduced later in case the situation doesn't improve. Then the spammers under the existing members can be gradually weeded out so that the forum returns to its original quality.

There's yet another load of spam messages... I think approval of new users should start right away!

2

µTasker general / Re: CW refuses to flash the uTasker demo

« on: June 02, 2010, 11:21:44 AM »

I just wanted to add that the only difference between the Special Edition version of Codewarrior and all other versions is the license file.
If you install a Special Edition version and copy the license file of a (not expired) evaluation version over the special edition license file, it will turn the SE version into an evaluation version until the evaluation period expires...

3

NXP^TM M522XX, KINETIS and i.MX RT / Getting control over port TC

« on: March 06, 2010, 10:02:28 AM »

Hello Mark,

I would like to use port TC in my application, but this port is already being used by uTasker itself for the blinking LEDs.
Is there a simple, straightforward way to disable the uTasker use of this port, or do I have to go through the code to remove all uTasker use of that port myself?

4

NXP^TM M522XX, KINETIS and i.MX RT / Re: MCF5223X New Mask Revision

« on: November 27, 2009, 12:59:41 PM »

I wonder why it took so long...

5

NXP^TM M522XX, KINETIS and i.MX RT / Connecting a T6963c based LCD

« on: November 22, 2009, 08:05:52 PM »

I was wondering if a Toshiba T6963C based graphical LCD module can be connected directly to a Coldfire microcontroller, as the Toshiba chips are specified to work at a power supply voltage of 5V only. Or do they also work at 3,3V?

6

µTasker general / Re: Trying to get some TCP work done...

« on: October 29, 2009, 08:54:18 PM »

Great, seems to work now, thanks! It looks like, after the connection is attempted, all the work has to be done in the listener routine.

Another question:
With a TCP transmission it is possible for the data packets to arrive out-of-order. How is this handled by the uTasker?

7

µTasker general / Trying to get some TCP work done...

« on: October 27, 2009, 06:28:45 PM »

I'm currently trying to download some HTTP data from the internet using the uTasker. I used the TCP tutorial that was posted here a while ago as a reference, together with the NTP client code from the demo application.

Definitions...

Code: [Select]

#define METAF_TCP_PORT 8080
#define MAX_DATA_LEN 500
typedef struct stTCP_MESSAGE
{
TCP_HEADER     tTCP_Header;                    // reserve header space
unsigned char  ucTCP_Message[MAX_DATA_LEN];    // data payload space
} TCP_MESSAGE;

const char postData[] = "station_ids=EBAW&std_trans=standard&chk_metars=on&hoursStr=most+recent+only&chk_tafs=on&submitmet=Submit";
static TCP_MESSAGE MetafData;
USOCKET Metaf_TCP_socket;
static unsigned char ucRemoteIP[IPV4_LENGTH] = {204,227,127,34};

My code first obtains a free socket and then performs a connect to the server. So far it's all working fine.
When the connection is successful, the data that is to be sent is created and sent using fnSendTCP. Tracing the code indicates that the data transmission is successful.

Connecting and sending data...

Code: [Select]

extern void fnMETAF(TTASKTABLE *ptrTaskTable)
{
char printstring[2048];

Metaf_TCP_socket = fnGetTCP_Socket(TOS_MINIMISE_DELAY, TCP_DEFAULT_TIMEOUT, fnMetafListener);
if (Metaf_TCP_socket >= 0)
{
fnTCP_Connect(Metaf_TCP_socket, ucRemoteIP, METAF_TCP_PORT, 0, 0);

strcpy ((char*)MetafData.ucTCP_Message, "POST /metars/index.php HTTP/1.1\r\n");
strcat ((char*)MetafData.ucTCP_Message, "Content-Type: application/x-www-form-urlencoded\r\n");
strcat ((char*)MetafData.ucTCP_Message, "User-Agent: Mozilla/2.0 (compatible; WS4.9e.667)\r\n");
strcat ((char*)MetafData.ucTCP_Message, "Host: adds.aviationweather.gov\r\n");
sprintf (printstring, "Content-Length: %d\r\n", strlen(postData));
strcat ((char*)MetafData.ucTCP_Message, printstring);
strcat ((char*)MetafData.ucTCP_Message, "Cache-Control: no-cache\r\n\r\n");
strcat ((char*)MetafData.ucTCP_Message, postData);

if (fnSendTCP(Metaf_TCP_socket, (unsigned char *)&MetafData, strlen((char*)MetafData.ucTCP_Message), TCP_FLAG_PUSH) > 0)
{
strcpy (printstring, (char*)MetafData.ucTCP_Message);    // just some code to put a breakpoint on
}
}
}

The listener code is never reached. Wireshark doesn't indicate a received packet either.

Listener code...

Code: [Select]

static int fnMetafListener(USOCKET Socket, unsigned char ucEvent, unsigned char *ucIp_Data, unsigned short usPortLen)
{
char printstring[2048];
switch (ucEvent)
{
case TCP_EVENT_ARP_RESOLUTION_FAILED:
break;

case TCP_EVENT_DATA:
// process data
strcpy (printstring, (char*)ucIp_Data);
break;

case TCP_EVENT_CLOSE:
case TCP_EVENT_CLOSED:
case TCP_EVENT_ABORT:                                                // no connection was established
break;
}
return APP_ACCEPT;
}

I have a windows program that sends the same request to the same server and processes the same data. The lines in the trace window that indicate the transmission and reception of the relevant data in Wireshark are all in green. The lines that come from the uTasker are all grey though. Also, the packets that come from the uTasker don't contain the data that I'm trying to send and don't have the PUSH flag set either.

There is obviously something not being done right here. Any help is appreciated! 

8

µTasker general / Re: Simulator and host PC with wireless network

« on: October 21, 2009, 11:45:48 AM »

Thanks. I understand it's not a DHCP issue, but this is just the way I noticed that it isn't working.
So basically WinPCap is the limiting factor here?

9

µTasker general / Simulator and host PC with wireless network

« on: October 20, 2009, 07:40:39 PM »

I'm picking up the uTasker again after messing with Interniche/Coldfire Lite for some time.

While playing around with the simulator, I noticed that DHCP does not resolve when the host PC is connected to the network via WLAN. It does work when connected via the wired network interface though. I didn't forget to select the right physical interface in the simulator by the way.

I have noticed this on more than one PC, so it's probably not hardware related. Is this maybe a limitation of a wlan connection?

10

µTasker general / Re: uTasker V1.4 Update

« on: October 18, 2009, 06:46:48 PM »

It's working now, thanks!

- Marc

11

µTasker general / Re: uTasker V1.4 Update

« on: October 18, 2009, 08:07:56 AM »

Hello Mark,

I just downloaded the update (coldfire version) and tried to unzip it (using winzip 12.1) but there appears to be a problem with the zip file being corrupt. I tried by downloading it again but to no avail. Could it be that the file is corrupt?

- Marc