• State Resolved
  • Locked Locked
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 529 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Unflash "MiniDump.dll" error

Lucas Holzen
Prodigy 101 points
Part Number: UNIFLASH
Other Parts Discussed in Thread: CC1312R7, CODECOMPOSER, CC1352P7, LP-CC1312R7

Whenever I try and use Uniflash I get the error in the image. This happens regardless of whether its the online or Windows version.

Its not the debugger or connection. Using CodeComposer Studio I can download connect to my board and chip (CC1312R7) over the debugger without any issue. I even updated the firmware on the debugger (XDS110).

Error: 0x00007858 115 3 LIB C: dlopen( "MiniDump.dll", 0 ) 0x00007858 115 3 LIB R: dlopen( "MiniDump.dll", 0 )   OR

0x00002C08 532 3 LIB C: dlopen( "MiniDump.dll", 0 ) 0x00002C08 532 3 LIB R: dlopen( "MiniDump.dll", 0 ) = 00007FFE04B30000

I have reinstalled Uniflash 8.3 multiple times. Any ideas?

  • 0
    TI__Mastermind 20407 points

    Hi Lucas,

    At which stage do you see the error? Does this pop up at device detection or when you are flashing the board?

    If it is during flashing, please can you try a different project to see if an example project works?

    Uniflash 8.5 is already released in November, Is there a reason you are still in 8.3?(this is likely not a fix, but just curious). www.ti.com/.../UNIFLASH

    Regards,

    Sid

  • 0 in reply to Sid
    Prodigy 101 points

    Hi Sid,

    Uniflash 8.5 has the same problem (I just tried it). I get the issue by pressing the "Read Device Info" button after the programmer is detected but before it has tried to communcate to the board. Pressing the "Load Image" button with a valid image of your choice produces the same result.


  • 0 in reply to Lucas Holzen
    TI__Mastermind 20407 points

    Hi Lucas, 

    Your screenshots, seem to differ with the device, did you try both CC1352P7 and CC1312R7? 

    I tried Uniflash 8.5 and was able to read infor from both CC1352P7 and CC1312R7. I will reach out to the Uniflash team. 

    Regards,

    Sid

  • 0 in reply to Sid
    Prodigy 101 points

    Hi Sid, Good eye. When using using auto-detect, it pulls up the CC1352P7. However, I can manually select the CC1312R7. I get the same issue regardless of which chip Uniflash targets. Even using the LP-CC1312R7 

  • 0 in reply to Lucas Holzen
    TI__Guru**** 465341 points

    Lucas - Do you get the same error when trying to read contents of memory? I am going to guess that you do but would like to confirm.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 101 points

    Hi Ki,

    That's correct. Same issue.

    Lucas

  • 0 in reply to Lucas Holzen
    TI__Guru**** 465341 points

    Can you generate a Debug Server log and attach it to this thread?

    See section called "Defect Reporting and Logging": https://software-dl.ti.com/ccs/esd/uniflash/docs/v8_5/uniflash_quick_start_guide.html#defect-reporting-and-logging

    Can you also provide the host OS (and version) being used?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 101 points

    Hi Ki,

    Windows 11 Pro 10.0.22621 Build 22621.

    I was able to do the GUI debug (attached). The DS Server debug shows the "Enable" button whenever I open Settings. When I click on it the button changes to "Disable" but it does not show a path to the ds.log file (as in https://software-dl.ti.com/ccs/esd/uniflash/docs/v8_5/uniflash_quick_start_guide.html#defect-reporting-and-logging). Closing and re-opening the Settings window has the DS Server debug logging disabled again. I tried running in admin mode and looking on the file system for a ds.log file but to no avail.

    Fullscreen 8637.uniflash_gui_debug_log.txt Download 
    07:51:32:571 log - NWAgentAPI: dinfraConfigue resolved successfully.
07:51:33:161 error - {}
07:51:33:171 error - {}
07:51:33:179 error - {}
07:51:33:180 error - {}
07:51:33:198 error - {}
07:51:33:201 error - {}
07:51:33:232 error - {}
07:51:33:235 error - {}
07:51:33:257 error - {}
07:51:33:265 error - {}
07:51:33:284 error - {}
07:51:33:290 error - {}
07:51:33:292 error - {}
07:51:33:381 error - {}
07:51:33:391 error - {}
07:51:34:036 error - {}
07:51:34:039 error - {}
07:51:34:075 error - {}
07:51:34:383 error - {}
07:51:35:487 error - {}
07:51:35:495 error - {}
07:51:38:467 error - {}
07:51:38:478 error - {}
07:51:38:492 error - {}
07:51:38:516 error - {}
07:51:38:519 error - {}
07:51:38:526 error - {}
07:51:38:538 error - {}
07:51:38:547 error - {}
07:51:38:568 error - {}
07:51:38:573 error - {}
07:51:38:583 error - {}
07:51:38:587 error - {}
07:51:38:598 error - {}
07:51:38:604 error - {}
07:51:38:609 error - {}
07:51:38:620 error - {}
07:51:38:625 error - {}
07:51:38:654 error - {}
07:51:49:033 error - {}
07:51:49:105 error - {}
07:51:49:115 error - {}
07:51:49:154 error - {}
07:51:49:165 error - {}
07:51:49:238 error - {}
07:51:49:249 error - {}
07:51:49:254 error - {}
07:51:52:719 error - {}
07:51:52:726 error - {}
07:51:52:868 error - {}
07:51:52:876 error - {}
07:51:59:738 error - {}
07:51:59:757 error - {}
07:51:59:780 error - {}
07:51:59:789 error - {}
07:52:03:404 error - {}
07:52:03:415 error - {}
07:52:05:804 error - {}
07:52:05:809 error - {}
07:52:06:455 error - {}
07:52:06:461 error - {}
07:52:06:466 error - {}
07:52:06:489 error - {}
07:52:07:404 error - {}
07:52:07:412 error - {}
07:52:08:063 error - {}
07:52:08:068 error - {}
07:52:25:345 error - {}
07:52:25:367 error - {}
07:52:27:444 error - {}
07:52:27:452 error - {}
07:52:27:457 error - {}
07:52:27:572 error - {}
07:52:27:708 error - {}
07:52:27:760 error - {}
07:52:27:804 error - {}
07:52:27:852 error - {}
07:52:27:895 debug - ufDS, session.configured, partnum of current session = cc1352p7
07:52:27:897 error - {}
07:52:27:911 error - {}
07:52:27:986 debug - addTargetStateListener on Cortex_M4_0
07:52:28:034 error - {}
07:52:34:319 debug - returning new configure
07:52:34:706 error - {"message":"0x00005E88 172 3  LIB C: dlopen( \"MiniDump.dll\", 0 )\r\n0x00005E88 172 3  LIB R: dlopen( \"MiniDump.dll\", 0 ) = 00007FFDFCBE0000\r\n"}
07:52:34:706 error - configure failed: 0x00005E88 172 3  LIB C: dlopen( "MiniDump.dll", 0 )
0x00005E88 172 3  LIB R: dlopen( "MiniDump.dll", 0 ) = 00007FFDFCBE0000

07:52:34:707 error - {"message":"0x00005E88 172 3  LIB C: dlopen( \"MiniDump.dll\", 0 )\r\n0x00005E88 172 3  LIB R: dlopen( \"MiniDump.dll\", 0 ) = 00007FFDFCBE0000\r\n"}
07:52:34:707 error - 0x00005E88 172 3  LIB C: dlopen( "MiniDump.dll", 0 )
0x00005E88 172 3  LIB R: dlopen( "MiniDump.dll", 0 ) = 00007FFDFCBE0000

07:52:40:007 error - {}
07:52:40:012 error - {}

  • 0 in reply to Lucas Holzen
    TI__Guru**** 465341 points
    Lucas Holzen said:
    The DS Server debug shows the "Enable" button whenever I open Settings. When I click on it the button changes to "Disable" but it does not show a path to the ds.log file

    That's really odd. When I press "Enable", I get the full path like:

    I am using Windows 10. I'll try to see if this works on Windows 11.

  • 0 in reply to Ki
    Prodigy 101 points

    Huh. I do not get that path when pressing Enable. I can go to that that path. It has some config files in there, but no ds.log files. One of the log files attached for reference. They're very dull.

    Fullscreen uniflash-2024-02-02.log Download 
    {
    "stamp": "2024-02-02T21:42:36.254Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "VMware Network Adapter VMnet1",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T21:42:36.255Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "VMware Network Adapter VMnet8",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T21:42:36.255Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "Wi-Fi",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T21:42:36.256Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "vEthernet (WSL (Hyper-V firewall))",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T21:50:53.231Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "VMware Network Adapter VMnet1",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T21:50:53.233Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "VMware Network Adapter VMnet8",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T21:50:53.233Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "Wi-Fi",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T21:50:53.233Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "vEthernet (WSL (Hyper-V firewall))",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T22:05:24.105Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "VMware Network Adapter VMnet1",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T22:05:24.107Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "VMware Network Adapter VMnet8",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T22:05:24.107Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "Wi-Fi",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T22:05:24.107Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "vEthernet (WSL (Hyper-V firewall))",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T22:26:29.024Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "VMware Network Adapter VMnet1",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T22:26:29.026Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "VMware Network Adapter VMnet8",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T22:26:29.026Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "Wi-Fi",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},
{
    "stamp": "2024-02-02T22:26:29.026Z",
    "priority": "INFO",
    "facility": "DAEMON",
    "service": "dinfra",
    "args": [
        "multiple candidate address ignored",
        "vEthernet (WSL (Hyper-V firewall))",
        {
            "address": "100.85.55.81",
            "netmask": "255.255.255.255",
            "family": "IPv4",
            "mac": "00:00:00:00:00:00",
            "internal": false,
            "cidr": "100.85.55.81/32"
        }
    ]
},

  • 0 in reply to Lucas Holzen
    TI__Guru**** 465341 points

    I tried this on my Windows 11 PC and everything still worked as expected. You have this issue with both 8.3 and 8.5?

  • 0 in reply to Ki
    Prodigy 101 points

    Correct. 

  • 0 in reply to Lucas Holzen
    TI__Guru**** 465341 points

    Can try a different way to generate the log:

    Go to the section "Diagnostic Server Logs -> Command Line") in the below article and follow the steps to enable DS logging from a DOS console:

    https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html#command-line

    Then from the same console, launch Uniflash via:

    > C:\ti\uniflash_8.5.0\node-webkit\nw.exe "C:\ti\uniflash_8.5.0"

    If you installed UniFlash 8.5 in a custom location then update the above accordingly.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 101 points

    Okay, I think I fixed the issue. At some point I had set a windows envionment variables below. It must have been what was messing with the uniflash instance. Uniflash now works just fine.

    TI_DS_ENABLE_LOGGING=true
    TI_DS_LOGGING_OUTPUT=c:/temp

  • 0 in reply to Lucas Holzen
    TI__Guru**** 465341 points
    Lucas Holzen said:
    At some point I had set a windows envionment variables below.

    Interesting. Did you set those in the past to troubleshoot something else in the past?

    In any case I'm glad you found the root of the issue. Thanks for the update!

  • 0 in reply to Ki
    Prodigy 101 points

    I did run into issues with it previously, but CCS was working and it was a lower priority issue so after some failed debugging I moved on.

  • 0 in reply to Lucas Holzen
    TI__Guru**** 465341 points

    After some investigation, it appears that the issue is that TI_DS_LOGGING_OUTPUT was set to a directory that already exists without an additional file name. The apparently causes some issue with TI Cloud Agent which was impacting UniFlash.

    I filed a bug for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-11635

    Thanks

    ki