I have tested to execute a very simply program (Only BX LR at address 0x10000300) in RAM. I believe this shouldn't influence the ISP software, but I receive two bytes 0x30 followed by 0xFF. From other test programs (setting a LED) I know the software executes. After code execution ISP doesn't respond to commands any more.
So the LPC800 doesn't respond with 0x30, 0x0D, 0x0A, which can be worked around and therefore isn't such a problematic issue. What is important in this matter is making an announcement about the future. It's an issue that will be fixed and therefore only present in version 13.1, .... or it's a new ISP feature, which from now on will be included in every ISP release. So NXP, please make up your mind and be clear about these changes/issues (Also inform about the binairy data transfers, which are not conform the ASCII protocol with UU encoding, used in previous ISP bootrom's).
A larger problem is that after receiving the response, ISP no longer responds to commands. This way it's not possible to execute code snippets, which access hardware, normally not available using the ISP ROM. For example a serial EEPROM , containing configuration data, connected to the device using I2C. I have used such programs a lot on LPC17xx and LPC21xx devices and never had any problems.
Sander
I have also seen the GO command work differently than the manual. As Axel indicates, the manual indicates we can't use addresses under 0x0200. However, in my experience, I am using the command: "GO 0 T" (That's 'G' 'O' 'Space' 'Zero' 'T') and it's working perfectly. Including setting the stack. So, am I getting lucky? Or is this dangerous?
Thanks
-Mark