Messages

436

µTasker general / Re: Boot Loader

« on: July 21, 2007, 05:38:04 PM »

Hi mark,
  Thanks for the reply. It sounds perfect for our needs. One thing, is it possible to have the downloaded code stored in an external flash, rather than internal flash? This way we can use more space for our code (as it will grow in time).

Neil

437

µTasker general / Re: Using TCP in the uTasker project

« on: July 21, 2007, 05:09:12 PM »

Hi Mark,
  The above worked fine, thanks, I can now connect to the server application.  I will soon start looking at sending/receiving side.

Many Thanks
Neil

438

µTasker general / Re: Using TCP in the uTasker project

« on: July 21, 2007, 02:49:44 PM »

Hi Mark,
 I quickly tried to add a client, and have it connecting to my server application, but without any luck.  Could you let me know what I am doing wrong? Here is the small code.. (It just simply connects, no sends/receives)

USOCKET Test_socket;

static int fnTestSocket(USOCKET Socket, unsigned char ucEvent, unsigned char *ucIp_Data, unsigned short usPortLen)
{

    switch (ucEvent)
   {
      case TCP_EVENT_CONREQ:                                             
      case TCP_EVENT_CONNECTED:
      case TCP_EVENT_CLOSE:
      case TCP_EVENT_ACK:
      case TCP_EVENT_ARP_RESOLUTION_FAILED:
      case TCP_EVENT_PARTIAL_ACK:
         break;
      case TCP_EVENT_REGENERATE:
      case TCP_EVENT_DATA:
         if ((ucEvent == TCP_EVENT_REGENERATE) || (!uMemcmp((CHAR*)ucIp_Data, "TEST" , 4)))
         {
         }            }
         break;
      case TCP_EVENT_ABORT:
      case TCP_EVENT_CLOSED:
         break;
   }
    return APP_ACCEPT;
}


Within the 'fnApplication(..)', making it the last bit of code within 'if (!iAppState)':

Test_socket = fnGetTCP_Socket(TOS_MINIMISE_DELAY, (unsigned short)20, fnTestSocket);
fnTCP_Connect(Test_socket, "192.168.0.184", 10000, 0, 0); //my server address and port...

The connection is never made (all done within simulator), and the call back function always gets called with switch value of '9'.

I have my server application running in debug, so I can tell when a connection is made.
Regards
Neil

439

µTasker general / Re: Using TCP in the uTasker project

« on: July 21, 2007, 02:19:40 PM »

Hi Mark,
In the previous reply you mentioned:

>>Note that several listeners (servers) are possible on a single port (each needs a seperate socket) >>but only one client is possible.

Does this mean its not possible to have 2 or more clients connecting to a server?

Neil

440

µTasker general / Boot Loader

« on: July 21, 2007, 01:49:17 PM »

Hi,
  We have a new project coming up, and hopefully be using the utasker (just downloaded the utasker for the first time a few weeks ago, and testing it out).

We will have many units throughout the world, and some will be in remote areas where getting to will take hours, so we are thinking of having the ability to re-programm the firmware remotely.

I have a couple of questions regarding this feature in uTasker.

1. In our system there are 2 options the way the user can use our product, either by GPRS, or ethernet(if there is a connection). If the connection is GPRS (to our M52233), can we still use the boot feature? Or can we modify the code to do so?

2. what would happen in the following scenario: A connection is made, the firmware is being updated and the connection is lost half way through. Would the processor restart, and we can reconnect and restart upload procedure again?

Many Thanks
Neil

441

µTasker general / Re: Using TCP in the uTasker project

« on: July 21, 2007, 09:21:42 AM »

Hi Mark,
  In the above call back function 'static int fnTestListener(...)' , would it be best to leave as it is in most applications ? Simply call a task when data comes in, and leave all the rest as it is?

 Also..
 'fnGetTCP_Socket(TOS_MINIMISE_DELAY, (unsigned short)10, fnTestListener); '

Our application will have a permanent TCP connection to our server, and sends a byte of information to the server every 2 minutes, so is it feesable to have a timeout of 130 seconds?

I also assume that for creating a client connection application, it will be the same as your server description, but instead of listning, simply make a connection, then all else is the same?

Many Thanks
Neil