Messages

And do you program the x2 (6clk) flag when/after updating the bootloader?
What is the version of bootloader BEFORE updating?

JW

Not sure what your questions mean.  AFAIK, the 6clk flag is not an option on the bootloader update.  I program that when I load in my app.  And I have no idea how I would or could know what version of the bootloader is in there.

Well, my idea was, that the problem might be related to the 6clk flag rather than bootloader version. I.e. that you might be update the flash as long as you won't program the 6clk flag.

The version of bootloader should be displayed together with signature when you perform "ISP->Read Device Signature" in FM, on the bottom of that window.

JW

If I take a new, virgin part of the "bad" batch (0627 date code) and update the bootloader first, it takes just fine.  I can program it and reprogram it many times.

And do you program the x2 (6clk) flag when/after updating the bootloader?
What is the version of bootloader BEFORE updating?

JW

OK so I have to apologize, Andy - yes, version 4 of bootloader is flawed as far as page erase is concerned.

Jan Waclawek

Are you using the exact same USB to RS232 cable? They are frequency a cause of problems.

Also, a different driver to that "cable" might make a significant difference...

JW

Most of the devices in this family have their own signature and a generic signature, which is BF, 00, 91. However the one the OP mentioned isn't know to us.

As I said already so many times, these are most probably relabelled SST devices. The 91 device signature is of the older, discontinued SST89E564RD, the 93 is of the newer SST89E516RD - there are only very minor differences between these two devices, based on the published datasheet.

Andy is not aware of the difference as it is irrelevant for IAP - the bootloader is presumably the same(*) and the signature there is not read from the chip's hardware, rather, it is set directly in the bootloader's firmware as a constant. The difference is seen only when the signature is read via a parallel programmer.

Jan Waclawek.


(*) ...although on 8052.com I have seen reports of a factory-installed bootloader version 6 - Andy, can you confirm this, perhaps also what is the difference to other versions?).

Although there may be other possible causes, upgrading the bootloader is a quick and easy test. Let us know what you find out.

Andy

Hummmm....

I tried and it indeed does work; however, I am now quite convinced that it is FM which behaves in a different way for the v4 and v7 bootloader. I will make more experiments and report.

JW

If I recall, the failure to erase some flash blocks was due to a bug in the bootloader. Are you running the latest version? I know this problem has been posted on here several times in the past.

Although I am running bootloader v4 (as came with the chip), I am not quite convinced this is the case, sorry. When I will grab some time to get back to my '51 hobby I will make a sniffer cable and post the result...

Jan

... it would also be interesting to hear how do they behave on a parallel programmer, including the signature read thereof... Any chance?

JW

Is there any chance to try a different clock (crystal) - say, half of the current value? The rationale being a guess that the troubles started with setting the 6-clock mode, maybe a marginal FLASH controller?

Not that makes you really happy... :-(

JW

PS. Actually, what IS the frequency and the supply voltage?

1. It tells me I'm using the wrong device, but I'm okay with that. Still, it's a symptom.

And what is the device (signature) it returns? Which version of bootloader?

JW

... erasing blocks 0 and/or 1 only (I installed a freshly downloaded version of FM to confirm).

This is most probably the classical pitfall of sending "page number" rather than address of the first byte in page - but I was lazy to verify by sniffing the communication ;-)

While speaking about page erase, could you please add an Erase Pages used by Hex File option? Thanks.

Jan Waclawek

What version of bootloader does your p89V51RD2 have (check it via Read device signature)?
Haven't you updated to bootloader v7 and then selected Device Configuration->ISP etry mode ->Run Bootloader?

JW

There are '51RD2-s around with at least two different device id - you should contact the device programmer manufacturer for updated firmware/software to account for this.

As per IAP, this is not really the appropriate forum to deal with this - please come to 8052.com forum with the same question, posting also a short example of your code, stating exactly how does it fail your expectations.

JW

I know that I am reviving a pretty old thread.

As a Linux user (most of the time), I feel that we should have ISP software for Open Source OS as Linux.

Desktop Linux is quite mature today.

I think you better throw this up on the 8052.com Forum.
Andy Ayre of ESAcademy/FlashMagic is regular there, too.

JW

As this is not a FlashMagic related issue, you better post it on 8052.com's Forum for help.

You also are should post a really tried code, presenting your findings and also how they fall short of your expectations.

Jan Waclawek