Project

General

Profile

T-DisplayTel » History » Version 15

laforge, 10/03/2022 08:45 AM

1 2 laforge
h1. T-DisplayTel
2 1 laforge
3
This is probably the only ISDN Phone with built-in [[BTX]] Terminal that was ever made.
4
5
h2. Pictures
6
7
FIXME
8 2 laforge
9 8 laforge
h2. Hardware
10
11
The hardware consists of 3 circuit boards:
12
13 9 laforge
* Mainboard (527/393-86211b)
14 8 laforge
* Display Board
15
* Keyboard
16
17 9 laforge
h3. Mainboard (527/393-86211b)
18 1 laforge
19 9 laforge
The mainboard contains the main processor, RAM, Flash, EPROM as well as display + keyboard controller and ISDN interface.
20
21 14 laforge
{{thumbnail(20221001_103719.jpg,size=500)}}
22
23 8 laforge
h4. Main CPU
24
25
* 1x NEC uPD70236AGD-12 (V53A) 16bit CPU (I101) attachment:UPD70236_NECElectronics.pdf
26
* 1x Samsung KM29C010-15 128k x 8 CMOS Flash Memory (I281) attachment:KM29C010.pdf
27 13 laforge
* 1x TI TMS27C240-12 256k x 16 EPROM (I271) attachment:TMS27C240.pdf
28
** EPROM image: attachment:DisplayTel_I271_24677_054_PROD_C_5293.bin
29 8 laforge
* 2x Samsung KM658128ALG-8  28k x 8 PSRAM (I231, I241) attachment:KM658128.pdf
30
* 24.576 MHz XTAL
31
* TI TL770SACP Supply Voltage Supervisor
32
33
h4. Keyboard Interface
34
35
* 1x OKI M80C51F-368 8-bit 8051 controller with 4k mask ROM (LOEWE 349-025514) (I611) attachment:M80C51F.pdf
36
* 11.0592 MHz XTAL
37
* connects to keyboard via 2x8 header (W651)
38
39
h4. Display Interface
40
41
* 1x OKI M6355 Display Controller (I361)
42 10 laforge
** connects to Display via 14pin FPC (W371)
43
** 3 MHz XTAL
44 8 laforge
* 1x Samsung KM62256BLG-10 32k x 8 CMOS SRAM (I381) attachment:KM62256.pdf
45
* 1x Motorola 34063AP1 KDI DC/DC connverter controller (for display supply voltage)
46
47
h4. ISDN Interface
48
49 15 laforge
Looks pretty similar to one of the passive HiSax (HSCX/ISAC) ISA ISDN cards for PCs:
50
51
* 1x Siemens SAB 82526 HSCX-1 V2.1 attachment:SAB82526.pdf
52
* 1x Siemens PSB 2186N V1.1 ISAC-S TE attachment:PSB2186.pdf
53 8 laforge
54 11 laforge
h3. Keyboard (86227.050)
55
56 14 laforge
{{thumbnail(20221001_111335.jpg,size=500)}}
57
{{thumbnail(20221001_111347.jpg,size=500)}}
58
59 11 laforge
* 4x LED (directly connected to header)
60
* 2x TI HC164 8-bit shift register
61
* 16x Diode (mini-MELF)
62 8 laforge
63 12 laforge
h3. Display board (Hitachi LMG6917RPGR-X)
64 14 laforge
65
{{thumbnail(20221001_112344.jpg,size=500)}}
66
{{thumbnail(20221001_112406.jpg,size=500)}}
67 12 laforge
68
* 3x BD66285BFC Common Drivre IC(IC5, IC6, IC7)
69
* 3x HD66284BFC Column Driver IC (IC1, IC2, IC3, IC4)
70
* 1x 530003HEB-S (IC9)
71
* 1x TA 423 75902FB (IC8)
72 8 laforge
73 2 laforge
h2. Making the BTX / Datex-J terminal work
74
75
@laforge has been attempting to find out what needs to be done to get the BTX/terminal part of T-DisplayTel to work.
76
77
On the D-channel signaling side, it is establshing a normal _UDI (unrestricted digital information)_, no specific HLC/LLC.
78
79 4 laforge
The more interesting question is what it speaks on the B-channel.
80 2 laforge
81
h3. Accepting the call, dumping raw B channel
82
83
When accepting a call (from the simulated BTX server side), the T-DisplayTel unexpectedly doesn't send HDLC but some 0xff-padding based signaling:
84
85
<pre>
86
00000000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
87
*
88
00000040  ff ff ff ff ff ff ff ff  ff ff ff ff fb 05 7c 59  |..............|Y|
89
00000050  df ed f7 ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
90
00000060  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
91
*
92
00001f20  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff fb  |................|
93
00001f30  05 7c 59 df ed f7 ff ff  ff ff ff ff ff ff ff ff  |.|Y.............|
94
00001f40  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
95
*
96
00007ce0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff fb  |................|
97
00007cf0  05 7c 59 df ed f7 ff ff  ff ff ff ff ff ff ff ff  |.|Y.............|
98
00007d00  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
99
*
100
0000daa0  ff ff ff ff ff ff ff ff  ff ff ff ff fb 05 7c 59  |..............|Y|
101
0000dab0  df ed f7 ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
102
0000dac0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
103
*
104
00013860  ff ff ff ff ff ff ff ff  7e 01 5f d6 77 fb fd ff  |........~._.w...|
105
00013870  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
106
*
107
00019620  ff ff ff ff ff ff fb 05  7c 59 df ed f7 ff ff ff  |........|Y......|
108
00019630  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
109
*
110
0001f3e0  ff ff ff ff 7e 01 5f d6  77 fb fd ff ff ff ff ff  |....~._.w.......|
111
0001f3f0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
112
*
113
000251a0  ff fb 05 7c 59 df ed f7  ff ff ff ff ff ff ff ff  |...|Y...........|
114
000251b0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
115
*
116
0002b310  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ab ab  |................|
117
0002b320  ab ab ab ab ab ab ab ab  ab ab ab ab ab ab ab ab  |................|
118
</pre>
119
120
So we see two messages, with a lot of 'ff' padding in between:
121
<pre>
122
fb 05 7c 59 df ed f7
123
7e 01 5f d6 77 fb fd
124
</pre>
125 1 laforge
126 7 laforge
If we re-order the bits of each byte and then HDLC decode (e.g. with https://gitea.osmocom.org/cellular-infrastructure/osmo-e1-recorder/src/branch/master/src/hdlc-test.c) we get
127 4 laforge
<pre>
128
fffb057c59dfedf7ff => F 01 3f eb df F
129
ff7e015fd677fbfdff => F 01 3f eb df F
130
</pre>
131
132
so it's actually a repeat transmission of the same frame.
133 2 laforge
134
h3. establishing a call against an ISDN TA
135
136
Establishing call towards ISDN TA ([[US_Robotics_Sportster_ISDN_TA_Ext]]) and playing with the B-channel protocol on the TA, I can get a "proper" connection established when putting the TA into *T.70-NL* mode (@ATB22@).  No success with HDLC, X.75 or V.120.
137
138
When the T.70-NL call is established, the DisplayTel cleaars its screen, and any characters sent by the TA are displayed on the screen. Great.
139
140
However, no characters are transmitted from the DisplayTel in the opposite direction.  In fact, it doesn't even ever leave the 'ff' mode, i.e. no HDLC flag octets are sent by it.  No keypress on the DisplayTel generates any non-ff data to be transmitted on the B-channel.
141
142
I'm attaching raw B-channel traces for both directions (attachment:displaytel-32-rx.raw and attachment:displaytel-32-tx.raw)
143 3 laforge
144
Interstingly, in this situation, the uplink from the Displaytel only contains a single, non-ff message:
145
146
<pre>
147
df a0 3e 9a fb b7 ef
148
</pre>
149 5 laforge
150
Decoded (bit order inversal + HDLC decode):
151
<pre>
152
F 01 3f eb df F 
153
</pre>
154 6 laforge
155
The same behavior can be observed when replacing the hardware ISDN TA with a software implementation: isdn4linux/ttyI0 in BTX mode (AT&X1) on Fritz!Card PCI.
Add picture from clipboard (Maximum size: 48.8 MB)