Target Image for the Developer Package on the STM32MP257F-EV1 board

[Carson]

Hello, I am working on getting the Developer Package for the STM32MP257F-EV1 board up and running. I am confused on the step where tells us to do the following command:

[ "${ARCH}" = "arm" ] && imgtarget="uImage" || imgtarget="Image.gz"

export IMAGE_KERNEL=${imgtarget}

Followed by

make ${IMAGE_KERNEL} vmlinux dtbs LOADADDR=0xC2000040 O="${OUTPUT_BUILD_DIR}"

I am assuming that for ARCH I should be writing arch64 which is proved by the fact that when I try to run that I am getting an error for the first Image target, But I keep getting the error *** No rule to make target 'uImage' or whatever I put for the Image, I have tried a variety of Image names that I found in some of the files like: Image, uImage, zImage, Image.gz, and bzImage. The only one that will not get this error is bzImage, which will end up getting errors with the files later about undeclared variables and it seems that it is making it for x86 architecture. So what is the Image target I should be using and where do I find that info? Thanks!

Carson

[Olivier GALLIEN]

Hi Carson,

>>I am assuming that for ARCH I should be writing arch64 

No, $ARCH is set when you source the SDK to "arm64" and you might not have to change it.

Simply executing lines as they are written in the README might works. 

Olivier 

[Carson]

Hi Oliver,

I have tried following both the READ ME HOW TO text file and the getting started webpage and both run into the same problems when I follow them exactly. And I am wondering if it has something to do with the configuration? I think this because when I run the command:

sudo make ${IMAGE_KERNEL} vmlinux dtbs LOADADDR=0xC2000040 O="${OUTPUT_BUILD_DIR}"

I get the following output:

SYNC include/config/auto.conf.cmd
GEN Makefile
*
* Restart config...
*
*
* General setup
*
Compile also drivers which will not load (COMPILE_TEST) [N/y/?] n
Compile the kernel with warnings as errors (WERROR) [N/y/?] n
Local version - append to kernel release (LOCALVERSION) []
Automatically append version information to the version string (LOCALVERSION_AUTO) [Y/n/?] y
Build ID Salt (BUILD_SALT) []
Kernel compression mode
> 1. Gzip (KERNEL_GZIP) (NEW)
2. Bzip2 (KERNEL_BZIP2) (NEW)
3. LZMA (KERNEL_LZMA) (NEW)
4. XZ (KERNEL_XZ) (NEW)
5. LZO (KERNEL_LZO) (NEW)
6. LZ4 (KERNEL_LZ4) (NEW)
7. ZSTD (KERNEL_ZSTD) (NEW)
choice[1-7?]: ^Z

If I answer this question it asks me many more and if I get to the end then it gives me the same old error of *** No rule to make target 'uImage'

[Olivier GALLIEN]

Hi Carson,

Seems you didn't source properly the SDK prior to execute README instruction. 

Please follow carefully Install the SDK - stm32mpu 

Check with the 3.2 section commands that all is fine. 

The following checks ensure that the environment is correctly set up:

• Check the target architecture

 echo $ARCH
arm64

• Check the toolchain binary prefix for the target tools

 echo $CROSS_COMPILE
aarch64-ostl-linux-

Olivier  

[Carson]

Hi Oliver,

I tried re-doing the kernel with sourcing the SDK prior and when I run all 4 of the commands to check if the SDK is installed correctly they all give the expected output. When I went through the READ ME file again I got the same output as I did last time when I ran the line:

sudo make ${IMAGE_KERNEL} vmlinux dtbs LOADADDR=0xC2000040 O="${OUTPUT_BUILD_DIR}"

Is there anything else that could be wrong? One thing I wasn't sure on was that the READ ME file keeps referencing a "directory to kernel source code" that is the linux-6.1.82 file correct?

[Olivier GALLIEN]

Hi Carson,

Please remove usage of "sudo"

Olivier 

[Carson]

Hi Oliver,

If I run the lines without sudo I get permission errors, here are the errors:

SYNC include/config/auto.conf.cmd
GEN Makefile
fopen: Permission denied

*** Error during sync of the configuration.

[Olivier GALLIEN · Accepted solution]

Hi Carson

I suppose you have to restart full procedure without sudo in all steps. 

Olivier 

[Carson]

Hello Oliver,

This worked! There was another error that I had to fix since I wasn't in sudo but it did end up working. Thanks!

[Olivier GALLIEN]

Great ! Thanks for feedback 

Olivier