Z-Tool: How to run scripts correctly?

ZC_Com in the script has been changed to COM30 (please see the original message).

I wrote a simple script to test:

import System;
import System.Text;
import TI.ZPI2;

class TheScript
{
  // Main class function that effects the work of this test script.
  function run()
  {
      ZEngine.WriteLog("TEST\n");  // Display the message.
  }
}

// The script engine will execute the following code.
var script:TheScript = new TheScript();
script.run();

The result is the same, no messages in the logs.

Thanks for the advice. I would also like to know the opinion of the developers of the program. Probably, there are diagnostic procedures that will allow to establish the exact cause of the malfunction.

I have tried 4 versions of Z-Tool:

- C:\Texas Instruments\Z-Stack Home 1.2.2a.44539\Tools\Z-Tool
- C:\Texas Instruments\simplelink\zstack_home_1_02_02a_44539\Tools\Z-Tool
- C:\Texas Instruments\Z-Stack 3.0.2\Tools\Z-Tool
- C:\ti\simplelink_cc13x2_26x2_sdk_3_10_00_53\tools\zstack\ztool

The result is the same.
As I understood, since there is no possibility to turn on a detailed debug log in  Z-Tool, I have to either use the VirtualBox or not use scripts.

By the way, when I tried Z-Tool from Z-Stack 3.0.2 together with the CC2531 firmware from the same stack, I received a message:

*** WARNING ***
    Expected Z-Stack version (2.7.1) does not match with actual Z-Stack version (2.7.2).  Z-Tool may not work properly.

YiKai Chen said:

For different ZNP, you need matched Z-Tool so you should use matched Z-Tool embedded in the same Z-Stackinstallation.

I use Z-Tool from Z-Stack 3.0.2 together with the CC2531 firmware from the SAME stack.

From C:\Texas Instruments\Z-Stack 3.0.2\Z-Stack Core Release Notes.txt:
The Z-Stack 3.0.2 release is based on Z-Stack Core 2.7.2.

From C:\Texas Instruments\Z-Stack 3.0.2\Tools\Z-Tool\ZToolConfig.xml:
<zstack_version>2.7.1</zstack_version>

Apparently, this is the reason for the warning.

Trying to connect Z-Tool with CC2530, I came across the need to change the connection speed to 115200 and got an error (English translation):
System.ArgumentException: The surrogate pair (0xD88B, 0xFFFF) is invalid. The top surrogate mark (0xD800 - 0xDBFF) must always be a pair with the bottom surrogate mark (0xDC00 - 0xDFFF).
The next start Z-Tool leads to an error:
System.IndexOutOfRangeException: The index was outside the bounds of the array.
The investigation revealed that the Windows registry element HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Texas Instruments\ZStack-Apps-1.2.0\Z-Tool 2.0\Settings\ComsInfo looks very strange, when I delete it, Z-Tool can be run without error.

Video from the screen can be viewed here.

Toby Pan said:

Please check on a different Windows 10 machine.

I don’t have access to other computers with Windows 10 x64 at the present, but I can use the Z-Tool with  Windows 7 x86 without problems.

Which OS is the video showing? I assume Windows 10?
Does this happen in your windows 7 VM?

You were able to interface successfully before w/ Windows 10, right?

Looks like there's some corruption in ComsInfo.

This is likely due to a .NET issue, as one of the popup indicates.

Toby Pan said:

Which OS is the video showing? I assume Windows 10?

Yes, this is Windows 10 Pro x64 (1809 build 17763).

Toby Pan said:

Does this happen in your windows 7 VM?

No. Z-Tool in Windows 7 VM works fine with CC2531 USB dongle directly and with CC2530 via CP2102 USB-UART dongle. Scripts also work ok.

Toby Pan said:

You were able to interface successfully before w/ Windows 10, right?

I could connect Z-Tool in Windows 10 with CC2531 before. But I didn't change the rate because it doesn't matter when working through the USB CDC-ACM driver directly with the CC2531 USB dongle. Scripts didn't work. But when I establish a connection with the CC2530, the rate must be changed, which led to what can be seen on the video. 

I added error logs to this post.0066.logs.zip

Toby Pan said:

What language is used in the Windows 7 VM?

Do you mean the Windows display language? Russian in both Windows.