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.

USB-C-PD-DUO-EVM: USB-C-PD-DUO-EVM Configuration / Flashing problems

Part Number: USB-C-PD-DUO-EVM

Hello,
I'm trying to use the USB-C-PD-DUO-EVM by following the USB-C-PD-DUO-EVM User's Guide,
but I'm noticing that there are differences between the SW release date

"
TPS65981_2_7_8 Application Customization Tool

GUI Version: 6.1.4

Release date: March 29, 2023
"
and the date of the manual
"SLVUBJ5–October 2018".
Q1 - Would it be possible to have a version of the manual aligned with the SW release date?

In any case I'm trying to take the first steps, but I'm having a lot of problems.

My HW is this: J1 powered with 19,5V, PC connected with a usb micro cable to the EVM.


As for the interface connection, I believe this is there, in fact with the usb micro disconnected
I get this message 
"Exception Encountered during FTDI Adapter Selection:No FTDI I2C channels (I2C_GetNumChannels) detected, exiting....

<type 'exceptions.Exception'>

"
while when the micro usb cable is connected I get this popup when I click on "adapter"
 
but if I perform the Sweep I2C Addresses it fails

then if I try "TEST I2C HI READ (MODE REGISTER 0x03)

I get this FAIL MESSAGE

then if I try "TEST I2C HI READ (MODE REGISTER 0x0F)

I get this FAIL MESSAGE

then if I try "TEST SPI FLASH READ (Address 0x00)

I get this SUCCESS MESSAGE

Q2 - how can I fix the problem (if any) with I2C?

Q3 - which is the file to be loaded, that I cannot find source.bin or sink.bin?

Q4 - when loaded a .bin file wuth "change file" button, which is the command to start flash?

Thanks

      Alessandro

  • Hi Alex,

    hope you are doing well,

    can we please follow the topic.

    Thanks

  • Hi Alessandro,

    To flash the TPS65987DDJ EVM with the full binary I provided you, follow the steps below:

    1.) Open the 6.1.4 GUI and create a new project. You can select TPS65987DDK.

    2.) On the next screen, select any port type for the project, as this is not relevant. We are only opening a new project so we can flash the binary.

    3.) Once the new project is created, go to the adapter tab at the top and perform an I2C sweep as usual with the TIVA option.

    4.) Next, go to the binary tab at the top and select "flash from binary file".

    5.) On the window that pops up, you must now load a binary file to flash to the device. Click on the "change file" button to load a binary, and select the binary I provided, named "987DDJ_Source_Sink.bin".

    6.) Now click ok and the binary should start flashing to the device.

    Please try these steps and if any fail, let me know at what step the failure occurs.

    Best,

    Alex

  • I noticed you were trying to flash to the binary with no binary file selected in the previous messages. This is not allowed as there needs to be some file to flash from. The process automatically erases the flash at the start, so no need to manually attempt an erase.

  • Hi Alex,

    I followed exactely the steps up to the 6th (STEP 3 ALL TESTs OK), but when click the OK I get this

    closing this popup I get this 

    and it does not proceed.

    Please, can I fix some way?

    Thank you very much.

        Alessandro

  • Hi Alessandro,

    I will try to find and replicate on 987DDJ EVM. In the meantime, do you happen to have an Aardvark I2C/SPI Adapter tool?

    Best,

    Alex

  • Hi Alex,

    No I've not exactely that model, but I've the possibility to interact with that buses with other boards if needed.

    Thank you very much.

          Alessandro

  • Hi Alex,

    please, how can we continue with this topic?

    Thanks

        Alessandro

  • Hi Alessandro,

    I only have a TPS65987DDJ EVM with FTDI available to me, not an EVM with TIVA. With FTDI instead of TIVA, the steps I gave you did work. The flashing was successful. I need to test again with TIVA by doing some custom pin jumping between EVMs. I will update you tomorrow.

    Best,

    Alex

  • Hi Alessandro,

    I was able to obtain a TPS65987DDJ EVM with TIVA and test flashing a FW. I used the same binary file I sent you and followed the same steps. I was able to flash the TPS65987DDJ binary I provided successfully using the 6.1.4 GUI tool and a TPS65987DDK empty project template. This is done with same hardware, GUI, and procedure. It seems like the issue may be an issue with the GUI or EVM itself.

    Could you try uninstalling and reinstalling the 6.1.4 Application Customization GUI (allow the installation process to reinstall all necessary drivers for FTDI/TIVA)? 

    Please also confirm the jumper and switch settings on the top side of the EVM:

    • Switch S3 (Near Barrel Jack) - Disable Flash Config: OFF
    • Switch S4 (Bottom Right): 
      • 1 - OFF
      • 2 - OFF
      • 3 - OFF
      • 4 - ON
      • 5 - OFF
      • 6 - OFF
    • Jumper J5 (PP_HV2): 2 & 3
    • Jumper J4 (PP_HV1): 1 & 2

    Attached is the binary I used, which I previously sent to you. Providing it again for reference:

    6835.987DDJ_Source_Sink.bin

    Best,

    Alex

  • Hi Alex,

    I performed the suggested actions, and I performed the suggested chech:

    - I unistalled the application and installed the application again checking that the driver phase is closed correctely

    - I checked that all jumpers and switches are in the indicated positions

    - I tried again to flash the EVM but unfortunately the behaviour is exactely the previuos observed.

    Please suggest us how to proceed

    Thanks

       Alessandro

  • Hi Alessandro,

    We provided steps to flash the EVM and ensured those steps were working with the same hardware. Unfortunately, something is causing the flashing to fail on your end. At this point, we don't have any other recommendations to flash the EVM other than loading the FW binary to the SPI Flash itself on the EVM. This can be done with most SPI Flash programmer tools sold online, as well as the Aardvark I2C/SPI Host Adapter I mentioned before.

    Best,

    Alex