firmware_log_client.py

When the IP-STB is initially powered on, the IP-STB firmware is responsible for locating and downloading a suitable boot image. There are several ways to transmit the boot image to the IP-STB (infocast, http, tftp...) and each have their own configuration and potential problems. The firmware_log_client.py script is provided in the SDK to help debugging boot problems.

Difference from the regular log client

The logclient is used under normal STB operation, that is, once the KreaTV platform has been successfully booted. On the other hand, the firmware logging is only available during the initial part of the boot up sequence, and only contains information on the booting process.

Logclient is an outgoing connection from your host PC. Logclient takes as an argument the IP of the STB you want to receive a log from, and then connects to the IP-STB. The IP-STB is always listening and ready for an incoming logclient connection.

firmware_log_client.py listens passively for incoming connections to your host PC. The STB initiates the connection shortly after power on, and transmits the log to the host PC. If the host PC is not running the firmware_log_client.py script, the log is lost.

Note that firewalls around your host PC or IP-STB may block one or both of these logging connections. firmware_log_client.py should only be used in a lab setting, not in a live deployment

Configuring firmware logging

As described above, the STB will initiate the firmware log connection, and so needs to know the IP address of the host PC. This is sent to the IP-STB by configuring the DHCP message type option code 3 (option Kreatel.firmware-log, see example DHCP config)