Difference between revisions of "Customizing the splash screen (Axel)"

From DAVE Developer's Wiki
Jump to: navigation, search
(3 intermediate revisions by 2 users not shown)
Line 11: Line 11:
 
!Date
 
!Date
 
!XELK version
 
!XELK version
 +
!Hardware Part Nr
 
!Notes
 
!Notes
 
|-
 
|-
|1.0.0
+
|2.3.1
 
|June 2017
 
|June 2017
|[[Axel_Embedded_Linux_Kit_(XELK)#XELK_2.3.1|XELK 2.3.1]]<br/>[[Axel_Embedded_Linux_Kit_(XELK)#XELK_3.0.0|XELK 3.0.1]]<br/>[[Axel_Embedded_Linux_Kit_(XELK)#XELK_4.0.0|XELK 4.0.0]]
+
|[[Axel_Embedded_Linux_Kit_(XELK)#XELK_2.3.1|XELK 2.3.1]]
 +
|XELK 2.0.0
 +
|
 +
|-
 +
|3.0.1
 +
|Nov 2017
 +
|[[Axel_Embedded_Linux_Kit_(XELK)#XELK_3.0.0|XELK 3.0.1]]
 +
|XELK 3.0.1
 
|
 
|
 
|-
 
|-
Line 21: Line 29:
  
 
Starting from version 2013.04-xelk-2.2.0, U-Boot for Axel SOMs provides support for a customizable splash screen. The following sections describe how to use this feature.
 
Starting from version 2013.04-xelk-2.2.0, U-Boot for Axel SOMs provides support for a customizable splash screen. The following sections describe how to use this feature.
 
The splash screen image should be a 24 bpp BMP file.
 
  
 
== Resources ==
 
== Resources ==

Revision as of 15:52, 16 November 2017

Info Box
Axel-04.png Applies to Axel Ultra
Axel-lite 02.png Applies to Axel Lite
Axel-02.png Applies to AXEL ESATTA


Introduction[edit | edit source]

Version Date XELK version Hardware Part Nr Notes
2.3.1 June 2017 XELK 2.3.1 XELK 2.0.0
3.0.1 Nov 2017 XELK 3.0.1 XELK 3.0.1

Starting from version 2013.04-xelk-2.2.0, U-Boot for Axel SOMs provides support for a customizable splash screen. The following sections describe how to use this feature.

Resources[edit | edit source]

For further details on splash screen support in U-Boot, please refer to:

Customizing the splash screen[edit | edit source]

The following U-Boot environment variables are required:

  • splashimage: RAM address where the BMP image is loaded. Please note that it must be a 32-bit aligned address with a 0x2 offset (eg: 0x20000002)
  • loadsplash: comand for loading the BMP image from the storage device (e.g flash memory) to RAM. This command is automatically run by U-Boot at startup
  • splashpos: image position (eg: splashpos=m,m, for centering the image)

Splash image in NOR SPI flash[edit | edit source]

U-Boot variables[edit | edit source]

loadsplash=run spi_loadsplash
spi_loadsplash=sf probe; sf read ${splashimage} 0x800000 ${splashsize}
splashfile=splash_image.bmp
splashimage=0x20000002
splashpos=m,m
splashsize=0x400000
loadsplashfile=tftpboot ${loadaddr} axel/${splashfile}
spi_updatesplash=sf probe; sf erase 0x800000 +${filesize}; sf write ${loadaddr} 0x800000 ${filesize}

Commands[edit | edit source]

The following commands are used to store in NOR SPI flash a BMP image loaded via tftp:

run loadsplashfile
run spi_updatesplash

Splash image in NAND flash[edit | edit source]

U-Boot variables[edit | edit source]

mtdparts=mtdparts=gpmi-nand:8M(nand-uboot),1M(nand-env1),1M(nand-env2),1M(nand-fdt),1M(nand-spare),8M(nand-kernel),4M(nand-splash),-(nand-ubi)
loadsplash=run nand_loadsplash
nand_loadsplash=nand read ${splashimage} nand-splash
splashfile=splash_image.bmp
splashimage=0x20000002
splashpos=m,m
splashsize=0x400000
loadsplashfile=tftpboot ${loadaddr} axel/${splashfile}
nand_updatesplash=nand erase.part nand-splash; nand write ${loadaddr} nand-splash ${filesize}

Please note that the NAND mtd partition for the splash image (nand-splash) is defined using the mtdparts parameter, and then referenced by the nand {erase,read,write} commands.

Commands[edit | edit source]

The following commands are used to store in NAND flash a BMP image loaded via tftp:

run loadsplashfile
run nand_updatesplash