Page Comparison

The Flash-N-Go infrastructure (or FnG infragstructure) is a software product for NXP i.MX Edge devices created by SECO Nothern Europe. Consisting of 3 parts, Flash-N-Go Boot, Flash-N-Go System and Flash-N-Go Update it provides a convenient means of booting, flashing, testing and updating of edge devices.

What is …

What is Flash-N-Go System?

Flash-N-Go System is a non-volatile Linux distribution to aid with initial installation, production test and upgrade tasks but is limited to a small set of features. It is sometimes coined a management or recovery system. Flash-N-Go System is the backbone of the Flash-N-Go infrastructure.

It is designed to run entirely from RAM and can modify the whole non-volatile memory (eMMC). This enables the user to upgrade anything from inside a Linux based environment.

Pre-installed in the factory, Flash-N-Go System can be used in the field and during development to upgrade the devices and possibly install all components from scratch.

In production Flash-N-Go System is used conduct the production test. This de-couples the testing process from the target-end-system and makes it possible to test devices with customer specific OS configurations, with limited testing capabilities.

What is Flash-N-Go Boot?

Flash-N-Go Boot is an simple, non-interactive and open-source bootloader for i.MX6 and i.MX6ULL devices. With its condensed functionalities it is capable of initializing the RAM dynamically and booting Linux, Android, and Windows CE.

Even though it uses a serial port to output informative and debugging messages, it does not provide any kind of console interface, network drivers, display drivers or even the capability to write any data to storage media. All installation, configuration, update and other maintenance tasks usually provided by bootloaders like RedBoot, U-Boot, or Barebox are missing in Flash-N-Go Boot on purpose and provided by Flash-N-Go System instead, which is always expected to be installed on a device using Flash-N-Go Boot.

All actions necessary to boot any kind of OS are controlled by one of two simple ASCII-text boot-scripts, which Flash-N-Go Boot looks for in all FAT12/16/32-partitions on the storage medium it is booted from itself. Normally Flash-N-Go Boot looks for a boot-script called boot.cfg. In three special cases it looks for a boot-script called boot-alt.cfg, instead:

• if no boot.cfg can be found or loaded and executed successfully,

• if the SW2-button of the device is pressed during power-up or reset, or

• if some software - usually a tool called bootselect provided in any OS - has set a special flag in a particular place of non-volatile storage of the system.

Flash-N-Go Boot itself only uses the SoC-internal SRAM for its code and all runtime heap, stack, and data. All other RAM-areas of a device are free to use by boot-scripts and operating systems and as soon as Flash-N-Go Boot has started another binary executable, this in turn may also use the SoC-internal SRAM for its own purposes.

By using Flash-N-Go Boot it is possible to use different DDR-memory hardware without adapting the bootloader to the specific RAM configuration, and by this makes the SD-RAM equipment of embedded board very flexible, no pre-initialization and no matching of bootloader to board or RAM of DDR-RAM is necessary.

What is Flash-N-Go Update?

The Flash-N-Go Update software tool provides a update solution for Flash-N-Go System based i.MX6 devices.

Normally coming as USB flash drive and it uses an auto-start feature of the device to bring up the graphical update process. The available operating systems can be directly downloaded, if the device is setup up with internet access and by this provides a way to implement an OTA update behavior.

Basic Flash-N-Go Architecture

The following figure show the basic boot-up and file system structure of a Flash-N-Go Boot based system.

...

The Flash-N-Go architecture consists of the bootloader, the recovery, device specific data and the target operating system. Flash-N-Go System and the target system may use the device-specific data to initialize and configure hardware interfaces like display, touch and network interfaces.

The first stage bootloader Flash-N-Go Boot initializes the board and decides which OS needs to be booted. The decision is based on the availability of boot-able systems, the hardware boot-mode switch and the internal bootselect setting. The internal boot select setting is stored on the battery backed RTC, and thus independent of the non-volatile Flash memory (eMMC), but may be impacted by changing the battery.

