[coreboot] USB3.0 enumeration in Baytrail E3845 with coreboot

Thu Aug 4 08:28:22 CEST 2016

Hello Mayuri,

There are two root hub controllers in BYT: USB 3.0 - xHCI and USB 2.0
(legacy one) - EHCI. The trick here is that you could not have them both
working at the same time. Either you set one, or another. Why? They are on
the different clocking domains. In other words all your USBs will hang out
either of USB 3.0 root hub, either of USB 2.0 root hub. You could NOT mix
outside USB ports (to have them hanging out from both root hubs mixed).

I would recommend to you to set USB 2.0 - EHCI one in Coreboot, for the
starters, and see if this will help you to bring board up, for the reasons
Naveed already mention here. (legacy support for WIN 7 as example).

In order to help you, I did some googling, and found the following public
useful info:
https://www.phoronix.com/scan.php?page=news_item&px=Siemens-MC-TCU3-Coreboot
http://anzwix.com/a/Coreboot/Mainboardsiemensmctcu3AddNewMainboard

I have checked in my newest Coreboot tree (4.4-1038-gdd65ef8): support for
TCU3 is there, so you should look upon the following directories and files:
src/mainboard/siemens/mc_tcu3/
src/mainboard/siemens/mc_tcu3/devicetree.cb

And you can peek around, to see if you can make something out of it.

Hope this helps,
Zoran
_______

On Thu, Aug 4, 2016 at 7:27 AM, Naveed Ghori <naveed.ghori at dti.com.au>
wrote:

> Mayuri
>
>
>
> If you have eHCI enabled then it may use that instaed of xHCI. With eHCI
> you will not have any USB 3.0 support.
>
> There is switching mode for enabling xHCI in the OS and use eHCI during
> boot but it does not appear to be supported as is in the FSP.
>
> I had attempted to get this going but found the easier way is to enabled
> xHCI only. However you then have to mod Windows 7 install image (boot,img)
> file to support the xHCI intel drivers or you will not have any USB devices
> working in the installer (including the installation USB).
>
>
>
> Naveed
>
>
>
>
>
> *From:* coreboot [mailto:coreboot-bounces at coreboot.org] *On Behalf Of *Mayuri
> Tendulkar
> *Sent:* Thursday, 4 August 2016 1:15 PM
> *To:* Zoran Stojsavljevic
> *Cc:* coreboot
>
> *Subject:* Re: [coreboot] USB3.0 enumeration in Baytrail E3845 with
> coreboot
>
>
>
> Hi Zoran
>
>
>
> Thanks for your inputs.
>
>
>
> I am checking on Ubuntu.
>
>
>
> As per minnowmax, devicetree.cb file, below like says default will be EHCI.
>
>
>
> How we should change it at runtime, what is the setting?
>
>
>
> device pci 14.0 on end     # 8086 0F35 - USB XHCI - Onboard & HSEC  -
> Enabling both EHCI and XHCI will default to EHCI if not changed at runtime
>
> device pci 1d.0 on end     # 8086 0F34 - USB EHCI - Enabling both EHCI and
> XHCI will default to EHCI if not changed at runtime
>
>
>
> regards
>
> Mayuri
>
>
>
> *From:* Zoran Stojsavljevic [mailto:zoran.stojsavljevic at gmail.com
> <zoran.stojsavljevic at gmail.com>]
> *Sent:* 04 August 2016 01:06
> *To:* Mayuri Tendulkar <mayuri.tendulkar at aricent.com>
> *Cc:* coreboot <coreboot at coreboot.org>
> *Subject:* Re: [coreboot] USB3.0 enumeration in Baytrail E3845 with
> coreboot
>
>
>
> Hello Mayuri,
>
>
>
> Some of us (at least me) know that INTEL USB 3.0 implementations have here
> and there mortal problems for years, as well as in CORE, also in ATOM
> families. There are lists of problems, but most of them are closed
> Intellectual Properties, INTEL Inside.
>
>
>
> I had yesterday terrible problem to set CANON PIXMA MG3650 home printer
> edition I bought in Saturn to pair over USB with my mobile i5-4300 INTEL
> Inside HSW laptop (CPUID 0x40561), so I needed 4 hours to investigate and
> find the interim solution for INTEL buggy embedded USB 3.0 root port (it is
> consumers' QA issue with INTEL design, so INTEL should take care of this,
> my best guess)... :-((
>
>
>
> In this lieu I will advise you the two way approach.
>
>
>
> One is to contact/to engage with your INTEL FAE/representative, and ask
> him about the problems which are well described in internal INTEL documents
> (BYT wise).
>
>
>
> The other approach is to work out these problems yourself. So, there are
> several facts about the USB 3.0.
>
>
>
> There are (my best guess) some BYT USB fixes done by other people in
> Coreboot. I'll let these people to speak for themselves. If? You can also
> try to bring some Linux distros (Fedora for example) and try to see what is
> going on while you bring up the system (dmesg log). Also you can do the
> following commands:
>
>        lsusb -v
>
>        lsusb -t
>
>
>
> At least, you can do lsusb --h to see options which can help you to start
> debugging this issue.
>
>
>
> Zoran
>
>
>
> On Wed, Aug 3, 2016 at 11:23 AM, Mayuri Tendulkar <
> mayuri.tendulkar at aricent.com> wrote:
>
> Hi
>
>
>
> I am facing issue in enumerating USB3.0 device on baytrail processor with
> coreboot with seabios.
>
>
>
> Is there any setting in coreboot where we need to enable this separately.
>
>
>
> Regards
>
> Mayuri
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
>
> --
> coreboot mailing list: coreboot at coreboot.org
> https://www.coreboot.org/mailman/listinfo/coreboot
> <https://linkprotect.cudasvc.com/url?a=https://www.coreboot.org/mailman/listinfo/coreboot&c=E,1,lK8AEa2HmSCsSpyRNb0dw-eVDF_wv7RIlsTTQifpSwvIs_MS4J9c3OpC9TJGYLnSlPWnC_BCeYVtB4rzfllGI-pR1muAkc_4NwYmlD9aN2iKfHE3vcvr5qID&typo=1>
>
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20160804/3d5196c9/attachment.html>