Kelvin,

You should've mention that this is a continuation of a discussion on the FlashMagic forum: http://www.esacademy.com/software/...037&t=3037

The problem is, that during IAP the 0000h-1FFFh code memory is switched to Block1, which contains the bootloader. There are no provisions in the default bootloader for the interrupts; the vector addresses are occupied by bootloader code.

As we discussed there, the relevant Philips documentation is... ehm... insufficient in this respect; so you cannot get other than recommendations here. And, as I mentioned, you can start from the SST documentation, where the IAP details (registers, programming procedures) are described in sufficent detail (again, no guarantee that the SST documentation will apply to ALL Philips P89V51xD2).

So, to make our story short, you have the following options:

• make provisions that you won't receive bytes via serial during IAP (I doubt you can do that reasonably, otherwise you most probably won't ask at all)
  
• disable interrupts during IAP and hope you won't lose any byte (as the programming times are not specified in Philips' documentation, some risk is involved, too)
  
• modify the bootloader so that the interrupt vectors can be used and copy your interrupt service routines into Block1 so they will continue to run during IAP
  
• ask NXP (exPhilips) to make the modification mentioned above for you (additional question: how many millions of their parts are you buying per month? :-)
  
• program the received bytes into Block 1 (where te bootloader sits - most of that 8kB (around 6kB) space is occupied by softICE, which you won't use in the application anyway).
  Viability of this solution depends on the nature of the data and the application - can you tell us more on this?
  
• something else I missed

Jan Waclawek