Flashing Linux Image version 2.6 to T20 problem -Help needed

I have a Colibri Evaluation Board With T20 and I have successfully flashed it with “Colibri_T20_LinuxImageV2.3” downloaded from Toradex site. I am doing this over USB in Recovery mode by running ‘update.sh’ script without any Memory card or USB drive. So far OK.
I have installed a tool chain and deployed a Hello world application using eclipse IDE following the instructions in Toradex site.

Now I need to develop an application using Qt.
So I followed instructions on this page.
I have successfully built

$ bitbake -k meta-toolchain-qt5

and installed QT and created a small form and it is running in my development machine also.
Now I need linux images for T20 with QT runtime files. (correct me if I am wrong).
So I built following successfully.

$ bitbake -k angstrom-lxde-image
$ bitbake -k console-trdx-image

I got folders what I believe contains images for T20

‘Colibri_T20_LinuxConsoleImageV2.6’ and ‘Colibri_T20_LinuxImageV2.6’

I tried to run the update.sh script in this folder as I have done in version 2.3 with T20 in recovery mode. but it seems something different here.
I got the following output

Prepares and copies files for flashing internal eMMC/NAND of Apalis T30/TK1 and
Colibri T20/T30

Will require a running U-Boot on the target. Either one already flashed on the
eMMC/NAND or one copied over USB into the module's RAM

-b           : T20: selects boot device (hsmmc/nand) (default: nand)
-c           : split resulting rootfs into chunks usable for TFTP transmission
-d           : use USB recovery mode to copy/execute U-Boot to/from module's RAM
-f           : flash instructions
-h           : prints this message
-m           : module type: 0: autodetect from ./rootfs/etc/issues (default)
                            1: Apalis T30
                            2: Apalis TK1
                            3: Colibri T20
                            4: Colibri T30
-o directory : output directory
-r           : T20 recovery mode: select RAM size (256 | 512)
-s           : T20: optimise file system for V1.1 or 256MB V1.2 modules,
               increases usable space a little, but limits 512MB V1.2 modules
               to 512MB usable NAND space
-v           : T20 recovery mode: select Colibri version (V1_1 | V1_2)

Example "./update.sh -o /srv/tftp/" copies the required files to /srv/tftp/

*** For detailed recovery/update procedures, refer to the following website: ***
http://developer.toradex.com/knowledge-base/flashing-linux-on-tegra-modules

I tried by changing arguments also. but it seems not the correct way.
Please help

I can access uboot console via cutcom and see the kernel messages as well as login after booting in 2.3 image.

Hi

Yes the update procedure changed with the introduction of the V2.4 release.
Did you have a look at the website mentioned at the end of the help text?

 *** For detailed recovery/update procedures, refer to the following website: ***
 http://developer.toradex.com/knowledge-base/flashing-linux-on-tegra-modules

> Now I need linux images for T20 with QT runtime files. (correct me if I am wrong).

That is correct. However neither angstrom-lxde-image nor console-trdx-image does have this installed.
Probably starting with angstrom-qt5-x11-image would be closer to your goal.

Max

I follwed this below part from this page

Build the Target Image for Qt

On the target module you will need the
Qt runtime environment installed.
Therefor a new image with the Qt
run-time libraries to allow executing
Qt applications on the target is
required.

For Qt 5, build and setup with
OpenEmbedded as per
High performance, low power Embedded Computing Systems | Toradex Developer Center

angstrom-lxde-image: Qt 5 X11 image with Angstrom LXDE desktop

environment
console-trdx-image: Qt 5 image with framebuffer EGLFS without X11

$ bitbake -k angstrom-lxde-image

$ bitbake -k console-trdx-image

But now I have built the image you mentioned also.(angstrom-qt5-x11-image)

Regarding the flash instructions part for T20 in page you suggested there I cannot figure out the method to flash without USB or Memmory card storage.

That is also no longer supported.

Thanks.for the info.