Hello,

I have a VAR-SOM-MX6 with the following details:

Board: Variscite VAR_SOM_MX6 SOM-Solo SOC_FAMILY = "mx6:mx6q:mx6dl" PREFERRED_PROVIDER_virtual/kernel_var-som-mx6 ?= "linux-variscite" PREFERRED_VERSION_linux-imx_mx6 = "4.1.15"

and the following u-boot details:

U-Boot SPL 2013.10-00027-g58782ac (Mar 09 2015 - 13:33:44) i.MX6SOLO SOC DDR EEPROM configuration Part number: VSM-SOLO-102 Assembly: AS151004858 Date: 2016 Feb 08 Ram size 1024 Boot Device: NAND NAND: 512 MiB

U-Boot 2013.10-00027-g58782ac (Mar 09 2015 - 13:33:44)

CPU: Freescale i.MX6SOLO rev1.2 at 792 MHz CPU: Temperature 51 C, calibration data: 0x5744e269 Reset cause: POR Board: Variscite VAR_SOM_MX6 SOM-Solo I2C: ready DRAM: 1 GiB NAND: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 In: serial Out: serial Err: serial Board: Variscite VAR_SOM_MX6 SOM-Solo Net: using phy at 7

I am using Yocto to create my images (.swu) to update my board through swupdate https://sbabic.github.io/swupdate/swupdate.html . The update process and loading process via NFS and NAND causes no issues.

I am trying to implement a system whereby if the board fails to boot, it should boot to a recovery configuration where the user is presented with the swupdate landing page to allow for an image (.swu) upload to update or boot to a recovery .img (uImage, .dtb, rootfs stored on MMC or NAND).

I have read about uboot's Boot Count Limit http://www.denx.de/wiki/view/DULG/UBootBootCountLimit which is along the lines of what I would like to implement i.e. after x failed boot attempts use an alternate boot action. However this functionality is not supported by my board.

I am new to this and was wondering if anyone could shed any light on what I need to look at or how I can somehow implement the Boot Count Limit functionality or similar.

Thanks for your help.

-- View this message in context: http://u-boot.10912.n7.nabble.com/VAR-SOM-MX6-Boot-Count-Limit-support-tp276... Sent from the U-Boot mailing list archive at Nabble.com.