SamyGO - User contributions [en]

Setting up a cross-compilation toolchain

2011-05-04T13:11:16Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
 
==Microsoft Windows (i686/AMD)==
===Native===
The Codesourcery tool chain works in Microsoft Windows

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
 
===Cygwin===
See Microsoft windows, the cross tool chain described there works in Cygwin as well

Done
 
----
 
==GNU/Linux environment (i686/AMD architecture)==
===Samsung tool chain===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example Ubunutu/Debian on a standard PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| VDLinux-mips34kc-toolchain-lite-20100223.tgz
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for Mips cpu little endian architectures 
toolchain_mips24ke_nfp_be.tgz for Mips cpu big endian architectures. 
In this example the little endian version will be used 
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hellovd to the TV and execute at the prompt
./hellovd

Done
 
----
 
===Emdebian toolchain)===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example Ubunutu/Debian on a standard PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| gcc-4.4-mipsel-linux-gnu
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other pre compiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
mipsel-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file helloed to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
 
==Hello world==

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
 
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-05-04T08:03:40Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
 
==Microsoft Windows==
===Native for i686/AMD architecture===
The Codesourcery tool chain works in Microsoft Windows

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
 
===Cygwin for i686/AMD architecture===
See Microsoft windows, the cross tool chain described there works in Cygwin as well

Done
 
----
 
==GNU/Linux environment==
===Samsung tool chain for i686/AMD architecture===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example Ubunutu/Debian on a standard PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| VDLinux-mips34kc-toolchain-lite-20100223.tgz
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for Mips cpu little endian architectures 
toolchain_mips24ke_nfp_be.tgz for Mips cpu big endian architectures. 
In this example the little endian version will be used 
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hellovd to the TV and execute at the prompt
./hellovd

Done
 
----
 
===Emdebian toolchain for i686/AMD architecture===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example Ubunutu/Debian on a standard PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| gcc-4.4-mipsel-linux-gnu
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other pre compiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
mipsel-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file helloed to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
 
==Hello world==

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
 
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-22T09:43:44Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| VDLinux-mips34kc-toolchain-lite-20100223.tgz
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for Mips cpu little endian architectures 
toolchain_mips24ke_nfp_be.tgz for Mips cpu big endian architectures. 
In this example the little endian version will be used 
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hellovd to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| gcc-4.4-mipsel-linux-gnu
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other pre compiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
mipsel-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file helloed to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-22T09:43:16Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
'''===Codesourcery tool chain, Microsoft Windows==='''
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| VDLinux-mips34kc-toolchain-lite-20100223.tgz
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for Mips cpu little endian architectures 
toolchain_mips24ke_nfp_be.tgz for Mips cpu big endian architectures. 
In this example the little endian version will be used 
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hellovd to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| gcc-4.4-mipsel-linux-gnu
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other pre compiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
mipsel-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file helloed to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T13:25:34Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| VDLinux-mips34kc-toolchain-lite-20100223.tgz
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for Mips cpu little endian architectures 
toolchain_mips24ke_nfp_be.tgz for Mips cpu big endian architectures. 
In this example the little endian version will be used 
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hellovd to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="400" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| gcc-4.4-mipsel-linux-gnu
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other pre compiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
XXXXXXX -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file helloed to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T13:24:53Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="200" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| VDLinux-mips34kc-toolchain-lite-20100223.tgz
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for Mips cpu little endian architectures 
toolchain_mips24ke_nfp_be.tgz for Mips cpu big endian architectures. 
In this example the little endian version will be used 
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hellovd to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="200" align="left" | Cross compiler
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| gcc-4.4-mipsel-linux-gnu
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other pre compiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
XXXXXXX -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file helloed to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T13:20:46Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hellovd to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
XXXXXXX -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file helloed to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T12:18:23Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hellovd to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/XXXXXX/bin/XXXXXXX -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file helloed to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T12:17:38Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/XXXXXX/bin/XXXXXXX -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code 
The switch <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T12:15:04Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
|
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/XXXXXX/bin/XXXXXXX -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for a specific variant of the CPU. Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T12:10:38Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum, http://forum.samygo.tv/index.php 
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite, this is free of charge) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for any type of CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/toolchain_mips24ke_nfp_be/bin/mips24ke_nfp_be-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T12:08:37Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This part of the article about pre compiled cross tool chains was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum.
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for any type of CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/toolchain_mips24ke_nfp_be/bin/mips24ke_nfp_be-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T11:50:34Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This article was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum.
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for any type of CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/toolchain_mips24ke_nfp_be/bin/mips24ke_nfp_be-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the <code>apt-get install linux .....</code> 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T09:40:38Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This article was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum.
Done
 
----
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for any type of CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
 
----
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
 
----
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/toolchain_mips24ke_nfp_be/bin/mips24ke_nfp_be-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the apt-get 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
 
----
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
 
----
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T09:38:58Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This article was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

 
==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum.
Done
----
 
===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for any type of CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
----
 
===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
----
 
===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/toolchain_mips24ke_nfp_be/bin/mips24ke_nfp_be-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the apt-get 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
----
 
===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
----
 
=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T09:37:28Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This article was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output for a TV set UEC46C5105
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum.
Done
----

===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for any type of CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
----

===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
----

===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/toolchain_mips24ke_nfp_be/bin/mips24ke_nfp_be-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the apt-get 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
----

===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
----

=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

The C Series Wiki

2011-04-21T09:35:47Z

Stefanth:

[[File:c_wiki.png|140px|right]]

==SamyGO C Series Wiki Page Main==
On this page, you will find hacks related for only C series TVs.
*[[BEFORE YOU START: Safety measures for C series TVs]]
*[[Compatibility Table for C series TVs]]
*[[For what we need all these C-Series Hacks%3F]]

==Hacking/rooting==
*[[Hacking C-Series TV with Internet@TV only]]
*[[Hacking TV over Hotel mode (most C series models)]]
*[[How to get root access on a C series TV]]
*[[PSxxC7000]]

==ServiceMenu tricks==
*[[Enabling the PVR for C-Series]]
*[[How to change your Internet@TV region]]
*[[How to enable MHP for C-Series]] (available only in Italy)

==Software Applications==
*[[Applications list for C seres TVs]]
*[[Desktop applications list]]
*[[Android applications list]]
*[[iOS applications list]]
*[[PVR Recording over NFS for C-Series]] - Samygo-All-Extensions.
*[[How to connect C series to NFS under WIN7 using Hanewin NFS Server]]

==Software Tools==
*[[Setting up a cross-compilation toolchain]]

==Hardware==
*[[Ex-Link Cable for C-Series]]
*[[Using NoN-Samsung USB WiFi dongles with TV]]
*[[Fix low speed USB devices (keyboard, mouse, ...) on C-Series Trident]]

==Other==
*[[How to downgrade T-VALDEUC firmware]]
*[[How to format /mtd_rwarea/ to reset USB hack]]
*[[How to identify CPU type]]
*[http://tobias.schroepf.de/doku/doku.php?id=garage:samsung_tv_hacking External page dealing with the C series] TODO: The contents from this page should be copied to this Wiki.

Setting up a cross-compilation toolchain

2011-04-21T09:32:31Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This article was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum.
Done
----

===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Download the (lite) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for any type of CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
----

===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
----

===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

{| class="The test program have been tested on the following TV sets"
|-
! scope="col" width="100" align="left" | TV
! scope="col" width="100" align="left" | CPU
! scope="col" width="100" align="left" | Architecture
! scope="col" width="100" align="left" | Status
|-
| UE46C5105
| Mips
| Little endian
| Working
|}

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/toolchain_mips24ke_nfp_be/bin/mips24ke_nfp_be-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the apt-get 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
----

===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
----

=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Setting up a cross-compilation toolchain

2011-04-21T09:17:56Z

Stefanth:

A tool chain is a set of executable programs that enables you to build (assemble, compile and link) your own executable programs from source code (typically C, C++, fortran or other programming languages). To build these executables, the source code needs to be translated into machine-readable code. This is what a tool chain does. The translation proceeds in three steps (well, you may think of it this way): translation into low-level code (compilation), translation to machine-readable code (assembly), combination with other code libraries (linking). Compilation/assembly mostly proceeds in a single go. So, for a tool chain you need at least three programs: a compiler, an assembler, and a linker. In almost all cases you will also need a C-library to link with.

Unlike source code, executables are machine-specific. That means that executables built for the Intel x86 architecture (the basis for most computers in the world today) will not run on other types of processors, for example the ARM architecture, the basis for many embedded systems. To build executables for a Samsung TV on an x86-based machine, you will need a tool chain that runs on the x86-architecture and builds executable code for the ARM-architecture. This procedure is called cross-compilation, and requires a cross compilation tool chain. This wiki page deals with the installation of different tool chain provided by various providers, executing on various platforms such as on an x86, Linux or Windows (Cygwin) platform. 

This tutorial describes different ways to set up a cross tool chain to compile programs that can be executed on a TV set. 

The tutorial do not describe how to create applications that can be downloaded and executed on the TV via it's standard menus or by Samsung provided value chain systems. 
The TV need to be hacked according to one of the several ways described on the SamyGo Wiki so it is possible to use telnet/ssh to log on to the TV and execute the example program via a shell.

__TOC__

=Using pre compiled compilers=

A pre compiled compiler means that someone have already built the compiler and the user only have to install the tool, there are no steps involving building the tool chain from scratch 
The example source code in this tutorial is using stdout for output and do not include any drawing on the actual TV screen. 

This article was inspired by the following persons work
scottrix, arris69, aaaaa75 from the SamyGo forums http://forum.samygo.tv/viewtopic.php?f=12&t=1537&start=0&hilit=codesourcery and 
Moozing, http://moozing.wordpress.com/2011/04/05/cross-compile-in-debian/

Thanks to Roman, the original designer and developer of WebGui SamyGo used in the hotel mode hack.

==First step==
As a first step it is necessary to know what type of CPU there is in the target TV set and it's architecture so the right tool chain can be downloaded.
The CPU is easily recognised by executing the following at the telenet/ssh prompt of the TV set 
# cat /proc/cpuinfo 
produce the following output
system type : MStar Titania3
processor : 0
cpu model : MIPS 34Kc V5.4
BogoMIPS : 351.23
wait instruction : yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x02a0, 0x0448, 0x0288]
ASEs implemented : mips16 dsp mt
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
 
In this example the target CPU is a Mips of the type 34kc. 

It is also necessary to know if the CPU is running in little endian or big endian mode, on some TV series it can be guessed from the name of the software,
enable the service menu on the TV and look at the top most lines that indicate the software version, 

For the C series TV set. 
If the number starts with T-MSX the architecture is little endian 
If the number starts with T-TDT the architecture is big endian 

For example, for the TV set UEC465105 it says 
<code>
T-MSX5DEUC-2005.4 
T-MSX5DEUS-1001 
</code> 

This indicate that that the architecture for UEC465105 is little endian. If there are any doubts about what type of architecture the CPU is executing in, ask in the SamyGo forum.
Done
----

===Codesourcery tool chain, Microsoft Windows===
This tool chain works in Microsoft Windows, this tool does not work in a Cygwin environment on a PC.

The test program have been tested on the following TV sets
TV CPU Architecture Status
UE46C5105 Mips Little endian Working

