This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

tusb8041: EEPROM Configuration & Programming

Part Number: TUSB8041
Other Parts Discussed in Thread: TUSB8041

Hello,

I have 4 fold question;

1.     Do you have a default file for configuring the EEPROM, so I only have to change the parts I need, and the rest are as default (i.e the registers if no EEPROM attached). This is because the “reset” function in the software simply sets it all to “FF” not the default from inside the usb hub.

2.     Is there a command line utility to automate the programming?

3.     If I write “55” to address 0x00 it will use th EEPROM. But from reading the document with the software, you can then not wipe or reconfigure the EEPROM from the software? Is this correct?! If so, how do I wipe the EEPROM if we need to configure it differently after programming? (.e. SMD devices we don’t want to be removing just to reconfigure them!)

4. Furthermore, the recommendation in the TUSB8041 data sheet USB-B upstream port and the implementation on the evaluation board do not match:The datasheet shows as below. However, this does not flow without swapping the P/M lines. This appears (after continuity checking) on the evaluation board.

Is there a reason that this has been intentionally avoided? Which is the best practice

Will appreciate responses on this

  • Hello,

    1. File attached

    2. No, we just have a windows GUI, this is only for test purposes not for mass production.

    3. You can write and re-write the eeprom as many times as you want using the software we provide or using your mass production methods, address 00h=55h means there is a valid eeprom attached.

    4. Sorry, I don't understand, can you elaborate more on what the mismatch is?

    If you need the windows GUI, please provide an email address.

    Regards

    00	55	01010101	'ROM Signature - Do NOT modify!
    01	51	01010001	'Vendor ID LSB - Can be modified
    02	04	00000100	'Vendor ID MSB - Can be modified
    03	40	01000000	'Product ID LSB - Can be modified
    04	81	10000001	'Product ID MSB - Can be modified
    05	10	00010000	'Device Configuration - U1U2 ON
    06	00	00000000	'Battery Charging (1 = enabled) - Can be modified 
    07	0F	00001111	'Device Removable- Can be modified 
    08	0F	00001111	'Port Used - Can be modified
    09	00	00000000	'Phy Custom - Can be modified
    0A	22	00100010	'Device Configuration 2 - Can be modified
    0B	00	00000000	'usb 20 Port Polarity
    20	09	00001001	'Language ID - Can be modified
    21	04	00000100	'Language ID -  Can be modified
    22	00	00000000	'Serial Number String Length -  Can be modified
    23	00	00000000	'Manufacturer String Length 
    24	00	00000000	'Product String Length 
    F0	00	00000000	'Additional Features
    
    
    
    'DATA FILE FORMAT: <HEX ADDRESS><TAB><HEX DATA>. EVERYTHING AFTER <DATA> IS IGNORED.
    'USE <'> FOR IN-LINE COMMENTING.
    'DATA FILE PARSING STOPS AT FIRST BLANK LINE.
    

  • Hi Elias,

    Can you still provide the windows GUI for testing the TUSB8041?

    My email: l-Igboanugo@ti.com

  • Hello Linda, 

    I have sent you the details through email. Please let us know if you have questions or comments. 

    Regards

  • Hi Joel,

    THanks for you email although it seems I mis-wrote; What my customer islooking for is the source code for the programmer tool.

    see comment from customer below;

    I understand that it is not command-line compatible. Would it be possible to get the source code so I can make it command-line compatible and automate it for our in-house testing?

    I have forced it to endpoint programming. If I do not, then it will not work as a hub. Is this correct as on the demo-board it would (with a version 0100 chip).
    The ones we have on production board report as version 0101 and will not work as a hub if not in endpoint programming mode.

    We believe it to be something with the EEPROM. If the device is placed the TUSB8041 sees it, does not act as a hub.
    It allows connection as a programming endpoint which your software connects to.
    It will thou not allow programming. I have checked the WP (write-protect) pin and it is low.

    We are about to try a different make of EEPROM in case there is an issue there.

    Hope you can still help?
  • Hello Linda,

    The TUSB80XX EEPROM programming GUI was developed to be used during the development phase of a project, not on a mass production environment; hence we cannot provide the applications source code.

    EEPROM should be programmed using industrial grade EEPROM programmers either before soldering the EEPROM on the board, or after soldering it during ICT.

    Regards,
    Jorge
  • HI Jorge,

    the request is not for mass production, but just to allow them easily get the design up and running, to show proof of concept.

    Can you help?

  • Hello Linda,

    I don't think the EEPROM programming GUI source code is needed for a proof of concept.
    Can you please elaborate on what the issue is? It is still not clear to me.

    Please provide the model of the EEPROM they are using.

    Note: EEPROMs used along with TUSB8041 are required to use a single byte for register addressing.

    Regards,
    Jorge