view tcsm2-notes/tr16 @ 94:f9ef582c199c

tfo-ut: check in tfo-fr.bin and tfo-efr.bin Each of these binary files is an extract from MSC-side E1 timeslot recording in a Nokia TCSM2 TFO session involving a cross-connect between two TRAU channels. The extracts have been chosen to begin at the point where the TRAU starts emitting TFO frames, thereby beginning with a series of TFO frames that contain an embedded TFO_TRANS message. In each experiment, one of the two cross-connected TRAU channels emitted two "plain" TFO frames (not containing embedded TFO messages) in between the initial embedded TFO_TRANS and the subsequent embedded TFO_REQ_L; this channel was chosen for the present extracts. Each extract is thus 2560 PCM samples, containing 16 aligned TFO frames: 5 carrying TFO_TRANS, 2 plain, 9 carrying TFO_REQ_L.
author Mychaela Falconia <falcon@freecalypso.org>
date Tue, 18 Mar 2025 22:56:23 +0000
parents 2daf8f209707
children
line wrap: on
line source

TR16-S is the 16-channel transcoder card, providing 16 TRAU channels.
Examination of the board reveals the following major components:

Global for the whole TR16-S:

One Lattice ispLSI1032E: a programmable logic device, non-volatile configuration
bits inside.

One CY62128BLL-70SI chip: 128K x 8 static RAM.

Replicated 16x, one set for each TRAU channel:

One DSP chip, has these markings in addition to TI logo:

	TRLPRB 1.1
	D36884PZ-66
	ADW-4BAORLW

I had no success in finding any documentation for this DSP chip - was it one of
those semi-custom Skunkworks parts without public documentation?  I surmise
(without any proof!) that it is probably based on C54x architecture.

In addition to this DSP, there is one more chip replicated 16x per channel, one
next to each DSP: IDT 71V016, 64K x 16 static RAM.

Note the absence of any flash or other non-volatile memory chips: there is
non-volatile storage of configuration bits inside the Lattic PLD, but that's
just logic, no code.  The available documentation for TCSM2 strongly suggests
that operational DSP code is loaded from TRCO, presumably on each system boot,
but what about boot code, how does the "cold" TR16-S card communicate with TRCO?
The custom DSP ASICs probably have some ROM in them, supporting boot and maybe
providing some common routines or tables for the operational code, who knows...