External memory on a XC16x Board

Hi Stefan,

Yes, you're right about the starter kit. The kits that have been made in the past (by Phytec) all had more I/O on board, like I2C-components, more LED's, etc. I'm missing these things on this board. It's indeed not easy starting up, this way.

I had looked in the system manual already and saw the area you mentioned. But that still doesn't explain the 3F'8000 value for ?C_NDATBASESEG in some cases, because there's nothing on that address. No memory, no I/O. Don't know why Keil creates this value. Because my software works OK, in spite of these values, I've decided to ignore them.

Stefan, thanks again (second time now) for all your help and time. Things are clear to me again. :)

Kind regards,
Dennis

Hi Stefan,

Yes, you're right about the starter kit. The kits that have been made in the past (by Phytec) all had more I/O on board, like I2C-components, more LED's, etc. I'm missing these things on this board. It's indeed not easy starting up, this way.

I had looked in the system manual already and saw the area you mentioned. But that still doesn't explain the 3F'8000 value for ?C_NDATBASESEG in some cases, because there's nothing on that address. No memory, no I/O. Don't know why Keil creates this value. Because my software works OK, in spite of these values, I've decided to ignore them.

Stefan, thanks again (second time now) for all your help and time. Things are clear to me again. :)

Kind regards,
Dennis

Hi Dennis,

thanks for this, but no matter.
OK I found out what is the meaning of
?C_NDATABASE and ?C_NDATABASESEG.

I configured my program as yours regarding the hardware.
For the following it can be usefull to have a look to system user manual section 4.5. Data adressing.

As you know the code is accessed by segments
( a 64kBytes each ) and data memory with pages ( a 16k each ).
So you have for pages per segment.
First you should ensur that your
?C_PAGEDPPx are the following values:

000000H         ?C_PAGEDPP0
000301H         ?C_PAGEDPP1
000100H         ?C_PAGEDPP2

3F'8000h is
0011 1111 1000 0000 0000 0000
where       00 0000 0000 0000 is Page offset
                              (14-bit)
          10                  selects DPP2
in DPP2 you find value 100    (10-bit)
01 0000 0000
now we will assemble the real address
(it results in 10-bit DDP2 value and 14-bit
 page offset)

0100 0000 0000 0000 0000 0000 ( 24 - bit )
in
HEX it is 40'0000h your NDATA area in RAM !

Thats where the DPP2 points by default after startup.
Let's do for DPP1 (301h)

11 0000 0000 ( 10-bit )

   01 00 0000 0000 0000
   01 is DPP1
      00 0000 0000 0000  is Page offset.
for Segment : Offset
    8-bit   : 16-bit
  1100 0000 : 0100 0000 0000 0000
   C    0      4    0    0    0
   C0'4000

the DPP1 points to you MAIN routine, you
find in map file as
C04000h    ......   ?NC?MAIN.

Hi Stefan,

I never really understood the DPP's. I think that it's really clear now (also to other readers of this thread). Thanks again. :)

What version of the datasheets do you use?? You mentioned chapter 4.5 (which is correct in version v1.1, feb 2002). Since the release of that manual there have been released 2 new versions:

* v2.0, 3-2003
* v2.1, 6-2003

The last one is the one I use now. In this version it's chapter 4.7 that handles about data addressing.

There are still some things that cannot be found in the new manuals, like the ADC-bug that's also known from the XC164 (ADBSY is set after x clock cycles, not immediately after starting an ADC-conversion).

Kind Regards,
Dennis

Hi Dennis,

cool that you understand now the DPP's.
It is really not complicated.
I need at my start two times and than I calculated three examples and now I have it.
( If questions concerning to this, do not hesitate to ask me )

I used the XC167 manual for this, since the register mappings are similar.
So if you write a program for a module, which is available on the other XC16x too,
you can be sure in 98% of cases it will run there.
So at XC161 the CAPCOM6 will not work and at
XC164 the I2C module.

Bugs, problems and workaround (if any) you can find in the errata sheets.
Please have additional a look of the step code of your device.

But you are right with the manuals specially for XC161.
There in the new version is the complete description of SCU missing.
I reported to Infineon and it will be updated with next release.

Stefan

Hi Stefan,

I know that the other XC16x devices are almost the same, but it's weird that there isn't any link on the site on the XC161 page to errata sheets of the other (similar) devices.

Also the starter kit isn't described on the Infineon site. The info about this controller and applications are really poor. But perhaps this will change in the future, for it's a new controller.

Does Infineon also have a forum, like Keil? If so, maybe we can discuss this there. :)

Kind Regards,
Dennis

Hi Dennis,

Infineon unfortunately has no discussion forum, so we have to discuss here, or we can do it by mail.
The kit indeed is only described at the
CD-ROM you find at the kit.

But I wonder, that the eratas are not on the web, since I got them from there.

I can mail you the last I have, if you are interested.

Stefan

Hi Stefan,

I've only found XC164 and XC167 errata sheets. No XC161. Searched for them again a few minutes ago, but still couldn't find them. :S

