Hi, triggered by the proposal and discussions on the forum to add a combined SIM/SD-Reader for another internal Micro-SD card (which I find a nice idea):
http://boards.openpandora.org/topic/14698-overview-of-soc-options/?p=309418
I have checked the mechanical fit - and there is no problem to add such a piece.
For the electrical/logical interface, I have analysed all the TRMs and data sheets for understanding the limitations of the SDIO controllers of the OMAP5 [2].
We have no problems running one internal eMMC, one bootable high-speed SD slot, a second non-bootable standard speed SD slot and WLAN.
But we have a problem to interface a third Micro-SD slot because the SDIO5 port is n/a on the 5432 chip.
Options to solve this are * replace the eMMC by the Micro-SD (which will have a much lower speed limit!) * interface WLAN though SPI (is not optimal for 802.11n) and use the SDIO3 port * interface WLAN through (internal) HS-USB (likely to draw more power and needs different chipset/module) and use the SDIO3 port * interface the Micro-SD slot (or even the second full speed) slot though USB (needs a probably power hungry SD-USB controller chip like [1])
In any case only the master SD slot is bootable and not the Micro-SD slot (even if connected through USB because the Boot ROM can't handle USB memory for booting).
BR, Nikolaus
[1]: http://www.genesyslogic.com/jp/product_view.php?show=46 [2]:
Am 31.01.2014 um 10:49 schrieb Dr. H. Nikolaus Schaller:
Hi, triggered by the proposal and discussions on the forum to add a combined SIM/SD-Reader for another internal Micro-SD card (which I find a nice idea):
http://boards.openpandora.org/topic/14698-overview-of-soc-options/?p=309418
I have checked the mechanical fit - and there is no problem to add such a piece.
For the electrical/logical interface, I have analysed all the TRMs and data sheets for understanding the limitations of the SDIO controllers of the OMAP5 [2].
We have no problems running one internal eMMC, one bootable high-speed SD slot, a second non-bootable standard speed SD slot and WLAN.
But we have a problem to interface a third Micro-SD slot because the SDIO5 port is n/a on the 5432 chip.
Options to solve this are
- replace the eMMC by the Micro-SD (which will have a much lower speed limit!)
- interface WLAN though SPI (is not optimal for 802.11n) and use the SDIO3 port
- interface WLAN through (internal) HS-USB (likely to draw more power and needs different chipset/module) and use the SDIO3 port
- interface the Micro-SD slot (or even the second full speed) slot though USB (needs a probably power hungry SD-USB controller chip like [1])
With such a chip http://www.genesyslogic.com/jp/product_view.php?show=7 we could also think about this configuration:
SDIO1: SIM/Micro-SD (used only for factory programming or unbricking or by user if he/she likes) SDIO2: internal eMMC SDIO3: WLAN SDIO4: unused HSUSB: 2 full sized SD slots which magically mount as USB memory drives - without any need for an OMAP SD driver; but they are only bootable if U-Boot in eMMC recognizes them
But let me check first that we have enough USB ports for any such configuration...
It is sort of a puzzle of limitations :)
In any case only the master SD slot is bootable and not the Micro-SD slot (even if connected through USB because the Boot ROM can't handle USB memory for booting).
BR, Nikolaus
Kernel mailing list Kernel@pyra-handheld.com http://pyra-handheld.com/cgi-bin/mailman/listinfo/kernel
On Fri, Jan 31, 2014 at 11:49 AM, Dr. H. Nikolaus Schaller hns@goldelico.com wrote:
...
Options to solve this are
- replace the eMMC by the Micro-SD (which will have a much lower speed
limit!)
- interface WLAN though SPI (is not optimal for 802.11n) and use the SDIO3
port
- interface WLAN through (internal) HS-USB (likely to draw more power and
needs different chipset/module) and use the SDIO3 port
- interface the Micro-SD slot (or even the second full speed) slot though
USB (needs a probably power hungry SD-USB controller chip like [1])
Both eMMC and internal SD would be a bit overkill IMO, so we probably should choose one of them. The forum posters claim there is not much speed difference but I'm not sure if it's really so in practice, as eMMC has 8 data lines and SD only has 4 and not all MMC interfaces support high speed clocks.
About using SPI, the Jorjin modules ED inquired about don't seem to have SPI mode any more, so probably different modules would be needed (unless Jorjin can offer SPI versions of the same modules).
Another thing that needs to be checked is if pin mux options allow the whatever configuration we want, as lots of things share pins and some peripheral we want to use may use up some pins and make another peripheral unavailable.
Gražvydas
Am 31.01.2014 um 14:07 schrieb Grazvydas Ignotas:
On Fri, Jan 31, 2014 at 11:49 AM, Dr. H. Nikolaus Schaller hns@goldelico.com wrote:
...
Options to solve this are
- replace the eMMC by the Micro-SD (which will have a much lower speed
limit!)
- interface WLAN though SPI (is not optimal for 802.11n) and use the SDIO3
port
- interface WLAN through (internal) HS-USB (likely to draw more power and
needs different chipset/module) and use the SDIO3 port
- interface the Micro-SD slot (or even the second full speed) slot though
USB (needs a probably power hungry SD-USB controller chip like [1])
Both eMMC and internal SD would be a bit overkill IMO, so we probably should choose one of them. The forum posters claim there is not much speed difference but I'm not sure if it's really so in practice, as eMMC has 8 data lines and SD only has 4 and not all MMC interfaces support high speed clocks.
That assumption is definitvely wrong. As you say eMMC has 8 data lines while SD has only 4. But the main factor is the different protocol and clock. So eMMC can go up to 200 MHz clock while AFAIK SD(XC) is limited to 50 or 96 MHz.
Basically I like the idea to have an additional permanently installed SD slot. If we can make it available w/o big problems, I would do it. People will find out what they can do with it... E.g. they could split the rootfs between eMMC and MicroSD, e.g. for permanently storing photos where the high eMMC speed is not that important.
About using SPI, the Jorjin modules ED inquired about don't seem to have SPI mode any more, so probably different modules would be needed (unless Jorjin can offer SPI versions of the same modules).
Another thing that needs to be checked is if pin mux options allow the whatever configuration we want, as lots of things share pins and some peripheral we want to use may use up some pins and make another peripheral unavailable.
I have checked that while trying to get an understanding which interfaces we really have and for the OMAP5 it appears not to be that critical as for the OMAP3. Most pads have a main function and can be used as GPIO and then only have rarely used things (SDIO1 is e.g. shared with JTAG).
So unless I did miss some problem, it will be fine. But this asks for an independent double-check...
BR, NIkolaus