Thanks for the feedback. I have improved the Eclipse install and debug lessons since your first contact and will further keep improving the guide as a whole.
Below are my comments to your points:
However, when I follow the link to the toolchain in your post, I find there are two different toolchains available for the colibri-vf SOM. One is for the angstrom-lxde-image, and is called angstrom-glibc-x86_64-armv7at2hf-neon-v2017.12-toolchain.sh, with a size of 436M. The other is for the console-tdx-image, and is called angstrom-glibc-x86_64-armv7at2hf-neon-v2017.12-toolchain.sh, with a size of 304M. Yes, the file name is exactly the same, but the file size is different! At this point I don’t know if the toolchain that I downloaded and installed matches either one of these, since you apparently have different toolchains with different file sizes with exactly the same file name!
The provided SDKs are meant only to be used with the Getting Started Guide.
They are provided as-is, which is stated in the SDKs directory: https://developer1.toradex.com/files/toradex-dev/uploads/media/Colibri/Linux/SDKs/ReadMe.txt
I will further add a note in the Getting Started Guide highlighting this specific points. Pardon for your trouble. That being said, to build the Getting Started Guide examples, choosing either the angstrom-lxde-image or console-tdx-image SDKs/toolchains will provide the same results.
Regarding the naming, the deafult name is the same as generated from an OpenEmbedded build. I may rename the SDKs to prevent this confusion.
I followed that link, and downloaded and installed a Linux image called Colibri-VF_LXDE-image_2.8b3.111-20180626.tar.bz2, with a size of 80582109 bytes, since I am using a VF61 with more memory then the VF50.
You are correct, that is appropriate.
Note that my application does NOT require a GUI desktop interface at all. It will use a web interface accessed via a browser, and a simple keypad and character based LCD display.
The default pre-built evaluation image provided by Toradex may not be a perfect fit for all customers, even though it is a production-ready image. You can use it as-is or customize the image, in which case we recommend the use of OpenEmbedded, and we provide instructions for recreating and customizing the image. Please see https://developer.toradex.com/software/linux/linux-software#Recreate_and_Customize_BSP_with_OpenEmbedded_core
- Are there really different toolchains I need to use depending on whether I have installed the LXDE or the console based Linux image?
As mentioned above, for the trivial Getting Started Guide examples, both the angstrom-lxde-image and console-tdx-image toolchains will work. For more complex matters, you are encouraged to create your own toolchain.
The SDKs/toolchains are provided as-is. Same as with the embedded Linux image customization, you can generate an SDK tailored for your custom image using OpenEmbedded: https://developer.toradex.com/knowledge-base/board-support-package/openembedded-(core)#Building
- Given that I do not need a GUI desktop environment, can you please give me links to both the Linux image that I should install, and the proper COMPATIBLE toolchain that I should install?
As of now, the official Toradex pre-built evaluation image is an Ångström based image with the LXDE desktop environment. The Linux Console image is an alternative provided for the Colibri VFxx modules, which are on the low end of HW configuration (i.e. RAM size, flash size). Using OpenEmbedded you can also build an image without a desktop environment.
If you choose to use our pre-built image, either Linux LXDE image or Linux Console Image can be chosen.
Perhaps if I install all the right things, everything might work better. But honestly, I did try to follow the Getting Started guide very precisely, and things simply did not work as expected.
Since we are driven towards customer focus, I will use your feedback to improve the documentation in order to provide a better customer experience.