Application Note Testing C167 Single Chip Applications - Hitex

Hitex Germany 

– Head Quarters – 

Greschbachstr. 12 

76229 Karlsruhe 

Germany 

� +049-721-9628-0 

Fax +049-721-9628-149 

E-mail: Sales@hitex.de 

WEB: www.hitex.de 

Hitex UK 

Warwick University 

Science Park 

Coventry CV47EZ 

United Kingdom 

� +44-24-7669-2066 

Fax +44-24-7669-2131 

E-mail: Info@hitex.co.uk 

WEB: www.hitex.co.uk 

Application Note 

Hitex USA 

2062 Business Center Drive 

Suite 230 

Irvine, CA 92612 

U.S.A. 

� 800-45-HITEX (US only) 

� +1-949-863-0320 

Fax +1-949-863-0331 

E-mail: Info@hitex.com 

WEB: www.hitex.com 

Testing C167 Single Chip Applications 

This application note describes how to adapt the standard test 

application created by Tessy to a C167 running without external 

memory. 

It assumes some familiarity with Infineon's C167 architecure, 

the in-circuit emulator DProbe167 from Hitex, and Tasking's 

cross compiler for C167. 

This is a very specialized and detailed application note and 

does not serve as an introduction to Tessy. 

Architecture: TESSY 

Author: Frank Buechner 

Revision: 01/2008 - 003 

© Copyright 2008 - Hitex Development Tools GmbH 

All rights reserved. No part of this document may be copied or reproduced in any form or by any means without prior written consent of Hitex Development Tools. Hitex Development Tools retains 

the right to make changes to these specifications at any time, without notice. Hitex Development Tools makes no commitment to update nor to keep current the information contained in this 

document. Hitex Development Tools makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular 

purpose. Hitex Development Tools assumes no responsibility for any errors that may appear in this document. DProbe, Hitex, HiTOP, Tanto, and Tantino are trademarks of Hitex Development 

Tools. All trademarks of other companies used in this document refer exclusively to the products of these companies. 

ApplicationNote.dot - 11/2007 - 005


Preface 

In order to keep you up-to-date with the latest developments on our products, we provide Application 

Notes containing additional topics, special hints, examples and detailed procedures etc. 

For more information on the current software and hardware revisions, as well as our update service, 

please contact www.hitex.de, www.hitex.co.uk or www.hitex.com. 

Contents 

1 Testing C167 Single Chip Applications 3 

1.1 Microcontroller Specific Issues 3 

1.2 Using the Tasking Development Environment 4 

1.2.1 Startup 4 

1.2.2 Considerations for Locating 6 

1.3 Using DProbe167 with HiTOP 4 7 

1.3.1 Set Mode 7 

1.3.2 Do Not Map 7 

1.4 Testing Single Chip Applications with Tessy 7 

1.4.1 Startup 7 

1.4.2 Reducing the Data Size Required by Tessy 8 

1.4.3 Setting the Memory Model 10 

1.4.4 Locating 11 

1.4.5 Avoid Mapping by Tessy 12 

1.5 Versions Used 12 

© Copyright 2008 Hitex Development Tools GmbH Page 2/12


1 Testing C167 Single Chip Applications 

Caution: 

This is a very specialized and detailed application note. You should be familiar with the 

Infineon C167 architecture, the in-circuit emulator DProbe167, and the Tasking compiler for 

C167. 

It is no introduction to Tessy! 

1.1 Microcontroller Specific Issues 

If a C167 microcontroller comes up in single chip mode or not, is determined during the power-up / 

reset of the microcontroller. The outcome is reflected in the bit 10 (ROMEN) of the register SYSCON, 

which is set to 1, if single chip mode is enabled. The default value of the register SYSCON is 0x0000, 

with ROMEN enabled, it becomes 0x0400. 

If SingleChip mode is enabled, the microcontroller is supposed to use only chip-internal memory, 

especially internal ROM for Code and internal RAM for data. 

Using a C167CR, the internal ROM is 32k Bytes wide and normally starts at address 0 (0x0000 – 

0x7FFF). (The internal ROM can be remapped to start in segment 1 (0x10000 – 0x17FFFF) by the bit 

ROMS1 (bit 12) of the SYSCON register.) 

Using a C167CR, the internal RAM is 2k Bytes wide and starts at address 0xF600 (0xF600 – 

0xFDFF). 

Using a C167CR, the on-chip extension RAM (XRAM) is 2k Bytes wide and start at address 0xE000 

