Messages

DTR and RTS are used to place the device into ISP before the 'U' is transmitted. So, yes you could use these signals to tell when the device is being reset - if that helps. You can also configure Flash Magic to keep RTS asserted during the whole time ISP is being used. See section 7.3.1 of the manual for details.

Did you enable the break detect in the code you first programmed into the device?

Do you have the watchdog enabled in UCFG1?

Did you enable the break detect in the code you first programmed into the device?

Do you have the watchdog enabled in UCFG1?

Is this a P89C51Rx2Hxx or a P89C51Rx2xx?

Go to www.codearchitect.org/philips
Choose the LPC9xx family
Select your device
Configure the clock to match how you are using the device
Configure the UART. Make sure "enable break detect" is checked
Add the code to your project.

Philips are working on an application note that should give you the information you need. I currently don't know when the application note will be released.

After reset the device must receive a 'U' within a certain timeframe to enter ISP mode, otherwise it executes whatever is programmed into it. Flash Magic takes care of sending this 'U' fast enough. All you have to do is reset the device when Flash Magic tells you to.

To my knowledge, /PSEN is not involved in entering ISP mode.

Note also, that it is not a requirement to control /PSEN and Reset via the serial port on Philips devices. You can control them manually or use a software method to enter ISP mode.

The ISP to ICP bridge is now available from Philips, directly from their web site. The part numbers are:

PAB90X-1 for LPC901/2/3
PAB90X-2 for LPC906/7/8

You can find these tools by visiting the microcontroller tools homepage:
http://www.semiconductors.philips.com/markets/mms/products/microcontrollers/support/development_tools

- Click on "Tools by tool type"
- Click on "Programming Adapters"
- Click on the "X" next to "PAB90x-1" or "-2" or click on the "LPC90x" family

General 8051 questions are better addressed in the forums on www.8052.com. This forum is for discussion of Philips ISP.

www.codearchitect.org/philips will generate I2C code in C for you.

Using your parallel programmer, set the Boot Vector to FCH and the Status Byte to FFH. This is how the device came from the factory.
Place the device back in your hardware. Power up.
Open a terminal program on your PC such as Hyperterminal. Use, 8 bits, no parity, 1 stop bit, no flow control, 9600 baud.
Send a single 'U' (not 'u'). Is it echoed back?

If the 'U' is echoed back then the problem lies with Flash Magic for some reason - let me know.

If the 'U' is not echoed back then you have either a hardware problem, non-functional device, serial cable problem or COM Port problem. If you have successfully programmed the device once via ISP, then that proves the COM Port, serial cable and hardware are working.

There are more detailed ISP debugging steps in the application note on the Flash Magic web page.

Note that the RD2BA defaults to 12 clocks/cycle unless you program it via ISP after each erase to 6 clocks/cycle. The RD2HBA defaults to 6 clocks/cycle and is only programmed to 12 clocks/cycle once, via a parallel programmer.

If you are using the high speed communications option in Flash Magic, you must select the correct number of clocks/cycle for the device you are using, so if you are switching between these two devices, both using the default configuration, then you need to change the high speed communications setting in Flash Magic.

Also, if you have high speed communications turned on, try turning it off and see what happens.

If you are using different crystal frequencies, or the same crystal frequency but both devices are using the default clocks/cycle settings, then the highest baud rate you can use may be different for the devices as they are operating as different speeds. So try lowering the baud rate also.

If a brand new, unused device enters ISP mode, but won't enter ISP mode again after be programmed once, this is usually an indication that the hardware conditions for ISP entry are not being met. From the factory, devices have the status byte set to a non-zero value, resulting in them entering ISP mode on reset regardless of the hardware entry conditions. It is only after programming the device for the first time and you try to get back into ISP mode that you really test your hardware entry method.

The default is the internal RC oscillator, so you need to use Flash Magic to connect and then change the device configuration to external crystal.

The ISP Hardware Entry app note now includes a circuit, description and expected waveforms for hardware ISP entry when using the LPC932.

I've added links to the Flash Magic page to both of Erik Malund's papers on ISP entry.

I agree. I've never liked method 2. But some people like to punish themselves...

Because of the extra bit that is set - it turns on the watchdog.

No, it isn't possible or necessary to do this via IAP. You simply turn on the watchdog yourself and let it time out. Or use a jump to zero after messing with the interrupts, etc. More info on that method on www.8052.com. I have always found a watchdog reset to be the easiest and most reliable.