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.

Messages - aaronlawrence

Pages: 1 ... 3 4 [5]
NXPTM LPC2XXX and LPC17XX / Re: LPC2366 Flash size wrong
« on: January 06, 2010, 12:06:20 AM »
Thanks Mark. I've turned all Flash support off because I really don't need it - or a web server, or FTP. It would have made a nice demo but I can't justify the time to get it working.

I've got the LAN8720 PHY working now, after some confusion over the address (somehow 1 in our board) and model number (datasheet wrongly says its 0x0C, but really 0x0F).

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 ... :)

NXPTM LPC2XXX and LPC17XX / Re: LPC2366 Flash size wrong
« on: December 31, 2009, 03:44:51 AM »
Hm, there are further hard coded references to sectors assuming 512k, e.g. in
fnGetFlashSector(unsigned long FlashAddress) it refers to FLASH_SECTOR_22_OFFSET

Looks like there is substantial rework to be done here to make the file system and parameters work in 256k or 128k.....
I think I will disable the whole thing and do something myself - I don't need a web server or file system for the end product, just using this to get a demo going as easily as possible.

NXPTM LPC2XXX and LPC17XX / Re: LPC2366 Flash size wrong
« on: December 31, 2009, 03:18:07 AM »
My problem is that fnGetValidPars uses PARAMETER_BLOCK_1 which is defined as PARAMETER_BLOCK_START. which is simply defined as
        #define PARAMETER_BLOCK_START   FLASH_SECTOR_26_OFFSET           // 496k
(except for LPC21xx)
so it always puts the configuration at 496k. Thats the part that doesn't work.
It's not obvious what the alternative layout is when using only 256k.
Since I don't see any diagrams of how the memory is used I can't speculate where it is safe to put

µ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 ... 3 4 [5]