DAS driver cannot open Access HW on Win10 (64-bit)

[Floki]

I am using AURIX development Studio 1.6.0 on Win10 (64-bit) machine and I am facing some issues when trying to connect to the TC275_LK board

I get the following message when trying to start a debug session

Error creating session
The debug instrument IO could not be initialized.
The GDI debug instrument provided the following error message.
Could not open Access HW

Using Debug Target Configuration:
Target: Generic Infineon AURIX Board
Selected CPU type: tc27xd
Register file: C:/Infineon/AURIX-Studio-1.6.0/plugins/com.tasking.ctc.debug.win32.x86_64_1.12.14.0/ctc/include/sfr/regtc27xd.xml
Communication: Universal Debug Access Server
Debug Instrument Module: gdi2mcdtc
Using Flash Configuration:
Monitor : C:\Infineon\AURIX-Studio-1.6.0\plugins\com.tasking.ctc.debug.win32.x86_64_1.12.14.0\ctc\etc\ftc27x.sre
Workspace address : 0x70000000
Number of devices : 5
Sector buffer size : 8192
Device 0:
Address : 0xA0000000,0x80000000
Vendor : Infineon
Chip : TC2_4560k
Subname : Program Flash 0
Width : 32
Size : 2097152
Number of chips : 1
Unused address lines : 0
Device 1:
Address : 0xA0200000,0x80200000
Vendor : Infineon
Chip : TC2_4560k
Subname : Program Flash 1
Width : 32
Size : 2097152
Number of chips : 1
Unused address lines : 0
Device 2:
Address : 0xAF000000
Vendor : Infineon
Chip : TC2_4560k
Subname : Data Flash Bank 0a
Width : 32
Size : 393216
Number of chips : 1
Unused address lines : 0
Device 3:
Address : 0xAF100000
Vendor : Infineon
Chip : TC2_4560k
Subname : Data Flash Bank 0b
Width : 32
Size : 16384
Number of chips : 1
Unused address lines : 0
Device 4:
Address : 0xAF110000
Vendor : Infineon
Chip : TC2_4560k
Subname : Data Flash Bank 1
Width : 32
Size : 65536
Number of chips : 1
Unused address lines : 0
Configuration: TC27xD
Starting Debugger...
The debug instrument IO could not be initialized.
The GDI debug instrument provided the following error message.
Could not open Access HW

I open DAS and see that the server is started, but I cannot see any device.

I thought it could be connected to some antivirus and firewalls programs .So I deactivated all of them. Unfortunately it is still not running.

Then I deleted the DAS driver manually and installed older DAS drivers. AURIX development studio detected that an outdated version is currently in-use, but it asked me for permission to continue the operation. After accpetiing that step, same result.

Then I replugged the board and tried all USB port available on my laptop.

Same result.

I took another laptop running having Win10 (64-bit) installed, but  this time I used  a virtual machine with Win7 on top of that.

I followed again all the steps as decriped in the manual and installed everything inside the virtual machine. When the installation finished, I plugged the development kit and saw that Win7 was looking for some drivers in the background. 

I cannot recall all the steps inside that checkbox

(USB ready for use)

(Aurix driver ..... ready)

Those steps mentioned above didn't appear during my original installation on the Win10 machine.

However, after compiling and downloading, I was able to start a debug session with the same example project and step through the code.

So it looks like there are no hardware issues with the development kit. 

Due to performance reasons, debugging over  the low cost FTDI driver on a virtual machine is not the best solution.

Therefore, I swapped to the previous machine and tried different development kits from different semidonductors on all USB ports and all of them worked as expected expect the Aurix Development Studio.

Any hints?

Thanks

[Di_W]

Hi Floki,

I am using TriBoard TC3X7 TH V2.01 and Windows 10, debugging works. I post PC info and debug console info here for reference.

Edition	Windows 10 Enterprise
Version	21H2
Installed on	<u+200e>13/<u+200e>12/<u+200e>2021
OS build	19044.1706
Experience	Windows Feature Experience Pack 120.2212.4170.0


