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

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
04/24/08 11:46
Read: times


 
#153950 - Thanks a lot
Responding to: ???'s previous message
Jan Waclawek said:
I came across the same question a couple of years ago and concluded, that as the uPSDs are in fact literally glued together from a standard '51 and the PSD part, so I concluded that it should be safe to use the P2:Ri couple with movx @Ri. I was using it so ever since without any problems (uPSD3212).

Thanks for your replies. Jan, that's the ideal scenario that I was hoping.

We are re-designing an old board based around an 80C32 for cost reduction and the decision was to use the uPSD3233B. The code was written in assembler and it implements a communication protocol which is time sensitive, so the request from the client was that we leave the code pretty much intact. Sadly, it is full of movx @Ri instructions using P2 for the high address byte.

By the way, I contacted a ST FAE yesterday about this. I also asked what would be the behavior of using the 52-pin version that doesn't have P0 & P2 external ports. I hope that this won't make any difference but I'll post the response here.

Carlos

List of 6 messages in thread
TopicAuthorDate
movx @ri,A in uPSD3200 micros            01/01/70 00:00      
   Try the datasheet            01/01/70 00:00      
      Not the (complete) answer?            01/01/70 00:00      
   internal/external memory in uPSD32xx            01/01/70 00:00      
      Thanks a lot            01/01/70 00:00      
         I had the 52 pin version, too...            01/01/70 00:00      

Back to Subject List