A regular target OS is booted iff:

1. A FAT32 partition is available containing a valid boot.cfg file

2. The bootselect setting set to "regular" or "initialized".

3. The boot mode button is not pressed.

Otherwise the Flash-N-Go Boot bootloader will try to load the Flash-N-Go System that resides in a FAT partition containing the boot-alt.cfg file.

...

...

The Flash-N-Go infrastructure (or FnG infrastructure) is a software product for NXP i.MX Edge devices created by SECO. Consisting of three parts: Flash-N-Go Boot, Flash-N-Go System and Flash-N-Go Update; it provides a convenient way of booting, flashing, testing and updating edge devices. FnG Infrastructure is available on the following series of devices:

• Products of the SAN* family of devices with i.MX6: SANTARO, SANTOKA, SANTINO,…

• NALLINO with i.MX6ULL

• TANARO with i.MX8MM

...

What is …

Flash-N-Go System?

Flash-N-Go System is a versatile Linux distribution to aid with the initial installation, production test and upgrade tasks but is limited to a small set of features. It is sometimes referred to as a management or recovery system. Flash-N-Go System is the backbone of the Flash-N-Go infrastructure.

It is designed to run entirely from RAM and can modify the whole non-volatile memory (eMMC). This enables the user to upgrade anything from inside a Linux based environment.

Pre-installed in the factory, Flash-N-Go System can be used in the field and during development to upgrade the devices and possibly install all components from scratch.

In production, Flash-N-Go System is used to conduct the production test. This de-couples the testing process from the target-end system and makes it possible to test devices with customer-specific OS configurations, with limited testing capabilities.

Flash-N-Go Boot?

Flash-N-Go Boot is a simple, non-interactive and open-source bootloader for i.MX6 and i.MX6ULL devices. With its condensed functionalities, it is capable of initializing the RAM dynamically and booting Linux, Android, and Windows CE.

Even though it uses a serial port to output informative and debugging messages, it does not provide any kind of console interface, network drivers, display drivers or even the capability to write any data to storage media. All installation, configuration, update and other maintenance tasks usually provided by bootloaders like RedBoot, U-Boot, or Barebox are missing in Flash-N-Go Boot on purpose and provided by Flash-N-Go System instead, which is always expected to be installed on a device using Flash-N-Go Boot.

All actions necessary to boot any kind of OS are controlled by one of two simple ASCII-text boot-scripts, which Flash-N-Go Boot looks for in all FAT12/16/32-partitions on the storage medium it is booted from itself. Normally Flash-N-Go Boot looks for a boot-script called boot.cfg. In three special cases it looks for a boot-script called boot-alt.cfg, instead:

• if no boot.cfg can be found or loaded and executed successfully,

• if the bootmode-button of the device is pressed during power-up or reset, or

• if some software - usually a tool called bootselect provided in any OS - has set a special flag in a particular place of non-volatile storage of the system.

Flash-N-Go Boot itself only uses the SoC-internal SRAM for its code and all runtime heap, stack, and data. All other RAM-areas of a device are free to use by boot-scripts and operating systems and as soon as Flash-N-Go Boot has started another binary executable, this, in turn, may also use the SoC-internal SRAM for its own purposes.

By using Flash-N-Go Boot it is possible to use different DDR-memory hardware without adapting the bootloader to the specific RAM configuration, and this makes the SD-RAM equipment of embedded board very flexible. Pre-initialization and matching of the bootloader to board or RAM isn’t necessary.

Flash-N-Go Update?

The Flash-N-Go Update software tool provides an all-in-one update solution for Flash-N-Go System based i.MX6 devices.

Normally coming as a USB flash drive, it uses an auto-start feature of the device to bring up the graphical update process. The available operating systems can be directly downloaded if the device is setup up with internet access and by this provides a way to implement an OTA update behaviour.

