K1297-G20 Protocol Tester

Hello,

I have 2 Tektronix K1297-G20 protocol testers that I want to use to monitor the A and Abis interface in our lab. The problem is that the battery that was keeping the boot parameters of the AP-4 boards has discharged, and the boards are not booting (the boot command line is lost, I have only garbage).
Does anyone have access to a functional system to retrieve the boot parameters or does anyone know the right values for the boot command line?

Thank you,
Dan.

Hm, after digging out my device it is a K1297-1SA01 with Award PowerBIOS 1.00, which boots NT4 from SCSI disk. Guess the plattform is completely different since there is no boot command line, but a graphical BIOS menu.

From BIOS it probes the floppy drive and then jumps to the NT4 loader.

Edit: Just found out it has an AP-1 board. Didn’t know about the additional application processor, which seems to use VxWorks. It has a RJ12 serial port hidden under an “EMI do not remove” sticker, but there is no battery on it.

I’ve pinged a contact that used to be involved with those devices back in the Tektronix days. I’ll follow-up if there’s any result.

my former tektronix contact says: can you please post pictures of the top and rear sections? this way they know which exact components you have in your unit.

Furthermore, the question is whether or not you can boot the windows on the PC board. If yes, there should be some kind of K1297 window with output that can be saved (and would be of interest).

1 Like

Thank you very much for the feedback. I am not close to the equipment, but I will receive today the pictures. It will be very valuable for our lab at tye University.

I have the pictures of the two tracers. They seem clear enough to read the type of boards that we have in the system.
As a side note, I have also an older type of tracer, K1103, that has a broken video card. It broke due to old age. Can you please ask your friend of he has some hints where I could find the electronic schematic.

Thank you,
Dan.

It seems that I can attach only one picture, due to the fact that I am a new user.

This the front, it’s the same for both machines.

can you please answer the question?

1 Like

The Windows operating system is booting normally, the K1297-G20 application is giving timeout and not starting because the boards are not responding. I will post the log file and a screenshot.
The problem with the boards is that the boot command, which is stored in the NVRAM. Because the lithium battery has discharged, this parameter was lost. I replaced the component that has the battery (it’s a combination of 2 components a lithium battery and a crystal called SNAPHAT), but now I need to store in the NVRAM the correct boot command line, since now it is just a sequence of bogus characters (on one ofthe tracers it was only a line full of “U” characters, on the other one just some random characters).

It seems that I can not connect remotely to the system atbthe moment. When I will get access I will post the screenshot and the logfile

I have now the screenshots, one is the debug output of the AP-4 board over the serial interface and the other one is the main K1297-G20 application which is giving timeout due to the missing response from the AP-4 board.


I also found this in the log file of the application (TekMain.log). This is the lastest section (with the unsuccessful startup and timeout):

* Start of K1297-G20 application on  6/9/2026  6:27:57 PM 

**********************************************************************
[6/9/2026  6:27:50 PM] AP-1 [2]: boot started
[6/9/2026  6:27:51 PM] AP-1 [2]: tyco device installed
[6/9/2026  6:27:52 PM] AP-1 [2]: log server started
[6/9/2026  6:27:56 PM] PRIME [1]: boot started
[6/9/2026  6:28:00 PM] PRIME [1]: 32 MB RAM, S/N 00000A6DB4FE
[6/9/2026  6:28:00 PM] AP-1 [2]: 32 MB RAM
[6/9/2026  6:28:01 PM] PRIME [1]: Interface drivers installed
[6/9/2026  6:28:16 PM] PRIME [1]: log server started
[6/9/2026  6:38:28 PM] AP-1 [2]: boot OK
[6/9/2026  6:38:33 PM] PRIME [1]: boot OK

And this is the old successful startup:

* Start of K1297-G20 application on  4/17/2018  6:24:12 AM 

