diff options
Diffstat (limited to 'release-notes/Colibri_VF_LinuxReleaseNotesV2.x.txt')
| -rw-r--r-- | release-notes/Colibri_VF_LinuxReleaseNotesV2.x.txt | 206 |
1 files changed, 80 insertions, 126 deletions
diff --git a/release-notes/Colibri_VF_LinuxReleaseNotesV2.x.txt b/release-notes/Colibri_VF_LinuxReleaseNotesV2.x.txt index 8c34594..4085223 100644 --- a/release-notes/Colibri_VF_LinuxReleaseNotesV2.x.txt +++ b/release-notes/Colibri_VF_LinuxReleaseNotesV2.x.txt @@ -3,12 +3,83 @@ Release Notes: Linux Image V2.x for Colibri VF50/VF61 ****************************************************** Contents: -- U-Boot 2014.10 boot loader -- Linux 3.18.5 kernel -- Angstrom/OpenEmbedded/Yocto 2014.06/daisy/1.6 based root file system, using +- U-Boot 2015.04 boot loader +- Linux 4.0.2 kernel +- Angstrom/OpenEmbedded/Yocto 2014.12/dizzy/1.7 based root file system, using LXDE desktop environment -==> Flashing instructions can be found at the very bottom of this release notes +==> Flashing instructions can be found on the Toradex developer article: +http://developer.toradex.com/knowledge-base/flashing-linux-on-vybrid-modules + +******************************************************************************** +Linux Image V2.4 Beta 1 (May 18, 2015) +- U-Boot: + - update to U-Boot 2015.04 + - new standard NAND ECC format which is able to fix up to 32-errors per page + - enable ONFI detection, allows to retrieve more details about the NAND chip + - improve NAND read performance by supporting OOB only read + - improve NAND write performance by removing unnecessary page reads on write + - add generic Toradex config block handling, print exact product description, + board revision and serial number to the console + - create device-tree properties which make board information available from + within Linux userspace through procfs (/proc/device-tree/serial-number, + toradex,board-rev and toradex,product-id) + - add command to restore Toradex config block ("cfgblock create") + - add "bmode" command which allows to select a specific boot device + - add display (DCU) support along with some default modes, display the Toradex + logo at VGA resolution by default + - add GPIO support through "gpio" command + - enable USB power for host port explicitly (fixes USB host support on Iris + and Viola Carrier Board) +- Linux kernel: + - update to 4.0.2 stable Linux kernel + - add audio capture support on Colibri VF61 (AC97) + - use configfs for USB Gadget configuration + - improve NAND read performance by supporting OOB only read + - improve NAND write performance by removing unnecessary page reads on write + - export Vybrid SoC information such as ROM revision and unique ID through + SoC bus (/sys/devices/soc0/machine, family, soc_id and revision) +- Linux user-space: + - update OpenEmbedded from daisy to dizzy: + - glibc 2.20 (instead of eglibc) + - systemd 2.18 + - Xorg 1.14.7 + - updated various LXDE packages to newer versions + - use libusbg to configure USB Gadget through configfs, provides a default + configuration which configures a serial connection using CDC ACM protocol + - enable a serial console on the tty provided by USB Gadget CDC ACM (ttyGS0 + on module side, typically ttyACM0 on host side) + - replace full NTP daemon with systemd's NTP client only systemd-timesyncd + - blacklist USB RNDIS for connman, use systemd-networkd to configure RDNIS + network interface (new standard IP of the module is 192.168.11.1!) + - enable BusyBox resize command to resize the terminal on serial console + - remove e2fsprogs for VF default image (image feature ext2) + - fix GPIOConfig CPU detection on Colibri VF50 (GPIOConfig V1.3) + +- sources git.toradex.com tag Colibri_VF_LinuxImageV2.4Beta1_20150518 + - repository linux-toradex branch toradex_vf_4.0 + - repository u-boot-toradex branch 2015.04-toradex + +Note: +- mount point names changed from /media/<block device name> to /media<label> +- The kernel requires now the device tree from within the root filesystem to + boot. Board customisation within code are for most use cases not necessary. + For custom carrier boards, it is recommended to create a customised + device tree file and deploy it in the root filesystems /boot directory. + U-Boot reads the device tree according to the following name scheme: + => ${soc}-colibri-${fdt_board}.dtb + + Hence, a custom carrier board needs to set the fdt_board variable accordingly + and would name the device tree files using the SoC prefix depending on the + supported module type: + => vf500-colibri-mycarrier.dtb + => vf610-colibri-mycarrier.dtb + +Known Issues: +- If the module does not boot, remove all displays connected to HSYNC, VSYNC and reset. + (This has been observed on an Evaluation Board V2.1C) +- Downgrade is not possible through "run update" due to NAND ECC layout changes + refer to the flashing instruction article to flash the module from scratch ******************************************************************************** Linux Image V2.3 Beta 7 (February 03, 2015) @@ -379,7 +450,6 @@ Notes: - user account: root with empty password - UBIFS flash root file system - opkg package manager -- Linux host used for update preparation requires proper 32-bit execution environment (e.g. install ia32-libs on 64-bit Ubuntu) and awk (e.g. install gawk on Ubuntu) Working on latest image: - U-Boot boot loader @@ -393,6 +463,7 @@ Working on latest image: - module type auto detection - USB storage as host on USB host port - USB device firmware upgrade (DFU) as device on USB OTG port + - framebuffer support - Linux kernel - GPIOlib /sys/class/gpio - temperature sensor /sys/bus/iio/devices/iio\:device0/in_temp_input @@ -411,6 +482,7 @@ Working on latest image: - serial number and board revision - watchdog - USB host port + - USB webcam - USB raw HID device /dev/hidrawX - USB device Ethernet RNDIS - USB device CDCACM @@ -429,134 +501,16 @@ Working on latest image: Not working or not tested: - U-Boot boot loader - USB keyboard - - framebuffer support - Linux kernel - Colibri VF61: AC97 analogue audio capture - USB audio driver - - USB webcam - automatic USB device/host detection aka OTG support - IrDA - RS-422/485 - optional parallel camera interface ****************************************************************************** -NAND Boot: Colibri VF50 V1.0a and V1.1a, Colibri VF61 V1.0b and V1.1b (Sample) -****************************************************************************** +Flashing instruction have been moved to the Toradex developer article: +http://developer.toradex.com/knowledge-base/flashing-linux-on-vybrid-modules -If the boot loader in NAND got corrupted UART/SD card boot as described further -down can be used as a means of recovery. - -Initial Preparation: -- download and extract Colibri_VF_LinuxImageVx.yz.tar.bz2 package with root - permissions -- use any VFAT formatted SD, uSD card or USB flash drive with at least 100 MB - of free space -- optionally format the SD or uSD card using the format_sd.sh script - (warning: everything on the SD card will be erased!) -- run update.sh script with optional -o argument pointing to mount point of - above mentioned SD card or USB flash drive -- insert prepared SD card into SD card/MMC SDIO-socket (X15/X10 on Iris) - -Flash NAND: -- EvalBoard V3.1a - - 115200 baud serial debug console on UART_A - (lower X25 resp. X27 depending on JP17/19) without any handshake -- Iris V1.1a - - 115200 baud serial debug console on UART_A - (X13) without any handshake -- apply power or reset -- hit any key to stop auto booting -- use 'run setupdate' commands - (for old U-Boot versions 'mmc part 0 ; fatload mmc 0:1 $loadaddr flash_mmc.img ;source $loadaddr') -- use 'run update' command - -Boot from NAND: -- EvalBoard V3.1a/V3.2a or Iris V1.1a -- above given update command should automatically perform a soft re-boot upon - successful completion -- optionally power cycle -- upon first boot post-install scripts are run which take some time - -******************************************************************** -UART Boot: Colibri VF50 V1.1a and Colibri VF61 V1.1b (Sample, fused) -******************************************************************** - -If the boot loader in NAND got corrupted this can be used as a means of recovery. - -For detailed description, see also: -http://developer.toradex.com/knowledge-base/vfxx-recovery-mode - -For initial Preparation, refer to NAND Boot above. -- If you have a 32-bit Linux host, replace vf_flash/imx_uart with its 32-bit - version vf_flash/imx_uart.m32 i.e. sudo mv vf_flash/imx_uart - vf_flash/imx_uart.m64; sudo ln -s vf_uart.m32 vf_flash/imx_uart -- For config block recovery, run the ./create_configblock.sh script to - generate a configblock.bin file before creating the SD card - -Connect UART_A: -- On EvalBoard V3.1a, use on-board FTDI (bridge RTS/CTS on module side, X11 5/6) -- On EvalBoard V3.2a, use on-board FTDI (do not bridge RTS/CTS!) -- On Iris, use RS232 adapter with RTS/CTS support - -Enter recovery mode: -- Turn the module off -- On EvalBoard V3.1a, press the recovery button -- On Iris, short pin 1-2 of JP1 on Iris for recovery -- Turn the module on - -Boot using UART: -- Use update.sh -d /dev/ttyUSB0 -- When RTS/CTS is shortened on module side, disable RTS/CTS on PC side by using - argument -n - -Flash NAND: -- EvalBoard V3.1a/V3.2a - - 115200 baud serial debug console on UART_A - (lower X25 resp. X27 depending on JP17/19) without any handshake -- Iris V1.1a - - 115200 baud serial debug console on UART_A - (X13) without any handshake -- hit enter to verify the U-Boot command prompt -- Use 'run setupdate' command to load update commands from SD card - - Migrating from images before V2.2: use 'run migrate_v2.1b3' to migrate - config block to new flash layout. - - To re-create boot configuration block: use 'run create_bcb' to re-create - the boot configuration block. Then, use 'run update_configblock' to flash - the config block again. - Finally, use 'run update' command to update the boot loader, kernel and - root file system. - -Note: After UART recovery, the module is resetted automatically, however when -resetting, the module enters recovery mode again. One need to power cycle the -module to start the flashed image. - -Note: This also works for non-fused modules. However, the jumper X11-37 need to -be removed. The reason is that non-fused modules determine the UART for serial -loader from SO-DIMM 105 (X11-37) and SO-DIMM 101 (X22-9), which both need to -be low in order to boot from UART0. - -*************************************************************************** -SD Card Boot: Colibri VF50 V1.0a and Colibri VF61 V1.0b (Sample, non-fused) -*************************************************************************** - -If the boot loader in NAND got corrupted this can also be used as a means of recovery. - -Initial Preparation: -- EvalBoard V3.1a - - select SD boot bootstrap option - - pull the following X8 pins down aka to ground with 1 k ohm resistors: 23 and 33 - - pull the following X8 pins up aka to 3.3 volt with 1 k ohm resistors: 21, 27, 34 and 44 -- download and extract Colibri_VF_LinuxImageVx.yz.tar.bz2 package with root permissions - -Flash SD Card: -- use any SD resp. uSD card of at least 100 MB capacity -- format and flash SD resp. uSD card using format_sd.sh script giving -d argument pointing to - device file of SD card and -f argument (warning everything will be erased) - -Boot from SD Card: -- EvalBoard V3.1a - - insert SD card into SD card/MMC SDIO-socket (X15) -- apply power -- upon first boot post-install scripts are run which takes around 2 minutes, please be patient - -Toradex, March 25, 2015 +Toradex, May 19, 2015 |