Hello everyone,
I required to interface MCR20A with twr k60 board.
Earlier I have ported MCR20A code for K22F (SPI1)board from K64F and working fine.
Now for twr K60 (SPI0) board i gone through the same procedure but not working.
may be the DSPI interface is not communicate properly.
I write the GPIO_DIR resigster and read it back for verification of DSPI functionality.
But not able to get same data.
Any help would be appreciated.
Thanks in advance.
Ronak Panchal
Hello Ronak,
Yes, the DSPI is different from SPI, the DSPI is more powerful than SPI, i recommend you check the RM of them to porting and change the
related configuration of the registers .
And you can also refer to the K60 spi demo to configure , for example the KINETIS_V2_SC , there is a spi demo of IAR :
Kinetis K60 100 MHz MCU Tower System Module|Freescale
If it still can not work ,you can describe it in detail .
Hope it helpsd
Alice
Hello Alice,
I have found another thing while testing.
As earlier i have said,
I write the GPIO_DIR resigster and read it back for verification of DSPI functionality.
But not able to get same data.
I found that every time i read the data, i am able to get lower nibble proper.
e.g.
I write oxab then when I read the same register i got 0xb every time.
Regards,
Ronak
Hello Ronak,
The chip on TWR-K60D100 is MK60DN512VMD10 , it is also SPI, not DSPI.
Could you check the transmit signal by OSC or other to check whether the K60 spi send is right .
BR
Alice
Hello Alice,
Thanks for your reply.
Let me give you brief idea about the problem.
I required to use MCR20A with my TWR K60 Board.
SMAC Stack for MCR20A is Given for K64F and KL46Z.
I have ported the SMAC code from K64F to K22F board and working proper for that porting i required to change only the pinouts as per K22F board and SPI Instance.K22F uses DSPI for communication with MCR20A.
Now i have gone through the same Procedure for TWR K60 board.which also uses DSPI.
I have used SPI0 for k60 board where as in K22F it is SPI1.
Is the difference between DSPI module of both board or different SPI instance cause the problem?
Regards,
Ronak