Kind Regards,
Dennis

Hi Dennis,

I send you my Erratas concerning Xc161CJ
step AA,AB and AC.

Please check your account.

Stefan

Hi Stefan,

I received your mail with errata sheets. I really can NOT find them on Infineon's site. Even when I log in to My Infineon I still can't find them.

Seems like you have more permissions to view/download files than I have. :)

Thanks a lot for de documents. I'll read them tomorrow morning.

Kind Regards,
Dennis

Hi Dennis,

it is not your mistake. At the moment there are really no erratas available for XC161CJ.
I got them some time before and save them all for such times. ;-}

Stefan

Hi Dennis,

I did a mistake.
The board works with 16-bit muxed bus.
Not demuxed.

Sorry for this,
Stefan

Hello Stefan,
I've red the thread very carefully, but at the moment I'm a little bit confused about the right configurations for accessing the external RAM.
I've an XC164 Starterkit, Rev. 200 without FLASH and I got the RAM not working yet. Do you have an working configuration and because everything depends from everything, I need the DIP Switch configuration, the right settings in Start_A2.a66, the Target configuration and if I have something to code in main(),like special PORT configuration, it was also interesting, to get it.
Thank you very much in advance
Steffen

Hi Steffen,

Board Settings
------------------------
| JUMPERSETTINGS |
------------------------
Jumper 401 ( 1-2 ) ON
Jumper 402 ( 1-2 ) ON
Jumper 501 ( 1-2 ) ON

------------------------
| DIPSWITCH - SETTING's |
------------------------
DIP102:
=======
1-3
Clock-Configuration: ON OFF ON Fin = 8 - 12 MHz
4-5
SALSEL: OFF OFF
2 Bit Segmentadresslines A17 ... A16
6-7
CSEL: ON OFF 2 CS - Lines
8
WRC: OFF /WR and /BHE work as /WR and /BHE
=============================================
SUM: ON OFF ON OFF OFF ON OFF OFF 10100100
=============================================

DIP103:
=======
1-2
Bus-Konfiguration: OFF OFF 16 Bit databus - multiplexed
3-6
Startup Mode: OFF OFF OFF OFF Standart Start
7
Adaptermode: OFF Standartoperation
8
ROC: OFF /RSTOUT remains LOW until
deactivation by USER-software
=============================================
SUM: OFF OFF OFF OFF OFF OFF OFF OFF 00000000
=============================================

DIP101:
=======
1-8
external memory configuration
OFF OFF OFF OFF OFF ON ON OFF
/CS0 = ext. RAM
/CS1 = ext. FLASH (not usefull)=============================================
SUM: OFF OFF OFF OFF OFF ON ON OFF 00000110
=============================================

DIP104/105:
===========
These settings depend from the selected segment address lines. For two bit lines
SALSEL = OFF OFF ( 2 Bit A17 ... A16 )
set DIP-switches as follows:
=============================================
DIP104: ON ON OFF OFF OFF OFF OFF OFF 11000000
DIP105: OFF OFF ON ON ON ON ON ON 00111111
( allways mirrored )
=============================================

DIP106:
=======
1-4
OFF OFF OFF OFF 0000 Normal program execution
ON OFF OFF OFF 1000 bootstraploader mode for programming
the micro e.g. with memtool


DIP104:
=======
1 2 3 4
Enable/Disable Peripherie
| | | |
nc nc CAN1 CAN2
for XC164
enable = ON disable = OFF
J1850
for XC161

Set as you need

Startup file I generated with DAvE.
You should enable the EBC and
set the phases for CS0 (RAM)timing to:
phase a: 0
phase b: 1
phase c: 1
phase d: 0
phase e: 1
phase f: 1 read
phase f: 0 write

Than no special port settings are required.
( I setup the data/ address port with DAvE too, so it stands in startup file)

Hope this helps, otherwise leave a message here and I will answer asap.
(But tomorrow ;-} )

Stefan

Hi Stefan,
thank you for all the information, it works fine.
Based on this, I'll try to get the board working with demultiplexed memory access.
Do you think, there are some speed differences between multiplexed and demultiplexed memory access?
Best regards
Steffen

Hi Steffen,

no matter about this. I do not know, whether the layout gives the possibility to work in demultiplexed mode.
But if you got it, it would be nice to have a short info about it.

Speed differences:

Yes there are some, since you have not to need latching the addresses.
But since the memory need some cycles per phase, it may be possible that you have to delay the phases in demuxed access mode.
So I can not exactly determine, if this would be a really improvement of the time.

Stefan

Hi Stefan,

I haven't been here for 2 weeks, because of my holidays. That's the reason I haven't replied since [7/24/03 8:07:42]. Now I'm back, so here is my reply: :)

I'm using the board in 16-bit demux. This works fine (didn't try 16-bit mux). I just switched the dip switches to the right configuration and changed the CS0-settings in the startup file.

Kind Regards,
Dennis Ebben