Additional Pin mux functions - which silicon revisions did they start?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Additional Pin mux functions - which silicon revisions did they start?

Jump to solution
1,106 Views
mjbcswitzerland
Specialist V

Hi All

Newer user manuals show that the K60s have additional pin mux options. Of particular interest is the fact that the SPI OUT and SPI IN connections which are shared with SDHC pins can be set to be crossed (that is swap IN for OUT) so that the SD card interface can be used in SDHC or SPI mode without having to modify hardware.

Trying this on tower boards K60F120 and K70F120 proved that the K70F120 allowed this and direct comparisons between SDHC and SPI performance with an SD card were possible by switching the interface in SW. However this didn't prove possible on the K60F120 board (the pin mux didn't work).

The question is, which revision of K60 chips started offering these extra mux possibilities? Is the chip that I have on my tower board a little too old? (ON96B QEAC1144C). In order to use the new features it it will presumably be necessary to ensure that no devices from older batches are used, and/or avoid certain types - what are the rules???

Regards

Mark

Labels (1)
Tags (3)
0 Kudos
1 Solution
724 Views
anthony_huereca
NXP Employee
NXP Employee

Hi Mark,

  I agree, it can get quite confusing. Hopefully I can explain it clearly.

There are basically three types of K60 parts:

100MHz 1.x parts - on TWR-K60N512 board - no SPI1_IN on PTE1

100MHz 2.x parts - on TWR-K60D100M board - has SPI1_IN on PTE1

120/150MHz parts - on TWR-K60F120M board - has SPI1_IN on PTE1

The differences between the 1.x and 2.x 100MHz parts are in this app note and it includes the change in SPI1_IN that you noticed. Likewise a K60 device going from 100Mhz to 120MHz has differences as well described in this app note (it specifically talks about differences between Kinetis 100Mhz 1.x to Kinetis 120MHz, but you'll notice a lot of the differences described are still valid when going from Kinetis 100Mhz 2.x to Kinetis 120Mhz to cover changes required for new modules on the 120Mhz parts). So while they are all generically a "K60" part, there's quite a lot of internal differences as you see. Also yes, the K60F 150MHz reference manual is valid for the 120MHz parts (there's a list of parts a particular RM is valid for on the first page).

That all said, the external pins were meant to be compatible with each other. So the K60 120Mhz part should have the same mux options on PTE1 as a K70 120Mhz part. And a 2.x K60 100Mhz part should also have those mux options. (I linked to the datasheets for the specific parts on those boards). The only differences of course being instances like on the K70 where you also have an LCD option because only that chip has an LCDC  module.

So if you are using a TWR-K60F120M board, then I would expect your scenario to work. Since it's not, it would not be because of the pin muxing but something else. Maybe double check the rest of your muxing and code to ensure it matches the correct K60 120Mhz datasheet.

View solution in original post

0 Kudos
4 Replies
724 Views
anthony_huereca
NXP Employee
NXP Employee

Hi Mark,

  Which pins specifically are you looking at? The two boards do have different packages (144 LQFP for the K60F, and 256BGA for the K70F) but the muxing should be the same between them for pins like SDHC. Any changes you saw in the RM for K60F devices should be only documentation updates.

Looking at the schematics, the same pins on the boards are connected to the SDHC socket, and they have the same muxing options, so it should work.

-Anthony

0 Kudos
724 Views
mjbcswitzerland
Specialist V

Hi Anthony

I an not quite sure of the situation at the moment.

As an example, PTE1 (144 K60 100MHz) has LLWU_P0 function (on port) according to the latest user's manual. This was added to the user's manual but was possibly already there (?)

But I think thatI have made a mistake with the SPI1_SIN function (ALT7) on the same pin (PTE1). This is NOT shown in any K60-144 100MHz user manuals but it is shown in the K60-144 150MHz User's manual, as it is shown in the K70 (256 MAPBGA). As far as I can make out the K60 and K70 150MHz User's manuals are also valid for K60 and K70 120MHz parts (both have FPU) since there is no User's manual for the 120MHz parts.

However, both K60F120 and K70F120 parts should have the SPI1_SIN function on PTE1 (ALT7) but it only actually works on the K70F120 board and not on the K60F120 board, although the SDHC mode (using PTE1 set to SDHC0_D0) does work correctly on both boards.

Therefore I think that the original question was in fact not correct because the 100MHz K60 (still) doesn't have the SPI1_SIN function on PTE1 (but I incorrectly read that it did from the K60 150MHz User's manual), but I am not sure that the pin mux details are correct for the K60 120MHz parts since it doesn't respond as expected.

What sparked the real interest was the fact that the SPI mode can not be used to communicate with the SD card on the K60N512 tower board since the SPI1_IN and SPI1_OUT functions are crossed (it only works when the HW is swapped) but the PTE1 pin can be used as either SPI1_IN or SPI1_OUT on the F70F120 board since it can also be crossed in SW - I think that the original K60 mux. design was slightly flawed since most manufacturers ensure that SDHC and SPI pin multiplexing is possible on the SD card connection. The new ALT7 setting corrects this and I was probably (secretly) hoping that this would also be the case for newer K60N100 silicon...

Regards

Mark

0 Kudos
725 Views
anthony_huereca
NXP Employee
NXP Employee

Hi Mark,

  I agree, it can get quite confusing. Hopefully I can explain it clearly.

There are basically three types of K60 parts:

100MHz 1.x parts - on TWR-K60N512 board - no SPI1_IN on PTE1

100MHz 2.x parts - on TWR-K60D100M board - has SPI1_IN on PTE1

120/150MHz parts - on TWR-K60F120M board - has SPI1_IN on PTE1

The differences between the 1.x and 2.x 100MHz parts are in this app note and it includes the change in SPI1_IN that you noticed. Likewise a K60 device going from 100Mhz to 120MHz has differences as well described in this app note (it specifically talks about differences between Kinetis 100Mhz 1.x to Kinetis 120MHz, but you'll notice a lot of the differences described are still valid when going from Kinetis 100Mhz 2.x to Kinetis 120Mhz to cover changes required for new modules on the 120Mhz parts). So while they are all generically a "K60" part, there's quite a lot of internal differences as you see. Also yes, the K60F 150MHz reference manual is valid for the 120MHz parts (there's a list of parts a particular RM is valid for on the first page).

That all said, the external pins were meant to be compatible with each other. So the K60 120Mhz part should have the same mux options on PTE1 as a K70 120Mhz part. And a 2.x K60 100Mhz part should also have those mux options. (I linked to the datasheets for the specific parts on those boards). The only differences of course being instances like on the K70 where you also have an LCD option because only that chip has an LCDC  module.

So if you are using a TWR-K60F120M board, then I would expect your scenario to work. Since it's not, it would not be because of the pin muxing but something else. Maybe double check the rest of your muxing and code to ensure it matches the correct K60 120Mhz datasheet.

0 Kudos
724 Views
mjbcswitzerland
Specialist V

Hi Anthony

Sounds like the definitive answer and explanation.

Thanks

Mark

0 Kudos