<?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: T1042 eMMC version and device capacity in T-Series</title>
    <link>https://community.nxp.com/t5/T-Series/T1042-eMMC-version-and-device-capacity/m-p/1042984#M3587</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; "&gt;The T1042 eSDHC controller is compatible with the MMC system specification version 4.5. It is highly possible that EMMC standards are backward-compatible - to ensure it is required to refer to the Embedded Multi-Media Card (e•MMC) Electrical Standard (5.1) and the device Data Sheet.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; "&gt;&lt;BR clear="none" /&gt; There is a following description in the eMMC v4.5 spec. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; "&gt;---------------------------------------------------------- &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; "&gt;SEC_COUNT The device density is calculated from the register by multiplying the value of the register (sector count) by 512B/sector. The maximum density possible to be indicated is thus 2 Tera bytes (4 294 967 296 x 512B). ----------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 Apr 2020 18:03:12 GMT</pubDate>
    <dc:creator>ufedor</dc:creator>
    <dc:date>2020-04-01T18:03:12Z</dc:date>
    <item>
      <title>T1042 eMMC version and device capacity</title>
      <link>https://community.nxp.com/t5/T-Series/T1042-eMMC-version-and-device-capacity/m-p/1042983#M3586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a t1042 card with installed 8GB eMMC 4.5 and 5.0 version device. Both of them work well.&lt;/P&gt;&lt;P&gt;What's the maximum size of eMMC t1042 supported?&lt;/P&gt;&lt;P&gt;Can t1042 support eMMC 5.1 device? thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Apr 2020 03:53:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T1042-eMMC-version-and-device-capacity/m-p/1042983#M3586</guid>
      <dc:creator>wengangzhu</dc:creator>
      <dc:date>2020-04-01T03:53:35Z</dc:date>
    </item>
    <item>
      <title>Re: T1042 eMMC version and device capacity</title>
      <link>https://community.nxp.com/t5/T-Series/T1042-eMMC-version-and-device-capacity/m-p/1042984#M3587</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; "&gt;The T1042 eSDHC controller is compatible with the MMC system specification version 4.5. It is highly possible that EMMC standards are backward-compatible - to ensure it is required to refer to the Embedded Multi-Media Card (e•MMC) Electrical Standard (5.1) and the device Data Sheet.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; "&gt;&lt;BR clear="none" /&gt; There is a following description in the eMMC v4.5 spec. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; "&gt;---------------------------------------------------------- &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; "&gt;SEC_COUNT The device density is calculated from the register by multiplying the value of the register (sector count) by 512B/sector. The maximum density possible to be indicated is thus 2 Tera bytes (4 294 967 296 x 512B). ----------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Apr 2020 18:03:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T1042-eMMC-version-and-device-capacity/m-p/1042984#M3587</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2020-04-01T18:03:12Z</dc:date>
    </item>
  </channel>
</rss>

