u/EmbeddedBro

I am trying to run an example on arm development studio.

It turns out that in order to complete arm's fancy "Free" tutorial, I would need to install their software "arm development studio 6".

After installing, it asks for a license.

It costs around 4500 USD/year and there is no community edition available.

You can not even get 30 day evaluation license right away. you need to search for web page for authorized distribute and mail them.

So I tried to change armclang to gcc but now I am getting error about target=aarch64-arm-none-eabi.

What is the solution, anyone knows gcc alternative would work?

Anyone knows if there is an free edition for arm DS ?

According to Wikipedia:

on ARM, device trees have been mandatory for all new SoCs since 2012.

My question is:

Since bootz command is u-boot (or bootloader) specific, then what happens, if I just set my PC to that memory address of loaded zImage in RAM?

Is there any default place where Kernel tries to find the .dtb file which might be placed at compile time?

I am doing the bootling tutorial on Yocto.

https://bootlin.com/doc/training/yocto/yocto-stm32mp1-labs.pdf

In lab2: I do not understand this paragraph.

It is suggesting that I need to change MACHINE from linux-stm32mp to linux-dummy. in /build/conf/local.conf

What is it's relation with PREFERRED_PROVIDERS? I also could not find PREFERRED_PROVIDERS command in /build/local.conf

Can anybody shed some light on this subject?

Choose a package variant
Dependencies of a given package are explicitly defined in its recipe. Some packages may need a specific library or piece of software but others only depend on a functionality. As an example, the kernel dependency
is described by virtual/kernel.

To see which kernel is used, dry-run BitBake:
bitbake -vn virtual/kernel

In our case, we can see the linux-stm32mp provides the virtual/kernel functionality:
NOTE: selecting linux-stm32mp to satisfy virtual/kernel due to PREFERRED_PROVIDERS

We can force bitbake to select another kernel by explicitly defining which one to use in our local configuration.
Try switching from linux-stm32mp to linux-dummy only using the local configuration. Then check the previous step worked by dry-running again BitBake.

bitbake -vn virtual/kernel

Tip: you need to define the more specific information here to be sure it is the one used. The MACHINE variable can help here. As this was only to show how to select a preferred provider for a given package, you can now use linux-stm32mp again.