(0xE000 – 0xE7FF). The XRAM is not enabled by default, but must be enabled via bit 2 (XPEN) of the 

register SYSCON. 



1.2 Using the Tasking Development Environment 

The following reflects Tasking V8.0 R02 for C167/ST10. 

For a single chip application, the tiny memory model is appropriate, because all memory addresses 

are < 64k Bytes. 

The tiny model is not required, the small model should also work. 

1.2.1 Startup 

The startup code stemming from the Tasking development environment (and included in a Tasking 

C167 application) sets the value of the register SYSCON. By default, SYSCON is set to 0x0000. This 

value would disable the internal ROM, therefore, provisions must be made to use startup code which 

sets the ROMEN bit not to 0. 

Because we would like to use the XRAM also, we must take provisions that bit 2 (XPEN) is set. 

With SYSCON = 0x0404, both ROMEN and XPEN is set. 

This can be done in the Tasking EDE: 



This results in the following startup code and settings of SYSCON: 



1.2.2 Considerations for Locating 

Next, care must be taken that program code is located to the internal ROM and data is located in the 

internal RAM of the microcontroller. 

By default, program code is located to 0, so there is nothing special to do. 

The data portion of an application consists (at least) of the variables of the application, the (user and 

system) stack, and the heap. Also the register bank resides in data memory. 

However, by default (and appropriate for external applications), data is located mixed with code, i.e. by 

default data would be located to the internal ROM memory, what will cause the application to fail, e.g. 

because variables cannot be written by the program. 

Therefore, care must be taken, that data is located in the IRAM and the XRAM. This can be done by 

using CLASSES locator directives. Also some memory areas have to be reserved for microcontroller 

purposes. 

Section "Locating" on p. 11 describes how these considerations result in instructions for the locator. 



1.3 Using DProbe167 with HiTOP 4 

1.3.1 Set Mode 

Setup > pRocessor > System Startup configuration: 

Default: 16 bit external 

Set to: Single chip 

1.3.2 Do Not Map 

When emulating in single chip mode, the DProbe167 automatically provides emulation memory for the 

internal ROM. 

Therefore, there is no need to use the Setup > Map command to map any memory. 

1.4 Testing Single Chip Applications with Tessy 

Please read the Tessy document 006 "Customizing Makefile Templates" ! 

Use the help menu of Tessy: Help > Documents > Customization > Makefile templates. 

By default, the test application created by Tessy assumes a DProbe167 in external mode. Therefore, 

the creation process of the test application has to be changed with the two objectives: 

• 

• 

The startup code must not set SYSCON to 0, but to 0x0404. 

The near data must be located to the internal RAM. As a prerequisite for this, the data size required 

by Tessy must be reduced. 

1.4.1 Startup 

We take a start.obj holding the statup code assembled from start.asm, where SYSCON is not set to 0 

but to 0x0404. We could get such a file from a single chip application generated by the Tasking EDE 

or from the original user application. 

In our case, we have created a single chip application in the directory 

c:\Tessy\Tasking166_projects\SingleChip\167cr 

and can take the start.obj from there 

c:\Tessy\Tasking166_projects\SingleChip\167cr\start.obj 

We manipulate the appropriate makefile template, in our case 

c:\Programme\Razorcat\tessy\sys\templates\make\ts_make_hitop_tasking_c166.tpl 



Original content: 

S_LINK_OPTIONS := $(TASKING_HOME)\lib\ext\c166s.lib $(T7_FLOAT_LIB) 

$(T6_FLOAT_LIB) $(TASKING_7_LIB) CASE NOCC -Wo'SECSIZE(C166_US(1024)) 

RESERVE( MEMORY( 0E800h - 0EFFFh )) RESERVE( MEMORY( 0F200h - 0F9FFh ))' 

Manipulated content: 

S_LINK_OPTIONS := 

C:\Tessy\Tasking166_projects\SingleChip\167cr\start.obj 

$(TASKING_HOME)\lib\ext\c166s.lib $(T7_FLOAT_LIB) $(T6_FLOAT_LIB) 

$(TASKING_7_LIB) CASE NOCC -Wo'SECSIZE(C166_US(1024)) RESERVE( MEMORY( 

0E800h - 0EFFFh )) RESERVE( MEMORY( 0F200h - 0F9FFh ))' 

If start.obj is not explicitly given to the Tasking linker, the Tasking linker takes start.obj from the library, 

