I can do this with the u-boot repository and earlier in the day I could do it with the Linux repository. I deleted the whole local repository and cloned it again but same thing happened. What’s it complaining about?
All I really want to do is look at the pertinent .dts and .dtsi files for Apalis iMX8QM 4GB WB/IT V1.0B and V1.1B on the Ixora carrier board. Couldn’t care less about git. Any way to just get the files?
Some questions on the naming. The document Device Tree Customization | Toradex Developer Center shows Carrier Board Level names like fsl-imx8qm-apalis-v1.1-eval.dts. I don’t find those files. In the linux-toradex git repository I find files like imx8qm-apalis-v1.1-eval.dts. Is that the same thing, just maybe some documentation needs a little update? Or am I just looking in the wrong place?
Is it a fact that the device tree is split between the linux-toradex git repository and the u-boot-toradex git repository? Or again am I looking in the wrong place?
What “tool” are you using? I’ve successfully cloned toradex_5.4-2.1.x-imx branch with no errors and no warnings using git clone -b toradex_5.4-2.1.x-imx git://git.toradex.com/linux-toradex.git command.
BTW /drivers/gpu/drm/nouveau/nvkm/… is for NVIDIA and not included in NXP Linux mainline.
The toradex_5.4-2.1.x-imx is not officially released. And mentioned article is about 3.0x BSP. You can find mentioned there fsl-imx8qm-apalis-v1.1-eval.dts here.
Device tree is not split between linux-toradex git repository and the u-boot-toradex git repositories. Why do you decide so?
I was using GitHub Desktop which seemed to be working earlier. I also tried doing a git clone straight from the command line and saw the same errors when I tried to view the tree with GitHub Desktop. A check of this error online indicates a common reason for this on a Windows system is path or filename with characters that are illegal in Windows being used. That said, I know little about GIT and probably just enough to get in trouble…
I said it was split because I did not find all the files in one place. Half of them were under linux-toradex and half under u-boot-toradex, at least with respect to toradex_5.4-2.1.x-imx. So I think the answer as you point out is that I’m looking in the wrong place.
3.0x BSP would seem to be pretty old at this point. I do note that Toradex is trying to get itself aligned with Yocto for LTS so maybe 3.0x BSP is really the latest. I’ve got to pick a BSP as a base for creating a VxWorks BSP and within reason would pick the latest and greatest. It would seem that 5.0.0 would be the up and coming as 4.0.0 has been deferred. I also want to pick something reasonablly new enough that I can cover both the Apalis iMX8QM 4GB WB/IT modules of both the V1.0B and V1.1B flavor since over the timeframe of our project we are likely to use both. Can you make a suggestion of what repository branch might be a good selection for me? Thanks.
If you going to do a BSP modification you definitely need to get more familiar with GIT and use Linux as a dev OS. I’d recommend dedicated Linux box though you can use VM and run Linux inside your Windows OS.
5.0 BSP should be released soon, so you can start use it now just don’t expect that existing articles and documentations will be exactly aligned with it. We will update them after BSP release. However why do you care about it if you creating VXWork BSP which, as far as I know, not based on Linux?
Sorry but I don’t see anything in the article that references versions for the iMX8 so I presumed it was current…
You are correct that the VxWorks BSP is not the same as Linux but it is a useful starting point and in fact Wind River has worked with the NXP iMXQM MEK. Wind River uses a Flattened Device Tree schema (albeit they layered it internally themselves) so the Device Tree info is good info for what needs to go in a VxWorks BSP for supporting the Toradex modules.
Obviously a lot of these questions are due to my lack of knowledge here. For that I thank you for your patience.
