Messages

Can I programm P89V51RD2FA(new) devices with Flash Magic?

I can programm P89V51RD2FA devices, but recently I have received a new batch of devices and I can not programmed them. I think the problem is the new devices are P89V51RD2FA(new), but I don't know the differences between P89V51RD2FA(new) and P89V51RD2FA.

My provider tell me that they have programmed devices of the same production batch using Superpro USB series ISP programmer, but I can't using flash magic.

Can anyone help me?

Many thanks Mr. Waclawek,

I'm interesting in trying this bootvector restorer.
How can I get your email address?

Many thanks

Yes, I have used the "erase all" option, but nothing happens.
Any of the several ISP functions that I have tried work.

I have just tried to run the microcontroller with M27C512 external memory  and using the micro I can not reprogramm. It works properly. But this is not my final design. In my design I must use the on-chip flash memory.
Is there any function to perform an overall reset of the micro?
The ISP "Start Bootloader" function does not work.
If the bootloader is lost, how can I transfer it again to the micro?

I use a PCB with an external Watchdog and Flash Magic tool to programm a P89C51RD2FA micro.
Before programming I disable the watchdog by setting a jumper in my programming PCB.
Everything is ok, an I can programm and reprogramm the micro several times.
But sometimes the communications with the micro is lost, anf after that I can no longer programm the same micro I could before.
It seems to me that the jumper in my PCB fails to connect while trying to programm the micro, and after that I have always the same message: "Unable to connect at the specific baud rate. Try reducing the baud rate. Reset the hardware into ISP mode again".
It is not a problem on my PC or in the cable, because when I put a new micro in the PCB and connect the jumper to disable the watchdog, everything is ok.
But, what can I do to programm again the first wrong micro?
I have tried with some ISP functios but always the same message is returned.
Is it a problem with the bootvector?