Main Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - A. Ash

Thanks Andy,

I will take a look at the signals this morning. Your conclusion sounds correct. The funny thing is I have been using the hardware to program P89LV51RD2BA devices with no problem. It could be bad connection through to my daughter card like you said.

I also received a MCB900 board Friday, so I will try that as well.


Yes, I can open the terminal window and everything is echoed back correctly. I can read and write with the ISP commands manually in the terminal.

I am using my own hardware, a MAX232 and a transistor on the RST pin for the pulses. The device(unprogrammed) always seems to go into ISP mode with the terminal, however I did notice the first character it sends back is an 'O' with a tilda over it, not the 'U', but just the first character, after that it is all 'U' then whatever else is sent is correctly echoed.

Some additional information, I have (I believe) been able to get the device to program through the uVision3 'Flash-Download', it says programming completed, but even with no ERASE command, small code, and PROTECTISP on, the device will no longer go into ISP mode (even with the terminal). UCFG1 set to 63h, Security bits all 0, BootVector is 0Fh.

Thanks for any insights you might have.
Hi, newly registered here.

I am trying to program a P89LPC924 using ISP mode with FM 4.17.
I can get the device into ISP mode and communicating through the Flash Magic terminal, but it will not program through the graphic interface.

The top of the Flash Magic window says 'USING 7200 BAUD', but a window pops up saying
'Failed to read the device signature(Unable to communicate(transmit/receive)) Accessing a device using the wrong protocol could render the device unusable. Do you want to continue yes/no',
yet I can go immediately back to the FM terminal and read from the device with ISP commands.

One odd thing I did notice is the address for the BOOTVECTOR when read from the device is 0Fh, but in the startup file it is 1Eh.

I even just compiled the startup900.a51 to see if I was influencing anything with my code and no change.
I sure there us something simple I am still missing. Please help?