<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: K60N512 SDHC controller in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K60N512-SDHC-controller/m-p/217451#M3844</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not really possible...&lt;/P&gt;&lt;P&gt;Edit:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SDHC interface is basically 4 SPI lines in parallel when viewed from the perspective of the SD Simplified physical layer specs - the commands / data are split over 4 lines, and CRC'd individually. The SDHC takes care of this for you though. I believe to develop code for 4 wire SDIO access rather than SPI, you have to join the SD card developers group though.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SDHC interface as connected on the K60 tower kit does allow single wire SPI access to the SD card though.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll leave this below as I misread the question and people might find the following useful:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes it is possible. If you look on the schematics you will find:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SD Pin...Port...MCU&amp;nbsp;function:&lt;/P&gt;&lt;P&gt;5,CLK...PTE2...SPI1_SCK&lt;/P&gt;&lt;P&gt;2,SDI...PTE3...SPI1_SIN&lt;/P&gt;&lt;P&gt;7,SDO...PTE1...SPI1_SOUT&lt;/P&gt;&lt;P&gt;1,#CS...PTE4...SPI1_PCS0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm assuming SIN / SOUT refers to slave in, slave out. Therefore SIN is the MCU output, SOUT is the MCU input. SPI1_PCS0 I assume stands for "peripheral chip select". There are several of these so you can have SPI1 talking to several slave devices.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SPI1_PCS0...PTE4&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre;"&gt;SPI1_PCS&lt;/SPAN&gt;1&lt;SPAN style="white-space: pre;"&gt;...&lt;/SPAN&gt;PTE0&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre;"&gt;SPI1_PCS&lt;/SPAN&gt;2&lt;SPAN style="white-space: pre;"&gt;...&lt;/SPAN&gt;PTE5&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre;"&gt;SPI1_PCS&lt;/SPAN&gt;3&lt;SPAN style="white-space: pre;"&gt;...&lt;/SPAN&gt;PTE6&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, using SPI1, you can talk to the SD card in SPI mode, on the K60 twr kit. Handy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 09 Jul 2011 18:35:17 GMT</pubDate>
    <dc:creator>Frost</dc:creator>
    <dc:date>2011-07-09T18:35:17Z</dc:date>
    <item>
      <title>K60N512 SDHC controller</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K60N512-SDHC-controller/m-p/217450#M3843</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't really understand how SDHC controller work, so my question is : is it possible to use SDHC controller as simple SPI interface with multiple data lines?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Emmanuel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jun 2011 16:30:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K60N512-SDHC-controller/m-p/217450#M3843</guid>
      <dc:creator>Nouchi</dc:creator>
      <dc:date>2011-06-24T16:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: K60N512 SDHC controller</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K60N512-SDHC-controller/m-p/217451#M3844</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not really possible...&lt;/P&gt;&lt;P&gt;Edit:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SDHC interface is basically 4 SPI lines in parallel when viewed from the perspective of the SD Simplified physical layer specs - the commands / data are split over 4 lines, and CRC'd individually. The SDHC takes care of this for you though. I believe to develop code for 4 wire SDIO access rather than SPI, you have to join the SD card developers group though.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SDHC interface as connected on the K60 tower kit does allow single wire SPI access to the SD card though.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll leave this below as I misread the question and people might find the following useful:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes it is possible. If you look on the schematics you will find:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SD Pin...Port...MCU&amp;nbsp;function:&lt;/P&gt;&lt;P&gt;5,CLK...PTE2...SPI1_SCK&lt;/P&gt;&lt;P&gt;2,SDI...PTE3...SPI1_SIN&lt;/P&gt;&lt;P&gt;7,SDO...PTE1...SPI1_SOUT&lt;/P&gt;&lt;P&gt;1,#CS...PTE4...SPI1_PCS0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm assuming SIN / SOUT refers to slave in, slave out. Therefore SIN is the MCU output, SOUT is the MCU input. SPI1_PCS0 I assume stands for "peripheral chip select". There are several of these so you can have SPI1 talking to several slave devices.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SPI1_PCS0...PTE4&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre;"&gt;SPI1_PCS&lt;/SPAN&gt;1&lt;SPAN style="white-space: pre;"&gt;...&lt;/SPAN&gt;PTE0&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre;"&gt;SPI1_PCS&lt;/SPAN&gt;2&lt;SPAN style="white-space: pre;"&gt;...&lt;/SPAN&gt;PTE5&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre;"&gt;SPI1_PCS&lt;/SPAN&gt;3&lt;SPAN style="white-space: pre;"&gt;...&lt;/SPAN&gt;PTE6&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, using SPI1, you can talk to the SD card in SPI mode, on the K60 twr kit. Handy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 09 Jul 2011 18:35:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K60N512-SDHC-controller/m-p/217451#M3844</guid>
      <dc:creator>Frost</dc:creator>
      <dc:date>2011-07-09T18:35:17Z</dc:date>
    </item>
  </channel>
</rss>