Flash-N-Go Update is deprecated and is no longer being supported by SECO.

...

Basic Flash-N-Go Architecture

The following figure shows the basic boot-up and file system structure of a Flash-N-Go Boot based system.

...

The Flash-N-Go architecture consists of the bootloader, the recovery, device-specific data and the target operating system. Flash-N-Go System and the target system may use the device-specific data to initialize and configure hardware interfaces like display, touch and network interfaces.

The first stage bootloader Flash-N-Go Boot initializes the board and decides which OS needs to be booted. The decision is based on the availability of boot-able systems, the hardware boot-mode switch and the internal bootselect setting. The internal boot select setting is stored on the battery-backed RTC, and thus independent of the non-volatile Flash memory (eMMC), but may be impacted by changing the battery.

A regular target OS is booted iff:

1. A FAT32 partition is available containing a valid boot.cfg file

2. The bootselect setting set to "regular" or "initialized".

3. The boot mode button is not pressed.

Otherwise, the Flash-N-Go Boot bootloader will try to load the Flash-N-Go System that resides in a FAT partition containing the boot-alt.cfg file.

Flash-N-Go System is a RAM-based system and is loaded completely into SD-RAM memory by the bootloader and runs from the volatile memory. Thus changes made inside the FnG System, like changes inside the /etc directory will not be stored and lost after reboot. This guarantees a consistent environment after boot and provides a good basis for production tests and installing software.

Because FnG System is designed as a RAM-based system it can be used to change anything on the non-volatile memory including updating Flash-N-Go System itself.

...

The shared device-specific data is currently well-supported on iMX6 and iMX6ULL devices. HweverHowever, i.MX8 devices may use this scheme in the future as well.

...

The current backing-storage type of Flash-N-Go is eMMC (using the Linux naming mmblk0mmcblk0). In addition to the partitions for the basic Flash-N-Go components, there may be some more partitions depending on the system configuration.

...

...

...

...

...

After a few seconds a Flash-N-Go System prompt should be displayed on the serial console similar to this:

FLASH-N-GO:/

Alternatively the bootselect tool can be used, which is usually provided by Flash-N-Go compatible operating systems using Flash-N-Go System as well as by Flash-N-Go System itself.

Configuration tools

Several tools on the Flash-N-Go System solution are provided for configuring, testing and flashing the devices.

bootselect

This tool offers the possibility to switch the boot target between the flashed operation system (e.g. Linux, Windows Embedded) on the device and Flash-N-Go System itself. The following code block shows a list of all possible parameters:

FLASH-N-GO:/ bootselect -h
Usage: bootselect [-qv] [<bootmode>]
When called without parameters, bootselect reads the
current boot-mode setting from the RTC-register
Options:
  <bootmode>  Writes the given boot-mode into the RTC-register
              May be one of: initialized regular regularB alternative invalid
  -v Turns on debug messages on stderr
  -vv Turns on info messages on stderr
  -q Turns off warning messages on stderr
  -qq Turns off all messages on stderr

For selection of the target OS the bootselect tool should be called with the regular parameter:

FLASH-N-GO:/ bootselect regular
regular 

For selection of Flash-N-Go System the bootselect tool should be called with the alternative parameter:

FLASH-N-GO:/ bootselect alternative 
alternative

sconfig

...

...

Booting Flash-N-Go System

There are two possible options for booting the device into Flash-N-Go System instead of booting the target OS. The first one is pressing down and holding the bootmode switch while the power supply is switched on. The location of the bootmode switch is shown in the following figure

...

After a few seconds a Flash-N-Go System prompt should be displayed on the serial console similar to this:

FLASH-N-GO:/

Alternatively, the bootselect tool can be used, available modes are regular for normal target OS and alternative for Flash-N-Go System.

...

Configuration tools

Several tools on the Flash-N-Go System solution are provided for configuring, testing and flashing the devices.

bootselect

