MAJOR MCU issue...

[kittmaster]

Can someone verify the placement of the 8051 IC from the MCU module pin configuration.

My question is pins 39 and 38 for port 0 bits 0 and 1.

The datasheet shows pin 39 as port 0 bit0 and pin 38 as port 0 bit 1.

My MCU module seems to have these reversed!

HUGE problem.

LMK if others have this same thing

[lacy]

Hi Chris

I can confirm what you are seeing. The port adrresses are in the correct order. It is the pin numbers that are screwed. It goes from 37>39>38>40. This is actually the 8052 instead of the 8051. Now can we edit the symbol to take care of this?

Message Edited by lacy on 11-17-2007 08:27 PM

Message Edited by lacy on 11-17-2007 08:29 PM

[lacy]

You can edit this by right clicking on it and using the in-place edit to just swap the pin numbers around, but unfortunately since it is considered an interactive component you can't save these changes to the database and I don't know how swapping the pin numbers around would affect it simulation wise.

This definitely is something that need to be on the fix list.

[lacy]

I stand corrected. Both the 8051 and 8052 pins are out of order. This is only occuring with the DIP-40 package that I can tell. I believe that to use the in-place editor to modify these could affect simulation because the pins are mapped to the ports in the model detail report.

Message Edited by lacy on 11-17-2007 09:22 PM

Message Edited by lacy on 11-17-2007 09:23 PM

[lacy]

I have additional bad news concering this. When the schematic is exported to Ultiboard from Multisim the connections to the footprint follows the pin numbers. This would make the connections incorrect on the board.

I will post both my simple Multisim schematic and the Ultiboard file for review.

[kittmaster]

yep, I only caught it when I started to relay the board down and the resistor pack for port 0 has cross over sequence in the net bus.

There is no point of an inplace edit since you can not even save it to the user database. So I'd classify this as a major fault rendering 50% of the MCU module as useless.

This should be put on the high priority of fixes I suspect.

Glad its not just me!