Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - aaronlawrence

Pages: [1]
I don't want the Flash file system, but I do want to use the parameter block.

Defining USE_PARAMETER_BLOCK without FLASH_FILE_SYSTEM in Config.h, doesn't work because in lpc23xx.c
fnWriteBytesFlash does nothing if FLASH_FILE_SYSTEM or SPI_FILE_SYSTEM is not defined.

I also don't understand why the parameter system stores bytes to quadwords. Surely each time parameters are written we just erase the whole sector and write the parameters as a single block?

µTasker general / "Use dhcp" setting should be in NETWORK_PARAMETERS?
« on: March 18, 2010, 04:53:31 AM »
Is there a reason why the "use DHCP" setting is in the ucServers part of the main parameters, instead of being a part of the network parameters?

µTasker general / How do I use the serial port (UART) support?
« on: March 03, 2010, 05:28:06 AM »

What do I need to do to use serial ports? (For output only at this stage).
I want to use UART0 on LPC2366.
I tried looking through code, docs and forums but there doesn't seem to be any general guide.

We were previously using broadcast UDP packets to discover devices (destination = Now we changed to subnet broadcasts ( a.b.255.255 where a and b are for example 192 and 168).
uTasker does not seem to receive them though from Wireshark we are sure they are getting to the device. No UDP data is received.
Is this expected? Can we fix it?

NXPTM LPC2XXX and LPC17XX / Exception handler
« on: February 22, 2010, 11:51:40 PM »
Hi all, I have made myself a small loop to jump to, if my code crashes. It basically flashes some LEDs at the moment, and I suppose will do more later. I'm currently using it for Asserts and the like.

I would like to change the default exception handlers so if something else goes wrong, it also jumps to this loop.

I see that currently in jumps to default_code: label in startup_gnu.s. How would I change this? Is there some kind of API, or do I just overwrite the exception handler addresses, or ... ?

µTasker general / Success
« on: February 17, 2010, 10:31:16 AM »
We are nearing completion on our new board using uTasker for OS and TCP/IP stack. We are using ARP, DHCP, UDP, unbuffered TCP, ICMP. So far have not found any problems (maybe a few quirks) with the stack; I have found the RTOS a bit fussy to work with, but does the job.

Thanks for the rapid start and good code, Mark :)

µTasker general / IPCONFIG default zero ?
« on: February 17, 2010, 09:01:54 AM »
In Config.h there is:

Code: [Select]
#define USE_DHCP                                             // enable DHCP  - needs UDP - IPCONFIG default zero. Needs 1k Ethernet RX Buffers!! (set random number also)
What does "IPCONFIG default zero" mean??

µTasker general / Polling task goes to UTASKER_STOP
« on: February 08, 2010, 03:30:36 AM »
I have set my application to run in polling mode. It is declared like this:

Code: [Select]
{ "app", fnApplication,  MEDIUM_QUE,  (DELAY_LIMIT)((0.10 * SEC) + (PHY_POWERUP_DELAY)),
0, UTASKER_STOP}, // Application - start after Ethernet to be sure we have Ethernet handle

but the application sets itself to polling mode during init:

Code: [Select]
extern void fnApplication(TTASKTABLE *ptrTaskTable)
if ( g_AppState == STATE_INIT )
// set ourselves to uTasker "polling" mode, that is continuous

Is this correct? Can I combine the startup delay with polling mode like this?
It seemed to work fine but now for some reason, the task has stopped running and is waiting for an event. How can that happen?

Hello Mark,
Could you please finalise the TCP/IP API document?
I know about the forum thread, but it is a very clumsy way to read and not very complete.
I would really appreciate some standard API documentation describing the parameters, return codes and usage of each function.

NXPTM LPC2XXX and LPC17XX / Hang assigning EMAC_RxStatus
« on: January 06, 2010, 04:53:17 AM »
I have an intermittent hang in the second call to uMallocLAN_Align in fnConfigEthernet for LPC23xx.
Interestingly, when this hang happens CrossWorks cannot break into it (cannot stop target).

Sometimes when running the app, the startup works fine and the stack goes on to work fine (as far as I can tell, only have Ping so far). Other times it hangs as noted.

Code: [Select]
   EMAC_RxStatus = (unsigned long)uMallocLAN_Align((unsigned short)(sizeof(LPC23XX_RX_STATUS)*i), 8);    // create a smaller pool of buffer descriptors

Because it's intermittent and unstoppable once hung, I have to do this by trial and error so it's slow to find ...

NXPTM LPC2XXX and LPC17XX / NXP project - debug is set to optimise
« on: January 06, 2010, 12:03:46 AM »
Just a minor note - in the NXP CrossWorks project, it seems the Thumb Flash Debug configuration is set to Optimize (for size). And hence single stepping etc doesn't work as expected.

This confused me for a long time. However, I find the CrossWorks configuration setup incredibly confusing, so ... :)

µTasker general / General comments as new user
« on: December 30, 2009, 06:42:16 AM »
Some comments on my experience as a new user.

1) There is no guidance in the docs on how to port uTasker to your own hardware.
The tutorials work through the demo on standard eval hardware, and adding software, but don't deal at all with the critical task of fitting it to your own hardware.
I'm gradually figuring it out from the config.h and other stuff but it's not very clear.
For example: where and how to I set up clocks? Ports? Timers? Interrupts?

2) The forum search sucks - it always searches for parts of words. For example, if I search for "hang" it also finds "changing".

3) The demo app is really too complex.
While it contains a lot of features and does work out of the box (which is initially encouraging) there is simlpy too much in the demo app for starting up. It also feels kind of monolithic, rather than modular.

Merry Christmas!! B)


NXPTM LPC2XXX and LPC17XX / LPC2366 Flash size wrong
« on: December 30, 2009, 06:38:05 AM »

Just moved the LPC demo project (CrossWorks) over to our board with an LPC2366 and it dies immediately. Found that it's trying to access Flash at 7C000 (496k) which doesn't exist on LPC2366.
1) What do I do to correct it? The code seems to be written assuming only 21xx is different, but there are many differences in the different models.
2) How many more of these nasty surprises will I have? Is the support really only tested for LPC2368?


Pages: [1]