Device name	
Full device name	
Processor	Intel(R) Core(TM) i5-10310U CPU @ 1.70GHz   2.21 GHz
Installed RAM	16.0 GB (15.8 GB usable)
Device ID	
Product ID	
System type	64-bit operating system, x64-based processor
Pen and touch	Pen support

Using Debug Target Configuration:
	Target: Generic Infineon AURIX Board
	Selected CPU type: tc39xb
	Register file: C:/Infineon/AURIX-Studio-1.5.4/plugins/com.tasking.ctc.debug.win32.x86_64_1.12.12.0/ctc/include/sfr/regtc39xb.xml
	Communication: Universal Debug Access Server
	Debug Instrument Module: gdi2mcdtc
Using Flash Configuration:
	Monitor : C:\Infineon\AURIX-Studio-1.5.4\plugins\com.tasking.ctc.debug.win32.x86_64_1.12.12.0\ctc\etc\ftc39xb.sre
	Workspace address : 0x70000000
	Number of devices : 10
	Sector buffer size : 8192
	Device 0:
		Address  : 0xA0000000,0x80000000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 0
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 1:
		Address  : 0xA0300000,0x80300000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 1
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 2:
		Address  : 0xA0600000,0x80600000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 2
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 3:
		Address  : 0xA0900000,0x80900000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 3
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 4:
		Address  : 0xA0C00000,0x80C00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 4
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 5:
		Address  : 0xA0F00000,0x80F00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 5
		Width : 32
		Size : 1048576
		Number of chips : 1
		Unused address lines : 0
	Device 6:
		Address  : 0xAF000000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash 0
		Width : 32
		Size : 1048576
		Number of chips : 1
		Unused address lines : 0
	Device 7:
		Address  : 0xAF400000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash UCB
		Width : 32
		Size : 24576
		Number of chips : 1
		Unused address lines : 0
	Device 8:
		Address  : 0xAF800000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash CFS
		Width : 32
		Size : 65536
		Number of chips : 1
		Unused address lines : 0
	Device 9:
		Address  : 0xAFC00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash 1
		Width : 32
		Size : 131072
		Number of chips : 1
		Unused address lines : 0
	Configuration: TC39xB
Starting Debugger...

Launching configuration: Blinky_LED_1_KIT_TC397_TFT
Loading 'C:\Users\dw\AURIX-v1.5.4-workspace\Blinky_LED_1_KIT_TC397_TFT\Debug\Blinky_LED_1_KIT_TC397_TFT.elf'...
Re-loading 'C:\Users\dw\AURIX-v1.5.4-workspace\Blinky_LED_1_KIT_TC397_TFT\Debug\Blinky_LED_1_KIT_TC397_TFT.elf'...
Using Debug Target Configuration:
	Target: Generic Infineon AURIX Board
	Selected CPU type: tc39xb
	Register file: C:/Infineon/AURIX-Studio-1.5.4/plugins/com.tasking.ctc.debug.win32.x86_64_1.12.12.0/ctc/include/sfr/regtc39xb.xml
	Communication: Universal Debug Access Server
	Debug Instrument Module: gdi2mcdtc
Using Flash Configuration:
	Monitor : C:\Infineon\AURIX-Studio-1.5.4\plugins\com.tasking.ctc.debug.win32.x86_64_1.12.12.0\ctc\etc\ftc39xb.sre
	Workspace address : 0x70000000
	Number of devices : 10
	Sector buffer size : 8192
	Device 0:
		Address  : 0xA0000000,0x80000000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 0
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 1:
		Address  : 0xA0300000,0x80300000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 1
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 2:
		Address  : 0xA0600000,0x80600000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 2
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 3:
		Address  : 0xA0900000,0x80900000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 3
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 4:
		Address  : 0xA0C00000,0x80C00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 4
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 5:
		Address  : 0xA0F00000,0x80F00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 5
		Width : 32
		Size : 1048576
		Number of chips : 1
		Unused address lines : 0
	Device 6:
		Address  : 0xAF000000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash 0
		Width : 32
		Size : 1048576
		Number of chips : 1
		Unused address lines : 0
	Device 7:
		Address  : 0xAF400000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash UCB
		Width : 32
		Size : 24576
		Number of chips : 1
		Unused address lines : 0
	Device 8:
		Address  : 0xAF800000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash CFS
		Width : 32
		Size : 65536
		Number of chips : 1
		Unused address lines : 0
	Device 9:
		Address  : 0xAFC00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash 1
		Width : 32
		Size : 131072
		Number of chips : 1
		Unused address lines : 0
	Configuration: TC39xB