in this case ...\lib\ext\c166s.lib. In our case, the linker finds the start.obj, which sets SYSCON to 

0x0404 first, and therefore there is no need to take start.obj from the library. 

1.4.2 Reducing the Data Size Required by Tessy 

The test application (i.e. the program that is loaded by Tessy in the in-circuit emulator) contains a 

communication buffer. The size of this buffer is by default 1024 bytes. 

Because the test application can only use the chip-internal resources for RAM (on a C167CR 2k Bytes 

IRAM + 2k Bytes XRAM = 4k Bytes) and this RAM must also hold registers, system stack etc., it is a 

good idea to reduce the data size required for the communication buffer. 

This can be done by making two changes: 

(1) Edit the file tslow.h in the installation directory of Tessy, e.g. 

c:\Programme\Razorcat\tessy\sys\include\Tessy\comm\tslow.h 

In the tslow.h file, change 

/** 

* Communication Buffer Sizes 

*/ 

#if defined (TS_SOCKET) 

#define TSLOW_CONNECTION_LENGTH 10240 

#elif defined(TS_HITOP) || defined(TS_CROSSVIEW) 


#elif defined(TS_FASTVIEW66) || defined(TS_SSTEP) 


#elif defined(TS_SOFTUNE) || defined(TS_UDE) 


#elif defined(TS_CSPY) 


#elif defined(TS_SM78K0S) 


#else 


#endif 

to 



/** 

* Communication Buffer Sizes 

*/ 

#if defined (TS_SOCKET) 


#elif defined(TS_HITOP) || defined(TS_CROSSVIEW) 


#elif defined(TS_FASTVIEW66) || defined(TS_SSTEP) 


#elif defined(TS_SOFTUNE) || defined(TS_UDE) 


#elif defined(TS_CSPY) 


#elif defined(TS_SM78K0S) 


#else 


#endif 

in order to reduce the buffer size from 1024 to 256 Bytes. 

(2) In Tessy, create a new attribute named "BufferSize" for the respective Tessy module / testobject 

("Properties" in the context menu of the module / testobject > "Attributes" tab). 

and set the value of that attribute to the same size as in tslow.h. 



1.4.3 Setting the Memory Model 

By default, the test application created by Tessy uses the small memory model. 

What has to be done to use the tiny model? 

• 

• 

Create start.obj in the tiny model. 

In the makefile template: 

(1) Change the compiler command line option –Ms to –Mt: 

S_COMP_OPTIONS := -x -g -O0 -Mt -w -s -DTESSY -DTS_SLAVE -DTS_HITOP - 

DTS_C166 

(2) Change the model of the libraries linked to the test application from 

TASKING_7_LIB := $(shell tessy_file_exist 

"$(TASKING_HOME)\lib\ext\rt166s.lib") 

T7_FLOAT_LIB := $(shell tessy_file_exist 

"$(TASKING_HOME)\lib\ext\fp166s.lib") 


"$(TASKING_HOME)\lib\ext\ntf166t.lib") 

to 

TASKING_7_LIB := $(shell tessy_file_exist 

"$(TASKING_HOME)\lib\ext\rt166t.lib") 


"$(TASKING_HOME)\lib\ext\fp166t.lib") 


"$(TASKING_HOME)\lib\ext\ntf166t.lib") 

(3) Change the linker options from 

S_LINK_OPTIONS := … $(TASKING_HOME)\lib\ext\c166s.lib … 

to 

S_LINK_OPTIONS := … $(TASKING_HOME)\lib\ext\c166t.lib … 



1.4.4 Locating 

CUSTACK is the class name for the stack and heap. 

CNEAR is the class name for the "near data", i.e. the variables. 

CINITIRAM is the class name for initialized variables. 

Use the CLASSES and RESERVE directives of the locator to place the data to the desired memory 

addresses ... 

-Wo'SECSIZE(C166_US(1024)) IRAMSIZE(2048)\ 

RESERVE( MEMORY( 0E800h - 0EEFFh ))\ 

RESERVE( MEMORY( 0F200h - 0F5FFh ))\ 

CLASSES(CINITIRAM(0xf620 TO 0xf6FF))\ 

CLASSES(CUSTACK(0xE000 TO 0xE3FF))\ 

CLASSES(CNEAR(0xE400 TO 0xE7FF))' 

... in the makefile template file. This results in the following memory map: 

Name No. Start End Length Type 

--------------------------------------------------------------- 

?INTVECT................... ... 000000h 0001FFh 000200h .... 

