AnsweredAssumed Answered

Are 32-bit SPI slave frames possible on MK60DN512VMD10

Question asked by Piotr Fyda on Mar 15, 2016
Latest reply on Apr 6, 2016 by Piotr Fyda

Hello NXP,

I have 3 questions concerning the reference manual for the Kinetis MK60DN512VMD10 used in the TWR-K60D100M

      Document Number: K60P144M100SF2V2RM Rev. 2 Jun 2012

      K60 Sub-Family Reference Manual, Rev. 2 Jun 2012 -  Preliminary General Business Information


Question 1:

I'm trying to connect a 24-bit SigmaDelta ADC converter PCM1804 (master) to SPI (slave) on Tower_TWR-K60D100M.

It sends a 32-bit frames and so it is incompatible with KSDK_1.3.0 driver in


which accepts only 16-bit frames.

So I've started to program the SPI "manually" and I found out that there are problems!


The manual K60P144M100SF2V2RM Rev.2  says explicitly, that 32bit frames are supported in the in slave mode.:

Figure 50-1, page 1402 - shows 32-bit path from Shift Register  to RX FIFO


§50.3.4, page 1418 - shows SPIx_CTARn_SLAVE where FMSZ has 5 bits == 32bits frame size


§50.3.9, page 1427 - says:

POPR is used to read the RX FIFO. Eight- or sixteen-bit read accesses to the POPR have

the same effect on the RX FIFO as 32-bit read accesses.


§50.4.2, page 1431 - says:

the SPI frames can be 32 bits long


My test program gives only max. 16 bit frames which I can read.

The highest bit of FMSZ (bit 31) has no influence on the received data in the RXFIFO and POPR.

I see in the RXFIFO the high-word and low-word of a 32-bit frame (and I could assemble the 32-bit frame), but the Reference Manual says I should get 32-bit result in POPR.

So what is true ???


Question 2:

The manual K60P144M100SF2V2RM Rev. 2  shows (§50.3.1, page 1410)  the SPIx_MCR layout:

- bit 25 is ROOE and bits 24,23,22 are reserved

in the old manual, there was

- bit 25 was PCSSE and ROOE was on bit 24, bits 23,22 were reserved

Kinetis Desing Studio 3.1.0 shows in EmbSys Registers the "old" layout (MK60D10 chip selected)

So what is true ???


Question 3:

I have downloaded 2 versions of K60P144M100SF2V2RM Rev.2,

one is 14.229KB big - another only 13.853KB !

(they seem to be the same... but who knows - I'm not going to compare page by page...)

So how can it be ???

A version is A VERSION and should have always the same size (at least in my opinion) !


Thanks in advance for a quick responce.

best regards

Piotr Fyda