Texane debugger missing

[rolfnoot]

Hi,

 

I’m missing the Texane debugger from the list of packages. How can it be installed?

 

Also using openOCD is starting debugging much slower on VisualGDB than SW4STM32 (GBD load: 8 seconds vs 50 seconds).

 

Info: Open On-Chip Debugger 0.9.0 (2016-10-14) [https://github.com/sysprogs/openocd] on the latest VGDB.

 

Regards,

Rolf

[support]

Hi,

We have discontinued the Texane debugger as it was less reliable than OpenOCD. You can still download it from github and specify as “custom gdb stub”, but we no longer ship a pre-built one with VisualGDB.

Slow loads could be the case if you are using a VM with USB virtualization, but should normally not happen on physical machines. If you are not using a VM, please try enabling the timing analysis mode in the GDB Session window and then check which command takes most of the time. Perhaps you are programming a large image with OpenOCD and a smaller one with the ST tool?

[rolfnoot]

Thanks for your quick reply!

 

Yes, I’m using a VM with Windows (On mac using parallels). It’s the same code size I’m programming.

 

Also, can you tell me how to install the custom GBD stub to operate with Texane?

 

Thanks!

[support]

Hi,

You would need to download Texane ST-Link sources from github and build them.

Then you can actually reuse the definition file that we made when we supported it officially: create a %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\texane folder and copy st-util and st-flash there. Then create a edp.xml file with the following contents:

<?xml version="1.0"?>
<EmbeddedDebugPackage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <PackageID>com.sysprogs.arm.texane-stlink</PackageID>
  <PackageVersion>1.2</PackageVersion>
  <GNUTargetFilter>^arm-.*</GNUTargetFilter>
  <UserFriendlyName>Texane ST-Link</UserFriendlyName>
  <SupportedDebugMethods>
    <DebugMethod>
      <UserFriendlyName>Texane ST-Link</UserFriendlyName>
      <ID>texane-stlink</ID>
      <GDBServerApplication>$$SYS:DMSP_ROOT$$\st-util.exe </GDBServerApplication>
      <GDBServerArguments>
          <GNUStyle>true</GNUStyle>
          <Properties>
          <PropertyGroups>
            <PropertyGroup>
              <Properties>
                  <PropertyEntry xsi:type="Enumerated">
                  <Name>ST-Link Version</Name>
                  <UniqueID>com.sysprogs.arm.texane-stlink.version</UniqueID>
                  <Description>Specifies the ST-Link version</Description>
                  <SuggestionList>
                    <Suggestion>
                      <UserFriendlyName>ST-Link v1</UserFriendlyName>
                      <InternalValue>-1</InternalValue>
                    </Suggestion>
                    <Suggestion>
                      <UserFriendlyName>ST-Link v2</UserFriendlyName>
                      <InternalValue></InternalValue>
                    </Suggestion>
                  </SuggestionList>
                  <DefaultEntryIndex>1</DefaultEntryIndex>
                  <AllowFreeEntry>false</AllowFreeEntry>
                </PropertyEntry>
                <PropertyEntry xsi:type="Boolean">
                  <Name>Reset target before programming</Name>
                  <UniqueID>com.sysprogs.arm.texane-stlink.resetcommand</UniqueID>
                  <Description>Automatically resets the target before programming</Description>
                  <DefaultValue>false</DefaultValue>
                  <ValueForTrue>mon reset</ValueForTrue>
                </PropertyEntry>
              </Properties>
              <CollapsedByDefault>false</CollapsedByDefault>
            </PropertyGroup>
          </PropertyGroups>
        </Properties>
      </GDBServerArguments>
      <GDBServerDelay>500</GDBServerDelay>
      <GDBStartupCommands>
        <string>target remote :4242</string>
        <string>$$com.sysprogs.arm.texane-stlink.resetcommand$$</string>
        <string>load</string>
      </GDBStartupCommands>
      <UseContinueToStart>true</UseContinueToStart>
      <SendCtrlCToGDBServer>false</SendCtrlCToGDBServer>
      <RequireExplicitDisconnect>true</RequireExplicitDisconnect>
    </DebugMethod>
   </SupportedDebugMethods>
</EmbeddedDebugPackage>

This will add it to the list of VisualGDB’s debug methods so you won’t need to configure anything manually.

[rolfnoot]

Thanks a lot! I’ll try this.

 

For now I ended up reprogramming the ST-link as Segger J-link which works extremely fast and stable.

 

Regards!

[Author]

Posts