This tool offers the possibility to switch the boot target between the flashed operation system (e.g. Linux, Windows Embedded) on the device and Flash-N-Go System itself. The following code block shows a list of all possible parameters.:

FLASH-N-GO:/ 

bootselect -h
Usage: 

xconfig

xconfig is a command line tool to manipulate the XML-configuration data directly. Care should be taken when using these commands as miss-configured or corrupted XML- configuration data might render a system unusable. The following code block shows a list of all possible parameters.

bootselect [-qv] [<bootmode>]
When called without parameters, bootselect reads the
current boot-mode setting from the RTC-register
Options:
  <bootmode>  Writes the given boot-mode into the RTC-register
              May be one of: initialized regular regularB alternative invalid
  -v Turns on debug messages on stderr
  -vv Turns on info messages on stderr
  -q Turns off warning messages on stderr
  -qq Turns off all messages on stderr

root@santaro:~# bootselect a
alternative
root@santaro:~# bootselect r
regular

sconfig

sconfig is a small command-line tool that offers functionalities for device configurations like network settings, screen rotation etc. The following code block shows a list of all possible parameters.

FLASH-N-GO:/ sconfig -h
Usage: /usr/bin/sconfig {start | list | init | <setting> [value]}
  Call without [value] to read a setting, call with [value] to write it.
Available settings:
  serialdiag switch serial debug console on or off
  dhcp switch DHCP on or off
  ip set IP address
  mask set subnet mask
  gateway set standard network gateway
  mac set MAC address
  name set device name
  serial set serial number (affects MAC address and device name)
  rotation set display rotation
If a 2.Ethernet is present, it may be configured via serial2, mac2, etc.

xconfig

xconfig is a command-line tool to manipulate the XML-configuration data directly. Care should be taken when using these commands as miss-configured or corrupted XML- configuration data might render a system unusable. The following code block shows a list of all possible parameters.

FLASH-N-GO:/# xconfig
Usage: $0 [command] [options]

Script to manipulate the XML-configuration data of GuF i.MX Boards
inside the NAND Flash.

xconfig expect one of the following commands to define its behavior:
  list           show the current contents 

of 

the 

XML-configuration 

as

     obtained from NAND
  import         import an external XML-configuration 

file 

into 

the 

NAND

        Flash
  addnode        add a new (empty) 

XML 

node

delnode 

      delete XML 

node(s) and its/their children
  addattribute  

add 

a 

new 

or 

change 

an 

existing 

attribute
  delattribute   delete an existing 

attribute
If 

no 

command 

and 

option 

given 

xconfig 

will 

display 

its version and exit.

Syntax:
  xconfig list [-v] [-p <path>]
        -v 

        show whole (sub)tree instead of summary, the format is
           

    suitable to be used as input to "xconfig import"
        -s        

          search for a specific pattern
        -l    

               show long path syntax instead of xml
        

--node 

filter result by node name, basic wildcards are allowed

 --attribute  filter result by attribute name, basic wildcards are allowed
           

         format is either 
         

   --attribute linux* matches all nodes that 

have
          

        an attribute starting 

with 

linux 

or

  --attribute key="value" matching nodes that 
 

   have an attribute 'key' with the 

value 'value'
        

-p <path>    path to 

subtree, e.g.:
         

