TS-7250-V3 boot from USB: Difference between revisions

From embeddedTS Manuals
(Created page with "This board supports booting to an OS image written to a USB drive. This requires a Linux system to write the USB image. {{Note|This can be run from the board while booted to...")
 
m (Non-link text auto-updated for 2022 re-branding ( http://files.embeddedarm.com/ts-arm-sbc/ts-7250-v3-linux/distributions/debian/tsimx6ul-debian-bullseye-latest.tar.xz →‎ http://files.embeddedTS.com/ts-arm-sbc/ts-7250-v3-linux/distributions/debian/tsimx6ul-debian-bullseye-latest.tar.xz))
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
This board supports booting to an OS image written to a USB drive.  This requires a Linux system to write the USB image.
This board supports booting to an OS image written to a USB drive for developmentFor the most reliable boot we recommend eMMC boot.


{{Note|This can be run from the board while booted to eMMC, but this should not rewrite the same USB stick that the system has used to boot.  Rewriting an image while it is used as the boot media will result in a corrupt image.}}
{{Note|This can be run from the board while booted to eMMC, but this should not rewrite the same USB stick that the system has used to boot.  Rewriting an image while it is used as the boot media will result in a corrupt image.}}
This requires a Linux system to write the USB image.


Check <source lang=bash inline>lsblk</source> or <source lang=bash inline>dmesg</source> to find your USB drive, but the following examples will assume /dev/sdc.
Check <source lang=bash inline>lsblk</source> or <source lang=bash inline>dmesg</source> to find your USB drive, but the following examples will assume /dev/sdc.


<source lang=bash>
<source lang=bash>
wget http://ftp.embeddedarm.com/ftp/ts-arm-sbc/ts-7250-v3-linux/distributions/debian/tsimx6ul-debian-buster-latest.tar.bz2
wget http://files.embeddedTS.com/ts-arm-sbc/ts-7250-v3-linux/distributions/debian/tsimx6ul-debian-bullseye-latest.tar.xz
sudo sgdisk --zap-all /dev/sdc
sudo sgdisk --zap-all /dev/sdc
sudo sgdisk -n 0:0:0 -t 0:8300 /dev/sdc
sudo sgdisk -n 0:0:0 -t 0:8300 /dev/sdc
Line 12: Line 14:
sudo mkdir /mnt/usb/
sudo mkdir /mnt/usb/
sudo mount /dev/sdc1 /mnt/usb/
sudo mount /dev/sdc1 /mnt/usb/
sudo tar --numeric-owner -xf tsimx6ul-debian-buster-latest.tar.bz2 -C /mnt/usb/
sudo tar --numeric-owner -xf tsimx6ul-debian-bullseye-latest.tar.xz -C /mnt/usb/
sudo umount /mnt/usb/
sudo umount /mnt/usb/
</source>
</source>
Line 62: Line 64:
Starting kernel ...
Starting kernel ...


[    0.005353] /cpus/cpu@0 missing clock-frequency property
[    6.242409] cgroup: cgroup2: unknown option "nsdelegate,memory_recursiveprot"
[    0.909176] spi_imx 2010000.ecspi: dma setup error -19, use pio
[    6.251458] cgroup: cgroup2: unknown option "nsdelegate"
[    0.931343] spidev spi32766.0: buggy DT: spidev listed directly in DT
 
[    2.891057] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[    3.633452] cgroup: cgroup2: unknown option "nsdelegate"


Welcome to Debian GNU/Linux 10 (buster)!
Welcome to Debian GNU/Linux 11 (bullseye)
</console>
</console>

Latest revision as of 14:27, 18 January 2022

This board supports booting to an OS image written to a USB drive for development. For the most reliable boot we recommend eMMC boot.

Note: This can be run from the board while booted to eMMC, but this should not rewrite the same USB stick that the system has used to boot. Rewriting an image while it is used as the boot media will result in a corrupt image.

This requires a Linux system to write the USB image.

Check lsblk or dmesg to find your USB drive, but the following examples will assume /dev/sdc.

wget http://files.embeddedTS.com/ts-arm-sbc/ts-7250-v3-linux/distributions/debian/tsimx6ul-debian-bullseye-latest.tar.xz
sudo sgdisk --zap-all /dev/sdc
sudo sgdisk -n 0:0:0 -t 0:8300 /dev/sdc
sudo mkfs.ext4 /dev/sdc1
sudo mkdir /mnt/usb/
sudo mount /dev/sdc1 /mnt/usb/
sudo tar --numeric-owner -xf tsimx6ul-debian-bullseye-latest.tar.xz -C /mnt/usb/
sudo umount /mnt/usb/

If this USB is plugged into USB on startup, it will be chosen instead of the onboard eMMC. For example:

U-Boot 2020.01-00009-g99e2080fad (Mar 12 2020 - 08:43:22 -0700)

CPU:   Freescale i.MX6UL rev1.2 696 MHz (running at 396 MHz)
CPU:   Automotive temperature grade (-40C to 125C) at 34C
Reset cause: POR
Model: Technologic Systems i.MX6UL TS-7250-V3
Board: TS-7250-V3
DRAM:  512 MiB
MMC:   FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   
Warning: ethernet@20b4000 using MAC address from ROM
eth1: ethernet@20b4000
Warning: ethernet@2188000 using MAC address from ROM
, eth0: ethernet@2188000
Press ESC twice to abort autoboot in 1 second(s)
starting USB...
Bus usb@2184000: USB EHCI 1.00
Bus usb@2184200: USB EHCI 1.00
scanning bus usb@2184000 for devices... 1 USB Device(s) found
scanning bus usb@2184200 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

Device 0: Vendor: SanDisk  Rev: 0001 Prod: Extreme         
            Type: Removable Hard Disk
            Capacity: 59836.1 MB = 58.4 GB (122544516 x 512)
... is now current device
Scanning usb 0:1...
Found U-Boot script /boot/boot.scr
675 bytes read in 8 ms (82 KiB/s)
root ## Executing script at 82000000
5348808 bytes read in 145 ms (35.2 MiB/s)
33863 bytes read in 8 ms (4 MiB/s)
Booting Debian from usb 0:1...
root ## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Loading Device Tree to 9ef68000, end 9ef73446 ... OK

Starting kernel ...

[    6.242409] cgroup: cgroup2: unknown option "nsdelegate,memory_recursiveprot"
[    6.251458] cgroup: cgroup2: unknown option "nsdelegate"


Welcome to Debian GNU/Linux 11 (bullseye)