BrightSign Source Code Corresponding to brightsign-v6.2.147.2 (ca9a71a85a662ba33780ff9530112292dc041839) 2017-10-16 * Introduction Parts of the firmware for this BrightSign product make use of "Open Source" software under various different licenses. Under the terms of some of these licenses we are required to provide the source code used to generate the binaries we distribute. This file describes the components and where the source code can be found. Note that the firmware also contains many other proprietary parts from BrightSign and third parties. The source code for these parts is not provided. * Build System The BrightSign firmware is based on the OpenEmbedded build framework (http://www.openembedded.org) which in turn uses bitbake (https://www.yoctoproject.org/tools-resources/projects/bitbake) The brightsign-6.2.147.2-src-oe.tar.gz file contains Bitbake, OpenEmbedded and the Brightsign-specific recipes and configuration files necessary to build the open source components used by the BrightSign firmware. The brightsign-6.2.147.2-src-dl.tar.gz file contains the actual source package tarballs. You should be able to build the toolchain and the components included in the BrightSign firmware by running the following: tar xaf brightsign-6.2.147.2-src-oe.tar.gz tar xaf brightsign-6.2.147.2-src-dl.tar.gz cd brightsign-oe/build-bcm7425 Then, for HDx20, LSx22 and AUx20 models: MACHINE=panther ./bsbb brightsign-source-release-world for HDx22 models: MACHINE=bobcat ./bsbb brightsign-source-release-world for HDx23, LSx23, HOx23 and HSx23 models: MACHINE=pantera ./bsbb brightsign-source-release-world for XDx30 models: MACHINE=cheetah ./bsbb brightsign-source-release-world for XDx32 models: MACHINE=lynx ./bsbb brightsign-source-release-world for XDx33, XTx33 models: MACHINE=impala ./bsbb brightsign-source-release-world for 4K models: MACHINE=tiger ./bsbb brightsign-source-release-world Note that a 64-bit host with at least 12GiB of memory is probably required for a successful build. * Secure boot lock In order to comply with HDCP and DTCP content protection regulations some BrightSign players will only boot secure firmware and system access is limited. BrightSign players that do not support HDCP and DTCP do not have this restriction. The remainder of this section only applies to BrightSigns that have HDCP and DTCP capabilities. If you wish to take advantage of your right to modify the "Open Source" software and install updated versions on the BrightSign you will need to disable secure booting. Disabling secure booting requires that the HDCP and DTCP encryption keys are permanently deleted from the device. Once you do this your BrightSign will not be capable of receiving HDCP-encrypted signals on the HDMI In connector, or sending and receving encrypted DTCP content ever again. THIS OPERATION CANNOT BE UNDONE. Disabling secure booting requires a serial connection to the player. For LSx23 a 5V serial port is available via the USB type C connector. The BrightSign player receives via TX1- or TX2- and transmits via TX1+ and TX2+. If your BrightSign player has an RS-232 serial port then you should use that with a female to female null modem (cross over) cable. If your BrightSign player has a 3.5mm serial port then you should use that with an appropriate cable. If your player does not have an RS-232 serial port but has a VGA port then a 3.3V serial port is available via the VGA connector: the BrightSign player receives via pin 4 and transmits via pin 11. If your player has neither an RS-232 serial port nor a VGA port then a 3.3V serial port is available via the GPIO connector: the BrightSign player receives via GPIO 4 (DE-15 pin 12, Phoenix pin 9) and transmits via GPIO 5 (DE-15 pin 4, Phoenix pin 10.) To disable secure booting and permanently wipe your HDCP keys: 1. Connect a serial cable to your BrightSign player (115200 8-N-1.) 2. Remove power from your BrightSign player. 3. Hold the SVC button in whilst applying power. 4. You should see messages appear on the serial port. 5. Once you are invited to press Ctrl-C you should do so and let go of the SVC button. 6. At the SECURE> prompt type "help" and view the information about the "disable-secure-boot" command before using it if you so choose.