-p /configurationFile/variables/setting[@key='enable_serialdiag]
          

if 

omitted, 

the whole tree is shown
  xconfig import [-

v] [-y] [-b] <file>
      

-v           be verbose
        -y           

assume 

yes 

- apply changes without user interaction
   

<file> 

    path to file to import

 -b        

  deprecated 

- 

do 

not 

use
  xconfig 

addnode [-y] -p <path> -n 

<name>
        -y           same as above
        -p <path>    path to parent node
        -n <name> 

   name of 

new 

node
  xconfig

 delnode [-y] -p <path>
        -y     

Manual System Update

The manual system update considers a manual operating system (OS) installation via a console. The update process described here requires an Ethernet connection of the device to a development PC, either directly or via intranet. Also a TFTP-Server or HTTP-Server is required on the development PC. There are several, also free, TFTP-Servers and HTTP-Servers online available. Please make sure that the timeout settings of the TFTP-Server are set to 60 seconds at minimum. The installation of target OSes, and Flash-N-Go System and Flash-N-Go Boot should work via console one- or two-liners. All device partitioning, deployment actions should be done by shell scripts executed by the simple command. See Booting Flash-N-Go System

Accessing the target system via serial console

Before updating the target operating system we first need an access to the device. The easiest way to access the target is via the serial console. Simply connect the first RS-232 port of your target system with a COM port of your PC or a USB-to-RS-232 converter using a null modem cable. With the serial connection set up start your favorite terminal program (e.g. minicom or tera term) with the following settings:

• 115200 baud

• 8 data bits

• no parity

• 1 stop bit

• no hardware flow control

• no software flow control

...

      same as above
        -p <path>    path to node
  xconfig addattribute [-y] -p <path> -n <attr-name> -v <value>
        -y           same as above
        -p <path>    path to parent node
        -n <attr-name>   name of the attribute
        -v <value>   new value of attribute
  xconfig delattribute [-y] -p <path> -n <attr-name>
        -y           same as above
        -p <path>    path to parent node
        -n <attr-name>   name of the attribute
  xconfig listattributes -p <path>
        -p <path>    path to node
  xconfig getattribute -p <path> -n <attr-name>
        -p <path>    path to parent node
        -n <attr-name>   name of the attribute

...

Manual System Update

The manual system update considers a manual operating system (OS) installation via a console. The progress can be done locally using mass storage devices or using a network connection.

The installation of target OSes, and Flash-N-Go System and Flash-N-Go Boot should work via console one- or two-liners. All device partitioning, deployment actions should be done by shell scripts executed by the simple command. See Booting Flash-N-Go System for instructions on how to boot into the management system.

Establish a network connection

The Ethernet can be set up with the sconfig command-line tool, see also sconfig.

To set the IP address to the static IP 192.168.1.1 with the submask 255.255.255.0 use the following commands:

sconfig ip 192.168.1.1
sconfig mask 255.255.255.0
sconfig dhcp off

To set DHCP and reboot the system to apply the network configuration:

sconfig dhcp on
reboot 

Installation via network

The common concept of the installation is always similar.

1. Set the download source variable

2. Download the installation script (with curl) and

3. Execute the installation script (with sh).

These concatenating these steps the installation can be done in one-liner commands.

Example 1: Install Yocto Kirkstone 25.0

Set the variable location, then call curl to download it to pipe to sh

FNG="https://secostorage.blob.core.windows.net/seco-ne-public/HMI/Linux-Yocto/Releases/Yocto-kirkstone-25.0/seco-mx6/fng-install.sh"
curl --location "$FNG" | sh -s -- --url="$(dirname "$FNG")"

The parameter url of the script should point to the location of the folder where the installation files are located.

Example 2: Install Flash-N-Go System 51

The process is similar to installing the target OS

FNG="https://secostorage.blob.core.windows.net/seco-ne-public/HMI/Flash-N-Go/FNGSystem/FNGSystem-51.0/seco-mx6/fngsystem-self-update.sh"
curl --location "$FNG" | sh -s -- --url="$(dirname "$FNG")"

Offline installation

It is also possible to install FnG System as well as the target OS offline.

To do that, simply download and copy the installation script as well as the corresponding files to a USB stick. After that, simply boot the device into FnG System, mount the USB stick and directly call the script.

...

Security Considerations

The Flash-N-Go System is designed as a management system to install and update target operating systems and change the device configurations. Thus it runs with root privileges. This may be a concern for some scenarios. Therefore some security considerations are necessary.

...

License