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.

UNIFLASH: Error initializing emulator

Part Number: UNIFLASH
Other Parts Discussed in Thread: UCD3138,

Tool/software:

I encountered the following error while trying to download my program from my UCD3138 chip using Uniflash software. Could you please advise on how to resolve this issue。

  • There is only a generic error about initializing emulator. Are you able to connect to your board using CCS desktop?

    Thanks

    ki

  • Hi,Ki

    I can connect to the chip through CCS software。

    Thanks!

  • Can you try using the working ccxml file from CCS with UniFlash? You can use the option at the bottom in UniFlash to use an existing ccxml file:

  • Hi,Ki

    I have also used this method, but the phenomenon I obtained is the same as this problem

    Thanks!

  • Hi,Ki

    I retested the method of using ccxml files, and this is the result obtained

  • Which version of UniFlash are you using?

  • Hi,Ki
    This is my UniFlash software version.
  • Can you reproduce the issue while creating a debug server log?

    See the section at the end of the below document called "Defect Reporting and Logging"

    https://dev.ti.com/tirex/explore/node?node=A__AIteuKh6UsP.iRiklRLzUg__sdtoutilities__FUz-xrs__LATEST

    Please zip and attach the log to this thread.

    Thanks

    ki

  • Hi,Ki

    I conducted the test according to the above instructions and obtained the logs.

    uniflash_gui_debug_log.rar

    Thanks!

  • I conducted the test according to the above instructions and obtained the logs.

    uniflash_gui_debug_log.rar

    This appears to be just for the GUI Logging. I am more interested in the Debug Server Logging:

    Can you provide this one?

    Thanks

    ki

  • Hi,Ki

    I don't seem to be able to provide it. When I click Enable, the following error message pops up:

    I checked this folder and found that there is no ds.rog file

    Thanks!

  • Thank you for trying. I will try to find a UCD3138 device and try it myself.

  • Hi,Ki

    Okay, waiting for your reply

    Thanks!

  • Are you using a standalone XDS110 like the below?

    https://www.ti.com/tool/TMDSEMU110-U

  • Hi,Ki

    I did use the XDS110 device displayed for simulation, and here is the connection diagram I used. I can successfully simulate it on CCS software.

    Thanks!

  • Can you try UniFlash 8.8.1? I'm wondering if there was a regression with version 9.0

    https://www.ti.com/tool/download/UNIFLASH/8.8.1

    Thanks

    ki

  • Hi,Ki

    I have switched to version 8.8.1 for testing again. Here is the version:

    After retesting, it still has the same problem:

    Thanks!

  • Ok, I am a bit surprised (and a little disappointed) that 8.8.1 didn't work. This is because while I don't have a UCD3138, I do have another ARM7 based device to try with my XDS110 debug probe. I was able to reproduce the same issue with UniFlash 9.0 that you see but UniFlash 8.8.1 appears to work fine. 

    Sorry to keep bothering you but can you:

    1) attach the ccxml file you are using

    2) Try an even earlier UniFlash version like 7.2? 

  • Hi,Ki

    This is the ccxml file I am currently using:

    1732.test.zip

  • Thank you. The ccxml is similar to what I am using.

    Did you have a chance to try a older UniFlash version like 7.2? I am pretty certain that this issue only impacts more recent UniFlash versions.

  • I think I found the root cause.

    Can you try the following:

    1) Open a DOS command window and browse to: <UNIFLASH 9.0 INSTALL DIR>\deskdb\content\TICloudAgent\win\ccs_base\common\uscif\xds110

    2) run the following commands:

    > xdsdfu -m

    > xdsdfu -f firmware_3.0.0.33.bin -r

    3) After flashing is done, power cycle XDS110

    4) Launch UniFlash 9.0 and try again.

    Thanks

    ki

  • Hi,Ki

    I don't quite understand how to operate it. I found this folder and ran the command you provided, but it didn't work.

    Thanks!

  • In your DOS cmd window, please change the directory to the location to xdsdfu utility first. Right now, you are in your home folder "C:\Userss\Maliang". That is why the cmd window cannot find xdsdfu.

  • Hi,Ki

    Okay, I tried again and found that the first command was fine, but there was a problem with the second command. I modified it from instrware_3.0.0.0.33 to instrware_3.0.0.0.32, but it didn't work. I checked the folder and found that it should be the firmware 3.0.0.0.32.bin file. Then I tested that both firmware 3.0.0.0.32.bin and firmware 3.0.0.0.33.bin didn't work.

    Thanks!

  • Your first two screenshots have the firmware name incorrect.

    The third screenshot is referring version 32 of the firmware. UniFlash 9.0 should come with firmware 33.

    The forth screenshot looks odd. You put it in dfu mode but then the utility failed to find the file. Then you ran the utility again but it was not in dfu mode.

    Can you try the below. I would like for you to use the latest firmware that I attached below:

    firmware_3.0.0.36.bin.zip

    Download and extract the file to: <UNIFLASH 9.0 INSTALL DIR>\deskdb\content\TICloudAgent\win\ccs_base\common\uscif\xds110

    1) Open a DOS command window and browse to: <UNIFLASH 9.0 INSTALL DIR>\deskdb\content\TICloudAgent\win\ccs_base\common\uscif\xds110

    2) run the following commands:

    Check that the XDS110 is detected.

    > xdsdfu -e 

    Put XDS110 in DFU mode

    > xdsdfu -m

    Flash version 36 of the firmware that you just downloaded and extracted.

    > xdsdfu -f firmware_3.0.0.36.bin -r

    Check that the XDS110 is detected and that the firmware version is now version 36.

    Below is example video. double click on it to make it large.

  • Hi,Ki

    Okay, I tried following the instructions in the video and found that there was still the same problem as before. The utility couldn't find the file. I checked the corresponding directory and found that the file was inside.

    Thanks!

  • I'm very confused why that is not working. I see the file there in your screenshot. I assume it can't find firmware_3.0.0.32.bin either.

    Maybe try an absolute path? Could it be that some security software is blocking access to the file? I am very confused??