Download the (lite) tool chain for the Mips CPU from CodeSourcery (http://www.codesourcery.com/sgpp/lite_edition.html) and install it, during the installation it is possible add the path to the tool chain to the environment variables PATH which can be recommended.
This compiler have support both for little endian and big endian which is controlled by a switch, see below.

After installing the tool,
Start a command window and enter the following
c:\
mkdir C:\temp\sample1
cd C:\temp\sample1

create a helloword.c file, see [[#Hello world|Hello world]] 
mips-linux-gnu-gcc.exe -mel -mglibc -march=34kc helloworld.c -o hellocs
<code>-mel</code> tells the compiler to generate code for a little endian architecture, use switch <code>-meb</code> for big endian architecture. 
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs 
<code>-march</code> defines a very specific CPU type, if not given, the compiler generates generic code that is not optimized for any type of CPU 
<code>-o</code> defines the output file 

copy the file hellocs to the TV with ftp or any other file transfer tool and enter the following at the prompt 
./hellocs

Done
----

===Samsung tool chain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC.

The test program have been tested on the following models
TV CPU Architecture Status
UE46C5105 Mips Little endian Working

Samsung provide two tool chains via their open source download page, http://opensource.samsung.com
VDLinux-mips34kc-toolchain-lite-20100223.tgz for little endian architectures and toolchain_mips24ke_nfp_be.tgz for big endian architectures.
In this example the little endian version will be used
Download VDLinux-mips34kc-toolchain-lite-20100223.tgz from http://opensource.samsung.com and enter the following at the prompt
cd
mkdir tc
cd tc
tar -zxvf ../VDLinux-mips34kc-toolchain-lite-20100223.tgz
cd
mkdir sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/VDLinux-mips34kc-toolchain-lite-20100223/bin/mips-linux-gnu-gcc -mglibc -march=34kc helloworld.c -o hellovd
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./hellovd

Done
----

===Emdebian toolchain, GNU/Linux environment===
This tool chain works in GNU/Linux hosted on a i686 architecture, for example ubunutu/debian on a PC. This tool does not work in a Cygwin environment on a PC. 

The test program have been tested on the following models 
TV CPU Architecture Status
UE46C5105 Mips Little endian Working

Emdebian provides a number pre compiled packages that can be installed using apt-get, in this example the cross compiler will target a MIPS cpu with an little endian architecture.
Use http://www.emdebian.org/toolchains/search.php for other precompiled packages targeting other cpu's

At the prompt
cd
apt-get install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu
mkdir -p sample1
cd sample1
create the helloword.c file, see http://en.wikipedia.org/wiki/Hello_world_program_examples#C
~/tc/toolchain_mips24ke_nfp_be/bin/mips24ke_nfp_be-gcc -mglibc -march=34kc helloworld.c -o helloed
<code>-mglibc</code> tells the compiler to use GNU/libc instead of uclibs
<code>-march</code> defines the very specific target CPU, if not given, the compiler generates generic code that is not optimized for the CPU
Note, this tool chain can only produce little endian code, the flag <code>-mel</code> is not needed and the flag <code>-meb</code> will cause an error. 
copy the file hello to the TV and execute at the prompt
./helloed

Installing a big endian MIPS tool chain would be
apt-get install linux-libc-dev-mips-cross libc6-mips-cross libc6-dev-mips-cross binutils-mips-linux-gnu gcc-4.4-mips-linux-gnu g++-4.4-mips-linux-gnu

<big>'''Errors during apt-get'''</big> 
'''Not allowed''': You need to put <code>sudo</code> first on the line, like <code>sudo apt-get ....</code> 
'''Not found''': 
Do the following at the prompt (read http://emdebian.org/tools/crosstools.html) 
'''NOTE''' the >> on the <code>echo</code> line, '''DO NOT USE''' single > 
echo "deb http://www.emdebian.org/debian/ squeeze main" >> /etc/apt/sources.list
apt-get update
apt-get install emdebian-archive-keyring
then redo the apt-get 
'''Out of cache memory''': 
add "-o apt::Cache-Limit=XXXXXXX " to the apt-get line where XXXXXXX is a number bigger than the the reported cache size when the error message is given,
like this (using sudo, mips target, little endian, cache size 30000000) 
sudo apt-get -o apt::Cache-Limit=30000000 install linux-libc-dev-mipsel-cross libc6-mipsel-cross libc6-dev-mipsel-cross binutils-mipsel-linux-gnu gcc-4.4-mipsel-linux-gnu g++-4.4-mipsel-linux-gnu

Done
----

===Hello world===

#include <stdio.h>

int main(void)
{
printf("Hello world\n");
return (0);
}
----

=Toolchains 101, building and compiling the tool chain from scratch=

This page is a brief summary of the cross-compilation discussion on the SamyGO forum. Main contributors to this information are Robbiesz and marcelru.
The information in this page pertains to the building of a tool chain, based on the source code as stored in the file 32B650.zip, available from Samsung.

We are still in the testing phase, for now, check out the forum discussion (topic: cross-compilation [http://forum.samygo.tv/viewtopic.php?f=5&t=34]). Especially the Windows building procedure is not completely established yet and relies (for now) on the Linux scripts. When fully reliable, a separate set of scripts for Windows/Cygwin will be released. For more info, errors you may encounter, support for other Samsung tool chains, please refer to the forum, or better still, participate.

===The Samsung toolchain===
The source code for the Samsung ARM toolchain is available on the net, but needs some adjustments before it can be built. We will discuss that later.
The main parts are:
*GNU binutils (containing among other things an assembler and a linker)
*GCC, the GNU C/C++ compiler (and a host of other languages we will not use)
*Glibc, the GNU C library
*linux kernel sources, for operating system/processor specific details.

For the remainder of this wiki page, we will use the toolchain for the 32B650/32B550/... TV's as an example. The source code for this toolchain is stored in the file 32B650.zip [http://www.samsung.com/global/opensource/files/32B650.zip]. Download this file and store it in the directory where you want to build your toolchain.
Download the SamyGO patches that enable compilation of the toolchain here: [http://forum.samygo.tv/download/file.php?id=14]
===Building the toolchain on Linux===
Since most Linux distro's come standard with a full toolchain for building packages, building the cross-compilation toolchain on this platform is fairly straightforward, and proceeds in 6 stages (You will need approximately 2.5GB diskspace for the build).
====Source installation====
Unpack and install the source code files. This is done with the script install_sources.sh: edit paths and code versions to your liking:

#! /bin/sh
#
# install_sources.sh installs the source code for the toolchain for Samsung
# TV's, as found in the file 32B650.zip. Place this file together with the
# patches tarball (SamyGO-toolchain_fc11_patches.tgz) in the ${BUILDROOT}
# directory, defined below, and run this script.
#
BUILDROOT=/tmp/arm-tools # edit according to your needs.

cd ${BUILDROOT}
mkdir -p ${BUILDROOT}/src

# unpack the Samsung zip file

unzip 32B650.zip

# remove unnecessary stuff and move the kernel and toolchain code

rm -f libgphoto2-2.3.1.tar.zip
rm -f libusb-0.1.12.tar.gz
rm -f SDL-1.2.11.zip
mv linux.chelsea.tgz ${BUILDROOT}/src

# unpack the toolchain and remove unnecessary stuff

tar -zxvf SELP.3.2.x-Chelsea.src.tgz
rm -f SELP.3.2.x-Chelsea.src.tgz

mv ./SELP.3.2.x-Chelsea.src/Toolchain/gcc-4.2.0-4.0.9.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/binutils-2.17.50.tgz ${BUILDROOT}/src
mv ./SELP.3.2.x-Chelsea.src/Toolchain/glibc-2.5.90-9.0.9.tgz ${BUILDROOT}/src

rm -rf ./SELP.3.2.x-Chelsea.src

# unpack the patches and move them

tar -zxvf SamyGO-toolchain_fc11_patches.tgz
mv *.patch ${BUILDROOT}/src

'''Notice for binutils:''' If original binutils-2.17.50 don't compile on your computer, you can try it with different versions of binutils. On OpenSUSE 11.2, I compile it via binutils-2.19.1

====Kernel headers installation====
Install the kernel header files. You will need these when you want to build your own kernel modules for your TV. For that, the kernel source code's version has to match your TV's kernel version _exactly_. The installation is done with the install_kernel_src.sh script: again, edit to meet your needs.

#! /bin/sh

# how to install kernel headers using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_kernel_src.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the linux tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your needs
SYSROOT=${BUILDROOT}/sysroot

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove previous installation if it is there:
rm -rf linux
rm -rf linux-r011
rm -rf RFS
rm -rf ssdtv_platform

# unpack, move up one dir and link:

tar -zxvf linux.chelsea.tgz # from 32B650.zip
mv ./linux/* .
rm -rf linux/

ln -s ./linux-r011 linux

cd linux

# copy header files to sysroot:
mkdir -p ${SYSROOT}/usr/include
cp -a ${BUILDROOT}/src/linux/include/linux ${SYSROOT}/usr/include/linux
cp -a ${BUILDROOT}/src/linux/include/asm-arm ${SYSROOT}/usr/include/asm
cp -a ${BUILDROOT}/src/linux/include/asm-generic ${SYSROOT}/usr/include/asm-generic

# remove stale link to ssdtv headers:
rm -rf ${SYSROOT}/usr/include/asm/arch-ssdtv

# ... and copy these as well:
cp -a ${BUILDROOT}/src/ssdtv_platform/include/asm-arm/arch-ssdtv ${SYSROOT}/usr/include/asm

Everything is now installed (but not yet unpacked). The remainder of the installation consists of the actual building of the tools: First the binutils are built: as, ld and a bunch of others. For cross-compilation, these tools do not need any resources for the target platform (ARM, in this case).
====Building of binutils====
Apart from a small bug in one of the source files and a configuration change to be made to part of the code (patches are included) the build is straightforward, done with mkbinutils.sh:
#! /bin/sh

# how to build binutils using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkbinutils.sh) in it.
# In ${BUILDROOT}, create a directory ./src and put the binutils tarball and
# the patch in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
UTILS=binutils-2.17.50

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

tar -zxvf binutils-2.17.50.tgz # from 32B650.zip
patch -p0 < ./binutils-2.17.50_fc11.patch

mkdir -p BUILD/${UTILS}
cd BUILD/${UTILS}

../../${UTILS}/configure --prefix=${PREFIX} --target=${TARGET} \
--with-sysroot=${SYSROOT}
make

make install

mkdir -p $PREFIX/$TARGET/include
cp ${BUILDROOT}/src/${UTILS}/include/libiberty.h $PREFIX/$TARGET/include

When all goes well, you will now have the following executables in /usr/local/bin:

arm-SamyGO-linux-gnueabi-addr2line
arm-SamyGO-linux-gnueabi-ar
arm-SamyGO-linux-gnueabi-as
arm-SamyGO-linux-gnueabi-c++filt
arm-SamyGO-linux-gnueabi-gprof
arm-SamyGO-linux-gnueabi-ld
arm-SamyGO-linux-gnueabi-nm
arm-SamyGO-linux-gnueabi-objcopy
arm-SamyGO-linux-gnueabi-objdump
arm-SamyGO-linux-gnueabi-ranlib
arm-SamyGO-linux-gnueabi-readelf
arm-SamyGO-linux-gnueabi-size
arm-SamyGO-linux-gnueabi-strings
arm-SamyGO-linux-gnueabi-strip

====GCC installation, stage 1====
The C-compiler (gcc) has to be built in two stages: First, it is built and linked against the existing C-library (glibc). This version of the compiler is used to build glibc for the target platform, and then gcc is built again, now with the just compiled C-library.

The stage 1 build of gcc renders a barebones gcc, just useful for compiling glibc, as described in the next step: Edit install_gcc_stage1.sh according to your needs and execute. The source code will be patched to prevent building of two runtime objects that cannot be linked yet (because we don't have a working C-library for ARM, yet)
#! /bin/sh

# how to install gcc stage 1 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage1.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GCC}.tgz # from 32B650.zip

patch -p0 < ./gcc-4.2.0-4.0.9_t-linux-eabi.patch

mkdir -p BUILD/${GCC}-stage1

cd BUILD/${GCC}-stage1
../../${GCC}/configure --prefix=${PREFIX} --target=${TARGET} \
--enable-languages=c --disable-shared --disable-threads \
--disable-libmudflap --disable-libssp --disable-nls \
--disable-libgomp --with-cpu=arm1136jf-s --with-fpu=vfp

make all-gcc
make install-gcc
====Glibc installation====
Build glibc for ARM: Edit the paths in mkglibc.sh (if needed) and execute:

#! /bin/sh

# how to install glibc using this script:
#
# Create the ${BUILDROOT} directory, put this script (mkglibc.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the glibc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools # change to meet your needs
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GLIBC_VER=glibc-2.5.90-9.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# unpack

tar -zxvf ${GLIBC_VER}.tgz # from 32B650.zip

patch -p0 < ./${GLIBC_VER}_fc11.patch

rm -rf ${BUILDROOT}/src/glibc-build-localedef
mv ${BUILDROOT}/src/${GLIBC_VER}/glibc-build-localedef ./

mkdir -p ${BUILDROOT}/src/BUILD/${GLIBC_VER}
cd BUILD/${GLIBC_VER}

# create some cached defaults:
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache

export GCC_PATH=${PREFIX}/bin

BUILD_CC=gcc CC=${GCC_PATH}/${CROSS_COMPILE}gcc ../../${GLIBC_VER}/configure \
--target=${TARGET} --host=${TARGET} --prefix=${PREFIX}/${TARGET} \
--with-__thread \
--cache-file=config.cache --with-headers=${SYSROOT}/usr/include \
--with-glibc=${BUILDROOT}/src/${GLIBC_VER} \
--disable-profile --enable-add-ons
make
make install
====GCC installation, stage 2====
Finally, gcc needs to be rebuilt and linked against the just built glibc for ARM. Now C++-support will be included as well.

Edit install_gcc_stage2.sh and execute. In this script, links to the kernel header files are created in the include/ directory of the toolchain. That's not very elegant. Normally, the C-compiler should try and find the kernel headers in e.g., /usr/src/linux/include, but that's where the native kernel sources for your build platform reside. Your build platform is not necessarily the same as your target platform (most likely not). The method presented here works, but needs some editing in the future.
#! /bin/sh

# how to install gcc stage 2 using this script:
#
# Create the ${BUILDROOT} directory, put this script (install_gcc_stage2.sh)
# in it.
# In ${BUILDROOT}, create a directory ./src and put the gcc tarball in it.

# go up one directory and run this script.

TARGET=arm-SamyGO-linux-gnueabi
BUILDROOT=/tmp/arm-tools
PREFIX=/usr/local # change to your liking
SYSROOT=${BUILDROOT}/sysroot
GCC=gcc-4.2.0-4.0.9

export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin

cd ${BUILDROOT}/src

# remove links to kernel headers if they exist:
rm -f ${PREFIX}/${TARGET}/include/linux
rm -f ${PREFIX}/${TARGET}/include/asm
rm -f ${PREFIX}/${TARGET}/include/asm-generic

# create symlinks to kernel headers:

ln -s ${SYSROOT}/usr/include/linux ${PREFIX}/${TARGET}/include/linux
ln -s ${SYSROOT}/usr/include/asm ${PREFIX}/${TARGET}/include/asm
ln -s ${SYSROOT}/usr/include/asm-generic ${PREFIX}/${TARGET}/include/asm-generic

# make builddir:

mkdir -p BUILD/${GCC}-stage2

cd BUILD/${GCC}-stage2

CC=gcc ../../${GCC}/configure --target=${TARGET} --prefix=${PREFIX} \
--enable-languages=c,c++ --enable-threads --enable-shared \
--disable-nls --enable- __cxa_atexit --enable-long-long \
--enable-c99 --with-cpu=arm1136jf-s --with-fpu=vfp

make
make install

When you look in /usr/local/bin now, you should see the cross-compilers for C and C++ for arm-SamyGO-linux-gnueabi.

===Building the toolchain on Windows (Cygwin)===
The toolchain build on Windows/Cygwin proceeds in the same way as the build on Linux. If you have the choice between Windows and Linux, go for Linux. Shell script execution is orders of magnitude faster on Linux, and the installation procedure is carried out through _many_ shell scripts. Don't say that you haven't been warned. To be able to build the toolchain you need to have Cygwin installed, see the Cygwin website [http://www.cygwin.com] for details on installation. At the time of writing, the Cygwin stable release version was 1.5.25-15, and that is the version used for the build here, on Windows XP Home Edition. Cygwin creates a Unix-style environment on the Windows platform, and comes with pretty much the same development environment as GNU/Linux. You will need this GNU/Linux-style environment to be able to build your toolchain. The native Windows environment (visual studio and the likes) will NOT work.
====Cygwin installation notes====
When installing Cygwin, select "Unix-style linefeeds" (the default) when prompted. Otherwise you will find yourself editing ALL installation scripts, not just the handful presented here.
Apart from the default (minimal) installation, which you shouldn't touch, you should have at least the following packages installed:

(Untick the "Hide obsolete packages" box in the "Select Packages" installer window to view everything, the packages in the following list may have been selected already for default installation)

*autoconf
*automake
*bash
*binutils
*bison
*byacc
*bzip2
*diffutils
*flex
*gawk
*gcc
*gcc-core
*gcc-g++
*gcc4
*gcc4-core
*gcc4-g++
*gettext
*gzip
*libgcc1
*libiconv
*m4
*make
*patch
*patchutils
*texinfo
*unzip
*vim
*zip
It is not clear whether you actually need all of these, but most packages take little disk space and little time to install. Running into errors because of lacking packages will take more time.

With Cygwin properly installed, the same 6 steps as described in the Linux installation section need to be taken.
Download the SamyGO patches and scripts [http://forum.samygo.tv/download/file.php?id=14] and edit these.
====Editing of installation scripts====
In the following, only differences with respect to the Linux installation will be described. Start Cygwin by double-clicking on its Desktop icon.
You will get a window in which the standard Cygwin shell runs (ash, if I'm not mistaken).
At the prompt, type the following command to make the BUILDROOT directory (take your pick with respect to the name, this is what I've been using):
mkdir -p ./tmp/arm-tools
Copy the Samsung sources (32B650.zip) and the SamyGO patches and scripts to this directory. Windows explorer will do. Unpack the patches:
cd ./tmp/arm-tools
tar -zxvf SamyGO-toolchain-install_fc11.tgz
Edit the environment variable BUILDROOT in the installation scripts (all just installed files that end with .sh).
By default, Cygwin is installed in C:/cygwin. All paths used in Cygwin are relative to this installation path, but for some reason the BUILDROOT environment variable needs to point to the full path. Edit the line BUILDROOT in all installation scripts to make it point to the full path of your build (be sure to use the forward slashes!!):
...
BUILDROOT=c:/cygwin/home/username/tmp/arm-tools # edit according to your needs.
...
When using notepad.exe or another DOS-style editor, revert the scripts, after saving, to unix-style linefeeds with the command:
dos2unix ./install_sources.sh
Do this for all scripts you edit, BEFORE execution. Failing to do so may render errors like:
$'\r': command not found
This error type occurs when shell scripts with DOS rather than Unix-style linefeeds are being processed. When using the vi editor (in the Cygwin shell window) you don't have this problem.
====Installation of the sources and kernel headers====
Execute ./install_sources.sh and ./install_kernel_src.sh after one another by typing their names with a leading ./ and their extension .sh. Unlike Windows, Unix does not guess filename extensions. They are considered to be part of the filename, nothing else. This step installs the sources and kernel headers in the right place.
====Building of binutils and gcc, stage 1====
Edit ./mkbinutils.sh and ./install_gcc_stage1.sh. In both scripts, add a line to make the environment variable CC point to gcc-4:
...
export ARCH=arm
export CROSS_COMPILE=${TARGET}-
export PATH=$PATH:${PREFIX}/bin
export CC=/usr/bin/gcc-4
...

and build the binutils with ./mkbinutils.sh.
After successful completion, build gcc stage 1 with ./install_gcc_stage1.sh.

To be continued soon ...

Well, building glibc on Cygwin proves to be a bit harder than I thought. For now only statically linked stuff is possible. Will get back here as soon as it's working properly, sorry, folks ...

Hacking TV over Hotel mode (most C series models)

2011-04-10T09:42:42Z

Stefanth: /* TV is not hacked */

'''Universal USB disk to hack C series TV'''

''''''WARNING - Do not type ''reboot'' in console - it was the reason on few bricked TVs.'''

After hack your TV you can connect to TV via Telnet, you get CIFS (Samba) and NFS support, FTP Server, WebUI, crond, ... 
Moreover, if you attach USB with script file "SamyGO.sh", it will be executed. 
This hack has unificated structure for comfortable script execution for developers (read below).
 
==Safety measures for C series TVs==
Make some important settings before start hacking TV:
* In service menu, '''enable Debug mode''' for the RS232 port.
::With TV switched off, press the following sequence on the remote: '''[INFO] [MENU] [MUTE] [POWER]'''
::Enter the '''Control''' menu and set the value of the '''RS232 mode''' to '''Debug'''.
::Once you're back to the main Service menu, you will have to power off the TV for normal operation.
::Notice that your TV will reset RS232 mode back to UART when you install another firmware (no matter if it's older or newer).
* Have a working '''[[Ex-Link Cable for C-Series]]''' at hand. (desirable)
::If you don't feel capable of soldering such a cable, you can find and buy a cheap (under '''$5''') '''[http://shop.ebay.com/i.html?_trkparms=65%253A12%257C66%253A2%257C39%253A1%257C72%253A4030&rt=nc&_nkw=usb+ttl&_sticky=1&_trksid=p3286.c0.m14&_sop=15&_sc=1 USB to TTL adapter]''' at eBay.

== Supported TV models ==
TV model is not important, you should check your firmware. 
* This hack '''works''' on all firmware versions (even latest firmwares):
T-TDT5DEUC
T-MSX5DEUC
T-MSX6DEUC
T-VALDEUC
T-VALAUSC (modification of hack needed)
* Hack '''does not''' work on TV with '''T-VAL6DEUC''' firmware.

== Preparation ==
1. USB > 1GB space (Windows users can use FAT32 formatted USB) 
2. TV in normal mode. Export channels from TV to clean FAT32 USB 
3. Activate Hotel Mode
[Mute] [1] [1] [9] [Enter]
set to '''on''' by pressing [left]
4. Export settings from TV to the same FAT32 USB ("Clone TV to USB") 
5. Unplug USB stick from TV and save files you get anywhere on PC 
6. Download [http://download.samygo.tv/C%20Series/HotelMode%20hack/network_opt_18.02.2011_1.zip network_opt_18.02.2011_1.zip], extract archive. You get 1GB file '''network_opt_18.02.2011_sda2.img''' 
*'''IMPORTANT:''' This is the 3rd version of the USB image, updated on 18.2.2011. 
::If you have hacked TV with the earlier version or over widget and you want have benefits of this hack, 
::you should [http://wiki.samygo.tv/index.php?title=Hacking_TV_over_Hotel_mode_%28most_C_series_models%29#TV_is_already_hacked re-hack TV].[[File:Win32diskimage_howto.png |right]] 
7. Make USB from this image with help of included win32diskimager
* After win32diskimager finishes, you get two partitions on USB: one FAT32, accessible under Windows and a second, ext3 - not accessible under Windows. 
* You '''do not need''' to do any changes on ext3 partition. 
* '''All operations have to be done on the FAT32 partition, no linux needed.'''
 

== Installation. What to do if... ==
 
=== '''TV is not hacked''' ===
8. Attach Universal hack USB you made to PC. Copy channel settings file (you made in normal mode) to root of USB. 
9. Rename file (channel_list_LE32C550_1001.scm for C550) to zip
channel_list_LE32C550_1001.scm.zip
10. Add directory ''usb_mount'' with empty file in it (e.g. ''1.txt;'' - very important) to archive 
11. Rename back to channel_list_LE32C550_1001.scm
* You get files inside of archive:
Archive: channel_list_LE32C550_1001.scm
Length Date Time Name
--------- ---------- ----- ----
68 2038-01-19 06:14 CloneInfo
96 2038-01-19 06:14 FineTune_Digital
40000 2038-01-19 06:14 map-AirA
292000 2038-01-19 06:14 map-AirD
40000 2038-01-19 06:14 map-CableA
292000 2038-01-19 06:14 map-CableD
4 2038-01-19 06:14 map-ChKey
720 2038-01-19 06:14 RadioMap
0 2010-11-30 21:55 usb_mount/
8 2010-11-30 21:55 usb_mount/1.txt
--------- -------
664896 10 files
12. Copy files exported in Hotel mode (from the step "Clone TV to USB" above, only files, without directories) to '''/HotelMode''' directory on USB
* Exported in HotelMode files to copy:
./T-MSX5DEUC/Clone:

drwxr-xr-x 2 root root 4096 2010-12-27 18:39 .
drwxr-xr-x 3 root root 4096 2010-12-27 18:39 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat

13. Exit from Hotel mode:
Mute-1-1-9-Enter
set to '''off'''
* Hotel Mode → Off
14. Attach USB to TV and import channel settings to TV. Everything must work without errors. 
15. Activate Hotel mode again.
Mute-1-1-9-Enter
set to '''on''' by pressing "left"
16. Import HotelMode settings you exported before (as is, with directories) ("Clone USB to TV") 
17. Press OK. 
18. TV restarts few times and starts in ''black screen''. DO NOT POWER OFF, DO NOT DISCONNECT USB! 
* '''Wait 3 minutes'''. After three minutes you can switch off TV.
* Switch on TV again
* Try connect to TV over Telnet (Port 23).
* If you get to console, congratulations.
* TV starts in Hotel mode. If you have your channel settings, you can deactivate hotel mode from service menu.
19. If you haven't got your channels back and if you can't Telnet to TV, it means something went wrong.
* Look for file ''first_run.ok'' and content of directory ''/result'' on USB
20. If you have Telnet after hack, execute:
cp $OPT_DIR/usr/restore/start.sh /mtd_rwarea/start.sh
21. Done.

=== '''TV is already hacked''' ===
(Over Hotel Mode or Widget - doesn`t matter)
* Make USB (steps 6. and 7.)
* Do not change anything
* Attach to TV and connect via SSH/Telnet
* Find your usb:
df -h | grep "/dtv/usb/sd"
* execute script '''first_run.sh''' with parameter of path to USB.
::e.g. if path to USB is '''/dtv/usb/sda1''', then command to enter is:
sh +x /dtv/usb/sda1/first_run.sh /dtv/usb/sda1
Path might be different on your TV, for example:
::/dtv/usb/sdb1/first_run.sh /dtv/usb/sdb1
::/dtv/usb/sdc1/first_run.sh /dtv/usb/sdc1
Check exact path over Telnet before you start.
* Wait until you get the message "Installation Completed!", but '''do not reboot TV 3 minutes''' (TV is making some dumps in this time, do not interrupt it.)
* Reboot TV (switch off, wait, switch on again)
* Done

== Normal operating of hacked TV ==
* To get access to TV (Telnet/FTP/WebUI) you must attach the same USB-stick that you created for this hack '''or''' prepare USB-stick with the latest [http://download.samygo.tv/C%20Series/ SamyGO-Extensions]. (If you need to know your CPU type enter '''cat /proc/cpuinfo''' into console.)

* Example for mounting a NFS-share manually:
cd /dtv/usb/sda1
mkdir videos
/bin/mount -o nolock 192.168.1.123:/videos /dtv/usb/sda1/videos -t nfs
Change IP to your NFS-server IP, path to USB might differ too (sdb1/sdc1).
* To watch movies, create empty directory on root of usb:
!network

== Bricked TV ==
* ''''''WARNING - Do not type ''reboot'' in console - it was the reason on few bricked TVs.'''

=== '''ExLink cable available''' ===
==== Screen is blank ====
If your start.sh has been written with errors, TV does not boot properly... 
* Unplug TV and wait 30 sec. Plug to AC, power on TV.
This should remove /mtd_rwarea/start.sh. If that did not help, try:
* Connect [[Ex-Link Cable for C-Series]], switch to debug mode:
10041004
enter:
31337 (removes /mtd_rwarea/start.sh)
or:
666 (removes /mtd_rwarea/start.sh, /mtd_rwarea/usb_mount, /mtd_rwarea/network_opt)
or:
44337794 (check file to know better what it does /mtd_rwarea/network_opt/sbin/44337794)

==== No reaction to USB, no telnet, but screen is on ====
* create empty file named '''kill_start.sh''' on root of USB
* power off TV
* attach USB and power on TV
/mtd_rwarea/start.sh should be deleted

If no success, then:
==== format /mtd_rwarea/ ====
If you do not have success or script finishes with error,
or you have hacked over Widget and it stopped working (on latest firmwares),
Format /mtd_rwarea over ExLink and get "virgin" TV back:
* Make [[Ex-Link Cable for C-Series]] attach to TV.
* Power off TV.
* Unplug network and antenna cable. Leave only ExLink and power cable plugged.
* Power on TV.
* Open terminal and connect to TV over ExLink.
* Apply these commands (followed by Enter):
10041004
81588
20089999
2
0
0
2 (advanced)
2 (DeviceManager Debug)
90 (DeviceManager MW Debug)
12 (DLNA, FLASH, ODD, HDD, MoIP Test)
11 (FLASH, HDD Format Test)
10 (or another, /mtd_rwarea/ partition number (14)

::On the last line you have to enter number of your /mtd_rwarea/. On C550 it is 10, but on other TV it can be other (e.g. 14)
::Try to hack TV again starting from step 7.

=== '''no ExLink cable available''' ===

* Create script on USB '''emergency_start.sh''' (kill_start.sh is to delete)
* Attach USB to TV on stand-by mode and power it on
* TV executes this script on boot.
Factory reset on ServiceMenu. This operation should delete ''/mtd_rwarea/network_opt''
*Hack TV with universal USB disk again

== FAQ ==
To be updated...

== Tested and works on TV ==
* LE32C530 [T-MSX5DEUC-2007.4]
* LE32C550J1W [T-MSX5DEUC-2005.4]
* LE32C550J1WU [T-MSX5DEUC-2007.4]
* LE32C550J1WX [T-MSX5DEUC-2005.4]
* LE37C630 [T-MSX6DEUC 1002.1] 
* LE40C650L1WX [T-VALDEUC-2002]
* LE40C550 [T-MSX5DEUC-2003.1]
* LE40C750 [T-VALDEUC 3007.1]
* PN58C7000 [T-VALAUSC 001035] - some [http://forum.samygo.tv/viewtopic.php?f=13&t=974&p=13650#p13642 modification] of hack is needed.
* PS50C550 [T-TDT5DEUC]
* UE32C5100QW [T-MSX5DEUC-2007.4]
* UE32C5000QW [T-TDT5DEUC-1022.0 ]
* UE40C8700 [T-VALDEUC-'''3006.2''']
* UE40C8700 [T-VALDEUC '''3007.1''']
* UE40C6700 [T-VALDEUC '''3007.1''']
* UE46C6105 [T-MSX5DEUC-2005.4]
* UE55C7700 [T-VALDEUC '''3006.1''']
* UE55C8705 [T-VALDEUC '''3007.1''']
::To be updated... 
 
Author and developer of universal USB hack disk - Perforator from forum.ixbt.com (He made the first hack for C series TV also). 
 
 
--[[User:Juzis28|Juzis28]] 12:13, 11 March 2011 (UTC)

Hacking TV over Hotel mode (most C series models)

2011-04-10T09:40:07Z

Stefanth: /* TV is not hacked */

'''Universal USB disk to hack C series TV'''

''''''WARNING - Do not type ''reboot'' in console - it was the reason on few bricked TVs.'''

After hack your TV you can connect to TV via Telnet, you get CIFS (Samba) and NFS support, FTP Server, WebUI, crond, ... 
Moreover, if you attach USB with script file "SamyGO.sh", it will be executed. 
This hack has unificated structure for comfortable script execution for developers (read below).
 
==Safety measures for C series TVs==
Make some important settings before start hacking TV:
* In service menu, '''enable Debug mode''' for the RS232 port.
::With TV switched off, press the following sequence on the remote: '''[INFO] [MENU] [MUTE] [POWER]'''
::Enter the '''Control''' menu and set the value of the '''RS232 mode''' to '''Debug'''.
::Once you're back to the main Service menu, you will have to power off the TV for normal operation.
::Notice that your TV will reset RS232 mode back to UART when you install another firmware (no matter if it's older or newer).
* Have a working '''[[Ex-Link Cable for C-Series]]''' at hand. (desirable)
::If you don't feel capable of soldering such a cable, you can find and buy a cheap (under '''$5''') '''[http://shop.ebay.com/i.html?_trkparms=65%253A12%257C66%253A2%257C39%253A1%257C72%253A4030&rt=nc&_nkw=usb+ttl&_sticky=1&_trksid=p3286.c0.m14&_sop=15&_sc=1 USB to TTL adapter]''' at eBay.

== Supported TV models ==
TV model is not important, you should check your firmware. 
* This hack '''works''' on all firmware versions (even latest firmwares):
T-TDT5DEUC
T-MSX5DEUC
T-MSX6DEUC
T-VALDEUC
T-VALAUSC (modification of hack needed)
* Hack '''does not''' work on TV with '''T-VAL6DEUC''' firmware.

== Preparation ==
1. USB > 1GB space (Windows users can use FAT32 formatted USB) 
2. TV in normal mode. Export channels from TV to clean FAT32 USB 
3. Activate Hotel Mode
[Mute] [1] [1] [9] [Enter]
set to '''on''' by pressing [left]
4. Export settings from TV to the same FAT32 USB ("Clone TV to USB") 
5. Unplug USB stick from TV and save files you get anywhere on PC 
6. Download [http://download.samygo.tv/C%20Series/HotelMode%20hack/network_opt_18.02.2011_1.zip network_opt_18.02.2011_1.zip], extract archive. You get 1GB file '''network_opt_18.02.2011_sda2.img''' 
*'''IMPORTANT:''' This is the 3rd version of the USB image, updated on 18.2.2011. 
::If you have hacked TV with the earlier version or over widget and you want have benefits of this hack, 
::you should [http://wiki.samygo.tv/index.php?title=Hacking_TV_over_Hotel_mode_%28most_C_series_models%29#TV_is_already_hacked re-hack TV].[[File:Win32diskimage_howto.png |right]] 
7. Make USB from this image with help of included win32diskimager
* After win32diskimager finishes, you get two partitions on USB: one FAT32, accessible under Windows and a second, ext3 - not accessible under Windows. 
* You '''do not need''' to do any changes on ext3 partition. 
* '''All operations have to be done on the FAT32 partition, no linux needed.'''
 

== Installation. What to do if... ==
 
=== '''TV is not hacked''' ===
8. Attach Universal hack USB you made to PC. Copy channel settings file (you made in normal mode) to root of USB. 
9. Rename file (channel_list_LE32C550_1001.scm for C550) to zip
channel_list_LE32C550_1001.scm.zip
10. Add directory ''usb_mount'' with empty file in it (e.g. ''1.txt;'' - very important) to archive 
11. Rename back to channel_list_LE32C550_1001.scm
* You get files inside of archive:
Archive: channel_list_LE32C550_1001.scm
Length Date Time Name
--------- ---------- ----- ----
68 2038-01-19 06:14 CloneInfo
96 2038-01-19 06:14 FineTune_Digital
40000 2038-01-19 06:14 map-AirA
292000 2038-01-19 06:14 map-AirD
40000 2038-01-19 06:14 map-CableA
292000 2038-01-19 06:14 map-CableD
4 2038-01-19 06:14 map-ChKey
720 2038-01-19 06:14 RadioMap
0 2010-11-30 21:55 usb_mount/
8 2010-11-30 21:55 usb_mount/1.txt
--------- -------
664896 10 files
12. Copy files exported in Hotel mode (only files, without directories) to '''/HotelMode''' directory on USB
* Exported in HotelMode files to copy:
./T-MSX5DEUC/Clone: (These are the files coming from the step "Clone TV to USB")

drwxr-xr-x 2 root root 4096 2010-12-27 18:39 .
drwxr-xr-x 3 root root 4096 2010-12-27 18:39 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat

13. Exit from Hotel mode:
Mute-1-1-9-Enter
set to '''off'''
* Hotel Mode → Off
14. Attach USB to TV and import channel settings to TV. Everything must work without errors. 
15. Activate Hotel mode again.
Mute-1-1-9-Enter
set to '''on''' by pressing "left"
16. Import HotelMode settings you exported before (as is, with directories) ("Clone USB to TV") 
17. Press OK. 
18. TV restarts few times and starts in ''black screen''. DO NOT POWER OFF, DO NOT DISCONNECT USB! 
* '''Wait 3 minutes'''. After three minutes you can switch off TV.
* Switch on TV again
* Try connect to TV over Telnet (Port 23).
* If you get to console, congratulations.
* TV starts in Hotel mode. If you have your channel settings, you can deactivate hotel mode from service menu.
19. If you haven't got your channels back and if you can't Telnet to TV, it means something went wrong.
* Look for file ''first_run.ok'' and content of directory ''/result'' on USB
20. If you have Telnet after hack, execute:
cp $OPT_DIR/usr/restore/start.sh /mtd_rwarea/start.sh
21. Done.

=== '''TV is already hacked''' ===
(Over Hotel Mode or Widget - doesn`t matter)
* Make USB (steps 6. and 7.)
* Do not change anything
* Attach to TV and connect via SSH/Telnet
* Find your usb:
df -h | grep "/dtv/usb/sd"
* execute script '''first_run.sh''' with parameter of path to USB.
::e.g. if path to USB is '''/dtv/usb/sda1''', then command to enter is:
sh +x /dtv/usb/sda1/first_run.sh /dtv/usb/sda1
Path might be different on your TV, for example:
::/dtv/usb/sdb1/first_run.sh /dtv/usb/sdb1
::/dtv/usb/sdc1/first_run.sh /dtv/usb/sdc1
Check exact path over Telnet before you start.
* Wait until you get the message "Installation Completed!", but '''do not reboot TV 3 minutes''' (TV is making some dumps in this time, do not interrupt it.)
* Reboot TV (switch off, wait, switch on again)
* Done

== Normal operating of hacked TV ==
* To get access to TV (Telnet/FTP/WebUI) you must attach the same USB-stick that you created for this hack '''or''' prepare USB-stick with the latest [http://download.samygo.tv/C%20Series/ SamyGO-Extensions]. (If you need to know your CPU type enter '''cat /proc/cpuinfo''' into console.)

* Example for mounting a NFS-share manually:
cd /dtv/usb/sda1
mkdir videos
/bin/mount -o nolock 192.168.1.123:/videos /dtv/usb/sda1/videos -t nfs
Change IP to your NFS-server IP, path to USB might differ too (sdb1/sdc1).
* To watch movies, create empty directory on root of usb:
!network

== Bricked TV ==
* ''''''WARNING - Do not type ''reboot'' in console - it was the reason on few bricked TVs.'''

=== '''ExLink cable available''' ===
==== Screen is blank ====
If your start.sh has been written with errors, TV does not boot properly... 
* Unplug TV and wait 30 sec. Plug to AC, power on TV.
This should remove /mtd_rwarea/start.sh. If that did not help, try:
* Connect [[Ex-Link Cable for C-Series]], switch to debug mode:
10041004
enter:
31337 (removes /mtd_rwarea/start.sh)
or:
666 (removes /mtd_rwarea/start.sh, /mtd_rwarea/usb_mount, /mtd_rwarea/network_opt)
or:
44337794 (check file to know better what it does /mtd_rwarea/network_opt/sbin/44337794)

==== No reaction to USB, no telnet, but screen is on ====
* create empty file named '''kill_start.sh''' on root of USB
* power off TV
* attach USB and power on TV
/mtd_rwarea/start.sh should be deleted

If no success, then:
==== format /mtd_rwarea/ ====
If you do not have success or script finishes with error,
or you have hacked over Widget and it stopped working (on latest firmwares),
Format /mtd_rwarea over ExLink and get "virgin" TV back:
* Make [[Ex-Link Cable for C-Series]] attach to TV.
* Power off TV.
* Unplug network and antenna cable. Leave only ExLink and power cable plugged.
* Power on TV.
* Open terminal and connect to TV over ExLink.
* Apply these commands (followed by Enter):
10041004
81588
20089999
2
0
0
2 (advanced)
2 (DeviceManager Debug)
90 (DeviceManager MW Debug)
12 (DLNA, FLASH, ODD, HDD, MoIP Test)
11 (FLASH, HDD Format Test)
10 (or another, /mtd_rwarea/ partition number (14)

::On the last line you have to enter number of your /mtd_rwarea/. On C550 it is 10, but on other TV it can be other (e.g. 14)
::Try to hack TV again starting from step 7.

=== '''no ExLink cable available''' ===

* Create script on USB '''emergency_start.sh''' (kill_start.sh is to delete)
* Attach USB to TV on stand-by mode and power it on
* TV executes this script on boot.
Factory reset on ServiceMenu. This operation should delete ''/mtd_rwarea/network_opt''
*Hack TV with universal USB disk again

== FAQ ==
To be updated...

== Tested and works on TV ==
* LE32C530 [T-MSX5DEUC-2007.4]
* LE32C550J1W [T-MSX5DEUC-2005.4]
* LE32C550J1WU [T-MSX5DEUC-2007.4]
* LE32C550J1WX [T-MSX5DEUC-2005.4]
* LE37C630 [T-MSX6DEUC 1002.1] 
* LE40C650L1WX [T-VALDEUC-2002]
* LE40C550 [T-MSX5DEUC-2003.1]
* LE40C750 [T-VALDEUC 3007.1]
* PN58C7000 [T-VALAUSC 001035] - some [http://forum.samygo.tv/viewtopic.php?f=13&t=974&p=13650#p13642 modification] of hack is needed.
* PS50C550 [T-TDT5DEUC]
* UE32C5100QW [T-MSX5DEUC-2007.4]
* UE32C5000QW [T-TDT5DEUC-1022.0 ]
* UE40C8700 [T-VALDEUC-'''3006.2''']
* UE40C8700 [T-VALDEUC '''3007.1''']
* UE40C6700 [T-VALDEUC '''3007.1''']
* UE46C6105 [T-MSX5DEUC-2005.4]
* UE55C7700 [T-VALDEUC '''3006.1''']
* UE55C8705 [T-VALDEUC '''3007.1''']
::To be updated... 
 
Author and developer of universal USB hack disk - Perforator from forum.ixbt.com (He made the first hack for C series TV also). 
 
 
--[[User:Juzis28|Juzis28]] 12:13, 11 March 2011 (UTC)

Hacking TV over Hotel mode (most C series models)

2011-04-09T16:58:16Z

Stefanth: /* Tested and works on TV */

'''Universal USB disk to hack C series TV'''

''''''WARNING - Do not type ''reboot'' in console - it was the reason on few bricked TVs.'''

After hack your TV you can connect to TV via Telnet, you get CIFS (Samba) and NFS support, FTP Server, WebUI, crond, ... 
Moreover, if you attach USB with script file "SamyGO.sh", it will be executed. 
This hack has unificated structure for comfortable script execution for developers (read below).
 
==Safety measures for C series TVs==
Make some important settings before start hacking TV:
* In service menu, '''enable Debug mode''' for the RS232 port.
::With TV switched off, press the following sequence on the remote: '''[INFO] [MENU] [MUTE] [POWER]'''
::Enter the '''Control''' menu and set the value of the '''RS232 mode''' to '''Debug'''.
::Once you're back to the main Service menu, you will have to power off the TV for normal operation.
::Notice that your TV will reset RS232 mode back to UART when you install another firmware (no matter if it's older or newer).
* Have a working '''[[Ex-Link Cable for C-Series]]''' at hand. (desirable)
::If you don't feel capable of soldering such a cable, you can find and buy a cheap (under '''$5''') '''[http://shop.ebay.com/i.html?_trkparms=65%253A12%257C66%253A2%257C39%253A1%257C72%253A4030&rt=nc&_nkw=usb+ttl&_sticky=1&_trksid=p3286.c0.m14&_sop=15&_sc=1 USB to TTL adapter]''' at eBay.

== Supported TV models ==
TV model is not important, you should check your firmware. 
* This hack '''works''' on all firmware versions (even latest firmwares):
T-TDT5DEUC
T-MSX5DEUC
T-MSX6DEUC
T-VALDEUC
T-VALAUSC (modification of hack needed)
* Hack '''does not''' work on TV with '''T-VAL6DEUC''' firmware.

== Preparation ==
1. USB > 1GB space (Windows users can use FAT32 formatted USB) 
2. TV in normal mode. Export channels from TV to clean FAT32 USB 
3. Activate Hotel Mode
[Mute] [1] [1] [9] [Enter]
set to '''on''' by pressing [left]
4. Export settings from TV to the same FAT32 USB ("Clone TV to USB") 
5. Unplug USB stick from TV and save files you get anywhere on PC 
6. Download [http://download.samygo.tv/C%20Series/HotelMode%20hack/network_opt_18.02.2011_1.zip network_opt_18.02.2011_1.zip], extract archive. You get 1GB file '''network_opt_18.02.2011_sda2.img''' 
*'''IMPORTANT:''' This is the 3rd version of the USB image, updated on 18.2.2011. 
::If you have hacked TV with the earlier version or over widget and you want have benefits of this hack, 
::you should [http://wiki.samygo.tv/index.php?title=Hacking_TV_over_Hotel_mode_%28most_C_series_models%29#TV_is_already_hacked re-hack TV].[[File:Win32diskimage_howto.png |right]] 
7. Make USB from this image with help of included win32diskimager
* After win32diskimager finishes, you get two partitions on USB: one FAT32, accessible under Windows and a second, ext3 - not accessible under Windows. 
* You '''do not need''' to do any changes on ext3 partition. 
* '''All operations have to be done on the FAT32 partition, no linux needed.'''
 

== Installation. What to do if... ==
 
=== '''TV is not hacked''' ===
8. Attach Universal hack USB you made to PC. Copy channel settings file (you made in normal mode) to root of USB. 
9. Rename file (channel_list_LE32C550_1001.scm for C550) to zip
channel_list_LE32C550_1001.scm.zip
10. Add directory ''usb_mount'' with empty file in it (e.g. ''1.txt;'' - very important) to archive 
11. Rename back to channel_list_LE32C550_1001.scm
* You get files inside of archive:
Archive: channel_list_LE32C550_1001.scm
Length Date Time Name
--------- ---------- ----- ----
68 2038-01-19 06:14 CloneInfo
96 2038-01-19 06:14 FineTune_Digital
40000 2038-01-19 06:14 map-AirA
292000 2038-01-19 06:14 map-AirD
40000 2038-01-19 06:14 map-CableA
292000 2038-01-19 06:14 map-CableD
4 2038-01-19 06:14 map-ChKey
720 2038-01-19 06:14 RadioMap
0 2010-11-30 21:55 usb_mount/
8 2010-11-30 21:55 usb_mount/1.txt
--------- -------
664896 10 files
12. Copy files exported in Hotel mode (only files, without directories) to '''/HotelMode''' directory on USB
* Exported in HotelMode files to copy:
./T-MSX5DEUC/Clone:

drwxr-xr-x 2 root root 4096 2010-12-27 18:39 .
drwxr-xr-x 3 root root 4096 2010-12-27 18:39 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat

13. Exit from Hotel mode:
Mute-1-1-9-Enter
set to '''off'''
* Hotel Mode → Off
14. Attach USB to TV and import channel settings to TV. Everything must work without errors. 
15. Activate Hotel mode again.
Mute-1-1-9-Enter
set to '''on''' by pressing "left"
16. Import HotelMode settings you exported before (as is, with directories) ("Clone USB to TV") 
17. Press OK. 
18. TV restarts few times and starts in ''black screen''. DO NOT POWER OFF, DO NOT DISCONNECT USB! 
* '''Wait 3 minutes'''. After three minutes you can switch off TV.
* Switch on TV again
* Try connect to TV over Telnet (Port 23).
* If you get to console, congratulations.
* TV starts in Hotel mode. If you have your channel settings, you can deactivate hotel mode from service menu.
19. If you haven't got your channels back and if you can't Telnet to TV, it means something went wrong.
* Look for file ''first_run.ok'' and content of directory ''/result'' on USB
20. If you have Telnet after hack, execute:
cp $OPT_DIR/usr/restore/start.sh /mtd_rwarea/start.sh
21. Done.

=== '''TV is already hacked''' ===
(Over Hotel Mode or Widget - doesn`t matter)
* Make USB (steps 6. and 7.)
* Do not change anything
* Attach to TV and connect via SSH/Telnet
* Find your usb:
df -h | grep "/dtv/usb/sd"
* execute script '''first_run.sh''' with parameter of path to USB.
::e.g. if path to USB is '''/dtv/usb/sda1''', then command to enter is:
sh +x /dtv/usb/sda1/first_run.sh /dtv/usb/sda1
Path might be different on your TV, for example:
::/dtv/usb/sdb1/first_run.sh /dtv/usb/sdb1
::/dtv/usb/sdc1/first_run.sh /dtv/usb/sdc1
Check exact path over Telnet before you start.
* Wait until you get the message "Installation Completed!", but '''do not reboot TV 3 minutes''' (TV is making some dumps in this time, do not interrupt it.)
* Reboot TV (switch off, wait, switch on again)
* Done

== Normal operating of hacked TV ==
* To get access to TV (Telnet/FTP/WebUI) you must attach the same USB-stick that you created for this hack '''or''' prepare USB-stick with the latest [http://download.samygo.tv/C%20Series/ SamyGO-Extensions]. (If you need to know your CPU type enter '''cat /proc/cpuinfo''' into console.)

* Example for mounting a NFS-share manually:
cd /dtv/usb/sda1
mkdir videos
/bin/mount -o nolock 192.168.1.123:/videos /dtv/usb/sda1/videos -t nfs
Change IP to your NFS-server IP, path to USB might differ too (sdb1/sdc1).
* To watch movies, create empty directory on root of usb:
!network

== Bricked TV ==
* ''''''WARNING - Do not type ''reboot'' in console - it was the reason on few bricked TVs.'''

=== '''ExLink cable available''' ===
==== Screen is blank ====
If your start.sh has been written with errors, TV does not boot properly... 
* Unplug TV and wait 30 sec. Plug to AC, power on TV.
This should remove /mtd_rwarea/start.sh. If that did not help, try:
* Connect [[Ex-Link Cable for C-Series]], switch to debug mode:
10041004
enter:
31337 (removes /mtd_rwarea/start.sh)
or:
666 (removes /mtd_rwarea/start.sh, /mtd_rwarea/usb_mount, /mtd_rwarea/network_opt)
or:
44337794 (check file to know better what it does /mtd_rwarea/network_opt/sbin/44337794)

==== No reaction to USB, no telnet, but screen is on ====
* create empty file named '''kill_start.sh''' on root of USB
* power off TV
* attach USB and power on TV
/mtd_rwarea/start.sh should be deleted

If no success, then:
==== format /mtd_rwarea/ ====
If you do not have success or script finishes with error,
or you have hacked over Widget and it stopped working (on latest firmwares),
Format /mtd_rwarea over ExLink and get "virgin" TV back:
* Make [[Ex-Link Cable for C-Series]] attach to TV.
* Power off TV.
* Unplug network and antenna cable. Leave only ExLink and power cable plugged.
* Power on TV.
* Open terminal and connect to TV over ExLink.
* Apply these commands (followed by Enter):
10041004
81588
20089999
2
0
0
2 (advanced)
2 (DeviceManager Debug)
90 (DeviceManager MW Debug)
12 (DLNA, FLASH, ODD, HDD, MoIP Test)
11 (FLASH, HDD Format Test)
10 (or another, /mtd_rwarea/ partition number (14)

::On the last line you have to enter number of your /mtd_rwarea/. On C550 it is 10, but on other TV it can be other (e.g. 14)
::Try to hack TV again starting from step 7.

=== '''no ExLink cable available''' ===

* Create script on USB '''emergency_start.sh''' (kill_start.sh is to delete)
* Attach USB to TV on stand-by mode and power it on
* TV executes this script on boot.
Factory reset on ServiceMenu. This operation should delete ''/mtd_rwarea/network_opt''
*Hack TV with universal USB disk again

== FAQ ==
To be updated...

== Tested and works on TV ==
* LE32C530 [T-MSX5DEUC-2007.4]
* LE32C550J1W [T-MSX5DEUC-2005.4]
* LE32C550J1WU [T-MSX5DEUC-2007.4]
* LE32C550J1WX [T-MSX5DEUC-2005.4]
* LE37C630 [T-MSX6DEUC 1002.1] 
* LE40C650L1WX [T-VALDEUC-2002]
* LE40C550 [T-MSX5DEUC-2003.1]
* LE40C750 [T-VALDEUC 3007.1]
* PN58C7000 [T-VALAUSC 001035] - some [http://forum.samygo.tv/viewtopic.php?f=13&t=974&p=13650#p13642 modification] of hack is needed.
* PS50C550 [T-TDT5DEUC]
* UE32C5100QW [T-MSX5DEUC-2007.4]
* UE32C5000QW [T-TDT5DEUC-1022.0 ]
* UE40C8700 [T-VALDEUC-'''3006.2''']
* UE40C8700 [T-VALDEUC '''3007.1''']
* UE40C6700 [T-VALDEUC '''3007.1''']
* UE46C6105 [T-MSX5DEUC-2005.4]
* UE55C7700 [T-VALDEUC '''3006.1''']
* UE55C8705 [T-VALDEUC '''3007.1''']
::To be updated... 
 
Author and developer of universal USB hack disk - Perforator from forum.ixbt.com (He made the first hack for C series TV also). 
 
 
--[[User:Juzis28|Juzis28]] 12:13, 11 March 2011 (UTC)

Hacking TV over Hotel mode (most C series models)

2011-04-09T16:52:00Z

Stefanth: /* Tested and works on TV */

'''Universal USB disk to hack C series TV'''

''''''WARNING - Do not type ''reboot'' in console - it was the reason on few bricked TVs.'''

After hack your TV you can connect to TV via Telnet, you get CIFS (Samba) and NFS support, FTP Server, WebUI, crond, ... 
Moreover, if you attach USB with script file "SamyGO.sh", it will be executed. 
This hack has unificated structure for comfortable script execution for developers (read below).
 
==Safety measures for C series TVs==
Make some important settings before start hacking TV:
* In service menu, '''enable Debug mode''' for the RS232 port.
::With TV switched off, press the following sequence on the remote: '''[INFO] [MENU] [MUTE] [POWER]'''
::Enter the '''Control''' menu and set the value of the '''RS232 mode''' to '''Debug'''.
::Once you're back to the main Service menu, you will have to power off the TV for normal operation.
::Notice that your TV will reset RS232 mode back to UART when you install another firmware (no matter if it's older or newer).
* Have a working '''[[Ex-Link Cable for C-Series]]''' at hand. (desirable)
::If you don't feel capable of soldering such a cable, you can find and buy a cheap (under '''$5''') '''[http://shop.ebay.com/i.html?_trkparms=65%253A12%257C66%253A2%257C39%253A1%257C72%253A4030&rt=nc&_nkw=usb+ttl&_sticky=1&_trksid=p3286.c0.m14&_sop=15&_sc=1 USB to TTL adapter]''' at eBay.

== Supported TV models ==
TV model is not important, you should check your firmware. 
* This hack '''works''' on all firmware versions (even latest firmwares):
T-TDT5DEUC
T-MSX5DEUC
T-MSX6DEUC
T-VALDEUC
T-VALAUSC (modification of hack needed)
* Hack '''does not''' work on TV with '''T-VAL6DEUC''' firmware.

== Preparation ==
1. USB > 1GB space (Windows users can use FAT32 formatted USB) 
2. TV in normal mode. Export channels from TV to clean FAT32 USB 
3. Activate Hotel Mode
[Mute] [1] [1] [9] [Enter]
set to '''on''' by pressing [left]
4. Export settings from TV to the same FAT32 USB ("Clone TV to USB") 
5. Unplug USB stick from TV and save files you get anywhere on PC 
6. Download [http://download.samygo.tv/C%20Series/HotelMode%20hack/network_opt_18.02.2011_1.zip network_opt_18.02.2011_1.zip], extract archive. You get 1GB file '''network_opt_18.02.2011_sda2.img''' 
*'''IMPORTANT:''' This is the 3rd version of the USB image, updated on 18.2.2011. 
::If you have hacked TV with the earlier version or over widget and you want have benefits of this hack, 
::you should [http://wiki.samygo.tv/index.php?title=Hacking_TV_over_Hotel_mode_%28most_C_series_models%29#TV_is_already_hacked re-hack TV].[[File:Win32diskimage_howto.png |right]] 
7. Make USB from this image with help of included win32diskimager
* After win32diskimager finishes, you get two partitions on USB: one FAT32, accessible under Windows and a second, ext3 - not accessible under Windows. 
* You '''do not need''' to do any changes on ext3 partition. 
* '''All operations have to be done on the FAT32 partition, no linux needed.'''
 

== Installation. What to do if... ==
 
=== '''TV is not hacked''' ===
8. Attach Universal hack USB you made to PC. Copy channel settings file (you made in normal mode) to root of USB. 
9. Rename file (channel_list_LE32C550_1001.scm for C550) to zip
channel_list_LE32C550_1001.scm.zip
10. Add directory ''usb_mount'' with empty file in it (e.g. ''1.txt;'' - very important) to archive 
11. Rename back to channel_list_LE32C550_1001.scm
* You get files inside of archive:
Archive: channel_list_LE32C550_1001.scm
Length Date Time Name
--------- ---------- ----- ----
68 2038-01-19 06:14 CloneInfo
96 2038-01-19 06:14 FineTune_Digital
40000 2038-01-19 06:14 map-AirA
292000 2038-01-19 06:14 map-AirD
40000 2038-01-19 06:14 map-CableA
292000 2038-01-19 06:14 map-CableD
4 2038-01-19 06:14 map-ChKey
720 2038-01-19 06:14 RadioMap
0 2010-11-30 21:55 usb_mount/
8 2010-11-30 21:55 usb_mount/1.txt
--------- -------
664896 10 files
12. Copy files exported in Hotel mode (only files, without directories) to '''/HotelMode''' directory on USB
* Exported in HotelMode files to copy:
./T-MSX5DEUC/Clone:

drwxr-xr-x 2 root root 4096 2010-12-27 18:39 .
drwxr-xr-x 3 root root 4096 2010-12-27 18:39 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat

13. Exit from Hotel mode:
Mute-1-1-9-Enter
set to '''off'''
* Hotel Mode → Off
14. Attach USB to TV and import channel settings to TV. Everything must work without errors. 
15. Activate Hotel mode again.
Mute-1-1-9-Enter
set to '''on''' by pressing "left"
16. Import HotelMode settings you exported before (as is, with directories) ("Clone USB to TV") 
17. Press OK. 
18. TV restarts few times and starts in ''black screen''. DO NOT POWER OFF, DO NOT DISCONNECT USB! 
* '''Wait 3 minutes'''. After three minutes you can switch off TV.
* Switch on TV again
* Try connect to TV over Telnet (Port 23).
* If you get to console, congratulations.
* TV starts in Hotel mode. If you have your channel settings, you can deactivate hotel mode from service menu.
19. If you haven't got your channels back and if you can't Telnet to TV, it means something went wrong.
* Look for file ''first_run.ok'' and content of directory ''/result'' on USB
20. If you have Telnet after hack, execute:
cp $OPT_DIR/usr/restore/start.sh /mtd_rwarea/start.sh
21. Done.

=== '''TV is already hacked''' ===
(Over Hotel Mode or Widget - doesn`t matter)
* Make USB (steps 6. and 7.)
* Do not change anything
* Attach to TV and connect via SSH/Telnet
* Find your usb:
df -h | grep "/dtv/usb/sd"
* execute script '''first_run.sh''' with parameter of path to USB.
::e.g. if path to USB is '''/dtv/usb/sda1''', then command to enter is:
sh +x /dtv/usb/sda1/first_run.sh /dtv/usb/sda1
Path might be different on your TV, for example:
::/dtv/usb/sdb1/first_run.sh /dtv/usb/sdb1
::/dtv/usb/sdc1/first_run.sh /dtv/usb/sdc1
Check exact path over Telnet before you start.
* Wait until you get the message "Installation Completed!", but '''do not reboot TV 3 minutes''' (TV is making some dumps in this time, do not interrupt it.)
* Reboot TV (switch off, wait, switch on again)
* Done

== Normal operating of hacked TV ==
* To get access to TV (Telnet/FTP/WebUI) you must attach the same USB-stick that you created for this hack '''or''' prepare USB-stick with the latest [http://download.samygo.tv/C%20Series/ SamyGO-Extensions]. (If you need to know your CPU type enter '''cat /proc/cpuinfo''' into console.)

* Example for mounting a NFS-share manually:
cd /dtv/usb/sda1
mkdir videos
/bin/mount -o nolock 192.168.1.123:/videos /dtv/usb/sda1/videos -t nfs
Change IP to your NFS-server IP, path to USB might differ too (sdb1/sdc1).
* To watch movies, create empty directory on root of usb:
!network

== Bricked TV ==
* ''''''WARNING - Do not type ''reboot'' in console - it was the reason on few bricked TVs.'''

=== '''ExLink cable available''' ===
==== Screen is blank ====
If your start.sh has been written with errors, TV does not boot properly... 
* Unplug TV and wait 30 sec. Plug to AC, power on TV.
This should remove /mtd_rwarea/start.sh. If that did not help, try:
* Connect [[Ex-Link Cable for C-Series]], switch to debug mode:
10041004
enter:
31337 (removes /mtd_rwarea/start.sh)
or:
666 (removes /mtd_rwarea/start.sh, /mtd_rwarea/usb_mount, /mtd_rwarea/network_opt)
or:
44337794 (check file to know better what it does /mtd_rwarea/network_opt/sbin/44337794)

==== No reaction to USB, no telnet, but screen is on ====
* create empty file named '''kill_start.sh''' on root of USB
* power off TV
* attach USB and power on TV
/mtd_rwarea/start.sh should be deleted

If no success, then:
==== format /mtd_rwarea/ ====
If you do not have success or script finishes with error,
or you have hacked over Widget and it stopped working (on latest firmwares),
Format /mtd_rwarea over ExLink and get "virgin" TV back:
* Make [[Ex-Link Cable for C-Series]] attach to TV.
* Power off TV.
* Unplug network and antenna cable. Leave only ExLink and power cable plugged.
* Power on TV.
* Open terminal and connect to TV over ExLink.
* Apply these commands (followed by Enter):
10041004
81588
20089999
2
0
0
2 (advanced)
2 (DeviceManager Debug)
90 (DeviceManager MW Debug)
12 (DLNA, FLASH, ODD, HDD, MoIP Test)
11 (FLASH, HDD Format Test)
10 (or another, /mtd_rwarea/ partition number (14)

::On the last line you have to enter number of your /mtd_rwarea/. On C550 it is 10, but on other TV it can be other (e.g. 14)
::Try to hack TV again starting from step 7.

=== '''no ExLink cable available''' ===

* Create script on USB '''emergency_start.sh''' (kill_start.sh is to delete)
* Attach USB to TV on stand-by mode and power it on
* TV executes this script on boot.
Factory reset on ServiceMenu. This operation should delete ''/mtd_rwarea/network_opt''
*Hack TV with universal USB disk again

== FAQ ==
To be updated...

== Tested and works on TV ==
* LE32C530 [T-MSX5DEUC-2007.4]
* LE32C550J1W [T-MSX5DEUC-2005.4]
* LE32C550J1WU [T-MSX5DEUC-2007.4]
* LE32C550J1WX [T-MSX5DEUC-2005.4]
* LE37C630 [T-MSX6DEUC 1002.1] 
* LE40C650L1WX [T-VALDEUC-2002]
* LE40C550 [T-MSX5DEUC-2003.1]
* LE40C750 [T-VALDEUC 3007.1]
* PN58C7000 [T-VALAUSC 001035] - some [http://forum.samygo.tv/viewtopic.php?f=13&t=974&
* PS50C550 [T-TDT5DEUC]
* UE32C5100QW [T-MSX5DEUC-2007.4]
* UE32C5000QW [T-TDT5DEUC-1022.0 ]
* UE40C8700 [T-VALDEUC-'''3006.2''']
* UE40C8700 [T-VALDEUC '''3007.1''']
* UE40C6700 [T-VALDEUC '''3007.1''']
* UE46C6105 [T-MSX5DEUC-2005.4]
* UE55C7700 [T-VALDEUC '''3006.1''']
p=13650#p13642 modification] of hack is needed.
* UE55C8705 [T-VALDEUC '''3007.1''']
::To be updated... 
 
Author and developer of universal USB hack disk - Perforator from forum.ixbt.com (He made the first hack for C series TV also). 
 
 
--[[User:Juzis28|Juzis28]] 12:13, 11 March 2011 (UTC)

SamyGO ChanEdit - Chanel Editor

2011-04-09T14:05:22Z

Stefanth: /* Microsoft Windows */

=SamyGO ChanEdit=

With SamyGO ChanEdit you can edit your channel list of your Samsung TV Set using any Computer able to run a Java VM supporting SWT. This makes moving channels around a lot easier. Also the list can be extended by channels that are not found by the channel search engine. For example Sky.de interactive channels, which the editor can add automatically when a list containing Sky.de channels is loaded.

==Channel Import/Export Menu==
First you have to connect a USB drive with a FAT/FAT32 filesystem to your TV.

When the TV is switched ON press '''Volume Down''' [[File:Volume_down_key.png|30px]] once and then press '''the Enter [[File:Enter_key.png|30pxâ]] button for 10 seconds'''. This will display the "Channel Import / Export" Menu.

If this doesn't work, check that "Speaker Select" in "Sound Menu" is set to "TV Speaker". Anynet+ (HDMI-CEC) should be disabled.
[[File:Channel_Import_Export.png|300px|left|thumb|Channel Import / Export]]
 
Choose '''USB to TV''' for channeldata import or '''TV to USB''' for copying the channeldata to the USB drive.

When everything worked correct you'll find the following data on your USB drive:

kilroy@kilroy:~$ ls -la /media/USB2GB/T-CHLCIPDEUC/Clone/
total 744
drwx------ 2 kilroy kilroy 4096 1980-01-01 00:00 .
drwx------ 3 kilroy kilroy 4096 1980-01-01 00:00 ..
-rwxr-xr-x 1 kilroy kilroy 1920 1980-01-01 00:00 Clone.dat
-rwxr-xr-x 1 kilroy kilroy 20 1980-01-01 00:00 FineTune
-rwxr-xr-x 1 kilroy kilroy 1092 1980-01-01 00:00 FineTune_Digital
-rwxr-xr-x 1 kilroy kilroy 124 1980-01-01 00:00 LNBSettingsDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-AirA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-AirD
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-CableA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-CableD
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 map-ChKey
-rwxr-xr-x 1 kilroy kilroy 144000 1980-01-01 00:00 map-SateD
-rwxr-xr-x 1 kilroy kilroy 3184 1980-01-01 00:00 PTCCABLE
-rwxr-xr-x 1 kilroy kilroy 584 1980-01-01 00:00 SatDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 5616 1980-01-01 00:00 ServiceProviders
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 TransponderDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 88 1980-01-01 00:00 TSIDList
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 UserTransponderDataBase.dat

Now you can edit the channel list (for the moment only map-CableD for DVB-C) stored on the drive using SamyGO ChanEdit.

After that just use the same procedure to import the list again.

=== UE46C5105 (and probably other TV's from the C serie) ===
This TV have a slight different menu system than above described.

The "save to USB stick" is in the channel sub meny under "Antenna".

Also, Samsung does not save the channel files in a directory any more but instead all channel files are saved in one single file with the ending .scm

This scm file is an ordinary zip file so to unpack it the file have either to be "dropped" on WinZip (Windows) or feed to unzip.
Another way is to rename the file so it ends with .zip instead of .scm and then open it with WinZip or feed to unzip.

The unpacking of the file recreates the above described file structure.

After the edition is done, zip together the content and rename it to .scm again.

Added by [[User:Stefanth|Stefanth]]

==Downloading and Installing==
Download the SamyGO ChanEdit (and required Java library for you OS) from [http://download.samygo.tv/SamyGO%20Applications/ SamyGO Applications] file download area.

===Ubuntu 9.10 amd64===

You have to download the files '''SamyGO ChanEdit-v0.31.tar.bz2''' and '''SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2''' 
Ubuntu 9.10 is comes with openjdk-6-jre but you can also install Java from SUN (recommended).

# sudo aptitude install sun-java6-jre
[ -d ~/bin ] || mkdir ~/bin
tar xjf Downloads/SamyGO\ ChanEdit-v0.31.tar.bz2 -C ~/bin/
tar xjf Downloads/SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2 -C ~/bin/SamyGO\ ChanEdit-v0.31/
ln -s ~/bin/SamyGO\ ChanEdit-v0.31/SamyGoChanEd.jar Desktop/SamyGoChanEd.jar

Right click at the SamyGoChanEd.jar icon and select '''Properties -> Open With:''' ''OpenJDK Java 6 Runtime'' (or ''Sun Java 6 Runtime'')

===Microsoft Windows===
To execute the channel editor you need two parts, the channel editor program itself and a support library called swt.
The channel editor program can be found here [http://download.samygo.tv/SamyGO%20PC%20Applications SamyGO ChanEdit]

The SWT library can either be downloaded directly from [http://www.eclipse.org/swt http://www.eclipse.org/swt] or from [http://download.samygo.tv/SamyGO%20PC%20Applications/SamyGO%20ChanEdit%20SWT%20Libraries SamyGo]. For 64 bit swt library, you can check it out [https://jira.vuze.com/browse/SUP-19 this page].

Unpack the downloaded files and place the both .jar files,SamyGoChanEd.jar and swt.jar, in the same director.
These two jar files are the only files needed, there are other files and content in the downloaded zip/gz/bz2 files but they are not needed

Open a command prompt and enter

'''<tt>java -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

The following example is on a Windows 7 installation, the java.exe file might be in a different place depending on the installation and operating system.
If you get an error message saying that java is not a commando then you need to give the full path to the Java engine, like this

'''<tt>"c:\Program Files (x86)\Java\jdk1.6.0_23\bin\java.exe" -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

Of course it is possible to create a link on the desktop and execute the same command line.

NOTE (Added 2011-04-09):
There is another channel editor program here http://www.file-upload.net/download-2749294/chlpced-0.72-release.zip.html
It is not a java program but an executable, it also read the .scm file directly, no need to unpack the file.

Added by [[User:Stefanth|Stefanth]]

==Modifying Channel List==
You can modify your Channel list via SamyGO ChanEdit.

The files are under your USB at T-CHxxDEUC/Clone directory.
With Version 0.31 currently only map-CableD for digital Cable Channels is editable.

<center>[[File:SamyGO ChanEdit.png]]</center>

Afterwards you can import the channel list to TV from the USB stick.

SamyGO ChanEdit - Chanel Editor

2011-04-09T13:53:50Z

Stefanth: /* Microsoft Windows */

=SamyGO ChanEdit=

With SamyGO ChanEdit you can edit your channel list of your Samsung TV Set using any Computer able to run a Java VM supporting SWT. This makes moving channels around a lot easier. Also the list can be extended by channels that are not found by the channel search engine. For example Sky.de interactive channels, which the editor can add automatically when a list containing Sky.de channels is loaded.

==Channel Import/Export Menu==
First you have to connect a USB drive with a FAT/FAT32 filesystem to your TV.

When the TV is switched ON press '''Volume Down''' [[File:Volume_down_key.png|30px]] once and then press '''the Enter [[File:Enter_key.png|30pxâ]] button for 10 seconds'''. This will display the "Channel Import / Export" Menu.

If this doesn't work, check that "Speaker Select" in "Sound Menu" is set to "TV Speaker". Anynet+ (HDMI-CEC) should be disabled.
[[File:Channel_Import_Export.png|300px|left|thumb|Channel Import / Export]]
 
Choose '''USB to TV''' for channeldata import or '''TV to USB''' for copying the channeldata to the USB drive.

When everything worked correct you'll find the following data on your USB drive:

kilroy@kilroy:~$ ls -la /media/USB2GB/T-CHLCIPDEUC/Clone/
total 744
drwx------ 2 kilroy kilroy 4096 1980-01-01 00:00 .
drwx------ 3 kilroy kilroy 4096 1980-01-01 00:00 ..
-rwxr-xr-x 1 kilroy kilroy 1920 1980-01-01 00:00 Clone.dat
-rwxr-xr-x 1 kilroy kilroy 20 1980-01-01 00:00 FineTune
-rwxr-xr-x 1 kilroy kilroy 1092 1980-01-01 00:00 FineTune_Digital
-rwxr-xr-x 1 kilroy kilroy 124 1980-01-01 00:00 LNBSettingsDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-AirA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-AirD
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-CableA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-CableD
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 map-ChKey
-rwxr-xr-x 1 kilroy kilroy 144000 1980-01-01 00:00 map-SateD
-rwxr-xr-x 1 kilroy kilroy 3184 1980-01-01 00:00 PTCCABLE
-rwxr-xr-x 1 kilroy kilroy 584 1980-01-01 00:00 SatDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 5616 1980-01-01 00:00 ServiceProviders
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 TransponderDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 88 1980-01-01 00:00 TSIDList
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 UserTransponderDataBase.dat

Now you can edit the channel list (for the moment only map-CableD for DVB-C) stored on the drive using SamyGO ChanEdit.

After that just use the same procedure to import the list again.

=== UE46C5105 (and probably other TV's from the C serie) ===
This TV have a slight different menu system than above described.

The "save to USB stick" is in the channel sub meny under "Antenna".

Also, Samsung does not save the channel files in a directory any more but instead all channel files are saved in one single file with the ending .scm

This scm file is an ordinary zip file so to unpack it the file have either to be "dropped" on WinZip (Windows) or feed to unzip.
Another way is to rename the file so it ends with .zip instead of .scm and then open it with WinZip or feed to unzip.

The unpacking of the file recreates the above described file structure.

After the edition is done, zip together the content and rename it to .scm again.

Added by [[User:Stefanth|Stefanth]]

==Downloading and Installing==
Download the SamyGO ChanEdit (and required Java library for you OS) from [http://download.samygo.tv/SamyGO%20Applications/ SamyGO Applications] file download area.

===Ubuntu 9.10 amd64===

You have to download the files '''SamyGO ChanEdit-v0.31.tar.bz2''' and '''SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2''' 
Ubuntu 9.10 is comes with openjdk-6-jre but you can also install Java from SUN (recommended).

# sudo aptitude install sun-java6-jre
[ -d ~/bin ] || mkdir ~/bin
tar xjf Downloads/SamyGO\ ChanEdit-v0.31.tar.bz2 -C ~/bin/
tar xjf Downloads/SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2 -C ~/bin/SamyGO\ ChanEdit-v0.31/
ln -s ~/bin/SamyGO\ ChanEdit-v0.31/SamyGoChanEd.jar Desktop/SamyGoChanEd.jar

Right click at the SamyGoChanEd.jar icon and select '''Properties -> Open With:''' ''OpenJDK Java 6 Runtime'' (or ''Sun Java 6 Runtime'')

===Microsoft Windows===
To execute the channel editor you need two parts, the channel editor program itself and a support library called swt.
The channel editor program can be found here [http://download.samygo.tv/SamyGO%20PC%20Applications SamyGO ChanEdit]

The SWT library can either be downloaded directly from [http://www.eclipse.org/swt http://www.eclipse.org/swt] or from [http://download.samygo.tv/SamyGO%20PC%20Applications/SamyGO%20ChanEdit%20SWT%20Libraries SamyGo]. For 64 bit swt library, you can check it out [https://jira.vuze.com/browse/SUP-19 this page].

Unpack the downloaded files and place the both .jar files,SamyGoChanEd.jar and swt.jar, in the same director.
These two jar files are the only files needed, there are other files and content in the downloaded zip/gz/bz2 files but they are not needed

Open a command prompt and enter

'''<tt>java -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

The following example is on a Windows 7 installation, the java.exe file might be in a different place depending on the installation and operating system.
If you get an error message saying that java is not a commando then you need to give the full path to the Java engine, like this

'''<tt>"c:\Program Files (x86)\Java\jdk1.6.0_23\bin\java.exe" -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

Of course it is possible to create a link on the desktop and execute the same command line.

NOTE (Added 2011-04-09):
There is another channel editor program here http://www.file-upload.net/download-2749294/chlpced-0.72-release.zip.html
It is not a java program but an executable

Added by [[User:Stefanth|Stefanth]]

==Modifying Channel List==
You can modify your Channel list via SamyGO ChanEdit.

The files are under your USB at T-CHxxDEUC/Clone directory.
With Version 0.31 currently only map-CableD for digital Cable Channels is editable.

<center>[[File:SamyGO ChanEdit.png]]</center>

Afterwards you can import the channel list to TV from the USB stick.

Enabling the PVR for C-Series

2011-01-26T07:21:43Z

Stefanth: /* Tested on those models */

This has been tested on LE40C650L1KXXU

Be very careful what you press on the remote whilst in service menu.

Move through menu list by pressing down or up arrow only.

only press right arrow to change an option.

NOTE: All user settings will be reset to default after this so write all your settings down on paper and reset them afterwards.

1. Put in a blank USB HDD/flash formatted to FAT32.
UPDATE: This step is not necessary, it can be set up without a USB flashdisk.

2. Turn on TV, push on remote control: MUTE-1-1-9-ENTER, Hotel Mode menu appears (H1) set HOTEL MODE to ON (right arrow) and then turn off TV.

3. Whilst TV is off invoke service menu by pushing INFO-MENU-MUTE-POWER on remote control (If this doesn't work try MUTE-1-8-2-POWER). This will turn the TV on and show the Service Menu (S1).

4. In service menu move down to Control and select this (right arrow) - new menu appears (S2) - move down to Hotel Option and select this (right arrow) - new menu appears (S3) - move down to Clone TV to USB and select this (right arrow). TV then checks USB.
- Completed Successfully -select ok- enter.

H1 menu appears - press return.

S4 menu appears - move up to Sub Option category and select (right arrow).

new large menu appears (S5)

5. In this menu move down to PVR Support and set to ON (right arrow). (Move to PVR by pressing down button, no right!) This option now appears on its own on the TV screen, press return to go back to main menu again (S5)

5a. You can also set Gemstar Support to on if required for the GuidePlus EPG.

6. Press return to go back to previous menu (S4) and move down to Hotel Option and select this (right arrow). H1 menu appears then set Hotel Mode to OFF (right arrow) and power off your tv.

7. Turn tv on normally. PVR is now enabled

If you now press record or pause whilst watching live TV the TV will ask to format the USB drive. If this is done successfully the PVR function should now work and you enter timeshift mode and begin to record to the USB.

In media player mode there is a new "TV Recordings" category. You can select this to access your recordings and there are management functions in the tools menu.

In the EPG when you press info on a tv program you should now have the option to record it. and a red clock icon appears next to the program.

If you enabled Gemstar (GuidePlus) you can access this by going into:- Menu/Antenna/Guide

If you go into Menu/Antenna/Channel Manager and then press the tools button you can access the "Timer Recording" where you can easily setup any time, channel, start and end time - like oldie VHS recorder.

== Tested on those models ==
* LE40C650L1KXXU
* UE46C5105 (PVR mode can be switched on in the menu but the TV is lacking the PVR software itself so the PVR functionality does not work)

[[User:Stefanth|Stefanth]] 07:21, 26 January 2011 (UTC)

Enabling the PVR for C-Series

2011-01-26T07:20:26Z

Stefanth:

This has been tested on LE40C650L1KXXU

Be very careful what you press on the remote whilst in service menu.

Move through menu list by pressing down or up arrow only.

only press right arrow to change an option.

NOTE: All user settings will be reset to default after this so write all your settings down on paper and reset them afterwards.

1. Put in a blank USB HDD/flash formatted to FAT32.
UPDATE: This step is not necessary, it can be set up without a USB flashdisk.

2. Turn on TV, push on remote control: MUTE-1-1-9-ENTER, Hotel Mode menu appears (H1) set HOTEL MODE to ON (right arrow) and then turn off TV.

3. Whilst TV is off invoke service menu by pushing INFO-MENU-MUTE-POWER on remote control (If this doesn't work try MUTE-1-8-2-POWER). This will turn the TV on and show the Service Menu (S1).

4. In service menu move down to Control and select this (right arrow) - new menu appears (S2) - move down to Hotel Option and select this (right arrow) - new menu appears (S3) - move down to Clone TV to USB and select this (right arrow). TV then checks USB.
- Completed Successfully -select ok- enter.

H1 menu appears - press return.

S4 menu appears - move up to Sub Option category and select (right arrow).

new large menu appears (S5)

5. In this menu move down to PVR Support and set to ON (right arrow). (Move to PVR by pressing down button, no right!) This option now appears on its own on the TV screen, press return to go back to main menu again (S5)

5a. You can also set Gemstar Support to on if required for the GuidePlus EPG.

6. Press return to go back to previous menu (S4) and move down to Hotel Option and select this (right arrow). H1 menu appears then set Hotel Mode to OFF (right arrow) and power off your tv.

7. Turn tv on normally. PVR is now enabled

If you now press record or pause whilst watching live TV the TV will ask to format the USB drive. If this is done successfully the PVR function should now work and you enter timeshift mode and begin to record to the USB.

In media player mode there is a new "TV Recordings" category. You can select this to access your recordings and there are management functions in the tools menu.

In the EPG when you press info on a tv program you should now have the option to record it. and a red clock icon appears next to the program.

If you enabled Gemstar (GuidePlus) you can access this by going into:- Menu/Antenna/Guide

If you go into Menu/Antenna/Channel Manager and then press the tools button you can access the "Timer Recording" where you can easily setup any time, channel, start and end time - like oldie VHS recorder.

== Tested on those models ==
* LE40C650L1KXXU
* UE46C5105 (PVR mode can be switched on but the TV is lacking the PVR software)

[[User:Stefanth|Stefanth]] 07:20, 26 January 2011 (UTC)

Hacking TV over Hotel mode (most C series models)

2011-01-20T19:05:47Z

Stefanth: /* If you have linux and TV is not hacked */

Universal USB disk to hack C series TV. It should work on any C series TV with export settings to ext3 USB support. Some models does not support ext3 file system for settings export (C6000/C630...firmwares with T-VAL6DEUC)
Tested and works on models with T-MSX5DEUC, T-TDT5DEUC and T-VALDEUC (until 5.1.2011).

After this hack you can connect to TV over telnet, you get CIFS (samba) and NFS support.
Moreover, if you attach USB with script file "SamyGO.sh", it will executed.

This hack has unificated structure for comfortable script execution for developers (read below)

Author and developer - Perforator from forum.ixbt.com (He made the first hack for C series TV also).

'''IMPORTANT''': Until further notice, '''don't try this hack on a TV without Ethernet port''' (like C530).
Read the [http://forum.samygo.tv/viewforum.php?f=13 C series forum] for additional information and try [http://forum.samygo.tv/viewtopic.php?f=13&t=1076 the original juuso hack].

== To Do ==
* NFS automounts
* php script for administer TV over http
* implementations of easy installation/uninstallation of scripts

== Preparation ==
Only for USB, recognised as '''sda'''. 
How to check. Read this [http://forum.samygo.tv/viewtopic.php?f=13&t=1076&start=40#p10979 post]. Later limitation will be removed. 
1. USB > 1GB space. (windows user can use Fat32 formatted USB) 
2. TV in normal mode. Export channels from TV to USB 
3. Activate Hotel Mode
Mute-1-1-9-Enter
set to '''on''' by pressing "left"
4. Export settings from TV to USB 
5. Save files you get anywhere in PC 
6 Download [http://www.multiupload.com/UYW99RK4FG file], extract from archive. You get 1Gb file ''network_opt_28.12.2010_3_sda.img'' 
7 Make USB from this image. 
* Under windows you can use [http://launchpad.net/win32-image-writer/+download win32diskimager].
* After win32diskimager finishes, USB is not accessible under Windows, because it is ext3 format.

== Hack TV==
===If you have linux and TV is not hacked===
8. Attach USB you made to linux PC. Copy channel settings file (you made in normal mode) to root of USB

9. Rename file (channel_list_LE32C550_1001.scm for C550) to zip
channel_list_LE32C550_1001.scm.zip
10. Add directory ''usb_mount'' with empty file in it (e.g. ''1.txt;'' - very important) to archive 
11. Rename back to channel_list_LE32C550_1001.scm
* You get files inside of archive:
Archive: channel_list_LE32C550_1001.scm
Length Date Time Name
--------- ---------- ----- ----
68 2038-01-19 06:14 CloneInfo
96 2038-01-19 06:14 FineTune_Digital
40000 2038-01-19 06:14 map-AirA
292000 2038-01-19 06:14 map-AirD
40000 2038-01-19 06:14 map-CableA
292000 2038-01-19 06:14 map-CableD
4 2038-01-19 06:14 map-ChKey
720 2038-01-19 06:14 RadioMap
0 2010-11-30 21:55 usb_mount/
8 2010-11-30 21:55 usb_mount/1.txt
--------- -------
664896 10 files
12. Copy files exported in Hotel mode (only files, without directories) to /restore directory on USB
* Exported in HotelMode files to copy:
./T-MSX5DEUC/Clone:

drwxr-xr-x 2 root root 4096 2010-12-27 18:39 .
drwxr-xr-x 3 root root 4096 2010-12-27 18:39 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat
* You should get structure on USB/restore:
./restore:

drwxrwxrwx 2 root root 4096 2010-12-27 21:47 .
drwx------ 10 root root 4096 2010-12-27 20:14 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat
* Whole USB structure you have to get:
./:

drwx------ 10 perforator perforator 4096 2010-12-27 21:57 .
drwxr-xr-x 4 root root 4096 2010-12-27 21:35 ..
-rwxrwxrwx 1 root root 23443 2010-12-23 13:55 channel_list_LE32C550_1001.scm
-rwxrwxrwx 1 perforator root 4635 2010-12-27 16:08 first_run.sh
drwxrwsrwx 2 root root 4096 2010-12-23 14:50 link0_Clone
lrwxrwxrwx 1 root root 29 2010-12-27 20:14 link0_Temp -> /mtd_rwarea/usb_mount/usb_cmd
drwxrwsrwx 2 root root 4096 2010-12-23 14:50 link1_Clone
lrwxrwxrwx 1 root root 31 2010-12-27 20:14 link1_Temp -> /mtd_rwarea/usb_mount/usb_mount
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 modules
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 opt
drwxrwxrwx 2 root root 4096 2010-12-27 21:47 restore
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 T-MSX5DEUC
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 T-TDT5DEUC
drwxrwxrwx 3 root root 4096 2010-12-24 00:10 T-VALDEUC

./link0_Clone:

drwxrwsrwx 2 root root 4096 2010-12-23 14:50 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..

./link1_Clone:

drwxrwsrwx 2 root root 4096 2010-12-23 14:50 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..

./modules:

drwxrwxrwx 5 root root 4096 2010-12-24 03:32 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 T-MSX5DEUC
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 T-TDT5DEUC
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 T-VALDEUC

./modules/T-MSX5DEUC:

drwxrwsrwx 5 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwxrwx 3 root root 4096 2010-12-27 14:06 etc
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 lib
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-MSX5DEUC/etc:

drwxrwxrwx 3 root root 4096 2010-12-27 14:06 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 3 root root 4096 2010-12-27 14:07 init.d

./modules/T-MSX5DEUC/etc/init.d:

drwxrwxrwx 3 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:06 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 startup_run_once

./modules/T-MSX5DEUC/etc/init.d/startup_run_once:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:07 ..
-rwxrwxrwx 1 root root 240 2010-12-27 01:38 0_20_insmod.init

./modules/T-MSX5DEUC/lib:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 2 root root 4096 1970-01-01 03:02 modules

./modules/T-MSX5DEUC/lib/modules:

drwxrwxrwx 2 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
-rwxrwxrwx 1 root root 405132 1970-01-01 03:02 cifs.ko
-rwxrwxrwx 1 root root 136636 1970-01-01 03:02 lockd.ko
-rwxrwxrwx 1 root root 290572 1970-01-01 03:02 nfs.ko
-rwxrwxrwx 1 root root 342380 1970-01-01 03:02 sunrpc.ko

./modules/T-MSX5DEUC/usr:

drwxrwxrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 bin
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 sbin

./modules/T-MSX5DEUC/usr/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 1625796 1970-01-01 03:02 busybox

./modules/T-MSX5DEUC/usr/sbin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 138 1970-01-01 03:02 platform.sh

./modules/T-TDT5DEUC:

drwxrwsrwx 5 root root 4096 2010-12-24 04:17 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 etc
drwxrwsrwx 3 root root 4096 2010-12-25 18:36 lib
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-TDT5DEUC/etc:

drwxrwsrwx 3 root root 4096 2010-12-24 03:46 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 init.d

./modules/T-TDT5DEUC/etc/init.d:

drwxrwsrwx 3 root root 4096 2010-12-24 03:47 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 ..
drwxrwsrwx 2 root root 4096 2010-12-24 17:39 startup_run_once

./modules/T-TDT5DEUC/etc/init.d/startup_run_once:

drwxrwsrwx 2 root root 4096 2010-12-24 17:39 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 ..
-rwxrwxrwx 1 root root 240 2010-12-27 01:38 0_20_insmod.init

./modules/T-TDT5DEUC/lib:

drwxrwsrwx 3 root root 4096 2010-12-25 18:36 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 2 root root 4096 2010-12-24 04:19 modules

./modules/T-TDT5DEUC/lib/modules:

drwxrwsrwx 2 root root 4096 2010-12-24 04:19 .
drwxrwsrwx 3 root root 4096 2010-12-25 18:36 ..
-rwxrwxrwx 1 root root 62972 2010-12-11 00:00 auth_rpcgss.ko
-rwxrwxrwx 1 root root 399356 2010-12-11 00:00 cifs.ko
-rwxrwxrwx 1 root root 41076 1980-01-01 00:00 isofs.ko
-rwxrwxrwx 1 root root 106436 2010-12-11 00:00 lockd.ko
-rwxrwxrwx 1 root root 405780 2010-12-11 00:00 nfs.ko
-rwxrwxrwx 1 root root 15080 2010-12-11 00:00 rpcsec_gss_krb5.ko
-rwxrwxrwx 1 root root 105104 2010-12-11 00:00 smbfs.ko
-rwxrwxrwx 1 root root 240652 2010-12-11 00:00 sunrpc.ko
-rwxrwxrwx 1 root root 127728 1980-01-01 00:00 udf.ko

./modules/T-TDT5DEUC/usr:

drwxrwsrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 2 root root 4096 2010-12-25 18:36 bin
drwxrwsrwx 2 root root 4096 2010-12-27 14:10 sbin

./modules/T-TDT5DEUC/usr/bin:

drwxrwsrwx 2 root root 4096 2010-12-25 18:36 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 1694608 1980-01-01 00:00 busybox

./modules/T-TDT5DEUC/usr/sbin:
Ð¸ÑÐ¾Ð³Ð¾ 12
drwxrwsrwx 2 root root 4096 2010-12-27 14:10 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 perforator root 138 2010-12-24 17:40 platform.sh

./modules/T-VALDEUC:

drwxrwxrwx 5 root root 4096 2010-12-24 04:18 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 etc
drwxrwsrwx 3 root root 4096 2010-12-25 18:37 lib
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-VALDEUC/etc:

drwxrwsrwx 3 root root 4096 2010-12-24 03:46 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 init.d

./modules/T-VALDEUC/etc/init.d:

drwxrwsrwx 3 root root 4096 2010-12-24 03:47 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 ..
drwxrwsrwx 2 root root 4096 2010-12-27 14:11 startup_run_once

./modules/T-VALDEUC/etc/init.d/startup_run_once:

drwxrwsrwx 2 root root 4096 2010-12-27 14:11 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 ..
-rwxrwxrwx 1 root root 130 2010-12-27 14:11 0_20_insmod.init

./modules/T-VALDEUC/lib:

drwxrwsrwx 3 root root 4096 2010-12-25 18:37 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 2 root root 4096 2010-12-24 04:20 modules

./modules/T-VALDEUC/lib/modules:

drwxrwsrwx 2 root root 4096 2010-12-24 04:20 .
drwxrwsrwx 3 root root 4096 2010-12-25 18:37 ..
-rwxrwxrwx 1 root root 274304 2010-12-03 22:39 cifs.ko

./modules/T-VALDEUC/usr:

drwxrwsrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 2 root root 4096 2010-12-25 18:37 bin
drwxrwsrwx 2 root root 4096 2010-12-24 17:41 sbin

./modules/T-VALDEUC/usr/bin:

drwxrwsrwx 2 root root 4096 2010-12-25 18:37 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 904544 2010-10-29 01:27 busybox

./modules/T-VALDEUC/usr/sbin:

drwxrwsrwx 2 root root 4096 2010-12-24 17:41 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 perforator root 138 2010-12-24 17:41 platform.sh

./opt:

drwxrwxrwx 8 root root 4096 2010-12-27 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:04 bin
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 etc
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 lib
drwxrwxrwx 2 root root 4096 2010-12-27 01:53 sbin
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 usr
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 var

./opt/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:04 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..

./opt/etc:

drwxrwxrwx 4 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 init.d
drwxrwxrwx 2 root root 4096 2010-12-27 02:16 init.d-disabled

./opt/etc/init.d:

drwxrwxrwx 5 root root 4096 2010-12-27 17:03 .
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 ..
drwxr-xr-x 2 root root 4096 1970-01-01 03:04 start.sh_before_nonblock
drwxrwxrwx 2 root root 4096 2010-12-27 17:10 startup_run_once
drwxrwxrwx 2 root root 4096 2010-12-27 01:37 usb_mount_after

./opt/etc/init.d/start.sh_before_nonblock:

drwxr-xr-x 2 root root 4096 1970-01-01 03:04 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxr-xr-x 1 root root 521 1970-01-01 03:04 0_01_restore_start.sh.init

./opt/etc/init.d/startup_run_once:

drwxrwxrwx 2 root root 4096 2010-12-27 17:10 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxrwxrwx 1 root root 1430 2010-12-27 01:38 0_00_0_emergency_start.init
-rwxrwxrwx 1 root root 422 2010-12-27 17:10 0_10_telnetd.init

./opt/etc/init.d/usb_mount_after:

drwxrwxrwx 2 root root 4096 2010-12-27 01:37 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxrwxrwx 1 root root 243 2010-12-27 01:37 0_00_usbSamyGO.sh.init

./opt/etc/init.d-disabled:

drwxrwxrwx 2 root root 4096 2010-12-27 02:16 .
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 ..

./opt/lib:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:05 modules

./opt/lib/modules:

drwxrwxrwx 2 root root 4096 2010-12-27 14:05 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..

./opt/sbin:

drwxrwxrwx 2 root root 4096 2010-12-27 01:53 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
-rwxrwxrwx 1 root root 192 2010-12-27 01:40 31337
-rwxrwxrwx 1 root root 652 2010-12-27 01:52 44337794
-rwxrwxrwx 1 root root 178 2010-12-27 01:40 666
-rwxrwxrwx 1 root root 591 2010-12-27 01:53 event.sh

./opt/usr:

drwxrwxrwx 5 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:05 bin
drwxrwxrwx 2 root root 4096 2010-12-27 17:02 restore
drwxrwxrwx 3 root root 4096 2010-12-27 14:08 sbin

./opt/usr/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:05 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..

./opt/usr/restore:

drwxrwxrwx 2 root root 4096 2010-12-27 17:02 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..
-rwxr-xr-x 1 root root 213 1970-01-01 03:04 9_9_kill_start.sh_ok.init
-rwxr-xr-x 1 root root 418 1970-01-01 03:04 start.sh

./opt/usr/sbin:

drwxrwxrwx 3 root root 4096 2010-12-27 14:08 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 2 root root 4096 2010-12-27 01:32 usb_mount

./opt/usr/sbin/usb_mount:

drwxrwxrwx 2 root root 4096 2010-12-27 01:32 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:08 ..
-rwxrwxrwx 1 root root 841 2010-12-27 01:32 opt_path
-rwxrwxrwx 1 root root 723 2010-12-27 01:30 unknownDev_cmd
-rwxrwxrwx 1 root root 161 1970-01-01 03:02 usb_cmd
-rwxrwxrwx 1 root root 166 1970-01-01 03:02 usb_moip_cmd
-rwxrwxrwx 1 root root 181 1970-01-01 03:02 usb_mount

./opt/var:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 spool

./opt/var/spool:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 cron

./opt/var/spool/cron:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 2 root root 4096 1970-01-01 03:02 crontabs

./opt/var/spool/cron/crontabs:

drwxrwxrwx 2 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..

./restore:

drwxrwxrwx 2 root root 4096 2010-12-27 21:47 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat

./T-MSX5DEUC:

drwxrwsrwx 3 root root 4096 2010-12-23 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 2 root root 4096 2010-12-27 15:50 Clone

./T-MSX5DEUC/Clone:

drwxrwsrwx 2 root root 4096 2010-12-27 15:50 .
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

./T-TDT5DEUC:

drwxrwsrwx 3 root root 4096 2010-12-23 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 2 root root 4096 2010-12-27 14:13 Clone

./T-TDT5DEUC/Clone:

drwxrwsrwx 2 root root 4096 2010-12-27 14:13 .
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

./T-VALDEUC:

drwxrwxrwx 3 root root 4096 2010-12-24 00:10 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:16 Clone

./T-VALDEUC/Clone:

drwxrwxrwx 2 root root 4096 2010-12-27 14:16 .
drwxrwxrwx 3 root root 4096 2010-12-24 00:10 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

13. Exit from Hotel mode:
* Go to ServiceMenu
Info - Menu - Mute - Power
* Hotel Mode ->Off
14. Attach USB to TV and import channel settings to TV. Everything must go w/o errors. 
15. Activate Hotel mode again
16. Import HotelMode settings you exported before (as is, with directories)

17. Press OK.

18. TV restarts twice and starts in ''black screen''. DO NOT POWER OFF, DO NOT DISCONNECT USB.
* Wait 3 minutes. After trhee minutes or if you get to console earlier you can reboot TV.
* Try connect to TV over telnet (port:23)
* If you get to console, congratulations.
* TV starts in Hotel mode. If you have your channel settings right, you can deactivate hotel mode from service menu.

19. If you haven`t got your channels back and if you can`t telnet to TV, it means - something went wrong
* Look for file ''first_run.ok'' and content of directory ''/result'' on USB
20. If you have telnet after hack, execute:
cp $OPT_DIR/usr/restore/start.sh /mtd_rwarea/start.sh

===Do not have linux and TV is not hacked===
== Normal operating of hacked TV ==
== Ways to unbrick TV ==
== FAQ ===
== Tested on those models ==
* LE 32-C550J1W [T-MSX5DEUC-2005.4]
* LE 40-C550 [T-MSX5DEUC-2003.1]
* LE 32-C530 [T-MSX5DEUC-2007.4]
* LE 32-C550J1WUA [T-MSX5DEUC-2007.4]
* LE 32-C550J1WXRU [T-MSX5DEUC-2005.4]
* UE 32-C5100QW [T-MSX5DEUC-2007.4]
* PS 50-C550 [T-TDT5DEUC]
* LE 40-C650L1WXXH [T-VALDEUC-2002]

TO be updated in few days

--[[User:Juzis28|Juzis28]] 20:21, 5 January 2011 (UTC)

Hacking TV over Hotel mode (most C series models)

2011-01-20T19:03:09Z

Stefanth: /* If you have linux and TV is not hacked */

Universal USB disk to hack C series TV. It should work on any C series TV with export settings to ext3 USB support. Some models does not support ext3 file system for settings export (C6000/C630...firmwares with T-VAL6DEUC)
Tested and works on models with T-MSX5DEUC, T-TDT5DEUC and T-VALDEUC (until 5.1.2011).

After this hack you can connect to TV over telnet, you get CIFS (samba) and NFS support.
Moreover, if you attach USB with script file "SamyGO.sh", it will executed.

This hack has unificated structure for comfortable script execution for developers (read below)

Author and developer - Perforator from forum.ixbt.com (He made the first hack for C series TV also).

'''IMPORTANT''': Until further notice, '''don't try this hack on a TV without Ethernet port''' (like C530).
Read the [http://forum.samygo.tv/viewforum.php?f=13 C series forum] for additional information and try [http://forum.samygo.tv/viewtopic.php?f=13&t=1076 the original juuso hack].

== To Do ==
* NFS automounts
* php script for administer TV over http
* implementations of easy installation/uninstallation of scripts

== Preparation ==
Only for USB, recognised as '''sda'''. 
How to check. Read this [http://forum.samygo.tv/viewtopic.php?f=13&t=1076&start=40#p10979 post]. Later limitation will be removed. 
1. USB > 1GB space. (windows user can use Fat32 formatted USB) 
2. TV in normal mode. Export channels from TV to USB 
3. Activate Hotel Mode
Mute-1-1-9-Enter
set to '''on''' by pressing "left"
4. Export settings from TV to USB 
5. Save files you get anywhere in PC 
6 Download [http://www.multiupload.com/UYW99RK4FG file], extract from archive. You get 1Gb file ''network_opt_28.12.2010_3_sda.img'' 
7 Make USB from this image. 
* Under windows you can use [http://launchpad.net/win32-image-writer/+download win32diskimager].
* After win32diskimager finishes, USB is not accessible under Windows, because it is ext3 format.

== Hack TV==
===If you have linux and TV is not hacked===
8. Attach USB you made to linux PC. Copy channel settings file (you made in normal mode) to root of USB

9. Rename file (channel_list_LE32C550_1001.scm for C550) to zip
channel_list_LE32C550_1001.scm.zip
10. Add directory ''usb_mount'' with empty file in it (e.g. ''1.txt;'' - very important) to archive 
11. Rename back to channel_list_LE32C550_1001.scm
* You get files inside of archive:
Archive: channel_list_LE32C550_1001.scm
Length Date Time Name
--------- ---------- ----- ----
68 2038-01-19 06:14 CloneInfo
96 2038-01-19 06:14 FineTune_Digital
40000 2038-01-19 06:14 map-AirA
292000 2038-01-19 06:14 map-AirD
40000 2038-01-19 06:14 map-CableA
292000 2038-01-19 06:14 map-CableD
4 2038-01-19 06:14 map-ChKey
720 2038-01-19 06:14 RadioMap
0 2010-11-30 21:55 usb_mount/
8 2010-11-30 21:55 usb_mount/1.txt
--------- -------
664896 10 files
12. Copy files exported in Hotel mode (only files, without directories) to /restore directory on USB
* Exported in HotelMode files to copy:
./T-MSX5DEUC/Clone:

drwxr-xr-x 2 root root 4096 2010-12-27 18:39 .
drwxr-xr-x 3 root root 4096 2010-12-27 18:39 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat
* You should get structure on USB/restore:
./restore:

drwxrwxrwx 2 root root 4096 2010-12-27 21:47 .
drwx------ 10 root root 4096 2010-12-27 20:14 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat
* Whole USB structure you have to get:
./:

drwx------ 10 perforator perforator 4096 2010-12-27 21:57 .
drwxr-xr-x 4 root root 4096 2010-12-27 21:35 ..
-rwxrwxrwx 1 root root 23443 2010-12-23 13:55 channel_list_LE32C550_1001.scm
-rwxrwxrwx 1 perforator root 4635 2010-12-27 16:08 first_run.sh
drwxrwsrwx 2 root root 4096 2010-12-23 14:50 link0_Clone
lrwxrwxrwx 1 root root 29 2010-12-27 20:14 link0_Temp -> /mtd_rwarea/usb_mount/usb_cmd
drwxrwsrwx 2 root root 4096 2010-12-23 14:50 link1_Clone
lrwxrwxrwx 1 root root 31 2010-12-27 20:14 link1_Temp -> /mtd_rwarea/usb_mount/usb_mount
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 modules
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 opt
drwxrwxrwx 2 root root 4096 2010-12-27 21:47 restore
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 T-MSX5DEUC
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 T-TDT5DEUC
drwxrwxrwx 3 root root 4096 2010-12-24 00:10 T-VALDEUC

./link0_Clone:

drwxrwsrwx 2 root root 4096 2010-12-23 14:50 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..

./link1_Clone:

drwxrwsrwx 2 root root 4096 2010-12-23 14:50 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..

./modules:

drwxrwxrwx 5 root root 4096 2010-12-24 03:32 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 T-MSX5DEUC
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 T-TDT5DEUC
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 T-VALDEUC

./modules/T-MSX5DEUC:

drwxrwsrwx 5 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwxrwx 3 root root 4096 2010-12-27 14:06 etc
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 lib
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-MSX5DEUC/etc:

drwxrwxrwx 3 root root 4096 2010-12-27 14:06 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 3 root root 4096 2010-12-27 14:07 init.d

./modules/T-MSX5DEUC/etc/init.d:

drwxrwxrwx 3 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:06 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 startup_run_once

./modules/T-MSX5DEUC/etc/init.d/startup_run_once:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:07 ..
-rwxrwxrwx 1 root root 240 2010-12-27 01:38 0_20_insmod.init

./modules/T-MSX5DEUC/lib:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 2 root root 4096 1970-01-01 03:02 modules

./modules/T-MSX5DEUC/lib/modules:

drwxrwxrwx 2 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
-rwxrwxrwx 1 root root 405132 1970-01-01 03:02 cifs.ko
-rwxrwxrwx 1 root root 136636 1970-01-01 03:02 lockd.ko
-rwxrwxrwx 1 root root 290572 1970-01-01 03:02 nfs.ko
-rwxrwxrwx 1 root root 342380 1970-01-01 03:02 sunrpc.ko

./modules/T-MSX5DEUC/usr:

drwxrwxrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 bin
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 sbin

./modules/T-MSX5DEUC/usr/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 1625796 1970-01-01 03:02 busybox

./modules/T-MSX5DEUC/usr/sbin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 138 1970-01-01 03:02 platform.sh

./modules/T-TDT5DEUC:

drwxrwsrwx 5 root root 4096 2010-12-24 04:17 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 etc
drwxrwsrwx 3 root root 4096 2010-12-25 18:36 lib
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-TDT5DEUC/etc:

drwxrwsrwx 3 root root 4096 2010-12-24 03:46 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 init.d

./modules/T-TDT5DEUC/etc/init.d:

drwxrwsrwx 3 root root 4096 2010-12-24 03:47 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 ..
drwxrwsrwx 2 root root 4096 2010-12-24 17:39 startup_run_once

./modules/T-TDT5DEUC/etc/init.d/startup_run_once:

drwxrwsrwx 2 root root 4096 2010-12-24 17:39 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 ..
-rwxrwxrwx 1 root root 240 2010-12-27 01:38 0_20_insmod.init

./modules/T-TDT5DEUC/lib:

drwxrwsrwx 3 root root 4096 2010-12-25 18:36 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 2 root root 4096 2010-12-24 04:19 modules

./modules/T-TDT5DEUC/lib/modules:

drwxrwsrwx 2 root root 4096 2010-12-24 04:19 .
drwxrwsrwx 3 root root 4096 2010-12-25 18:36 ..
-rwxrwxrwx 1 root root 62972 2010-12-11 00:00 auth_rpcgss.ko
-rwxrwxrwx 1 root root 399356 2010-12-11 00:00 cifs.ko
-rwxrwxrwx 1 root root 41076 1980-01-01 00:00 isofs.ko
-rwxrwxrwx 1 root root 106436 2010-12-11 00:00 lockd.ko
-rwxrwxrwx 1 root root 405780 2010-12-11 00:00 nfs.ko
-rwxrwxrwx 1 root root 15080 2010-12-11 00:00 rpcsec_gss_krb5.ko
-rwxrwxrwx 1 root root 105104 2010-12-11 00:00 smbfs.ko
-rwxrwxrwx 1 root root 240652 2010-12-11 00:00 sunrpc.ko
-rwxrwxrwx 1 root root 127728 1980-01-01 00:00 udf.ko

./modules/T-TDT5DEUC/usr:

drwxrwsrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 2 root root 4096 2010-12-25 18:36 bin
drwxrwsrwx 2 root root 4096 2010-12-27 14:10 sbin

./modules/T-TDT5DEUC/usr/bin:

drwxrwsrwx 2 root root 4096 2010-12-25 18:36 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 1694608 1980-01-01 00:00 busybox

./modules/T-TDT5DEUC/usr/sbin:
Ð¸ÑÐ¾Ð³Ð¾ 12
drwxrwsrwx 2 root root 4096 2010-12-27 14:10 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 perforator root 138 2010-12-24 17:40 platform.sh

./modules/T-VALDEUC:

drwxrwxrwx 5 root root 4096 2010-12-24 04:18 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 etc
drwxrwsrwx 3 root root 4096 2010-12-25 18:37 lib
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-VALDEUC/etc:

drwxrwsrwx 3 root root 4096 2010-12-24 03:46 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 init.d

./modules/T-VALDEUC/etc/init.d:

drwxrwsrwx 3 root root 4096 2010-12-24 03:47 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 ..
drwxrwsrwx 2 root root 4096 2010-12-27 14:11 startup_run_once

./modules/T-VALDEUC/etc/init.d/startup_run_once:

drwxrwsrwx 2 root root 4096 2010-12-27 14:11 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 ..
-rwxrwxrwx 1 root root 130 2010-12-27 14:11 0_20_insmod.init

./modules/T-VALDEUC/lib:

drwxrwsrwx 3 root root 4096 2010-12-25 18:37 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 2 root root 4096 2010-12-24 04:20 modules

./modules/T-VALDEUC/lib/modules:

drwxrwsrwx 2 root root 4096 2010-12-24 04:20 .
drwxrwsrwx 3 root root 4096 2010-12-25 18:37 ..
-rwxrwxrwx 1 root root 274304 2010-12-03 22:39 cifs.ko

./modules/T-VALDEUC/usr:

drwxrwsrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 2 root root 4096 2010-12-25 18:37 bin
drwxrwsrwx 2 root root 4096 2010-12-24 17:41 sbin

./modules/T-VALDEUC/usr/bin:

drwxrwsrwx 2 root root 4096 2010-12-25 18:37 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 904544 2010-10-29 01:27 busybox

./modules/T-VALDEUC/usr/sbin:

drwxrwsrwx 2 root root 4096 2010-12-24 17:41 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 perforator root 138 2010-12-24 17:41 platform.sh

./opt:

drwxrwxrwx 8 root root 4096 2010-12-27 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:04 bin
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 etc
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 lib
drwxrwxrwx 2 root root 4096 2010-12-27 01:53 sbin
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 usr
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 var

./opt/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:04 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..

./opt/etc:

drwxrwxrwx 4 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 init.d
drwxrwxrwx 2 root root 4096 2010-12-27 02:16 init.d-disabled

./opt/etc/init.d:

drwxrwxrwx 5 root root 4096 2010-12-27 17:03 .
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 ..
drwxr-xr-x 2 root root 4096 1970-01-01 03:04 start.sh_before_nonblock
drwxrwxrwx 2 root root 4096 2010-12-27 17:10 startup_run_once
drwxrwxrwx 2 root root 4096 2010-12-27 01:37 usb_mount_after

./opt/etc/init.d/start.sh_before_nonblock:

drwxr-xr-x 2 root root 4096 1970-01-01 03:04 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxr-xr-x 1 root root 521 1970-01-01 03:04 0_01_restore_start.sh.init

./opt/etc/init.d/startup_run_once:

drwxrwxrwx 2 root root 4096 2010-12-27 17:10 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxrwxrwx 1 root root 1430 2010-12-27 01:38 0_00_0_emergency_start.init
-rwxrwxrwx 1 root root 422 2010-12-27 17:10 0_10_telnetd.init

./opt/etc/init.d/usb_mount_after:

drwxrwxrwx 2 root root 4096 2010-12-27 01:37 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxrwxrwx 1 root root 243 2010-12-27 01:37 0_00_usbSamyGO.sh.init

./opt/etc/init.d-disabled:

drwxrwxrwx 2 root root 4096 2010-12-27 02:16 .
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 ..

./opt/lib:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:05 modules

./opt/lib/modules:

drwxrwxrwx 2 root root 4096 2010-12-27 14:05 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..

./opt/sbin:

drwxrwxrwx 2 root root 4096 2010-12-27 01:53 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
-rwxrwxrwx 1 root root 192 2010-12-27 01:40 31337
-rwxrwxrwx 1 root root 652 2010-12-27 01:52 44337794
-rwxrwxrwx 1 root root 178 2010-12-27 01:40 666
-rwxrwxrwx 1 root root 591 2010-12-27 01:53 event.sh

./opt/usr:

drwxrwxrwx 5 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:05 bin
drwxrwxrwx 2 root root 4096 2010-12-27 17:02 restore
drwxrwxrwx 3 root root 4096 2010-12-27 14:08 sbin

./opt/usr/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:05 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..

./opt/usr/restore:

drwxrwxrwx 2 root root 4096 2010-12-27 17:02 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..
-rwxr-xr-x 1 root root 213 1970-01-01 03:04 9_9_kill_start.sh_ok.init
-rwxr-xr-x 1 root root 418 1970-01-01 03:04 start.sh

./opt/usr/sbin:

drwxrwxrwx 3 root root 4096 2010-12-27 14:08 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 2 root root 4096 2010-12-27 01:32 usb_mount

./opt/usr/sbin/usb_mount:

drwxrwxrwx 2 root root 4096 2010-12-27 01:32 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:08 ..
-rwxrwxrwx 1 root root 841 2010-12-27 01:32 opt_path
-rwxrwxrwx 1 root root 723 2010-12-27 01:30 unknownDev_cmd
-rwxrwxrwx 1 root root 161 1970-01-01 03:02 usb_cmd
-rwxrwxrwx 1 root root 166 1970-01-01 03:02 usb_moip_cmd
-rwxrwxrwx 1 root root 181 1970-01-01 03:02 usb_mount

./opt/var:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 spool

./opt/var/spool:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 cron

./opt/var/spool/cron:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 2 root root 4096 1970-01-01 03:02 crontabs

./opt/var/spool/cron/crontabs:

drwxrwxrwx 2 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..

./restore:

drwxrwxrwx 2 root root 4096 2010-12-27 21:47 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat

./T-MSX5DEUC:

drwxrwsrwx 3 root root 4096 2010-12-23 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 2 root root 4096 2010-12-27 15:50 Clone

./T-MSX5DEUC/Clone:

drwxrwsrwx 2 root root 4096 2010-12-27 15:50 .
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

./T-TDT5DEUC:

drwxrwsrwx 3 root root 4096 2010-12-23 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 2 root root 4096 2010-12-27 14:13 Clone

./T-TDT5DEUC/Clone:

drwxrwsrwx 2 root root 4096 2010-12-27 14:13 .
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

./T-VALDEUC:

drwxrwxrwx 3 root root 4096 2010-12-24 00:10 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:16 Clone

./T-VALDEUC/Clone:

drwxrwxrwx 2 root root 4096 2010-12-27 14:16 .
drwxrwxrwx 3 root root 4096 2010-12-24 00:10 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

13. Exit from Hotel mode:
* Go to ServiceMenu
Info - Menu - Mute - Power
* Hotel Mode ->Off
14. Attach USB to TV and import channel settings to TV. Everything must go w/o errors. 
15. Activate Hotel mode again
16. Import HotelMode settings you exported before (as is, with directories)
17. Press OK.
18. TV restarts twice and starts in ''black screen''. DO NOT POWER OFF, DO NOT DISCONNECT USB.
* Wait 3 minutes. After trhee minutes or if you get to console earlier you can reboot TV.
* Try connect to TV over telnet (port:23)
* If you get to console, congratulations.
* TV starts in Hotel mode. If you have your channel settings right, you can deactivate hotel mode from service menu.
19. If you haven`t got your channels back and if you can`t telnet to TV, it means - something went wrong
* Look for file ''first_run.ok'' and content of directory ''/result'' on USB
20. If you have telnet after hack, execute:
cp $OPT_DIR/usr/restore/start.sh /mtd_rwarea/start.sh

===Do not have linux and TV is not hacked===
== Normal operating of hacked TV ==
== Ways to unbrick TV ==
== FAQ ===
== Tested on those models ==
* LE 32-C550J1W [T-MSX5DEUC-2005.4]
* LE 40-C550 [T-MSX5DEUC-2003.1]
* LE 32-C530 [T-MSX5DEUC-2007.4]
* LE 32-C550J1WUA [T-MSX5DEUC-2007.4]
* LE 32-C550J1WXRU [T-MSX5DEUC-2005.4]
* UE 32-C5100QW [T-MSX5DEUC-2007.4]
* PS 50-C550 [T-TDT5DEUC]
* LE 40-C650L1WXXH [T-VALDEUC-2002]

TO be updated in few days

--[[User:Juzis28|Juzis28]] 20:21, 5 January 2011 (UTC)

Hacking TV over Hotel mode (most C series models)

2011-01-20T19:01:59Z

Stefanth: /* If you have linux and TV is not hacked */

Universal USB disk to hack C series TV. It should work on any C series TV with export settings to ext3 USB support. Some models does not support ext3 file system for settings export (C6000/C630...firmwares with T-VAL6DEUC)
Tested and works on models with T-MSX5DEUC, T-TDT5DEUC and T-VALDEUC (until 5.1.2011).

After this hack you can connect to TV over telnet, you get CIFS (samba) and NFS support.
Moreover, if you attach USB with script file "SamyGO.sh", it will executed.

This hack has unificated structure for comfortable script execution for developers (read below)

Author and developer - Perforator from forum.ixbt.com (He made the first hack for C series TV also).

'''IMPORTANT''': Until further notice, '''don't try this hack on a TV without Ethernet port''' (like C530).
Read the [http://forum.samygo.tv/viewforum.php?f=13 C series forum] for additional information and try [http://forum.samygo.tv/viewtopic.php?f=13&t=1076 the original juuso hack].

== To Do ==
* NFS automounts
* php script for administer TV over http
* implementations of easy installation/uninstallation of scripts

== Preparation ==
Only for USB, recognised as '''sda'''. 
How to check. Read this [http://forum.samygo.tv/viewtopic.php?f=13&t=1076&start=40#p10979 post]. Later limitation will be removed. 
1. USB > 1GB space. (windows user can use Fat32 formatted USB) 
2. TV in normal mode. Export channels from TV to USB 
3. Activate Hotel Mode
Mute-1-1-9-Enter
set to '''on''' by pressing "left"
4. Export settings from TV to USB 
5. Save files you get anywhere in PC 
6 Download [http://www.multiupload.com/UYW99RK4FG file], extract from archive. You get 1Gb file ''network_opt_28.12.2010_3_sda.img'' 
7 Make USB from this image. 
* Under windows you can use [http://launchpad.net/win32-image-writer/+download win32diskimager].
* After win32diskimager finishes, USB is not accessible under Windows, because it is ext3 format.

== Hack TV==
===If you have linux and TV is not hacked===
8. Attach USB you made to linux PC. Copy channel settings file (you made in normal mode) to root of USB
9. Rename file (channel_list_LE32C550_1001.scm for C550) to zip
channel_list_LE32C550_1001.scm.zip
10. Add directory ''usb_mount'' with empty file in it (e.g. ''1.txt;'' - very important) to archive 
11. Rename back to channel_list_LE32C550_1001.scm
* You get files inside of archive:
Archive: channel_list_LE32C550_1001.scm
Length Date Time Name
--------- ---------- ----- ----
68 2038-01-19 06:14 CloneInfo
96 2038-01-19 06:14 FineTune_Digital
40000 2038-01-19 06:14 map-AirA
292000 2038-01-19 06:14 map-AirD
40000 2038-01-19 06:14 map-CableA
292000 2038-01-19 06:14 map-CableD
4 2038-01-19 06:14 map-ChKey
720 2038-01-19 06:14 RadioMap
0 2010-11-30 21:55 usb_mount/
8 2010-11-30 21:55 usb_mount/1.txt
--------- -------
664896 10 files
12. Copy files exported in Hotel mode (only files, without directories) to /restore directory on USB
* Exported in HotelMode files to copy:
./T-MSX5DEUC/Clone:

drwxr-xr-x 2 root root 4096 2010-12-27 18:39 .
drwxr-xr-x 3 root root 4096 2010-12-27 18:39 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat
* You should get structure on USB/restore:
./restore:

drwxrwxrwx 2 root root 4096 2010-12-27 21:47 .
drwx------ 10 root root 4096 2010-12-27 20:14 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat
* Whole USB structure you have to get:
./:

drwx------ 10 perforator perforator 4096 2010-12-27 21:57 .
drwxr-xr-x 4 root root 4096 2010-12-27 21:35 ..
-rwxrwxrwx 1 root root 23443 2010-12-23 13:55 channel_list_LE32C550_1001.scm
-rwxrwxrwx 1 perforator root 4635 2010-12-27 16:08 first_run.sh
drwxrwsrwx 2 root root 4096 2010-12-23 14:50 link0_Clone
lrwxrwxrwx 1 root root 29 2010-12-27 20:14 link0_Temp -> /mtd_rwarea/usb_mount/usb_cmd
drwxrwsrwx 2 root root 4096 2010-12-23 14:50 link1_Clone
lrwxrwxrwx 1 root root 31 2010-12-27 20:14 link1_Temp -> /mtd_rwarea/usb_mount/usb_mount
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 modules
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 opt
drwxrwxrwx 2 root root 4096 2010-12-27 21:47 restore
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 T-MSX5DEUC
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 T-TDT5DEUC
drwxrwxrwx 3 root root 4096 2010-12-24 00:10 T-VALDEUC

./link0_Clone:

drwxrwsrwx 2 root root 4096 2010-12-23 14:50 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..

./link1_Clone:

drwxrwsrwx 2 root root 4096 2010-12-23 14:50 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..

./modules:

drwxrwxrwx 5 root root 4096 2010-12-24 03:32 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 T-MSX5DEUC
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 T-TDT5DEUC
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 T-VALDEUC

./modules/T-MSX5DEUC:

drwxrwsrwx 5 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwxrwx 3 root root 4096 2010-12-27 14:06 etc
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 lib
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-MSX5DEUC/etc:

drwxrwxrwx 3 root root 4096 2010-12-27 14:06 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 3 root root 4096 2010-12-27 14:07 init.d

./modules/T-MSX5DEUC/etc/init.d:

drwxrwxrwx 3 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:06 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 startup_run_once

./modules/T-MSX5DEUC/etc/init.d/startup_run_once:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:07 ..
-rwxrwxrwx 1 root root 240 2010-12-27 01:38 0_20_insmod.init

./modules/T-MSX5DEUC/lib:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 2 root root 4096 1970-01-01 03:02 modules

./modules/T-MSX5DEUC/lib/modules:

drwxrwxrwx 2 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
-rwxrwxrwx 1 root root 405132 1970-01-01 03:02 cifs.ko
-rwxrwxrwx 1 root root 136636 1970-01-01 03:02 lockd.ko
-rwxrwxrwx 1 root root 290572 1970-01-01 03:02 nfs.ko
-rwxrwxrwx 1 root root 342380 1970-01-01 03:02 sunrpc.ko

./modules/T-MSX5DEUC/usr:

drwxrwxrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwsrwx 5 root root 4096 2010-12-27 14:07 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 bin
drwxrwxrwx 2 root root 4096 2010-12-27 14:07 sbin

./modules/T-MSX5DEUC/usr/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 1625796 1970-01-01 03:02 busybox

./modules/T-MSX5DEUC/usr/sbin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:07 .
drwxrwxrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 138 1970-01-01 03:02 platform.sh

./modules/T-TDT5DEUC:

drwxrwsrwx 5 root root 4096 2010-12-24 04:17 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 etc
drwxrwsrwx 3 root root 4096 2010-12-25 18:36 lib
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-TDT5DEUC/etc:

drwxrwsrwx 3 root root 4096 2010-12-24 03:46 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 init.d

./modules/T-TDT5DEUC/etc/init.d:

drwxrwsrwx 3 root root 4096 2010-12-24 03:47 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 ..
drwxrwsrwx 2 root root 4096 2010-12-24 17:39 startup_run_once

./modules/T-TDT5DEUC/etc/init.d/startup_run_once:

drwxrwsrwx 2 root root 4096 2010-12-24 17:39 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 ..
-rwxrwxrwx 1 root root 240 2010-12-27 01:38 0_20_insmod.init

./modules/T-TDT5DEUC/lib:

drwxrwsrwx 3 root root 4096 2010-12-25 18:36 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 2 root root 4096 2010-12-24 04:19 modules

./modules/T-TDT5DEUC/lib/modules:

drwxrwsrwx 2 root root 4096 2010-12-24 04:19 .
drwxrwsrwx 3 root root 4096 2010-12-25 18:36 ..
-rwxrwxrwx 1 root root 62972 2010-12-11 00:00 auth_rpcgss.ko
-rwxrwxrwx 1 root root 399356 2010-12-11 00:00 cifs.ko
-rwxrwxrwx 1 root root 41076 1980-01-01 00:00 isofs.ko
-rwxrwxrwx 1 root root 106436 2010-12-11 00:00 lockd.ko
-rwxrwxrwx 1 root root 405780 2010-12-11 00:00 nfs.ko
-rwxrwxrwx 1 root root 15080 2010-12-11 00:00 rpcsec_gss_krb5.ko
-rwxrwxrwx 1 root root 105104 2010-12-11 00:00 smbfs.ko
-rwxrwxrwx 1 root root 240652 2010-12-11 00:00 sunrpc.ko
-rwxrwxrwx 1 root root 127728 1980-01-01 00:00 udf.ko

./modules/T-TDT5DEUC/usr:

drwxrwsrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwsrwx 5 root root 4096 2010-12-24 04:17 ..
drwxrwsrwx 2 root root 4096 2010-12-25 18:36 bin
drwxrwsrwx 2 root root 4096 2010-12-27 14:10 sbin

./modules/T-TDT5DEUC/usr/bin:

drwxrwsrwx 2 root root 4096 2010-12-25 18:36 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 1694608 1980-01-01 00:00 busybox

./modules/T-TDT5DEUC/usr/sbin:
Ð¸ÑÐ¾Ð³Ð¾ 12
drwxrwsrwx 2 root root 4096 2010-12-27 14:10 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 perforator root 138 2010-12-24 17:40 platform.sh

./modules/T-VALDEUC:

drwxrwxrwx 5 root root 4096 2010-12-24 04:18 .
drwxrwxrwx 5 root root 4096 2010-12-24 03:32 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 etc
drwxrwsrwx 3 root root 4096 2010-12-25 18:37 lib
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 usr

./modules/T-VALDEUC/etc:

drwxrwsrwx 3 root root 4096 2010-12-24 03:46 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 init.d

./modules/T-VALDEUC/etc/init.d:

drwxrwsrwx 3 root root 4096 2010-12-24 03:47 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:46 ..
drwxrwsrwx 2 root root 4096 2010-12-27 14:11 startup_run_once

./modules/T-VALDEUC/etc/init.d/startup_run_once:

drwxrwsrwx 2 root root 4096 2010-12-27 14:11 .
drwxrwsrwx 3 root root 4096 2010-12-24 03:47 ..
-rwxrwxrwx 1 root root 130 2010-12-27 14:11 0_20_insmod.init

./modules/T-VALDEUC/lib:

drwxrwsrwx 3 root root 4096 2010-12-25 18:37 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 2 root root 4096 2010-12-24 04:20 modules

./modules/T-VALDEUC/lib/modules:

drwxrwsrwx 2 root root 4096 2010-12-24 04:20 .
drwxrwsrwx 3 root root 4096 2010-12-25 18:37 ..
-rwxrwxrwx 1 root root 274304 2010-12-03 22:39 cifs.ko

./modules/T-VALDEUC/usr:

drwxrwsrwx 4 root root 4096 2010-12-27 17:12 .
drwxrwxrwx 5 root root 4096 2010-12-24 04:18 ..
drwxrwsrwx 2 root root 4096 2010-12-25 18:37 bin
drwxrwsrwx 2 root root 4096 2010-12-24 17:41 sbin

./modules/T-VALDEUC/usr/bin:

drwxrwsrwx 2 root root 4096 2010-12-25 18:37 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 root root 904544 2010-10-29 01:27 busybox

./modules/T-VALDEUC/usr/sbin:

drwxrwsrwx 2 root root 4096 2010-12-24 17:41 .
drwxrwsrwx 4 root root 4096 2010-12-27 17:12 ..
-rwxrwxrwx 1 perforator root 138 2010-12-24 17:41 platform.sh

./opt:

drwxrwxrwx 8 root root 4096 2010-12-27 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:04 bin
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 etc
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 lib
drwxrwxrwx 2 root root 4096 2010-12-27 01:53 sbin
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 usr
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 var

./opt/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:04 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..

./opt/etc:

drwxrwxrwx 4 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 init.d
drwxrwxrwx 2 root root 4096 2010-12-27 02:16 init.d-disabled

./opt/etc/init.d:

drwxrwxrwx 5 root root 4096 2010-12-27 17:03 .
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 ..
drwxr-xr-x 2 root root 4096 1970-01-01 03:04 start.sh_before_nonblock
drwxrwxrwx 2 root root 4096 2010-12-27 17:10 startup_run_once
drwxrwxrwx 2 root root 4096 2010-12-27 01:37 usb_mount_after

./opt/etc/init.d/start.sh_before_nonblock:

drwxr-xr-x 2 root root 4096 1970-01-01 03:04 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxr-xr-x 1 root root 521 1970-01-01 03:04 0_01_restore_start.sh.init

./opt/etc/init.d/startup_run_once:

drwxrwxrwx 2 root root 4096 2010-12-27 17:10 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxrwxrwx 1 root root 1430 2010-12-27 01:38 0_00_0_emergency_start.init
-rwxrwxrwx 1 root root 422 2010-12-27 17:10 0_10_telnetd.init

./opt/etc/init.d/usb_mount_after:

drwxrwxrwx 2 root root 4096 2010-12-27 01:37 .
drwxrwxrwx 5 root root 4096 2010-12-27 17:03 ..
-rwxrwxrwx 1 root root 243 2010-12-27 01:37 0_00_usbSamyGO.sh.init

./opt/etc/init.d-disabled:

drwxrwxrwx 2 root root 4096 2010-12-27 02:16 .
drwxrwxrwx 4 root root 4096 1970-01-01 03:02 ..

./opt/lib:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:05 modules

./opt/lib/modules:

drwxrwxrwx 2 root root 4096 2010-12-27 14:05 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..

./opt/sbin:

drwxrwxrwx 2 root root 4096 2010-12-27 01:53 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
-rwxrwxrwx 1 root root 192 2010-12-27 01:40 31337
-rwxrwxrwx 1 root root 652 2010-12-27 01:52 44337794
-rwxrwxrwx 1 root root 178 2010-12-27 01:40 666
-rwxrwxrwx 1 root root 591 2010-12-27 01:53 event.sh

./opt/usr:

drwxrwxrwx 5 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:05 bin
drwxrwxrwx 2 root root 4096 2010-12-27 17:02 restore
drwxrwxrwx 3 root root 4096 2010-12-27 14:08 sbin

./opt/usr/bin:

drwxrwxrwx 2 root root 4096 2010-12-27 14:05 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..

./opt/usr/restore:

drwxrwxrwx 2 root root 4096 2010-12-27 17:02 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..
-rwxr-xr-x 1 root root 213 1970-01-01 03:04 9_9_kill_start.sh_ok.init
-rwxr-xr-x 1 root root 418 1970-01-01 03:04 start.sh

./opt/usr/sbin:

drwxrwxrwx 3 root root 4096 2010-12-27 14:08 .
drwxrwxrwx 5 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 2 root root 4096 2010-12-27 01:32 usb_mount

./opt/usr/sbin/usb_mount:

drwxrwxrwx 2 root root 4096 2010-12-27 01:32 .
drwxrwxrwx 3 root root 4096 2010-12-27 14:08 ..
-rwxrwxrwx 1 root root 841 2010-12-27 01:32 opt_path
-rwxrwxrwx 1 root root 723 2010-12-27 01:30 unknownDev_cmd
-rwxrwxrwx 1 root root 161 1970-01-01 03:02 usb_cmd
-rwxrwxrwx 1 root root 166 1970-01-01 03:02 usb_moip_cmd
-rwxrwxrwx 1 root root 181 1970-01-01 03:02 usb_mount

./opt/var:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 8 root root 4096 2010-12-27 14:04 ..
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 spool

./opt/var/spool:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 cron

./opt/var/spool/cron:

drwxrwxrwx 3 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..
drwxrwxrwx 2 root root 4096 1970-01-01 03:02 crontabs

./opt/var/spool/cron/crontabs:

drwxrwxrwx 2 root root 4096 1970-01-01 03:02 .
drwxrwxrwx 3 root root 4096 1970-01-01 03:02 ..

./restore:

drwxrwxrwx 2 root root 4096 2010-12-27 21:47 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
-rw-r--r-- 1 root root 2304 1980-01-01 00:00 Clone.dat
-rw-r--r-- 1 root root 378 1980-01-01 00:00 FADAT
-rw-r--r-- 1 root root 144 1980-01-01 00:00 FineTune_Digital
-rw-r--r-- 1 root root 188 1980-01-01 00:00 LNBSettingsDataBase.dat
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-AirA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-AirD
-rw-r--r-- 1 root root 40000 1980-01-01 00:00 map-CableA
-rw-r--r-- 1 root root 292000 1980-01-01 00:00 map-CableD
-rw-r--r-- 1 root root 4 1980-01-01 00:00 map-ChKey
-rw-r--r-- 1 root root 144000 1980-01-01 00:00 map-SateD
-rw-r--r-- 1 root root 95 1980-01-01 00:00 PackageDataBase.dat
-rw-r--r-- 1 root root 5382 1980-01-01 00:00 PLDAT
-rw-r--r-- 1 root root 720 1980-01-01 00:00 RadioMap
-rw-r--r-- 1 root root 7979 1980-01-01 00:00 SatDataBase.dat
-rw-r--r-- 1 root root 324 1980-01-01 00:00 ServiceProviders
-rw-r--r-- 1 root root 9478 1980-01-01 00:00 SSDAT
-rw-r--r-- 1 root root 98554 1980-01-01 00:00 TransponderDataBase.dat
-rw-r--r-- 1 root root 28 1980-01-01 00:00 TSIDList
-rw-r--r-- 1 root root 4 1980-01-01 00:00 UserTransponderDataBase.dat

./T-MSX5DEUC:

drwxrwsrwx 3 root root 4096 2010-12-23 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 2 root root 4096 2010-12-27 15:50 Clone

./T-MSX5DEUC/Clone:

drwxrwsrwx 2 root root 4096 2010-12-27 15:50 .
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

./T-TDT5DEUC:

drwxrwsrwx 3 root root 4096 2010-12-23 14:04 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwsrwx 2 root root 4096 2010-12-27 14:13 Clone

./T-TDT5DEUC/Clone:

drwxrwsrwx 2 root root 4096 2010-12-27 14:13 .
drwxrwsrwx 3 root root 4096 2010-12-23 14:04 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

./T-VALDEUC:

drwxrwxrwx 3 root root 4096 2010-12-24 00:10 .
drwx------ 10 perforator perforator 4096 2010-12-27 21:57 ..
drwxrwxrwx 2 root root 4096 2010-12-27 14:16 Clone

./T-VALDEUC/Clone:

drwxrwxrwx 2 root root 4096 2010-12-27 14:16 .
drwxrwxrwx 3 root root 4096 2010-12-24 00:10 ..
-rwxrwxrwx 1 root root 256 2010-12-27 15:58 Clone.dat
-rwxrwxrwx 1 perforator root 319 2010-12-27 15:50 link0
-rwxrwxrwx 1 perforator root 39 2010-12-27 15:50 link1

13. Exit from Hotel mode:
* Go to ServiceMenu
Info - Menu - Mute - Power
* Hotel Mode ->Off
14. Attach USB to TV and import channel settings to TV. Everything must go w/o errors. 
15. Activate Hotel mode again
16. Import HotelMode settings you exported before (as is, with directories)
17. Press OK.
18. TV restarts twice and starts in ''black screen''. DO NOT POWER OFF, DO NOT DISCONNECT USB.
* Wait 3 minutes. After trhee minutes or if you get to console earlier you can reboot TV.
* Try connect to TV over telnet (port:23)
* If you get to console, congratulations.
* TV starts in Hotel mode. If you have your channel settings right, you can deactivate hotel mode from service menu.
19. If you haven`t got your channels back and if you can`t telnet to TV, it means - something went wrong
* Look for file ''first_run.ok'' and content of directory ''/result'' on USB
20. If you have telnet after hack, execute:
cp $OPT_DIR/usr/restore/start.sh /mtd_rwarea/start.sh

===Do not have linux and TV is not hacked===
== Normal operating of hacked TV ==
== Ways to unbrick TV ==
== FAQ ===
== Tested on those models ==
* LE 32-C550J1W [T-MSX5DEUC-2005.4]
* LE 40-C550 [T-MSX5DEUC-2003.1]
* LE 32-C530 [T-MSX5DEUC-2007.4]
* LE 32-C550J1WUA [T-MSX5DEUC-2007.4]
* LE 32-C550J1WXRU [T-MSX5DEUC-2005.4]
* UE 32-C5100QW [T-MSX5DEUC-2007.4]
* PS 50-C550 [T-TDT5DEUC]
* LE 40-C650L1WXXH [T-VALDEUC-2002]

TO be updated in few days

--[[User:Juzis28|Juzis28]] 20:21, 5 January 2011 (UTC)

SamyGO ChanEdit - Chanel Editor

2011-01-11T08:25:03Z

Stefanth: /* UE46C5105 */

=SamyGO ChanEdit=

With SamyGO ChanEdit you can edit your channel list of your Samsung TV Set using any Computer able to run a Java VM supporting SWT. This makes moving channels around a lot easier. Also the list can be extended by channels that are not found by the channel search engine. For example Sky.de interactive channels, which the editor can add automatically when a list containing Sky.de channels is loaded.

==Channel Import/Export Menu==
First you have to connect a USB drive with a FAT/FAT32 filesystem to your TV.

When the TV is switched ON press '''Volume Down''' [[File:Volume_down_key.png|30px]] once and then press '''the Enter [[File:Enter_key.png|30pxâ]] button for 10 seconds'''. This will display the "Channel Import / Export" Menu.

If this doesn't work, check that "Speaker Select" in "Sound Menu" is set to "TV Speaker". Anynet+ (HDMI-CEC) should be disabled.
[[File:Channel_Import_Export.png|300px|left|thumb|Channel Import / Export]]
 
Choose '''USB to TV''' for channeldata import or '''TV to USB''' for copying the channeldata to the USB drive.

When everything worked correct you'll find the following data on your USB drive:

kilroy@kilroy:~$ ls -la /media/USB2GB/T-CHLCIPDEUC/Clone/
total 744
drwx------ 2 kilroy kilroy 4096 1980-01-01 00:00 .
drwx------ 3 kilroy kilroy 4096 1980-01-01 00:00 ..
-rwxr-xr-x 1 kilroy kilroy 1920 1980-01-01 00:00 Clone.dat
-rwxr-xr-x 1 kilroy kilroy 20 1980-01-01 00:00 FineTune
-rwxr-xr-x 1 kilroy kilroy 1092 1980-01-01 00:00 FineTune_Digital
-rwxr-xr-x 1 kilroy kilroy 124 1980-01-01 00:00 LNBSettingsDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-AirA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-AirD
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-CableA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-CableD
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 map-ChKey
-rwxr-xr-x 1 kilroy kilroy 144000 1980-01-01 00:00 map-SateD
-rwxr-xr-x 1 kilroy kilroy 3184 1980-01-01 00:00 PTCCABLE
-rwxr-xr-x 1 kilroy kilroy 584 1980-01-01 00:00 SatDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 5616 1980-01-01 00:00 ServiceProviders
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 TransponderDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 88 1980-01-01 00:00 TSIDList
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 UserTransponderDataBase.dat

Now you can edit the channel list (for the moment only map-CableD for DVB-C) stored on the drive using SamyGO ChanEdit.

After that just use the same procedure to import the list again.

=== UE46C5105 (and probably other TV's from the C serie) ===
This TV have a slight different menu system than above described.

The "save to USB stick" is in the channel sub meny under "Antenna".

Also, Samsung does not save the channel files in a directory any more but instead all channel files are saved in one single file with the ending .scm

This scm file is an ordinary zip file so to unpack it the file have either to be "dropped" on WinZip (Windows) or feed to unzip.
Another way is to rename the file so it ends with .zip instead of .scm and then open it with WinZip or feed to unzip.

The unpacking of the file recreates the above described file structure.

After the edition is done, zip together the content and rename it to .scm again.

Added by [[User:Stefanth|Stefanth]]

==Downloading and Installing==
Download the SamyGO ChanEdit (and required Java library for you OS) from [http://download.samygo.tv/SamyGO%20Applications/ SamyGO Applications] file download area.

===Ubuntu 9.10 amd64===

You have to download the files '''SamyGO ChanEdit-v0.31.tar.bz2''' and '''SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2''' 
Ubuntu 9.10 is comes with openjdk-6-jre but you can also install Java from SUN (recommended).

# sudo aptitude install sun-java6-jre
[ -d ~/bin ] || mkdir ~/bin
tar xjf Downloads/SamyGO\ ChanEdit-v0.31.tar.bz2 -C ~/bin/
tar xjf Downloads/SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2 -C ~/bin/SamyGO\ ChanEdit-v0.31/
ln -s ~/bin/SamyGO\ ChanEdit-v0.31/SamyGoChanEd.jar Desktop/SamyGoChanEd.jar

Right click at the SamyGoChanEd.jar icon and select '''Properties -> Open With:''' ''OpenJDK Java 6 Runtime'' (or ''Sun Java 6 Runtime'')

===Microsoft Windows===
Note: The java engine must be a 32 bit version of the Java engine, the reason for this is that the swt.jar file only exists as a 32 bit build.
This mean that the 32 bit java engine have to be reinstall or be parallel installation if there only exist a 64 bit version on the PC.

To execute the channel editor you need two parts, the channel editor program itself and a support library called swt.
The channel editor program can be found here [http://download.samygo.tv/SamyGO%20PC%20Applications SamyGO ChanEdit]

The SWT library can either be downloaded directly from [http://www.eclipse.org/swt http://www.eclipse.org/swt] or from [http://download.samygo.tv/SamyGO%20PC%20Applications/SamyGO%20ChanEdit%20SWT%20Libraries SamyGo].

Unpack the downloaded files and place the both .jar files,SamyGoChanEd.jar and swt.jar, in the same director.
These two jar files are the only files needed, there are other files and content in the downloaded zip/gz/bz2 files but they are not needed

Open a command prompt and enter

'''<tt>java -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

The following example is on a Windows 7 installation, the java.exe file might be in a different place depending on the installation and operating system.
If you get an error message saying that java is not a commando then you need to give the full path to the Java engine, like this

'''<tt>"c:\Program Files (x86)\Java\jdk1.6.0_23\bin\java.exe" -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

Of course it is possible to create a link on the desktop and execute the same command line.

Added by [[User:Stefanth|Stefanth]]

==Modifying Channel List==
You can modify your Channel list via SamyGO ChanEdit.

The files are under your USB at T-CHxxDEUC/Clone directory.
With Version 0.31 currently only map-CableD for digital Cable Channels is editable.

<center>[[File:SamyGO ChanEdit.png]]</center>

Afterwards you can import the channel list to TV from the USB stick.

SamyGO ChanEdit - Chanel Editor

2011-01-11T08:21:22Z

Stefanth: /* Channel Import/Export Menu */

=SamyGO ChanEdit=

With SamyGO ChanEdit you can edit your channel list of your Samsung TV Set using any Computer able to run a Java VM supporting SWT. This makes moving channels around a lot easier. Also the list can be extended by channels that are not found by the channel search engine. For example Sky.de interactive channels, which the editor can add automatically when a list containing Sky.de channels is loaded.

==Channel Import/Export Menu==
First you have to connect a USB drive with a FAT/FAT32 filesystem to your TV.

When the TV is switched ON press '''Volume Down''' [[File:Volume_down_key.png|30px]] once and then press '''the Enter [[File:Enter_key.png|30pxâ]] button for 10 seconds'''. This will display the "Channel Import / Export" Menu.

If this doesn't work, check that "Speaker Select" in "Sound Menu" is set to "TV Speaker". Anynet+ (HDMI-CEC) should be disabled.
[[File:Channel_Import_Export.png|300px|left|thumb|Channel Import / Export]]
 
Choose '''USB to TV''' for channeldata import or '''TV to USB''' for copying the channeldata to the USB drive.

When everything worked correct you'll find the following data on your USB drive:

kilroy@kilroy:~$ ls -la /media/USB2GB/T-CHLCIPDEUC/Clone/
total 744
drwx------ 2 kilroy kilroy 4096 1980-01-01 00:00 .
drwx------ 3 kilroy kilroy 4096 1980-01-01 00:00 ..
-rwxr-xr-x 1 kilroy kilroy 1920 1980-01-01 00:00 Clone.dat
-rwxr-xr-x 1 kilroy kilroy 20 1980-01-01 00:00 FineTune
-rwxr-xr-x 1 kilroy kilroy 1092 1980-01-01 00:00 FineTune_Digital
-rwxr-xr-x 1 kilroy kilroy 124 1980-01-01 00:00 LNBSettingsDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-AirA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-AirD
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-CableA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-CableD
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 map-ChKey
-rwxr-xr-x 1 kilroy kilroy 144000 1980-01-01 00:00 map-SateD
-rwxr-xr-x 1 kilroy kilroy 3184 1980-01-01 00:00 PTCCABLE
-rwxr-xr-x 1 kilroy kilroy 584 1980-01-01 00:00 SatDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 5616 1980-01-01 00:00 ServiceProviders
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 TransponderDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 88 1980-01-01 00:00 TSIDList
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 UserTransponderDataBase.dat

Now you can edit the channel list (for the moment only map-CableD for DVB-C) stored on the drive using SamyGO ChanEdit.

After that just use the same procedure to import the list again.

=== UE46C5105 ===
This TV and perhaps all other C-series TV's have a slight different menu system.
The "save to USB stick" is in the channel sub meny under "Antenna".
Also, Samsung does not save the channel files as a directory anymore but instead all files are saved in one single file with the ending .scm
Lucky, this scm file is an ordinary zip file so to unpack it the file have either to be "dropped" on WinZip (Windows) or feed to unzip.

Another way is to rename the file so it ends with .zip instead of .scm and then open it with WinZip or feed to unzip.
After unpacking the file the file structure is the same as above.

After the edition is done, zip together the content and rename it to .scm again.

Added by [[User:Stefanth|Stefanth]]

==Downloading and Installing==
Download the SamyGO ChanEdit (and required Java library for you OS) from [http://download.samygo.tv/SamyGO%20Applications/ SamyGO Applications] file download area.

===Ubuntu 9.10 amd64===

You have to download the files '''SamyGO ChanEdit-v0.31.tar.bz2''' and '''SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2''' 
Ubuntu 9.10 is comes with openjdk-6-jre but you can also install Java from SUN (recommended).

# sudo aptitude install sun-java6-jre
[ -d ~/bin ] || mkdir ~/bin
tar xjf Downloads/SamyGO\ ChanEdit-v0.31.tar.bz2 -C ~/bin/
tar xjf Downloads/SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2 -C ~/bin/SamyGO\ ChanEdit-v0.31/
ln -s ~/bin/SamyGO\ ChanEdit-v0.31/SamyGoChanEd.jar Desktop/SamyGoChanEd.jar

Right click at the SamyGoChanEd.jar icon and select '''Properties -> Open With:''' ''OpenJDK Java 6 Runtime'' (or ''Sun Java 6 Runtime'')

===Microsoft Windows===
Note: The java engine must be a 32 bit version of the Java engine, the reason for this is that the swt.jar file only exists as a 32 bit build.
This mean that the 32 bit java engine have to be reinstall or be parallel installation if there only exist a 64 bit version on the PC.

To execute the channel editor you need two parts, the channel editor program itself and a support library called swt.
The channel editor program can be found here [http://download.samygo.tv/SamyGO%20PC%20Applications SamyGO ChanEdit]

The SWT library can either be downloaded directly from [http://www.eclipse.org/swt http://www.eclipse.org/swt] or from [http://download.samygo.tv/SamyGO%20PC%20Applications/SamyGO%20ChanEdit%20SWT%20Libraries SamyGo].

Unpack the downloaded files and place the both .jar files,SamyGoChanEd.jar and swt.jar, in the same director.
These two jar files are the only files needed, there are other files and content in the downloaded zip/gz/bz2 files but they are not needed

Open a command prompt and enter

'''<tt>java -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

The following example is on a Windows 7 installation, the java.exe file might be in a different place depending on the installation and operating system.
If you get an error message saying that java is not a commando then you need to give the full path to the Java engine, like this

'''<tt>"c:\Program Files (x86)\Java\jdk1.6.0_23\bin\java.exe" -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

Of course it is possible to create a link on the desktop and execute the same command line.

Added by [[User:Stefanth|Stefanth]]

==Modifying Channel List==
You can modify your Channel list via SamyGO ChanEdit.

The files are under your USB at T-CHxxDEUC/Clone directory.
With Version 0.31 currently only map-CableD for digital Cable Channels is editable.

<center>[[File:SamyGO ChanEdit.png]]</center>

Afterwards you can import the channel list to TV from the USB stick.

SamyGO ChanEdit - Chanel Editor

2011-01-11T08:14:06Z

Stefanth: /* Microsoft Windows */

=SamyGO ChanEdit=

With SamyGO ChanEdit you can edit your channel list of your Samsung TV Set using any Computer able to run a Java VM supporting SWT. This makes moving channels around a lot easier. Also the list can be extended by channels that are not found by the channel search engine. For example Sky.de interactive channels, which the editor can add automatically when a list containing Sky.de channels is loaded.

==Channel Import/Export Menu==
First you have to connect a USB drive with a FAT/FAT32 filesystem to your TV.

When the TV is switched ON press '''Volume Down''' [[File:Volume_down_key.png|30px]] once and then press '''the Enter [[File:Enter_key.png|30pxâ]] button for 10 seconds'''. This will display the "Channel Import / Export" Menu.

If this doesn't work, check that "Speaker Select" in "Sound Menu" is set to "TV Speaker". Anynet+ (HDMI-CEC) should be disabled.
[[File:Channel_Import_Export.png|300px|left|thumb|Channel Import / Export]]
 
Choose '''USB to TV''' for channeldata import or '''TV to USB''' for copying the channeldata to the USB drive.

When everything worked correct you'll find the following data on your USB drive:

kilroy@kilroy:~$ ls -la /media/USB2GB/T-CHLCIPDEUC/Clone/
total 744
drwx------ 2 kilroy kilroy 4096 1980-01-01 00:00 .
drwx------ 3 kilroy kilroy 4096 1980-01-01 00:00 ..
-rwxr-xr-x 1 kilroy kilroy 1920 1980-01-01 00:00 Clone.dat
-rwxr-xr-x 1 kilroy kilroy 20 1980-01-01 00:00 FineTune
-rwxr-xr-x 1 kilroy kilroy 1092 1980-01-01 00:00 FineTune_Digital
-rwxr-xr-x 1 kilroy kilroy 124 1980-01-01 00:00 LNBSettingsDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-AirA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-AirD
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-CableA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-CableD
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 map-ChKey
-rwxr-xr-x 1 kilroy kilroy 144000 1980-01-01 00:00 map-SateD
-rwxr-xr-x 1 kilroy kilroy 3184 1980-01-01 00:00 PTCCABLE
-rwxr-xr-x 1 kilroy kilroy 584 1980-01-01 00:00 SatDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 5616 1980-01-01 00:00 ServiceProviders
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 TransponderDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 88 1980-01-01 00:00 TSIDList
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 UserTransponderDataBase.dat

Now you can edit the channel list (for the moment only map-CableD for DVB-C) stored on the drive using SamyGO ChanEdit.

After that just use the same procedure to import the list again.

==Downloading and Installing==
Download the SamyGO ChanEdit (and required Java library for you OS) from [http://download.samygo.tv/SamyGO%20Applications/ SamyGO Applications] file download area.

===Ubuntu 9.10 amd64===

You have to download the files '''SamyGO ChanEdit-v0.31.tar.bz2''' and '''SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2''' 
Ubuntu 9.10 is comes with openjdk-6-jre but you can also install Java from SUN (recommended).

# sudo aptitude install sun-java6-jre
[ -d ~/bin ] || mkdir ~/bin
tar xjf Downloads/SamyGO\ ChanEdit-v0.31.tar.bz2 -C ~/bin/
tar xjf Downloads/SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2 -C ~/bin/SamyGO\ ChanEdit-v0.31/
ln -s ~/bin/SamyGO\ ChanEdit-v0.31/SamyGoChanEd.jar Desktop/SamyGoChanEd.jar

Right click at the SamyGoChanEd.jar icon and select '''Properties -> Open With:''' ''OpenJDK Java 6 Runtime'' (or ''Sun Java 6 Runtime'')

===Microsoft Windows===
Note: The java engine must be a 32 bit version of the Java engine, the reason for this is that the swt.jar file only exists as a 32 bit build.
This mean that the 32 bit java engine have to be reinstall or be parallel installation if there only exist a 64 bit version on the PC.

To execute the channel editor you need two parts, the channel editor program itself and a support library called swt.
The channel editor program can be found here [http://download.samygo.tv/SamyGO%20PC%20Applications SamyGO ChanEdit]

The SWT library can either be downloaded directly from [http://www.eclipse.org/swt http://www.eclipse.org/swt] or from [http://download.samygo.tv/SamyGO%20PC%20Applications/SamyGO%20ChanEdit%20SWT%20Libraries SamyGo].

Unpack the downloaded files and place the both .jar files,SamyGoChanEd.jar and swt.jar, in the same director.
These two jar files are the only files needed, there are other files and content in the downloaded zip/gz/bz2 files but they are not needed

Open a command prompt and enter

'''<tt>java -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

The following example is on a Windows 7 installation, the java.exe file might be in a different place depending on the installation and operating system.
If you get an error message saying that java is not a commando then you need to give the full path to the Java engine, like this

'''<tt>"c:\Program Files (x86)\Java\jdk1.6.0_23\bin\java.exe" -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

Of course it is possible to create a link on the desktop and execute the same command line.

Added by [[User:Stefanth|Stefanth]]

==Modifying Channel List==
You can modify your Channel list via SamyGO ChanEdit.

The files are under your USB at T-CHxxDEUC/Clone directory.
With Version 0.31 currently only map-CableD for digital Cable Channels is editable.

<center>[[File:SamyGO ChanEdit.png]]</center>

Afterwards you can import the channel list to TV from the USB stick.

SamyGO ChanEdit - Chanel Editor

2011-01-11T08:12:48Z

Stefanth: /* Microsoft Windows */

=SamyGO ChanEdit=

With SamyGO ChanEdit you can edit your channel list of your Samsung TV Set using any Computer able to run a Java VM supporting SWT. This makes moving channels around a lot easier. Also the list can be extended by channels that are not found by the channel search engine. For example Sky.de interactive channels, which the editor can add automatically when a list containing Sky.de channels is loaded.

==Channel Import/Export Menu==
First you have to connect a USB drive with a FAT/FAT32 filesystem to your TV.

When the TV is switched ON press '''Volume Down''' [[File:Volume_down_key.png|30px]] once and then press '''the Enter [[File:Enter_key.png|30pxâ]] button for 10 seconds'''. This will display the "Channel Import / Export" Menu.

If this doesn't work, check that "Speaker Select" in "Sound Menu" is set to "TV Speaker". Anynet+ (HDMI-CEC) should be disabled.
[[File:Channel_Import_Export.png|300px|left|thumb|Channel Import / Export]]
 
Choose '''USB to TV''' for channeldata import or '''TV to USB''' for copying the channeldata to the USB drive.

When everything worked correct you'll find the following data on your USB drive:

kilroy@kilroy:~$ ls -la /media/USB2GB/T-CHLCIPDEUC/Clone/
total 744
drwx------ 2 kilroy kilroy 4096 1980-01-01 00:00 .
drwx------ 3 kilroy kilroy 4096 1980-01-01 00:00 ..
-rwxr-xr-x 1 kilroy kilroy 1920 1980-01-01 00:00 Clone.dat
-rwxr-xr-x 1 kilroy kilroy 20 1980-01-01 00:00 FineTune
-rwxr-xr-x 1 kilroy kilroy 1092 1980-01-01 00:00 FineTune_Digital
-rwxr-xr-x 1 kilroy kilroy 124 1980-01-01 00:00 LNBSettingsDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-AirA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-AirD
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-CableA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-CableD
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 map-ChKey
-rwxr-xr-x 1 kilroy kilroy 144000 1980-01-01 00:00 map-SateD
-rwxr-xr-x 1 kilroy kilroy 3184 1980-01-01 00:00 PTCCABLE
-rwxr-xr-x 1 kilroy kilroy 584 1980-01-01 00:00 SatDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 5616 1980-01-01 00:00 ServiceProviders
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 TransponderDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 88 1980-01-01 00:00 TSIDList
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 UserTransponderDataBase.dat

Now you can edit the channel list (for the moment only map-CableD for DVB-C) stored on the drive using SamyGO ChanEdit.

After that just use the same procedure to import the list again.

==Downloading and Installing==
Download the SamyGO ChanEdit (and required Java library for you OS) from [http://download.samygo.tv/SamyGO%20Applications/ SamyGO Applications] file download area.

===Ubuntu 9.10 amd64===

You have to download the files '''SamyGO ChanEdit-v0.31.tar.bz2''' and '''SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2''' 
Ubuntu 9.10 is comes with openjdk-6-jre but you can also install Java from SUN (recommended).

# sudo aptitude install sun-java6-jre
[ -d ~/bin ] || mkdir ~/bin
tar xjf Downloads/SamyGO\ ChanEdit-v0.31.tar.bz2 -C ~/bin/
tar xjf Downloads/SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2 -C ~/bin/SamyGO\ ChanEdit-v0.31/
ln -s ~/bin/SamyGO\ ChanEdit-v0.31/SamyGoChanEd.jar Desktop/SamyGoChanEd.jar

Right click at the SamyGoChanEd.jar icon and select '''Properties -> Open With:''' ''OpenJDK Java 6 Runtime'' (or ''Sun Java 6 Runtime'')

===Microsoft Windows===
Note: The java engine must be a 32 bit version of the Java engine, the reason for this is that the swt.jar file only exists as a 32 bit build.
This mean that you have reinstall or parallel install a 32 bit Java engine if you have the 64 bit version.

To execute the channel editor you need two parts, the channel editor program itself and a support library called swt.
The channel editor program can be found here [http://download.samygo.tv/SamyGO%20PC%20Applications SamyGO ChanEdit]

The SWT library can either be downloaded directly from [http://www.eclipse.org/swt http://www.eclipse.org/swt] or from [http://download.samygo.tv/SamyGO%20PC%20Applications/SamyGO%20ChanEdit%20SWT%20Libraries SamyGo].

Unpack the downloaded files and place the both .jar files,SamyGoChanEd.jar and swt.jar, in the same director.
These two jar files are the only files needed, there are other files and content in the downloaded zip/gz/bz2 files but they are not needed

Open a command prompt and enter

'''<tt>java -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

The following example is on a Windows 7 installation, the java.exe file might be in a different place depending on the installation and operating system.
If you get an error message saying that java is not a commando then you need to give the full path to the Java engine, like this

'''<tt>"c:\Program Files (x86)\Java\jdk1.6.0_23\bin\java.exe" -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

Of course it is possible to create a link on the desktop and execute the same command line.

Added by [[User:Stefanth|Stefanth]]

==Modifying Channel List==
You can modify your Channel list via SamyGO ChanEdit.

The files are under your USB at T-CHxxDEUC/Clone directory.
With Version 0.31 currently only map-CableD for digital Cable Channels is editable.

<center>[[File:SamyGO ChanEdit.png]]</center>

Afterwards you can import the channel list to TV from the USB stick.

SamyGO ChanEdit - Chanel Editor

2011-01-11T08:11:43Z

Stefanth: /* Microsoft Windows */

=SamyGO ChanEdit=

With SamyGO ChanEdit you can edit your channel list of your Samsung TV Set using any Computer able to run a Java VM supporting SWT. This makes moving channels around a lot easier. Also the list can be extended by channels that are not found by the channel search engine. For example Sky.de interactive channels, which the editor can add automatically when a list containing Sky.de channels is loaded.

==Channel Import/Export Menu==
First you have to connect a USB drive with a FAT/FAT32 filesystem to your TV.

When the TV is switched ON press '''Volume Down''' [[File:Volume_down_key.png|30px]] once and then press '''the Enter [[File:Enter_key.png|30pxâ]] button for 10 seconds'''. This will display the "Channel Import / Export" Menu.

If this doesn't work, check that "Speaker Select" in "Sound Menu" is set to "TV Speaker". Anynet+ (HDMI-CEC) should be disabled.
[[File:Channel_Import_Export.png|300px|left|thumb|Channel Import / Export]]
 
Choose '''USB to TV''' for channeldata import or '''TV to USB''' for copying the channeldata to the USB drive.

When everything worked correct you'll find the following data on your USB drive:

kilroy@kilroy:~$ ls -la /media/USB2GB/T-CHLCIPDEUC/Clone/
total 744
drwx------ 2 kilroy kilroy 4096 1980-01-01 00:00 .
drwx------ 3 kilroy kilroy 4096 1980-01-01 00:00 ..
-rwxr-xr-x 1 kilroy kilroy 1920 1980-01-01 00:00 Clone.dat
-rwxr-xr-x 1 kilroy kilroy 20 1980-01-01 00:00 FineTune
-rwxr-xr-x 1 kilroy kilroy 1092 1980-01-01 00:00 FineTune_Digital
-rwxr-xr-x 1 kilroy kilroy 124 1980-01-01 00:00 LNBSettingsDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-AirA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-AirD
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-CableA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-CableD
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 map-ChKey
-rwxr-xr-x 1 kilroy kilroy 144000 1980-01-01 00:00 map-SateD
-rwxr-xr-x 1 kilroy kilroy 3184 1980-01-01 00:00 PTCCABLE
-rwxr-xr-x 1 kilroy kilroy 584 1980-01-01 00:00 SatDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 5616 1980-01-01 00:00 ServiceProviders
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 TransponderDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 88 1980-01-01 00:00 TSIDList
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 UserTransponderDataBase.dat

Now you can edit the channel list (for the moment only map-CableD for DVB-C) stored on the drive using SamyGO ChanEdit.

After that just use the same procedure to import the list again.

==Downloading and Installing==
Download the SamyGO ChanEdit (and required Java library for you OS) from [http://download.samygo.tv/SamyGO%20Applications/ SamyGO Applications] file download area.

===Ubuntu 9.10 amd64===

You have to download the files '''SamyGO ChanEdit-v0.31.tar.bz2''' and '''SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2''' 
Ubuntu 9.10 is comes with openjdk-6-jre but you can also install Java from SUN (recommended).

# sudo aptitude install sun-java6-jre
[ -d ~/bin ] || mkdir ~/bin
tar xjf Downloads/SamyGO\ ChanEdit-v0.31.tar.bz2 -C ~/bin/
tar xjf Downloads/SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2 -C ~/bin/SamyGO\ ChanEdit-v0.31/
ln -s ~/bin/SamyGO\ ChanEdit-v0.31/SamyGoChanEd.jar Desktop/SamyGoChanEd.jar

Right click at the SamyGoChanEd.jar icon and select '''Properties -> Open With:''' ''OpenJDK Java 6 Runtime'' (or ''Sun Java 6 Runtime'')

===Microsoft Windows===
Note: You need a 32 bit version of the Java engine, the reason for this is that the swt.jar file only exists as a 32 bit build.
This mean that you have reinstall or parallel install a 32 bit Java engine if you have the 64 bit version.

To execute the channel editor you need two parts, the channel editor program itself and a support library called swt.
The channel editor program can be found here [http://download.samygo.tv/SamyGO%20PC%20Applications SamyGO ChanEdit]

The SWT library can either be downloaded directly from [http://www.eclipse.org/swt http://www.eclipse.org/swt] or from [http://download.samygo.tv/SamyGO%20PC%20Applications/SamyGO%20ChanEdit%20SWT%20Libraries SamyGo].

Unpack the downloaded files and place the both .jar files,SamyGoChanEd.jar and swt.jar, in the same director.
These two jar files are the only files needed, there are other files and content in the downloaded zip/gz/bz2 files but they are not needed

Open a command prompt and enter

'''<tt>java -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

The following example is on a Windows 7 installation, the java.exe file might be in a different place depending on the installation and operating system.
If you get an error message saying that java is not a commando then you need to give the full path to the Java engine, like this

'''<tt>"c:\Program Files (x86)\Java\jdk1.6.0_23\bin\java.exe" -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

Of course it is possible to create a link on the desktop and execute the same command line.

Added by [[User:Stefanth|Stefanth]]

==Modifying Channel List==
You can modify your Channel list via SamyGO ChanEdit.

The files are under your USB at T-CHxxDEUC/Clone directory.
With Version 0.31 currently only map-CableD for digital Cable Channels is editable.

<center>[[File:SamyGO ChanEdit.png]]</center>

Afterwards you can import the channel list to TV from the USB stick.

SamyGO ChanEdit - Chanel Editor

2011-01-11T08:09:05Z

Stefanth: /* Ubuntu 9.10 amd64 */

=SamyGO ChanEdit=

With SamyGO ChanEdit you can edit your channel list of your Samsung TV Set using any Computer able to run a Java VM supporting SWT. This makes moving channels around a lot easier. Also the list can be extended by channels that are not found by the channel search engine. For example Sky.de interactive channels, which the editor can add automatically when a list containing Sky.de channels is loaded.

==Channel Import/Export Menu==
First you have to connect a USB drive with a FAT/FAT32 filesystem to your TV.

When the TV is switched ON press '''Volume Down''' [[File:Volume_down_key.png|30px]] once and then press '''the Enter [[File:Enter_key.png|30pxâ]] button for 10 seconds'''. This will display the "Channel Import / Export" Menu.

If this doesn't work, check that "Speaker Select" in "Sound Menu" is set to "TV Speaker". Anynet+ (HDMI-CEC) should be disabled.
[[File:Channel_Import_Export.png|300px|left|thumb|Channel Import / Export]]
 
Choose '''USB to TV''' for channeldata import or '''TV to USB''' for copying the channeldata to the USB drive.

When everything worked correct you'll find the following data on your USB drive:

kilroy@kilroy:~$ ls -la /media/USB2GB/T-CHLCIPDEUC/Clone/
total 744
drwx------ 2 kilroy kilroy 4096 1980-01-01 00:00 .
drwx------ 3 kilroy kilroy 4096 1980-01-01 00:00 ..
-rwxr-xr-x 1 kilroy kilroy 1920 1980-01-01 00:00 Clone.dat
-rwxr-xr-x 1 kilroy kilroy 20 1980-01-01 00:00 FineTune
-rwxr-xr-x 1 kilroy kilroy 1092 1980-01-01 00:00 FineTune_Digital
-rwxr-xr-x 1 kilroy kilroy 124 1980-01-01 00:00 LNBSettingsDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-AirA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-AirD
-rwxr-xr-x 1 kilroy kilroy 28000 1980-01-01 00:00 map-CableA
-rwxr-xr-x 1 kilroy kilroy 248000 1980-01-01 00:00 map-CableD
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 map-ChKey
-rwxr-xr-x 1 kilroy kilroy 144000 1980-01-01 00:00 map-SateD
-rwxr-xr-x 1 kilroy kilroy 3184 1980-01-01 00:00 PTCCABLE
-rwxr-xr-x 1 kilroy kilroy 584 1980-01-01 00:00 SatDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 5616 1980-01-01 00:00 ServiceProviders
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 TransponderDataBase.dat
-rwxr-xr-x 1 kilroy kilroy 88 1980-01-01 00:00 TSIDList
-rwxr-xr-x 1 kilroy kilroy 4 1980-01-01 00:00 UserTransponderDataBase.dat

Now you can edit the channel list (for the moment only map-CableD for DVB-C) stored on the drive using SamyGO ChanEdit.

After that just use the same procedure to import the list again.

==Downloading and Installing==
Download the SamyGO ChanEdit (and required Java library for you OS) from [http://download.samygo.tv/SamyGO%20Applications/ SamyGO Applications] file download area.

===Ubuntu 9.10 amd64===

You have to download the files '''SamyGO ChanEdit-v0.31.tar.bz2''' and '''SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2''' 
Ubuntu 9.10 is comes with openjdk-6-jre but you can also install Java from SUN (recommended).

# sudo aptitude install sun-java6-jre
[ -d ~/bin ] || mkdir ~/bin
tar xjf Downloads/SamyGO\ ChanEdit-v0.31.tar.bz2 -C ~/bin/
tar xjf Downloads/SamyGoChanEd_lib-Linux-GTK-x86_64.tar.bz2 -C ~/bin/SamyGO\ ChanEdit-v0.31/
ln -s ~/bin/SamyGO\ ChanEdit-v0.31/SamyGoChanEd.jar Desktop/SamyGoChanEd.jar

Right click at the SamyGoChanEd.jar icon and select '''Properties -> Open With:''' ''OpenJDK Java 6 Runtime'' (or ''Sun Java 6 Runtime'')

===Microsoft Windows===
Note: You need a 32 bit version of the Java engine, the reason for this is that the swt.jar file only exists as a 32 bit build.
This mean that you have reinstall or parallel install a 32 bit Java engine if you have the 64 bit version.

To execute the channel editor you need two parts, the channel editor program itself and a support library called swt.
The channel editor program can be found here [http://download.samygo.tv/SamyGO%20PC%20Applications SamyGO ChanEdit]

The SWT library can either be downloaded directly from [http://www.eclipse.org/swt http://www.eclipse.org/swt] or from [http://download.samygo.tv/SamyGO%20PC%20Applications/SamyGO%20ChanEdit%20SWT%20Libraries SamyGo].

Unpack the downloaded files and place the both .jar files,SamyGoChanEd.jar and swt.jar, in the same directory,
you only need these jar files, there are other files and content in the downloaded zip/gz/bz2 files but they are not needed

Open a command prompt and enter

'''<tt>java -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

The following example is on a Windows 7 installation, the java.exe file might be in a different place depending on the installation and operating system.
If you get an error message saying that java is not a commando then you need to give the full path to the Java engine, like this

'''<tt>"c:\Program Files (x86)\Java\jdk1.6.0_23\bin\java.exe" -classpath .;swt.jar;SamyGoChanEd.jar gui.Main</tt>'''

Of course it is possible to create a link on the desktop and execute the same command line.

==Modifying Channel List==
You can modify your Channel list via SamyGO ChanEdit.

The files are under your USB at T-CHxxDEUC/Clone directory.
With Version 0.31 currently only map-CableD for digital Cable Channels is editable.

<center>[[File:SamyGO ChanEdit.png]]</center>

Afterwards you can import the channel list to TV from the USB stick.