Starting Debugger...

Launching configuration: Blinky_LED_1_KIT_TC397_TFT
Loading 'C:\Users\dw\AURIX-v1.5.4-workspace\Blinky_LED_1_KIT_TC397_TFT\Debug\Blinky_LED_1_KIT_TC397_TFT.elf'...
Using Debug Target Configuration:
	Target: Generic Infineon AURIX Board
	Selected CPU type: tc39xb
	Register file: C:/Infineon/AURIX-Studio-1.5.4/plugins/com.tasking.ctc.debug.win32.x86_64_1.12.12.0/ctc/include/sfr/regtc39xb.xml
	Communication: Universal Debug Access Server
	Debug Instrument Module: gdi2mcdtc
Using Flash Configuration:
	Monitor : C:\Infineon\AURIX-Studio-1.5.4\plugins\com.tasking.ctc.debug.win32.x86_64_1.12.12.0\ctc\etc\ftc39xb.sre
	Workspace address : 0x70000000
	Number of devices : 10
	Sector buffer size : 8192
	Device 0:
		Address  : 0xA0000000,0x80000000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 0
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 1:
		Address  : 0xA0300000,0x80300000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 1
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 2:
		Address  : 0xA0600000,0x80600000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 2
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 3:
		Address  : 0xA0900000,0x80900000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 3
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 4:
		Address  : 0xA0C00000,0x80C00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 4
		Width : 32
		Size : 3145728
		Number of chips : 1
		Unused address lines : 0
	Device 5:
		Address  : 0xA0F00000,0x80F00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Program Flash 5
		Width : 32
		Size : 1048576
		Number of chips : 1
		Unused address lines : 0
	Device 6:
		Address  : 0xAF000000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash 0
		Width : 32
		Size : 1048576
		Number of chips : 1
		Unused address lines : 0
	Device 7:
		Address  : 0xAF400000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash UCB
		Width : 32
		Size : 24576
		Number of chips : 1
		Unused address lines : 0
	Device 8:
		Address  : 0xAF800000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash CFS
		Width : 32
		Size : 65536
		Number of chips : 1
		Unused address lines : 0
	Device 9:
		Address  : 0xAFC00000
		Vendor : Infineon
		Chip : TC3_17624k
		Subname : Data Flash 1
		Width : 32
		Size : 131072
		Number of chips : 1
		Unused address lines : 0
	Configuration: TC39xB
Starting Debugger...

Launching configuration: Blinky_LED_1_KIT_TC397_TFT
Loading 'C:\Users\dw\AURIX-v1.5.4-workspace\Blinky_LED_1_KIT_TC397_TFT\Debug\Blinky_LED_1_KIT_TC397_TFT.elf'...

You can watch DAS info under C:\Program Files\DAS64\clients

Otherwise, you can reinstall DAS from C:\Infineon\AURIX-Studio-1.5.4\DAS_V7.2.0_Setup_WIN64.exe

I list below from my Device Manager for USB devices of DAS, please refer too.

dw

[Di_W]

Another way to debug is using free UDE debugging tool to load .elf file as below screenshot showed:

Which is under path: C:\Program Files\pls\UDE Starterkit 2021

How to get UDE Starterkit 2021?

You can access here:https://free-entry-toolchain.hightec-rt.com/

dw

[Floki]

Hello @Di_W ,

thank you for your reply.

Where can I download an older version of AURIX development studio e.g.  v1.5.4?

I don't see any possibility to select the specific version of the executable.

It looks like it is fixed to version v1.6.0.

