IAP timout

Started by zizahum August 18, 2005
I use PLC2106 for my project, and have to store some data into
emulated EEPROM in flah using IAP. But I am not so shure about how
does IAP operations works and manual is lack of informations about
that. The thing I don't understand if I want to erase one sector (8 k)
will my program be able to continue, or I have to wait that IAP
operation finishes. I have the same question about write operation.

Thanks.

Srdan Suka


An Engineer's Guide to the LPC2100 Series

--- In lpc2000@lpc2..., "zizahum" <zizahum@y...> wrote:
> I use PLC2106 for my project, and have to store some data into
> emulated EEPROM in flah using IAP. But I am not so shure about how
> does IAP operations works and manual is lack of informations about
> that. The thing I don't understand if I want to erase one sector (8
> k) will my program be able to continue, or I have to wait that IAP
> operation finishes. I have the same question about write operation.

You have to wait. The IAP calls don't return until the operations
are complete.

You even have to disable all interrupts when calling IAP functions
for programming or erasure, unless you relocate all interrupt handler
code and data, including the vector area, to RAM. This relocation is
rather tricky.

Karl Olsen



--- In lpc2000@lpc2..., "Karl Olsen" <kro@p...> wrote:
> --- In lpc2000@lpc2..., "zizahum" <zizahum@y...> wrote:
> > I use PLC2106 for my project, and have to store some data into
> > emulated EEPROM in flah using IAP. But I am not so shure about how
> > does IAP operations works and manual is lack of informations about
> > that. The thing I don't understand if I want to erase one sector (8
> > k) will my program be able to continue, or I have to wait that IAP
> > operation finishes. I have the same question about write operation.
>
> You have to wait. The IAP calls don't return until the operations
> are complete.
>
> You even have to disable all interrupts when calling IAP functions
> for programming or erasure, unless you relocate all interrupt handler
> code and data, including the vector area, to RAM. This relocation is
> rather tricky.
>
> Karl Olsen

Thanks, I wasn't quite shure about this, but now I am much more :)