Difference between revisions of "Boot from USB using u-boot"
m (→Prepare USB drive (and optionally TFTP)) |
|||
(38 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
'''Note: This instruction apply and booting only to TV with firmwares listed below!''' | '''Note: This instruction apply and booting only to TV with firmwares listed below!''' | ||
− | T- | + | T-CHL7DEUC, T-CHEAUSC, T-CHL7DAUC (B650 and B750 series) |
− | |||
− | |||
'''This is for advanced users and developers only.''' | '''This is for advanced users and developers only.''' | ||
Line 13: | Line 11: | ||
* Serial connection | * Serial connection | ||
* Usb disk drive or pen drive (at least 256MB) | * Usb disk drive or pen drive (at least 256MB) | ||
− | * TFTP server outside TV on some host in case | + | * TFTP server outside TV on some host in case if you prefer load kernel from network (Do this only if you want faster kernel load or lack network). |
− | * Regular Linux based system to prepare usb disk/pen drive | + | * Regular Linux based system to prepare usb disk/pen drive (disk drive is preffered for speed) |
− | * Builded rootfs image | + | * Builded rootfs image and kernel. |
+ | |||
---- | ---- | ||
+ | '''Follow steps:''' | ||
+ | =Build OE kernel and rootfs= | ||
− | + | Or you can build your self from recent repository: | |
− | * Build rootfs image using [http://wiki.samygo.tv/index. | + | * Build rootfs image using [http://wiki.samygo.tv/index.php5?title=SamyGO_OpenEmbedded SamyGO OE Framework]. |
− | Builded rootfs image is located in '''build-samygo/tmp/deploy/images''' directory. File name looks like '''externalboot-base-rootfs-ssdtv- | + | Builded rootfs image is located in '''build-samygo/tmp/deploy/images''' directory. File name looks like '''externalboot-base-rootfs-ssdtv-b650.tar.gz'''. |
+ | =Prepare USB drive (and optionally TFTP)= | ||
* Partition usb disk/pen drive. | * Partition usb disk/pen drive. | ||
Partition drive using '''fdisk''' or other tool. | Partition drive using '''fdisk''' or other tool. | ||
− | First | + | First partition FAT type. It will be usefull or needed if you don't have network on tv. |
− | Second partition as Linux type. | + | Second partition set as Linux type. |
Format first partition with '''mtools''' or other tool as VFAT type filesystem. | Format first partition with '''mtools''' or other tool as VFAT type filesystem. | ||
Format second partition with '''ext2fsprogs''' as ext3. | Format second partition with '''ext2fsprogs''' as ext3. | ||
− | * Unpack rootfs image to | + | * Unpack rootfs image to second partition on usb disk/pen drive with '''root''' rights |
+ | |||
+ | * '''Follow two steps below only if you want install original samsung software (script can also download image from inside booted tv, but it's preffered download and copy into rootfs)''' | ||
+ | |||
+ | * Download [http://wiki.samygo.tv/index.php5?title=Old_%26_Good_Firmwares original firmware file from samsung site] (e.g T-CHL7DEUC.exe for B65x-B75x) and place as is on /home/root | ||
+ | |||
+ | * Download LaunchCLManager.zip from [https://www.dropbox.com/s/d3imer2aj7iyb2c/LaunchCLManager.zip?dl=0 here] and place as is on /home/root | ||
+ | |||
+ | * Get proper kernel image: | ||
+ | |||
+ | Find proper kernel image in '''build-samygo/tmp/deploy/images''' or download from http://download.samygo.tv/SamyGO%20Open%20Embedded/binaries/ . | ||
+ | |||
+ | It is: '''uImage-2.6.18.8-r0-ssdtv.multi-config-multi-config-b650.bin'''. (it's for B750 too) | ||
− | + | * Put kernel image to proper place: | |
− | + | ==TFTP kernel load method== | |
− | + | Copy kernel image into root directory of TFTP service directory like '''/tftpboot''' directory, or for NAS it is on '''/opt/tftpboot''' . | |
− | + | And rename kernel image to '''uImage''' . | |
− | + | ==USB kernel load method== | |
− | + | Put kernel image on FAT partition (first). | |
− | + | And rename kernel image to '''uImage''' . | |
− | + | =U-Boot shell= | |
+ | * Enable [http://wiki.samygo.tv/index.php5?title=Enable_Serial_Console_on_non_CI%2B_Devices serial debug console]. | ||
− | setenv ipaddr 192.168.1.100;setenv gatewayip 192.168.1.1;setenv serverip 192.168.1. | + | * Enter [http://wiki.samygo.tv/index.php5?title=Getting_access_to_u-boot u-boot] prompt shell. |
+ | |||
+ | =Booting TV= | ||
+ | You can load and boot kernel from USB or TFTP: | ||
+ | |||
+ | ==TFTP== | ||
+ | Set network variables first: | ||
+ | |||
+ | setenv ipaddr 192.168.1.100;setenv gatewayip 192.168.1.1;setenv serverip 192.168.1.200 | ||
where first IP is TV, second gateway is not important in this case, third is address of TFTP server. | where first IP is TV, second gateway is not important in this case, third is address of TFTP server. | ||
− | Boot linux kernel | + | Boot linux kernel over TFTP and rootfs from USB ext3 partition: |
setenv bootargs root=/dev/sda2 console=ttyS1;tftp;bootm | setenv bootargs root=/dev/sda2 console=ttyS1;tftp;bootm | ||
− | Boot linux kernel | + | ==USB== |
+ | Boot linux kernel from USB FAT partition, rootfs from USB ext3 partition: | ||
− | setenv bootargs root=/dev/sda2 console=ttyS1;usb start;fatload usb 0 61000000 uImage;bootm | + | setenv bootargs root=/dev/sda2 rootdelay=1 console=ttyS1;usb start;fatload usb 0 61000000 uImage;bootm |
where /dev/sda2 is linux rootfs. | where /dev/sda2 is linux rootfs. | ||
+ | ==NFS== | ||
+ | If you have NFS server on your home network working, you can boot file system for TV (rootfs) and kernel from OE over NFS! | ||
+ | |||
+ | ==='''Prepare rootfs and kernel'''=== | ||
+ | * [[#Prepare_USB_drive_.28and_optionally_TFTP.29|Prepare USB drive]], or you can simply extract rootfs.tar.gz from OE on your NAS directory: | ||
+ | (i use /mnt/disk1/TV_rootfs for filesystem) | ||
+ | cd /mnt/disk1/TV_rootfs | ||
+ | cp /<path to>/rootfs.tar.gz /mnt/disk1/TV_rootfs | ||
+ | tar xzf rootfs.tar.gz | ||
+ | |||
+ | * Copy kernel file (uImage) to /mnt/disk1/TV_rootfs | ||
+ | cp /<path to>/uImage /mnt/disk1/TV_rootfs | ||
+ | |||
+ | * Edit exports to enable your rootfs and uImage on NFS | ||
+ | |||
+ | If you use filesystem on USB, attached to NAS: | ||
+ | root@LS-GL984:~# cat /etc/exports | ||
+ | /mnt/usbdisk3 192.168.1.100/255.255.255.0(rw,async,all_squash,anonuid=99,anongid=99,no_subtree_check) | ||
+ | |||
+ | If you use filesystem on NAS directory: | ||
+ | root@LS-GL984:~# cat /etc/exports | ||
+ | /mnt/disk1/TV_rootfs 192.168.1.100/255.255.255.0(rw,async,all_squash,anonuid=99,anongid=99,no_subtree_check) | ||
+ | where 192.168.1.100 is my TV IP. 255.255.255.0 is submask, /mnt/usbdisk3 is my USB with TVs file system, /mnt/disk1/TV_rootfs - path to rootfs and kernel on NAS directory. | ||
+ | |||
+ | ==='''Boot kernel and rootfs over network'''=== | ||
+ | * Enter to u-boot promt. | ||
+ | |||
+ | * set network variables to load kernel | ||
+ | setenv ipaddr 192.168.1.100;setenv gatewayip 192.168.1.1;setenv serverip 192.168.1.200 | ||
+ | |||
+ | * set network variables to load rootfs | ||
+ | setenv bootargs root=/dev/nfs rw nfsroot=192.168.1.200:/mnt/disk1/TV_rootfs rootpath=/home/root ip=192.168.1.102:192.168.1.200:192.168.1.1:255.255.255.0:LS-GL984:eth0:off console=ttyS1 | ||
+ | |||
+ | Now you have to boot kernel. Choose method you prefer (use NFS or TFTP) | ||
+ | |||
+ | * load kernel over NFS and start booting TV | ||
+ | nfs 0x61000000 192.168.1.200:/disk1/TV_rootfs/uImage;bootm | ||
+ | |||
+ | *load kernel over TFTP and start booting TV | ||
+ | tftp;bootm | ||
+ | |||
+ | |||
+ | P.s. structure of commandline should for NFS should be: | ||
+ | setenv bootargs root=/dev/nfs rw nfsroot=${serverip} rootpath=${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off console=ttyS1 | ||
+ | Where rootpath of OE kernel is /home/root | ||
+ | |||
+ | ==Starting main Samsung TV software== | ||
+ | |||
+ | After boot system, login over serial console as root and execute followed commands: | ||
* Install Samsung original software: | * Install Samsung original software: | ||
samsung-install.sh | samsung-install.sh | ||
+ | |||
+ | Choose your firmware version: | ||
+ | root@localhost:~# samsung-install.sh | ||
+ | --- Installer of Original Samsung Software --- | ||
+ | --- SamyGO http://www.samygo.tv --- | ||
+ | |||
+ | Select proper firmware for your TV: | ||
+ | |||
+ | 1. T-CHL7DEUC | ||
+ | 2. T-CHEAUSC | ||
+ | 3. T-CHL7DAUC | ||
+ | |||
+ | Choice: | ||
+ | Wait while TV installs firmware. It is quite long process, be patient. | ||
+ | |||
* Start Samsung original software: | * Start Samsung original software: | ||
− | + | samsung-start.sh | |
+ | |||
+ | Done! | ||
− | + | '''NB!''' '''Kernel from OE does not support NAND writing and it does not help to restore bricked device.''' | |
+ | <br> | ||
+ | <br> |
Latest revision as of 06:49, 13 October 2014
Note: This instruction apply and booting only to TV with firmwares listed below!
T-CHL7DEUC, T-CHEAUSC, T-CHL7DAUC (B650 and B750 series)
This is for advanced users and developers only.
Requirements:
- Serial connection
- Usb disk drive or pen drive (at least 256MB)
- TFTP server outside TV on some host in case if you prefer load kernel from network (Do this only if you want faster kernel load or lack network).
- Regular Linux based system to prepare usb disk/pen drive (disk drive is preffered for speed)
- Builded rootfs image and kernel.
Follow steps:
Contents
Build OE kernel and rootfs
Or you can build your self from recent repository:
- Build rootfs image using SamyGO OE Framework.
Builded rootfs image is located in build-samygo/tmp/deploy/images directory. File name looks like externalboot-base-rootfs-ssdtv-b650.tar.gz.
Prepare USB drive (and optionally TFTP)
- Partition usb disk/pen drive.
Partition drive using fdisk or other tool.
First partition FAT type. It will be usefull or needed if you don't have network on tv. Second partition set as Linux type.
Format first partition with mtools or other tool as VFAT type filesystem. Format second partition with ext2fsprogs as ext3.
- Unpack rootfs image to second partition on usb disk/pen drive with root rights
- Follow two steps below only if you want install original samsung software (script can also download image from inside booted tv, but it's preffered download and copy into rootfs)
- Download original firmware file from samsung site (e.g T-CHL7DEUC.exe for B65x-B75x) and place as is on /home/root
- Download LaunchCLManager.zip from here and place as is on /home/root
- Get proper kernel image:
Find proper kernel image in build-samygo/tmp/deploy/images or download from http://download.samygo.tv/SamyGO%20Open%20Embedded/binaries/ .
It is: uImage-2.6.18.8-r0-ssdtv.multi-config-multi-config-b650.bin. (it's for B750 too)
- Put kernel image to proper place:
TFTP kernel load method
Copy kernel image into root directory of TFTP service directory like /tftpboot directory, or for NAS it is on /opt/tftpboot .
And rename kernel image to uImage .
USB kernel load method
Put kernel image on FAT partition (first).
And rename kernel image to uImage .
U-Boot shell
- Enable serial debug console.
- Enter u-boot prompt shell.
Booting TV
You can load and boot kernel from USB or TFTP:
TFTP
Set network variables first:
setenv ipaddr 192.168.1.100;setenv gatewayip 192.168.1.1;setenv serverip 192.168.1.200
where first IP is TV, second gateway is not important in this case, third is address of TFTP server.
Boot linux kernel over TFTP and rootfs from USB ext3 partition:
setenv bootargs root=/dev/sda2 console=ttyS1;tftp;bootm
USB
Boot linux kernel from USB FAT partition, rootfs from USB ext3 partition:
setenv bootargs root=/dev/sda2 rootdelay=1 console=ttyS1;usb start;fatload usb 0 61000000 uImage;bootm
where /dev/sda2 is linux rootfs.
NFS
If you have NFS server on your home network working, you can boot file system for TV (rootfs) and kernel from OE over NFS!
Prepare rootfs and kernel
- Prepare USB drive, or you can simply extract rootfs.tar.gz from OE on your NAS directory:
(i use /mnt/disk1/TV_rootfs for filesystem)
cd /mnt/disk1/TV_rootfs cp /<path to>/rootfs.tar.gz /mnt/disk1/TV_rootfs tar xzf rootfs.tar.gz
- Copy kernel file (uImage) to /mnt/disk1/TV_rootfs
cp /<path to>/uImage /mnt/disk1/TV_rootfs
- Edit exports to enable your rootfs and uImage on NFS
If you use filesystem on USB, attached to NAS:
root@LS-GL984:~# cat /etc/exports /mnt/usbdisk3 192.168.1.100/255.255.255.0(rw,async,all_squash,anonuid=99,anongid=99,no_subtree_check)
If you use filesystem on NAS directory:
root@LS-GL984:~# cat /etc/exports /mnt/disk1/TV_rootfs 192.168.1.100/255.255.255.0(rw,async,all_squash,anonuid=99,anongid=99,no_subtree_check)
where 192.168.1.100 is my TV IP. 255.255.255.0 is submask, /mnt/usbdisk3 is my USB with TVs file system, /mnt/disk1/TV_rootfs - path to rootfs and kernel on NAS directory.
Boot kernel and rootfs over network
- Enter to u-boot promt.
- set network variables to load kernel
setenv ipaddr 192.168.1.100;setenv gatewayip 192.168.1.1;setenv serverip 192.168.1.200
- set network variables to load rootfs
setenv bootargs root=/dev/nfs rw nfsroot=192.168.1.200:/mnt/disk1/TV_rootfs rootpath=/home/root ip=192.168.1.102:192.168.1.200:192.168.1.1:255.255.255.0:LS-GL984:eth0:off console=ttyS1
Now you have to boot kernel. Choose method you prefer (use NFS or TFTP)
- load kernel over NFS and start booting TV
nfs 0x61000000 192.168.1.200:/disk1/TV_rootfs/uImage;bootm
- load kernel over TFTP and start booting TV
tftp;bootm
P.s. structure of commandline should for NFS should be:
setenv bootargs root=/dev/nfs rw nfsroot=${serverip} rootpath=${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off console=ttyS1
Where rootpath of OE kernel is /home/root
Starting main Samsung TV software
After boot system, login over serial console as root and execute followed commands:
- Install Samsung original software:
samsung-install.sh
Choose your firmware version:
root@localhost:~# samsung-install.sh --- Installer of Original Samsung Software --- --- SamyGO http://www.samygo.tv --- Select proper firmware for your TV: 1. T-CHL7DEUC 2. T-CHEAUSC 3. T-CHL7DAUC Choice:
Wait while TV installs firmware. It is quite long process, be patient.
- Start Samsung original software:
samsung-start.sh
Done!
NB! Kernel from OE does not support NAND writing and it does not help to restore bricked device.