F28M35H52C Pin Mux Discrepency

Should have been more clear in my initial post.  I'm using the PIN mux utility version in control suite and it is recently updated. There are differences between the datasheet and the pin mux utility specifically on the following pins:

GPIO38 Pin 69

              Datasheet options: USB0VBUS

               pin mux utility options: USB0VBUS, CCP1, MII RXD2 U1RTS

GPIO46 Pin 70

              Datasheet options: USB0ID

               pin mux utility options: USB0ID, MII TXCK, U1RI

The proposed internal design using the MII functions on these pins as documented in the pin mux utility, will these pins work for this function?

Also, the issue I had with GPIO39,GPIO44 was internal documentation not datasheet or pin mux utility.

Thanks,

Justin

Hi team,

Justin called us this afternoon regarding this discrepancy.  I've checked the Pinmux utility that is included in the latest version of ControlSUITE (v1.0.1375.4) alongside the datasheet and can confirm the discrepancies.

In most cases, the correct documentation is usually the datasheet but with these devices still being TMX, I'm not sure if the mux'ing has been changed and is reflected in the utility and an update to the DS is on it's way or if I should have yielded to Occam's Razor.

Thank you for any insight you can offer.

Regards,

Is there any update on this?

In addition I have one more issue, Pin 91 in the datasheet of the device lists the pin as 'No Connect' but the control card for the concerto connects the pin to 1.2V and labels it as B_VDD12C.8.  Should this pin be left open?  Is there going to be a hardware change on the device shortly?  Should we avoid using it at this point?  We're not going into production for a little while but we need to get moving on prototypes and testing.

Thanks,

Justin

Justin - I'm investigating this.

Thanks Lois.  Is there a time frame on when the Rev A hardware will be released?

Justin