Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
10/10/07 16:51
Read: times


 
#145602 - yes, but that's because...
Responding to: ???'s previous message
Andrew Ayre said:
Some devices in this family have more than one siganature, but for the 89V51RD2 I know of only one:

BFH, 91H


Yes, but that's because you (read: FM) don't see the real signature, just what the bootloader returns. And the bootloader is written so that it does not read the real "silicon" signature (AFAIK there is no way to do it), it just simply returns a constant:
IAP_ReadID:
	mov	a,dpl		; 0390   e5 82      e.
	cjne	a,#0,IAP_ReadIDX1; 0392   b4 00 03   4..
	mov	a,#0bfh		; 0395   74 bf      t?	; Mfg ID
	ret			; 0397   22         "
;
IAP_ReadIDX1:
	cjne	a,#1,IAP_ReadIDX2; 0398   b4 01 03   4..
	mov	a,#91h		; 039b   74 91      t.	; Device ID 1
	ret			; 039d   22         "
;
IAP_ReadIDX2:
	mov	a,#4		; 039e   74 04      t.	; both ISP and IAP version number
	ret			; 03a0   22         "
;


And NXP apparently burns the same bootloader into both chips.

JW


List of 12 messages in thread
TopicAuthorDate
Philips --> NXP P89v51 problem            01/01/70 00:00      
   apparently yes            01/01/70 00:00      
      Thanks Jan            01/01/70 00:00      
         89V51RD2            01/01/70 00:00      
            yes, but that's because...            01/01/70 00:00      
               ISP            01/01/70 00:00      
         I know their answer...            01/01/70 00:00      
            Programmer Update            01/01/70 00:00      
               basically I agree            01/01/70 00:00      
                  on IDs, responsibility and decline of \'51            01/01/70 00:00      
                     OK the answer to P89v51 Device ID            01/01/70 00:00      
                     I asked...            01/01/70 00:00      

Back to Subject List