Unable to flash iMX7 after FCB/BCB Upgrade

Technical Support
, , , ,
1

Hello,

I am trying to flash my Colibri iMX7, and after updating the source repositories, I am no longer able to flash via SD card.

Now when I run “run setupdate”, then “run update”, I see the following message:

Colibri iMX7 # run update
WARNING: 'updlevel' neither in running nor in imported env!
reading colibri_imx7/u-boot-nand.imx
528384 bytes read in 46 ms (11 MiB/s)

NAND erase.part: device 0 offset 0x80000, size 0x380000
Erasing at 0x3e0000 -- 100% complete.
OK
  
NAND erase.part: device 0 offset 0x400000, size 0x80000
Erasing at 0x460000 -- 100% complete.
OK
Write bootloader...
Bootloader 655360 bytes written to 0x80000: OK
Bootloader 655360 bytes written to 0x200000: OK

NAND erase.part: device 0 offset 0x400000, size 0x80000
Erasing at 0x460000 -- 100% complete.
OK
  
NAND erase.part: device 0 offset 0x480000, size 0x1fb80000
Erasing at 0x1ffe0000 -- 100% complete.
OK
  
Upgraded U-Boot, please reset the board and complete update with
# run setupdate && run create_bcb && run update

When I perform those steps (reboot, run the command change), I still see the same message prompting me to reset the board and complete update, but no image is flashed to the device.

This change occurred after I updated “layers/meta-toradex-demos”, and it appears 5fe2de36e0380ee81c77dfb13b9b4ccebdbc3b0a (by Stefan Agner) prompted this change, but I am not getting the expected results following the given directions.

2

What exact module version do you use?

3

Here is a more complete output of the update process:

U-Boot 2015.04+fslc+g46aa70c (Dec 13 2016 - 12:07:50)

CPU:   Freescale i.MX7D rev1.2 at 792 MHz
CPU:   Temperature 36 C
Reset cause: POR
I2C:   ready
DRAM:  512 MiB
PMIC: RN5T567 LSIVER=0x1 OTPVER=0xd
NAND:  512 MiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

No panel detected: default to vga-rgb
Display: vga-rgb (640x480)
Video: 640x480x18
In:    serial
Out:   serial
Err:   serial
Model: Toradex Colibri iMX7 Dual 512MB V1.1C, Serial# 02844273
Net:   FEC0
Normal Boot
Hit any key to stop autoboot:  0 
Colibri iMX7 #
Colibri iMX7 # run setupdate
reading colibri_imx7/flash_blk.img
2636 bytes read in 22 ms (116.2 KiB/s)
## Executing script at 80800000
enter "run update" to update the entire module
Colibri iMX7 # run update
WARNING: 'updlevel' neither in running nor in imported env!
reading colibri_imx7/u-boot-nand.imx
528384 bytes read in 46 ms (11 MiB/s)

NAND erase.part: device 0 offset 0x80000, size 0x380000
Erasing at 0x3e0000 -- 100% complete.
OK
  
NAND erase.part: device 0 offset 0x400000, size 0x80000
Erasing at 0x460000 -- 100% complete.
OK
Write bootloader...
Bootloader 655360 bytes written to 0x80000: OK
Bootloader 655360 bytes written to 0x200000: OK

NAND erase.part: device 0 offset 0x400000, size 0x80000
Erasing at 0x460000 -- 100% complete.
OK
  
NAND erase.part: device 0 offset 0x480000, size 0x1fb80000
Erasing at 0x1ffe0000 -- 100% complete.
OK
  
Upgraded U-Boot, please reset the board and complete update with
# run setupdate && run create_bcb && run update

(note the create_bcb command in between!)
Colibri iMX7 #
Colibri iMX7 # reset
resetting ...
Colibr?

U-Boot 2015.04+fslc+g46aa70c (Dec 13 2016 - 12:07:50)

CPU:   Freescale i.MX7D rev1.2 at 792 MHz
CPU:   Temperature 43 C
Reset cause: POR
I2C:   ready
DRAM:  512 MiB
PMIC: RN5T567 LSIVER=0x1 OTPVER=0xd
NAND:  512 MiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

No panel detected: default to vga-rgb
Display: vga-rgb (640x480)
Video: 640x480x18
In:    serial
Out:   serial
Err:   serial
Model: Toradex Colibri iMX7 Dual 512MB V1.1C, Serial# 02844273
Net:   FEC0
Normal Boot
Hit any key to stop autoboot:  0 
Colibri iMX7 # 
Colibri iMX7 # run setupdate
reading colibri_imx7/flash_blk.img
2636 bytes read in 22 ms (116.2 KiB/s)
## Executing script at 80800000
enter "run update" to update the entire module
Colibri iMX7 #
Colibri iMX7 # run create_bcb

NAND read: device 0 offset 0x800, size 0x800
 2048 bytes read: OK

NAND erase.part: device 0 offset 0x0, size 0x80000
Erasing at 0x60000 -- 100% complete.
OK
Write FCB...
FCB 2048 bytes written to 0x0: OK
FCB 2048 bytes written to 0x20000: OK
Write DBBT...
DBBT 2048 bytes written to 0x40000: OK
DBBT 2048 bytes written to 0x60000: OK

NAND write: device 0 offset 0x800, size 0x800
 2048 bytes written: OK
Colibri iMX7 #    
Colibri iMX7 # run update
WARNING: 'updlevel' neither in running nor in imported env!
reading colibri_imx7/u-boot-nand.imx
528384 bytes read in 46 ms (11 MiB/s)

NAND erase.part: device 0 offset 0x80000, size 0x380000
Erasing at 0x3e0000 -- 100% complete.
OK
  
NAND erase.part: device 0 offset 0x400000, size 0x80000
Erasing at 0x460000 -- 100% complete.
OK
Write bootloader...
Bootloader 655360 bytes written to 0x80000: OK
Bootloader 655360 bytes written to 0x200000: OK

NAND erase.part: device 0 offset 0x400000, size 0x80000
Erasing at 0x460000 -- 100% complete.
OK
  
NAND erase.part: device 0 offset 0x480000, size 0x1fb80000
Erasing at 0x1ffe0000 -- 100% complete.
OK
  
Upgraded U-Boot, please reset the board and complete update with
# run setupdate && run create_bcb && run update

(note the create_bcb command in between!)
Colibri iMX7 #
4

Nevermind, the complete output shows Colibri iMX7 V1.1C

5

The current top-of-branch of meta-toradex-demos requires also the latest version of U-Boot. The changes have been pushed to the U-Boot 2015.04-toradex-next branch, but the recipe hasn’t been updated yet. I just pushed a commit which updates the U-Boot recipe to the latest U-Boot version. Pulling jethro-next in meta-toradex-nxp should fix your issue:

http://git.toradex.com/cgit/meta-toradex-nxp.git/log/?h=jethro-next

6

This fixed my problem, thanks!

Would this work for a clean checkout environment now (aka repo pull the “jethro-next” branch), or is this manual step needed until further notice?

7

With jethro-next you should get a coherent version, still without the update script and U-Boot changes. We do not plan to update the jethro branch as we move forward to morty…

8

So you keep a non coherent version for the jethro version? Should not happened on professionnal product…

9

So… I followed tutorial to build Linux Images on this page:

And try to update my board following information from:

All this should work, but no…

What do I have to change to have the update working?

10

Yeah sorry, there crept in a inconsistency across the layers with the intermediate Apalis TK1 release. The above update of the U-Boot should have solved the problem.

I also just reverted the update scripts and updated the manifest. With that U-Boot and the meta-toradex-demo scripts provide a coherent updateable state again.