Team,
Has the USB 3.0 support been tested on the K2E EVM?
It seems that it is not working "out of the box". We are wondering if it is a problem specific to this EVM (ie HW failure and need to be replace) or if it is a HW/SW setup issue.
Below is the email thread with interleaved information (see 1, 2, 3, 4 below) to clarify the SW version used, installation, HW setup and USB 3.0 device used.
can you please help to try to fix the issue?
> 1) What EVM HW release do you use?
https://einfochips.com/index.php/partnerships/texas-instruments/k2e-evm.html#4-versions
We are using XEVMK2EX ordered on your website. For the Hardware, the version is EVM v1.0.2.1.
> 2) What MCSDK version do you use? What is the kernel and u-boot version flashed on this board?
> Have you checked after upgrading the U-boot, Linux kernel and file system to the version provided in the lastest McSDK?
I just flashed the board with the files included in the newest MCSDK on your website, which version 3_01_00_03.
The U-Boot version written when I boot is 2013.01 (from August 2014).
The kernel is 3.10.10.
To start I do as stated on a page in your wiki, as it does not start automatically. So writing those commands in U-Boot:
env default -f -a
setenv boot ubi
boot
Is it fine or I have to load the image with fatload for example?
[AB] Using the below instructions should be fine to start the "out of the box demo":
http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Getting_Started#Run_Out_of_Box_Demonstrations
Still I would like to be sure how the NAND flash was updated with the new MCSDK target files.
What PC side OS do you use? Linux or windows?
Since you are using the EMK2E I guess that you follow the specific programming procedure from the below link:
http://processors.wiki.ti.com/index.php/Program_EVM_UG#Programming_the_bin_files
- The board is set in no-boot and using the DSS script (included in CCS) you program the NAND flash. Correct?
- Are all the steps happening error free?
- Once flashing is done what boot mode do you place the board in? ARM NAND or ARM SPI boot?
[KG] I use Windows on the host side.
Yes I followed the specific programming procedure from the below link:
http://processors.wiki.ti.com/index.php/Program_EVM_UG#Programming_the_bin_files
The board is set in no-boot and I use the DSS script to program the nand flash.
I just started the flash again and I noticed that the EEPROM50 and EEPROM51 flashing does not work as it says that the files do not exist.
But I checked the directory tree and it is the same as the one showed in the link above. One more thing is that flashing the NAND is really slow. I mean it waits a long time before actually flashing it.
Apart from that, everything else is fine.
When done I put the board in ARM SPI boot as stated in the link.
> 3) What is the console message you get for the USB device you connect?
Here is the debug messages:
xhci-hcd xhci-hcd.0.auto: Timeout while waiting for address device command
usb 2-1: device not accepting address 5, error -62
xhci-hcd xhci-hcd.0.auto: Bad Slot ID 4
xhci-hcd xhci-hcd.0.auto: Could not allocate xHCI USB device data structures
hub 2-0:1.0: couldn't allocate port 1 usb_device
> 4) What is the USB3.0 device that you are using?
I am using a USB 3.0 camera that works under Linux. Tested on my laptop before and another embedded board, but with a PCIE to USB 3.0 adapter using the xhci_hcd driver too.
When recognized, the camera is considered as a USB 2.0 device.
I also tried with a USB 3.0 stick (provided by e-infochips in the package) and it didn't work.
When I used a USB 2.0 stick, it was fine. Also when I did plug a USB 2.0 hub in the USB 3.0 port, the camera is always recognized as a USB 2.0 device, of course.
Could it be that there is not enough power for the USB 3.0 devices? We have seen on the schematics that there is a ENABLE pin (linked to ball grid AB1 on 66AK2E05) in the USB POWER SUPPLY. Could it be that we have to activate that to give the needed power to the port?
Because USB 2.0 is fine, but not USB 3.0, so that is why we thought that maybe the port wasn't providing enough power to the device.
[AB] Is it the USB stick mentionned as "Software (Flash drive)" here?
https://einfochips.com/index.php/partnerships/texas-instruments/k2e-evm.html#3-kit-content
[KG] Yes it is this one.
[AB]
For USB I would think that Linux kernel is already configure to enable USB 3.0 at the Linux driver level:
http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#USB_Driver
So the issue might on the HW side.
Thanks in advance,
Anthony