TS_IS_VALUE_IN_RANGE_S_IR_N 0 000200h 000201h 000002h LDAT 

C166_INIT.................. 5 000202h 000213h 000012h LDAT 

C166_BSS................... 6 000214h 00022Dh 00001Ah LDAT 

TSLOWS_HITOP_3_CO.......... 9 00022Eh 000236h 000009h LDAT 

TSTCOMM_IR_NB.............. 10 000238h 000238h 000001h LDAT 

TS_IS_VALUE_IN_RANGE_S_3_PR 2 00023Ah 000487h 00024Eh CODE 

TSLOWS_HITOP_1_PR.......... 7 000488h 000749h 0002C2h CODE 

TSTCOMM_3_PR............... 12 00074Ah 000ADDh 000394h CODE 

TS_TIMER_C166_1_PR......... 13 000ADEh 000B79h 00009Ch CODE 

TSCOML_1_PR................ 15 000B7Ah 000EE3h 00036Ah CODE 

TS_SRC01_1_PR.............. 17 000EE4h 000F35h 000052h CODE 

TS_IS_VALUE_IN_RANGE_USR_1_ 18 000F36h 000F45h 000010h CODE 

__C_INIT_PR................ 19 000F46h 000F9Fh 00005Ah CODE 

__CSTART_PR................ 20 000FA0h 000FE9h 00004Ah CODE 

__FPCODE................... 21 000FEAh 001011h 000028h CODE 

C166_US.................... 4 00E000h 00E3FFh 000400h LDAT 

TS_IS_VALUE_IN_RANGE_S_4_NB 3 00E400h 00E415h 000016h LDAT 

TSLOWS_HITOP_2_NB.......... 8 00E416h 00E625h 000210h LDAT 

TS_TIMER_C166_2_NB......... 14 00E626h 00E6F5h 0000D0h LDAT 

TSCOML_2_NB................ 16 00E6F6h 00E6FBh 000006h LDAT 

Reserved................... ... 00E800h 00EEFFh 000700h .... 

Extended SFR Area.......... ... 00F000h 00F1FFh 000200h .... 

Reserved................... ... 00F200h 00F5FFh 000400h .... 

Reg. bank 0................ ... 00F600h 00F61Fh 000020h .... 

TS_IS_VALUE_IN_RANGE_S_ID_N 1 00F620h 00F621h 000002h LDAT 

TSTCOMM_ID_NB.............. 11 00F622h 00F622h 000001h LDAT 

System Stack............... ... 00FA00h 00FBFFh 000200h .... 

SFR Area................... ... 00FE00h 00FFFFh 000200h .... 

The first 1k of the XRAM is used for the user stack (0xE000 – 0xE3FF). 

The second 1k of the XRAM is used for the data of the test application. 

The first 32 Bytes of the IRAM are used for the register bank 0 (0xF600 – 0xF61F). 

The system stack follows the initialized data (two parts) of the application (0xF620 – 0xF622). 



1.4.5 Avoid Mapping by Tessy 

Normally, Tessy maps emulation memory. This is done by sending the HiSCRIPT commands in 

c:\Tessy\hitop_init_c166.scr 

to HiTOP. 

The standard contents of c:\Tessy\hitop_init_c166.scr is 

// This is a Tessy generated init script for HiTOP C16x / ST10 

// You may edit this script but BE CAREFUL WITH ANY CHANGES! 

LOAD OBJECT "" 

MAP REMOVE 

BREAK REMOVE 

// Setup memory map 

MAP M1 AT 0x0000 END 0x7FFF 

MAP M2 AT 0xC000 END 0xFFFF 

MAP M3 AT 0x10000 END 0xFFFFF 

Changing this to 

// This is a Tessy generated init script for HiTOP C16x / ST10 

// You may edit this script but BE CAREFUL WITH ANY CHANGES! 

LOAD OBJECT "" 

MAP REMOVE 

BREAK REMOVE 

// Setup memory map 

// MAP M1 AT 0x0000 END 0x7FFF 

// MAP M2 AT 0xC000 END 0xFFFF 

// MAP M3 AT 0x10000 END 0xFFFFF 

avoids mapping by Tessy. (It is not harmful if mapping stays enabled.) 

1.5 Versions Used 

Tessy V2.2.15 

Tasking V8.0 R02 for C167/ST10 

HiTOP V4.11 for DProbe167

Application Note Testing C167 Single Chip Applications - Hitex

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?