Is that intended ?

As previously mentioned, I also tried a different version of DAS driver (v.7.1.8) which  didn't work.

I cannot find DAS  v7.2.0.

If I may ask, is it possible to provide me a link to download the AURIX development studio v.1.5.4 as the DAS driver version you work with is already incorporated in that executable?

For the  UDE, yes this could be an alternative solution, but you are also limited to the license model of High-Tec  after expiration of the evalution period.

Regarding the device manager, I don't see any Infineon DAS drivers

[Di_W]

Hi,

ADS 1.6.0 integrated 

DAS 7.3.7 

 Do you think newer version of ADS has problem?

I will ask if we can provide download of old versions, and reply you soon after.

Could you please re-install WIN10 from a clean PC? 

dw

I

[Floki]

Hello @Di_W ,

re-installing Win10 could be problematic at the moment as I have lot of stuff on the Laptop.

I just took the latest AURIX develoment studio v.1.6.0 executable to an older Tower-PC with Win7.

Here everything worked as expected. The behaviour is identical to the Virtual Machine with Win7-approach executed on a second Laptop.

I can summerize the following observations:

On the one hand, DAS drivers are working on machines with  Intel processors.

• Tower PC with Win7 (Intel)
• 2nd Laptop (Intel)
  • VM with Win7 
• For you, it is working with AURIX DS v1.5.4 without any issues on Win10 (i see you have an Intel machine as well)

On the other hand, DAS drivers seem to cause some issues on my machine with AMD Ryzen processors and Win10 (at least from my observations on the current laptop)

Are there some dependencies or known issues to AMD processors with DAS drivers?

[Di_W]

Hi Floki,

Could you please list below screenshot for DAS info windows and Device Manager on WIN10?

To see if this USBUART device is properly installed.

[Floki]

Hello @Di_W ,

sorry for my late response, I visited a fair this week.

For some reason, I cannot upload any images.

I get the following message, when I try to insert a JPG file, even after shrinking the size to 8kb, the reply box keeps complaining.

Uploading DASdrv_0.jpg resulted in the following error: A possible invalid request has been made. Make sure you are following the API spec and have used the correct URL, are included all required parameters and if a request payload is required you have included one.

I tried both approaches. 

• Dragging the image directly into the text box - didn't work
• Dragging the image into the attachment and trying to upload the image via "insert photo" button - didn't work

However, I will try to explain it:

After booting up the system and plugging the device into the USB port, the following scenario can be observed:

There is no server entry active when I open DAS Device Control Panel. I  need to look for "installed DAS Servers" and start it manually.

After that, I see in the DAS Server Control Panel the following new entry:

Running DAS Server: UDAS

PID: 8296

When I look at the Clients in DAS Device Scanner, the complete list is empty.

The device manager doesn't show any new devices for the USB.

USB Composite Device / Details / Value / USB Composite Device.

These additional Infineon devices don't appear at all inside the device manager

[Di_W · Accepted solution]

Hi Floki,

As device mgr has no any device of DAS USB, it's suggested to use a clean WIN10 computer.

It looks like your PC's USB port has some issues. Even if there is no device driver, it should has Unknown Device instead. Below is info for USB VID and PID.

https://treexy.com/products/driver-fusion/database/id/usb/vid_058b/pid_0043/

As you said it's a BIOS issue from your computer, it's resolved by update of BIOS.

Thank you for query!😊

dw

[Floki]

Hello @Di_W ,

I was just checking the latest USB driver versions on my system. According to Win10, everything was up to date.

However, I found out that BIOS required one update.

After updating BIOS, I was taking a look into the device manager and I saw  that the Infineon devices were recognized

Afterwards I tried a debug-session with a simple example and I was able to connect to the target.

[PedroSylvestre]

Hello everyone, I'm getting the same error as explained above. The BIOS of my notebook (Win10 x64) is updated.

The Device Manager doesn't show any Infineon USB drivers, but I already checked and DAS is installed.

I'm using a KIT AURIX TC297 TFT

Here's a print of the DAS Device Scanner: