TUSB9261: Serial number authorized values

Hi Bruno,

Could you explain in more detail what happens when you enter 64B as a serial number?  How does it fail?

Can you also confirm that the Die ID and auto-generation options are unchecked in the TUSB926x Flash Burner tool menu?  This will affect the serial number output.

There is a command line tool.  Please accept my friend request so we can discuss this through private messaging.

Regards,

Hi Nicholaus,

Thanks for the reply. I confirm that Die ID and auto-generation options are unchecked.

I get no failure message as it prints "Programming Succeeded" in both cases.

Here are 2 screenshots to make it clearer:

Thanks for the command line tool Nicholaus.

Here are some updates:

I tried to visualize the descriptors from USBView, and it actually works way better.

I can now write the serial number from the GUI tool TUSB926x Flash Burner and read it from USB View. 

So "lsusb" doesn't seem to be the right tool to use. Do you know any command line tool that I could use to get USB descriptors on Windows?

On the other hand, I cannot write the serial number from the command line tool you just sent me. I get a different serial number ( 8DF7C54DD3694823AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA instead of AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA )

Also, I unsuccessfully tried with the /ssn option.

2 more related questions:

- What is the best tool to access USB descriptors under Linux ( command line or GUI ) ?

- The User's guide states : "Serial Number String Descriptor – Must be unique for each device, maximum 64 characters long".

String Descriptor is here ambiguous: are characters hexadecimal or could it be ASCII characters?

Hi Bruno, 

1. The simplest way to see the serial number is by using the "Get Current Serial Number" button in the programmer itself.  Another method to see the serial, VID, and PID in Windows is by using the device manager. 

2. The only tool I am aware of that allows you to view USB descriptors in Linux is lsusb.  However, I am not well-versed in the Linux ecosystem. There may be another tool, but the environment we officially support for the TUSB9261 is Windows.
3.  Characters in this context refers to each symbols that is produced with a stroke of your keyboard.  0x30, for example, would be 4 characters.

Would you please post your descriptor file so we can try to reproduce the issue you are having with the console app?

Thanks,

Hi Nicholaus,

1. Thank you for the information. FYI there if also USBView on Windows

2. lsusb seems unreliable

3. However, I'm not able to put anything else than hexadecimal figures in the serial # textbox.

Can't attach the file, I'll try later.

Any feedback?

Hi Bruno,

I am working on replicating this on my side and will let you know the results as soon as possible, hopefully by the end of the week. 

Hi Bruno,

Much apologies for the delayed response, I was having some unrelated IT issues. I have not been able to reproduce your issue on my side with the flashburner command line tool. When I write 64 "B" characters in the utility, i see 64 "B" characters reported back in the USB descriptor using USBTreeview to check. Instead of using a descriptor file i used the "/ssn" command to achieve this. Could you share an example string you hope to write as the descriptor so I can try this or your descriptor file? See below for the specific command I used.

TUSB926x_CL_Burner.exe /s 0 /f "[Firmware Binary Name]" /ssn BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB

Hi Malik,

Thank you for your answer. I tried the exact same command but I still got the modified serial number string:

Whatever string I try to write in the serial number field, the 16 first characters are always 8DF7C54DD3694823.

Here is an example of what I'd like to write:

Product: DTR0000482017_Axxx_SSD512GB

Manufacturer: Centralp_K210489_xxx

SerialNumber: 1310090101907

When I try this, Product and Manufacturer fields are right, not the Serial Number field.

Let me know if you need more informations about my configuration.

Hi Bruno,

It seems you are using a different version of the command line software than I. This may have a unchangeable option to automatically write the serial number with what looks like the die ID. I will direct message you the version I am using, please let me know if this works with the same commands in my previous post. 

Bruno:

   any update?

Hi Brian,

According to Malik, it may be a problem with the flash.

We will produce the prototype of our board next week, I'll try again with it.

I can't do more meanwhile, since I have no other EVM board.

waiting from customer

Hi,

I've tried with the our prototype board, and I still get the same problem: 16 first characters of the serial number field are wrong.

I've tried with command line tool versions 1.0.0.1 and 1.3.1.0 with the same result.

Programming is OK with the GUI tool.

Hi,

I am not sure why this issue is present and I am unable to duplicate on my side. Do you see this issue on any PC you try? Each prototype board has a clean flash correct?

Hi Malik,

I'm trying to program from another computer.

Howerver I'm getting a problem with the driver installation: Flashburner driver installation failed. Please manually install the driver and try again.

So I've tried installing the driver manually from the device manager > update driver, but the automatic research of the driver fails.

Where can I get the driver?

Hi,

Sorry for the late reply. Have you tried running installer with admin privileges? The driver should be located in the folder designated at installation. Default folder path is C:\Program Files (x86)\Texas Instruments Inc\TUSB926x_Burner

Is there any more support needed for this issue? If so please reply with any relevant details so that I can further assist you. For now I will be marking this thread as "TI Thinks Resolved". If you have resolved your issue, please post the solution to the original problem/post for others with similar issues.

Hi Malik,

I've run the installer with admin privileges. I've tried installing it manually from device manager and I've try running Driver_Inst.exe with admin privileges. Still not working.

My other problem concerning the use of the command line tool is not resolved either since I cannot test on another computer.

Hi,

Please create a copy or confirm that the difxapi.dll driver is located at this file path C:\Windows\System32.

I confirm difxapi.dll is in C:\Windows\System32

Hi,

Sorry for the delay. I am still looking through the source to understand what could cause this issue. I will let you know as soon as I find a possible solution for you to try.

sorry, we are still working on it, will update as soon as we have solution

Hi Bruno,

Sorry for the very long delay. I have been searching for the root cause of the issue. Are you still experiencing the issues described? If so can you check if wdfcoinstaller01009.dll is located in C:\Windows\System32 and wdfapldr.sys is located in C:\Windows\System32\drivers? For the serial# issue, can you open Options.dat in C:\Program Files (x86)\Texas Instruments Inc\TUSB926x_Burner can OverrideSerialWithDieID to false?

Hi Malik,

Thank you for investigating.

I'm still facing the same issues, indeed.

• wdfcoinstaller01009.dll is in C:\Windows\System32
• wdfapldr.sys is in C:\Windows\System32\drivers
• The serial number issue occurs with the command line tools only. I changed OverrideSerialWithDieID to false but the problem is still there

Hi Malik,

Adding the /iid option worked !

I'll try to correct the driver install issue later, I'm not sure I need to fix it anymore since it works on my main computer.

Thank you for your help !

Hi Bruno,

I am happy to have helped with the main issue! If you do happen to see the driver install issue resolved please post here to help others with the same issue.