How to find the TripleX IP in Boot Mode

In a TripleX receiver that is operating normally, the IP of the receiver may be found in the IP configuration menu. This IP changes when the receiver gets stuck in boot mode and cannot finish loading. Without the receiver's IP, you cannot access any of the receiver's firmware files. The receiver's IP can be found even when it is stuck in Boot mode by using a few simple steps.

The TripleX is designed to communicate through the receiver's RS232 serial port. To see the data that the receiver is sending, you will need a null RS232 cable to attach the receiver to a computer, a computer with a working RS232 serial port, and a HyperTerminal or Putty communications program.

The HyperTerminal commutations program can be found on some Windows XP and older computers. I think HyperTerminal was discontinued beginning with Windows Vista, but a replacement called Putty may be downloaded from the internet if you Google it.

Settings for the HyperTerminal or Putty programs will need to be the same as the RS232 communications port on the computer. Here is a list of settings that I use:
Bits per second = 115200
Data bits = 8
Parity = NONE
Stop bits = 1
Flow Control = NONE
These settings are entered into the computer's RS232 serial port which can be found in the computer's Device Manager, and they are entered into the HyperTerminal or Putty communications programs. (Be sure to tick the serial connection if using Putty.)

To receive data from the the TripleX receiver after the correct settings for the computer's RS232 serial port and the Hyperterminal or Putty have been entered and verified, turn the TripleX receiver OFF using the rocker switch on the back, connect the RS232 null cable to the receiver and the computer's serial port. Start and Connect or Load the HyperTerminal or Putty communications program, then turn the receiver on. If everything is set correctly, a stream of data will be sent to the communications program as soon as the receiver is turned on.

The stream of data that is sent to the computer's communications program will contain many things. Error codes may be sent if the receiver is hung in boot, and the receiver's IP will be sent too. Listed below is an edited data stream from my TripleX receiver.

Loading from NAND 512MiB 3,3V 8-bit, offset 0x100000
Image Name: Kernel-Ramdisk-Image
Image Type: SuperH Linux Multi-File Image (gzip compressed)
Data Size: 5899691 Bytes = 5.6 MiB
Load Address: 80800000
Entry Point: 80801000
Contents:
Image 0: 3001582 Bytes = 2.9 MiB
Image 1: 2898095 Bytes = 2.8 MiB
## Booting image at 80000000 ...
Image Name: Kernel-Ramdisk-Image
Image Type: SuperH Linux Multi-File Image (gzip compressed)
Data Size: 5899691 Bytes = 5.6 MiB
Load Address: 80800000
Entry Point: 80801000
Contents:
Image 0: 3001582 Bytes = 2.9 MiB
Image 1: 2898095 Bytes = 2.8 MiB
Verifying Checksum ... OK
Uncompressing Multi-File Image ... OK
stmac_phy_get_addr(): id1 = 0xffff, id2 = 0xffff
found phy at addres = 2
stmac_phy_get_addr(): id1 = 0x7, id2 = 0xc0f1
stb_id = c060014f
Loading Ramdisk to 81d3c000, length 002c38af ... OK

Starting kernel console=ttyAS1,115200 rw ramdisk_size=6144 root=/dev/ram0 init=/linuxrc ip=192.168.0.63:192.168.31.119:192.168.31.1:255.25 5.0.0:Spark:eth0ff stmmaceth=msglvl:0,phyaddr:2,watchdog:5000 bigphysarea=7000 nwhwconf=device:eth0,hwaddr:30:00:06:00:01:4F Manufacture=Spark-Project STB_ID=0C:06:05:00:01:01:4F - 0x0152d000 - 2898195 ...

The IP for this receiver is 192.168.0.63. This is the IP that you would use if you needed to connect the receiver to FileZilla or another similar program to access the receiver's internal firmware files.

Note:This IP will not be valid for file communications and will not work if the TripleX receiver is not stuck in Boot Mode.
This IP is only valid for file transfers and communications if the receiver is stuck in Boot Mode. EB