Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: LPC2129 IAP Questions

2005-01-25 by firegenie1980

Hi,

Thanks for the information about the status code. I just hadn't 
realised that it was returned within the result variable.

The second part to do with the IRQ disabling is still proving to be 
a problem. I have tried writing it myself however my assembly 
experience is quite low and I have not managed to get it working.

I am using the GCC compiler with Kiel microVision 3. I tried the 
link I was given however it doesn't seem to contain any information, 
which is useful to my project even though I have located the IRQ 
enable/disable code fragments.

Any further information anyone?

On a related note, I have set the ARM/Thumb Interworking checkbox in 
the assembler options as I have read this is required to get the IAP 
working correctly. However I have the following warnings come up on 
all of my C files in this project. Any ideas?
 
Warning: /cygdrive/c/Cygnus/Arm-Tools/Bin/../lib/gcc-lib/arm-thumb-
elf/3.3.1/../../../../arm-thumb-elf/bin/ld: Warning: flash_record.o 
does not support interworking, whereas Scheduler.elf does

Thanks again,

FG


--- In lpc2000@yahoogroups.com, "firegenie1980" <firegenie1980@y...> 
wrote:
> 
> Hi,
> 
> I have been reading through all the posts about this topic, 
however 
> there are two question I have which I cant find the answers for so 
> far. Sorry if they have been answered and I have over looked them!
> 
> 1. How can you see the value of the status code? Is it output into 
a 
> vaiable anywhere?
> 
> 2. I know that you have to disable the IRQ for the period your 
> accessing the Flash. Where is the code for this located? Is it in 
a 
> general library as I cant seem to find it on my setup. I have 
found 
> the assembly for it, but I don't want to replicate teh code if it 
is 
> already somewhere.
> 
> Thanks very much,
> 
> FG

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.