TPS65982: Error Saving Binary file from the Application Customization Tool

Part Number: TPS65982
Other Parts Discussed in Thread: TPS65981

Hi,

We use TPS65982 with TUSB546AI for USB-C DP-Alt mode as a host.  The unit is working fine with the TI provided firmware (TPS65982.bin) file.  I need to generate a document, which includes the source file and verify the binary file.  From TI Application Customization Tool, I imported the binary file (by selecting "Change file" button) and then saved the binary file.  An error stated the file too big.  It seems the configuration size (see attached image below) is too big (4294967295 bytes).  If this is the problem, can I change the Configuration size?  I can provide the binary if needed.  Also, is there another war way to generate the source file?

FYI, I have tried using "default.bin" file from the application and also "Import Setting from Device", both binary files did not match the provided TPS65982.bin file.

Thank you in Advance

  • Hi,

    Thanks for reporting this issue. May I know which GUI version this occurred on and can you provide the binary you were using for me to replicate this issue on my end?

    Regards.

  • Hi,

    Can you also provide your project files?

    Regards.

  • Hi

    Thank you for your replied.  From the Help menu it is

    TPS65981_2_7_8 Application Customization Tool

    GUI Version : 6.1.2

    Date of release : 26th April, 2021

    Also, see attached binary file.  I have not save a project file since I cannot create a binary file that match to the attached binary file (Please rename the file without ".txt" extension).  I have tried saving a binary file from either imported from this programmed device or changed the bin file.  Changing the bin file method gave error when saving a file.  here is an error below

    Exception Encountered during Application Binary Save:range() result has too many items.

    Could it be the allocated app configuration size?

    Moda.bin.txt

  • Hi,

    There is a possibility that having too many GPIO event mapping can cause the config data overflow resulting in file size issue hence why I am asking for the .pjt file to double check.

    Also, the latest release of the TPS65981_2_7_8 Application Customization Tool is version 6.1.3.

    Regards.

  • import.bin.txtCOM Bd Config for TPS65982.pjtHi,

    There are only 4 events (AMSEL, Orientation, plug, and DP or USB events).  Anyway, I created a new project file and saved a binary files using "Import Settings from Device" under setting menu, see attached project file.  The new saved binary is different than the provided binary file after compared them.  After programmed the new binary file to the board, the TPS65982 seems to work correctly.  Can you provide descriptions for the different between the two binary files, see Import.bin file?  I cannot insert the 2 files is there other way to do this?

  • Hi,

    I will take a deeper look at it.

    What are the 2 files you tried to insert? You should be able to upload the attachments by dragging the files to the text box.

    Regards.

  • Hi Tommy,

    The two files are Moda.bin and import.bin, which were attached on previous chats, 4th and 6th respectively.

    Best Regards,  

  • Got it, will look into them and see if I can recreate them on my end.

    I will get back to you by the end of this week.

    Regards.

  • Hi,

    One thing to keep in mind is that the binary file imported from "Change file" should be a low region binary.

    The size of Moda.bin is way too large for a full flash binary or a low region binary, can I know how or where did you obtain the Moda.bin?

    The import.bin seems to be a full flash binary based on the size of the file and your description (flashed to the device).

    Regards

  • Hi Tommy,

    Yes, Moda.bin file is full a flash binary with the rest fill with FF to 1MB flash memory.  When I imported Moda.bin file, the application did not give an option to select only lower region or set offsets for region1 and region2.  Can you tell me how to import low region from "Change file"?

    The import.bin is also a full flash with region2 offset set to 0x12000.  Both binary files are working, but there are many differences.  Can you let me know the differences?  Attached is an excel file, which compares the 2 binary files.  On the "compare2import" sheet, a blank cell mean they are the same and only display import.bin content if they are different.  The differences of the binary files start from line 786 on the "compare2import" sheet.Compare Moda to import.xlsx

  • Hi,

    Since there are no pop-up warning when importing the incorrect binary in "Change file", I would suggest you that when you saved the low region binary using the GUI, change/add the file name with some characters that indicate which binary is a low region binary. I will provide this feedback to the GUI and see what they can do here for the future release to avoid this kind of issues.

    I will check the difference between the moda.bin and import.bin later and get back to you next Wednesday. There may be changes implemented such as a new FW patch was added when new GUI was released.

    Regards,

    Tommy

  • Hi Tommy,

    Did you have chance to look at the differences between the two binary files?

    Best Regards,

    Alex

  • Hi Alex,

    Tommy will be out of office until next Monday (7/18). Thank you for your patience. 

    Regards,

    Raymond Lin

  • Hi Tommy,

    Any comments?

  • Hi,

    Directly comparing two binary file content is not helpful in determine the difference in configuration between the two. My suggestion is load the binary to the device, then read the setting using the GUI (Device > Import Settings From Device).  If there are no difference in settings (in all the GUI tabs), then the difference is most likely some firmware or GUI fixes that we do not reveal to the public.

    Regards.