Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
Hi,
We are trying to use TUSB3210 EVM(REV 2) USB controller for our keyboard application.
Our goal is to download keypad firmware from host PC into 3210EVM.
I am referring to section 2.5 Jumpers and Switches of Page 2-3 in Below user's guide
for TUSB3210 keyboard Evaluation board.
http://focus.ti.com/lit/ug/sllu032a/sllu032a.pdf
For this purpose we tried below 2 steps, to ensure board is functioning properly,
1. Default setting functionality:
We tried to execute the firmware which by default written in EEPROM and see
Whether the keypad works fine. But, did’nt see key press on 3210EVM displayed
On hyperterminal.
Below are setting we did,
· Jumper setting:
U3: 1-2 Speed sense always ON(Execute firmware from EEPROM).
U9: 1-2 5V power supply from USB cable.
U12: 1-2 Self powered
· Connected USB cable to pc and to 3210EVM.
· Connect UART to COM1 of PC and 3210EVM.
· Configure Hypertrm with following setting.
BPS : 115200
Databits : 8
Parity : None
Stop bits : 1
Flow Control : Hardware
When USB connected to PC and 3210EVM, we see red light on D9 LED.
2. Download keypad firmware from host PC into 3210EVM.
We downloaded the keypad firmware source code for TUSB3210 EVM from
Below website.
http://focus.ti.com/docs/toolsw/folders/print/tusb3210kbdpdk.html
Our goal is to download this firmware into 3210EVM using a loading program. It is mentioned
In the spreadsheet, that it is possible to download firmware from host PC into 3210EVM. But,
We don’t see any steps as how we can do that download?
We truly appreciate TI team to help us on this regard.
Thanks,
-Subash
Hello Subash,
In order to download FW from the host PC to the TUSB3210 device, there's a driver (Apploader) that will do it and load FW in the 3210's RAM space. This driver loads the FW by issuing bulk endpoint transfers. Here’s the location of such driver: http://www.ti.com/litv/zip/sllc160 .
Please let me know if this helped in something.
Best,
Ismael
Hi Ismael,
Normal 0 false false false EN-US X-NONE X-NONE
Thanks for pointing the Apploader.
I had followed the steps as mentioned in the readme of the Apploader, for downloading the firmware from PC, but not successful.
Please let me know, if am I missing something.
Also can you give Us the linux version of this Apploader, else Please provide the source Code, we will port it to Linux version.
I am using windowsXP, below are steps I had followed.
# Install the apploader mentioned in below path http://www.ti.com/litv/zip/sllc160
# I noticed the inf file is located in below path.
C:\WINNT\inf\oem11.inf
# Downloaded firmware from below TI site, http://focus.ti.com/docs/toolsw/folders/print/tusb3210kbdpdk.html
# Placed the kb3210.bin file extracted from above link, renamed as TUSB2136.bin in below path
C:\WINNT\system32\drivers
# Now, I had did below Jumpers setting in 3210EVM board,
U3: 2-3 -> Download firmware from PC thro' loading program
U9: 1-2 -> Power thro' USB cable
U12: 1-2 -> Self powered.
# Plug USB cable to PC and 3210EVM, D9 blows red light indicates power supply is ON.
# Configured hyperterminal, and tried for keypresses on 3210EVM, there was no response.
Please find the C:\WINNT\inf\oem11.inf file attached for reference.
Thanks & Regards,
Just for quicker resolution, please let me know if we can have telcon to resolve this issue.
Since, its very critical we can quickly solve this.
-Subash.
Subash,
I’m attaching a new Apploader driver (this one is v2.0 and works for both 32-bit and 64-bit XP/Vista). Run the setup.exe and follow the directions (read the license agreement), by default the driver binaries will be located at C:\Program Files\Texas Instruments Inc\TI USB Apploader Drivers.
If you are going to use XP 32-bit, go to the “x86” directory and modify the INF file with the name of the BIN file included at the “BIN files” directory. Copy the proper BIN file within the “x86” directory.
The problem you are seeing at your end could be related to a BIN file that doesn’t have the proper header information for the TUSB3210 (2136) device.
Please let me know if this apploader works at your end.
I had downloaded the bin file from below TI website link, I am not sure whether it has proper
header information. As mentioned, I had placed the bin file renamed as TUSB2136.bin
as expected in x86 directory.
I still facing issue in loading the firmware using this latest attachment of Apploader driver.
Please let me know, the bin extracted from above link has proper header info and also
how we can would confirm if the firmware is downloaded into RAM?
Please let me know if we can have a telcon this even India time?
Hi Subash,
Please take a look to the documet I'm attaching to this post. This will guide with the Apploader installation.
In case this doesn't work for you, please answer the following questions:
1. How is your TUSB3210 device DETECTED at device manager (I need the VID, PID info)?
2. Do you have a serial EEPROM connected to the TUSB3210 device?
3. Did you try on a fresh OS installation (with no previous Apploader instances installed)?
Thanks for the document. Below are my observation:
1. I had followed instruction as documented the Apploader_driver.pdf file, I
don't see USB devices listed in the Device Manager after connecting the USB cable
into PC.This could be because we have EEPROM(24LC128) is attached in 3210EVM near U12 jumper.
2. I had installed Apploader as fresh, after uninsatlling the previous version of Apploader from control panel.
Please also find the screen snapshot after connecting the USB cable to 3210EVM to PC.
So it seems that this didn't work at your end, did it?
Could you please plug your TUSB3210 device in a different PC (one you are sure it doesn't have any apploader drivers of that stuff...)? I'll like to see which PID is reported at device manager. This could be due to the serial EEPROM you have near U12. If possible, break the SCL line of that serial EEPROM (I don't know if there's a jumper for that pourpose).
Please let me know your comments,
As you have suggested I had tried below 2 options but unsuccessful to see PID reported at device manager:
1. Remove EEPROM from TUSB3210 device and try to follow the instruction as mentioned in Apploader document.
I don't see any PID or VID listed at device manager.
2. Did the item 1 experiment in different PC where apploader is not installed. But didn't see PID at device manager.
Please let me know where could be the issue?
Apart from using Apploader, we also tried in connecting USB device of TUSB3210EVM to linux machine, to make sure firmware loading from EEPROM happens properly. For this we had changed the jumper setting of U3 to 1-2. We see an issue in USB enumeration. Please let us know if the chip itself is functioning properly, else the default firmware night be faulty. Below is the error log message: saurabh@saurabh-desktop:/sys/bus/usb/devices/4-0:1.0/usb_endpoint/usbdev4.1_ep81$ dmesg [ 731.448030] usb 4-1: new full speed USB device using uhci_hcd and address 6 [ 731.628037] usb 4-1: device descriptor read/64, error -71 [ 731.852023] usb 4-1: device descriptor read/64, error -71 [ 732.068019] usb 4-1: new full speed USB device using uhci_hcd and address 7 [ 732.244024] usb 4-1: device descriptor read/64, error -71 [ 732.468017] usb 4-1: device descriptor read/64, error -71 [ 732.684028] usb 4-1: new full speed USB device using uhci_hcd and address 8 [ 733.096028] usb 4-1: device not accepting address 8, error -71 [ 733.264016] usb 4-1: new full speed USB device using uhci_hcd and address 9 [ 733.672022] usb 4-1: device not accepting address 9, error -71 [ 733.672449] hub 4-0:1.0: unable to enumerate USB device on port 1
This is just a follow up in order to see if everything is doing good at your end with the new TUSB3210KBD Eval Board.
Thanks and Best Regards,
Sorry for late response. We are yet to receive the board, will
update the status with the new TUSB3210 EVM.
Please let me know if you had a chance to test the apploader for the TUSB3210 with your EVM.
We need to get our EVM soon, will let you know once we do the testing.
Meanwhile can you clarify how can we upload firmware into EEPROM. I thing we
have reference as how to upload the firmware into RAM using the Apploader driver that
you provided.
ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". TI AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY TI. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM TI.
Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.