how to make Aurix Studio working wit custom board via DAP miniWigger

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
karma-JC
Level 1
Level 1
10 sign-ins First like received First reply posted

HI:

I need some help on how to setup Aurix Studio to work with custom board(our sample board based on TC277 Applicate Kit reference board). 

 

I tried flash the board I got following error message :

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
at AurixFlasher.Program.Main(String[] args)
Flashing failed

 

For Debugging, the following Error message came out:

Starting Debugger...
The debug instrument IO could not be initialized.
The GDI debug instrument provided the following error message.
An internal error has occurred.
Using Debug Target Configuration:
Target: Generic Infineon AURIX Board
Selected CPU type: tc27xd
Register file: C:/Infineon/AURIX-Studio-1.9.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.9.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.
An internal error has occurred.

 

How to configure or setup Aurix Studio project to get around this problem?

 

Thank you

James

0 Likes
1 Solution
Di_W
Moderator
Moderator
Moderator
1000 replies posted 250 solutions authored 100 likes received

Please flash the default software into the chip, if you use your own software, you should check if any password is written to UCB_DBG. If you has password, sometimes you can unlock but it depends. You can review the Triboard user manual and software here.(Note: myICP required)

We can debug the Triboard with miniwiggler and ADS, but you first should use a Triboard and default software. 

1. Why and how MUC(TC277) would get into this "locked" state?

The chip's UCB_DBG contains a password to unlock debug interface.
2 Could we debug TC277 production chip using Aurix Studio and DAP? And how to set it up?

If your production chip has been programmed with a UCB debug interface password, you need to unlock it using the password. However, if you have a blank chip without a password in the UCB, you can debug and flash it using ADS (AURIX Development Studio) and DAP.
3 If MCU(TC277) got into this "locked" state, how to get MUC out of this state?

You must unlock the chip using a password; otherwise, there will be no way to recover from this state.

Please refer to pages 252 and 253 in the following document: Infineon TC27x D-step User Manual for below description: If debug password is wrong, and if Flash protection is activated, no debug access to device. If debug password is correct,  even if Flash protection is activated, debug access granted. If no debug password or wrong debug password, then check Flash protection is activated or not. If yes, no debug access. If no, debug interface will be unlocked.

View solution in original post

0 Likes
5 Replies
Di_W
Moderator
Moderator
Moderator
1000 replies posted 250 solutions authored 100 likes received

Hi James, do you have triboard or other board? And have you downloaded proper software for the board?

karma-JC
Level 1
Level 1
10 sign-ins First like received First reply posted

Hi:

This is few update on some finding.  We are in the process of bringing up our own custom board design(based on the reference design).  The development tool of our choice is using Aurix Studio + DAP miniWiggler.  According to our hardware engineer, the TC277 is production version on our custom board.   Once flashed Aurix Stuido generated debug image via DAP, the MCU got into no recoverable state after debug reset.  I used DAS tool for MUC detection.  A message " Device is locked" is appeared. 

The following are the questions:

  1. Why and how MUC(TC277) would get into this "locked" state?
  2. Could we debug TC277 production chip using Aurix Studio and DAP? And how to set it up?
  3. If MCU(TC277) got into this "locked" state, how to get MUC out of this state?

Thank you fort the help!!!

Di_W
Moderator
Moderator
Moderator
1000 replies posted 250 solutions authored 100 likes received

Please flash the default software into the chip, if you use your own software, you should check if any password is written to UCB_DBG. If you has password, sometimes you can unlock but it depends. You can review the Triboard user manual and software here.(Note: myICP required)

We can debug the Triboard with miniwiggler and ADS, but you first should use a Triboard and default software. 

1. Why and how MUC(TC277) would get into this "locked" state?

The chip's UCB_DBG contains a password to unlock debug interface.
2 Could we debug TC277 production chip using Aurix Studio and DAP? And how to set it up?

If your production chip has been programmed with a UCB debug interface password, you need to unlock it using the password. However, if you have a blank chip without a password in the UCB, you can debug and flash it using ADS (AURIX Development Studio) and DAP.
3 If MCU(TC277) got into this "locked" state, how to get MUC out of this state?

You must unlock the chip using a password; otherwise, there will be no way to recover from this state.

Please refer to pages 252 and 253 in the following document: Infineon TC27x D-step User Manual for below description: If debug password is wrong, and if Flash protection is activated, no debug access to device. If debug password is correct,  even if Flash protection is activated, debug access granted. If no debug password or wrong debug password, then check Flash protection is activated or not. If yes, no debug access. If no, debug interface will be unlocked.

0 Likes
karma-JC
Level 1
Level 1
10 sign-ins First like received First reply posted

Hi:

Thanks for the suggestion. However, we have encountered a issue of not able to flash the image even using Lauterbach debug.  To get some understanding, what is this default software?  Is this default software from Aurix Studio project creating process?

Thank you

James

0 Likes
Di_W
Moderator
Moderator
Moderator
1000 replies posted 250 solutions authored 100 likes received

If you have a Triboard and installed ADS, you can import from File menu, or access github for the default software, for example the code is used to blink the LEDs.

0 Likes