TEZI L4T Image for TK1

We have been using TEZI with great success (awesome job guys!).

The TEZI images for TK1 L4T releases lists the L4T 21.7 | 2.8b3 as the latest release. Are there any plans to release a 2.8b4 release image? Or 2.8b5? If so, what are the targetted release dates?

Otherwise are there any documented steps to generate the TEZI images from source?

Thanks!

We have been using TEZI with great success (awesome job guys!).

You are very welcome.

The TEZI images for TK1 L4T releases lists the L4T 21.7 | 2.8b3 as the latest release. Are there any plans to release a 2.8b4 release image?

Not really, no, as we are anyway about to release our regular 2.8b5 BSPs.

Or 2.8b5? If so, what are the targetted release dates?

Q4 for the regular BSPs. Updated L4T images probably Q1 2019. More information:

https://developer.toradex.com/software/linux/linux-software/release-details

https://developer.toradex.com/knowledge-base/toradex-embedded-linux-bsp-support-strategy

Otherwise are there any documented steps to generate the TEZI images from source?

Depending on what exactly you mean by “from source” as we do not have any sources of any NVIDIA proprietary parts (e.g. CUDA, graphics and multimedia). The base of L4T is Ubuntu ARM which you would need to inquire with Canonical how to go about building that from source. Other than that, it’s basically a combination of the following two articles on our developer website:

https://developer.toradex.com/knowledge-base/installing-nvidia-jetpack-with-l4t-on-apalis-tk1

https://developer.toradex.com/how-to-clone-embedded-linux-on-emmc-based-toradex-modules

Right gotcha. I guess I didn’t really mean completely “from source”.

What I’m looking for is to pick up some of the fixes in the Toradex BSP added after 2.8b3 and still use them with the L4T image.

I guess it would be possible to just swap out the zImage file in the TEZI image with the new 2.8b4 kernel to pick up the new changes, but still keep the rest of L4T setup unchanged.

You can always go to uboot and mount TK1 as Mass Storage device with OTG connection to the Host and with the following commands:

ums 0 mmc 0

Then you will see two partitions: BOOT and RFS. In the BOOT partition you can replace the kernel. You need to take care that the kernel modules have the same version number as kernel if not they won’t be loaded.