**********************************************************************
[4/17/2018  6:23:58 AM] ETH-100 [7]: 256 MB RAM
[4/17/2018  6:23:59 AM] PCE [3]: 256 MB RAM
[4/17/2018  6:23:59 AM] PCE [3]: log server started
[4/17/2018  6:24:04 AM] PRIME [1]: boot started
[4/17/2018  6:24:06 AM] AP-1 [2]: boot started
[4/17/2018  6:24:07 AM] AP-1 [2]: tyco device installed
[4/17/2018  6:24:07 AM] AP-1 [2]: log server started
[4/17/2018  6:24:09 AM] PCE [3]: Interface drivers loaded
[4/17/2018  6:24:15 AM] ETH-100 Flash: opening flash image file
[4/17/2018  6:24:16 AM] PRIME [1]: 32 MB RAM, S/N 00000A6DB4FE
[4/17/2018  6:24:16 AM] AP-1 [2]: 32 MB RAM
[4/17/2018  6:24:18 AM] PRIME [1]: Interface drivers installed
[4/17/2018  6:24:19 AM] ETH-100 [7] Comparing flash...
[4/17/2018  6:24:19 AM] PowerAp Flash: opening flash image file
[4/17/2018  6:24:19 AM] ETH-100 [7] Flash contents OK
[4/17/2018  6:24:20 AM] PCE [3]: Interface drivers started
[4/17/2018  6:24:21 AM] PowerAp [7]: Memory Extender installed
[4/17/2018  6:24:21 AM] PowerAp [0] Comparing flash...
[4/17/2018  6:24:22 AM] PowerAp [0] Flash contents OK
[4/17/2018  6:24:23 AM] ETH-100 [7]: CT loaded
[4/17/2018  6:24:23 AM] PowerAp [0]: CT loaded
[4/17/2018  6:24:30 AM] PowerAp [0]: 256 MB RAM
[4/17/2018  6:24:30 AM] PowerAp [0]: CT started
[4/17/2018  6:24:30 AM] PowerAp [0]: Management Software installed
[4/17/2018  6:24:30 AM] LEM [0]: recognized board with 256 MB
[4/17/2018  6:24:30 AM] LEM [0]: K12_EMU_HIGH_ENTRIES: 357
[4/17/2018  6:24:30 AM] LEM [0]: K12_EMU_LLNK_ENTRIES: 2500
[4/17/2018  6:24:30 AM] LEM [0]: K12_EMU_BUFFERS: 5000
[4/17/2018  6:24:30 AM] PowerAp [0]: Pipeline Manager started
[4/17/2018  6:24:32 AM] PCE [3]: Maximum ATM Links: 1000


[4/17/2018  6:24:33 AM] PCE [3]: STM1 Port A1 found
[4/17/2018  6:24:33 AM] PCE [3]: STM1 Port A2 found
[4/17/2018  6:24:33 AM] ETH-100 [7]: CT started
[4/17/2018  6:24:33 AM] PowerAp [0]: tq network installed (192.168.12.2)
[4/17/2018  6:24:33 AM] PowerAp [0]: route "0.0.0.0"->"192.168.12.1" installed
[4/17/2018  6:24:33 AM] PCE [3]: Management software installed
[4/17/2018  6:24:34 AM] ETH-100 [7]: Management Software installed
[4/17/2018  6:24:34 AM] ETH-100 [7]: Pipeline Manager started
[4/17/2018  6:24:35 AM] PowerAp [0]: sm network installed (192.168.13.1)
[4/17/2018  6:24:36 AM] PCE [3]: Hard- and Software OK
[4/17/2018  6:24:36 AM] PowerAp [0]: boot OK
[4/17/2018  6:24:38 AM] PRIME [1]: log server started
[4/17/2018  6:24:38 AM] PCE [3]: sm network installed (192.168.13.4)
[4/17/2018  6:24:38 AM] PCE [3]: route "0.0.0.0"->"192.168.13.1" installed
[4/17/2018  6:24:38 AM] PCE [3]: boot OK
[4/17/2018  6:24:39 AM] ETH-100 [7]: sm network installed (192.168.13.8)
[4/17/2018  6:24:39 AM] ETH-100 [7]: route "0.0.0.0"->"192.168.13.1" installed
[4/17/2018  6:24:39 AM] ETH-100 [7]: boot OK
[4/17/2018  6:24:43 AM] AP-1 [2]: boot OK
[4/17/2018  6:24:56 AM] PRIME [1]: boot OK
[4/17/2018  6:27:31 AM] GUI:   The Logical Link '5:C (Rx):16' in scenario 'Scenario' was not created because required hardware is missing. Please check the hardware configuration to make sure it is the same as it was used with this configuration file.



  The Logical Link '5:D (Rx):16' in scenario 'Scenario' was not created because required hardware is missing. Please check the hardware configuration to make sure it is the same as it was used with this configuration file.

my contact says it’s much more complex than just entering the correct bootline. Something about getting AP-4 to work again, which requires a floppy image of some sort. It’s unclear if any of those have survived in some ancient backup. It sounded rather complex. Also, he’s doubtful if the unit you have is actually capable fot perform Abis monitoring. Don’t ask me why, I know close to nothing on those devices, and I sadly also don’t really have the energy right now to be the messenger here. I thought I’d reach out if it just needs some kind of config / bootline, but apparently it is not as simple :frowning:

If your actual goal is to sniff (or trace) communication between your Siemens BSC and BTS, I still recommend that you use this gadget. Harald may be able to pitch in whether or not you could buy an assembled unit from Sysmocom (I don’t see it in the webshop), but in any case, all design files are published, so you should be able to build one yourself.

Thank you all for your responses. I will try to use the gadget that Mychaela recommended. I would have preferred to use the K1297 since I already have experience in using it. It has the protocol stack that the Siemens BSC/BTS uses, at it also have the license file for A and Abis interface.
If only I would have known that these boards have a battery that keeps the NVRAM in order to make a backup while it was still working. And all the systems that I know of died almost at the same time (during summer vacation).

@falconia - regarding the e1-tracer: I think if the parts are all available currently, we could produce a batch of 10 units or so and put it up in the webshop. Note that this would be a low-priority project compared to other tasks.

@laforge Thank you again. If I will manage to start the K12, I think I will buy a e1-tracer. I will let you know if this is the case.