Messages

When selective memory range is used for Memory display option, junk data is displayed.
The data displayed when memory "0xF000 to 0xFFFF" was selected is reproduced below.
The actual memory contents on the target in this memory area is 0xFF and the address shown does not exist in P89V51RD2.
This would require correction.

FFFFFF10 0200403200302C282420FF32011600FF ..@2.0,($ .2....
FFFFFF20 FFFFFF32FFFFFFFFFFFFFF023361FFFF ...2........3a..
FFFFFF30 FFFFFF023390FFFFFFFFFF327F031235 ....3......2...5
FFFFFF40 D6E4FF12344722FFFFFFFFFFFFFFFFFF ....4G".........
FFFFFF50 75818075D00075870075A80075891175 u..u..u..u..u..u
FFFFFF60 880075C83475C90075985075CBFF75CA ..u.4u..u.Pu..u.
FFFFFF70 D975D55175B80875A898D2B512010612 .u.Qu..u........
FFFFFF80 1FC49000EC7403F0900500740DF0A374 .....t.....t...t
FFFFFF90 01F0A37401F012207E123835D244C28E ...t... ~.85.D..
FFFFFFA0 758DB1758BD1D28EC23ED24275838093 u..u.....>.Bu...
FFFFFFB0 303D05C23D122000203C14E514B51502 0=..=. . <......
FFFFFFC0 800D758303851582E00515D23CF59930 ..u.........<..0
FFFFFFD0 38119000EDE0F508C238203E0612013F 8........8 >...?
FFFFFFE0 12130D30390E9000EEE0F509C239203E ...09........9 >
FFFFFFF0 03304000303A0E203E031214049000EF .0@.0:. >.......
0000 E0F50AC23A303BA49000F0E0F50BC23B ....:0;........;

Regards
Prabul

I have used sectors at starting address FE00 and FE80 to store nonvolatile In Application Pragrammable data. IAP works fine, but when I used FM to upload the application with an upgrade, the nonvolatile IAP data is erased, though I have selected only "Erase blocks used by HEX File" selection. The "Erase all flash" option was deselected. I also confirmed that the hex file of the loaded application does not have any entry above address 0x4000.

Could you also please update us on the data variables used by IAP low level routines. In Philips technical note "TN06007" titled  "V51RX2 Migration" para 7 it is indicated that the IAP routines of the P89V51Rx uses direct data memory 0x20 and 0x30 thru 0x32. However it is silent if the user application needs to avoid these data memory or are these memory locations being pushed into stack by the IAP routines before their use, so that the user data is not corrupted by IAP.

Your support would be highly appreciated.

Prabul

Dear Andy,

Thank you for your quick response. I tried the new DLL as per your instructions to upgrade the bootloader on a virgin chip.
Bootloader update operation halted after indicating "programming device (0x2100)", without any further progress.
After waiting for 30 seconds, I pressed update once again, as there was no exit route other than to kill the process.
A pop up window "Unable to communicate. (transmit/receive)" was displayed and the programming process repeated once again.
I pressed OK button on the pop up window and a new window indicating "There is no communication to the device" was displayed.
This pop up window was cleared by pressing OK button.
I then checked the bootloader version and it showed the same earlier version 4 and i quit FM.
The debug file recorded during the above operation is mailed to you for your further analysis as it could not be uploaded on this site due to size limitation (133KB file size).

Regards
Prabul

Dear Andy,

I am using windows 2000 PC and i tried to upgrade the bootloader of a fresh 89V51RD2BN IC with batch number KzNO439 AC in debug mode.
I first selected F1 to switch to debug mode. Then read the device signature by selecting "ISP" followed by "Read Device Signature" from the menu.
The Device signature was shown as "BF 91 04". Now I selected "ISP" followed by "Update Bootloader" from the menu and gave the file name "P89V51RD2_V07_UPD_ISP.HEX". Then pressed Update button. The screen indicated that the device was programming and at the end stopped by indicating "Programming device (0x2110)" followed by a display window "Operation Failed". After this, the bootloader is failing to even update user code through Flash Magic and also to update the bootloader, rendering the IC useless. Attached please find the debug file. Hope you will be able to let us know what is going wrong.

Thank you and Regards
Prabul

I tried to update bootloader Ver 7 using FM to a fresh P89V51RD2BN having bootloader ver 4. The operation failed. Boot Loader also gets corrupted some times during several trials.
Later I got bootloader Ver5 from the web with instructions to update the bootloader. The "bootloader updater" should be programmed as an application and then after resetting the target, use terminal console to update the bootloader by pressing char 'U' from the terminal console.

I tried the same procedure with Ver7 of the bootloader downloaded from the web. This works. Subsequent updates (after updating to ver5 of bootloader or higher) of the bootloader via Flash Magic Bootload update works fine. NXP needs to improve its documentation to ease the task of developers.

This information is shared to gather more comments and experiences for the benefit of developers.