cancel
Showing results for 
Search instead for 
Did you mean: 

Boot to v5.4-stm32mp-r1

Artem
Associate III

Hello,

has anyone successful booted linux  v5.4-stm32mp-r1 on the stm32mp157c-dk2 board?

If so can you please provide me a working config?

I am trying to switch from the 4.19 kernel to v5.4-stm32mp-r1 but the boards freezes after trying to load the kernel without any output, until it gets restarted by the WDG.

I have tried to use TF-A and also U-Boot as SPL, both with the same results.

Kernel 4.19 and also stock 5.7 are booting just fine... The kernel configs are also the same.

U-Boot SPL 2020.01-stm32mp-r1 (Aug 09 2020 - 23:04:31 +0200)
Model: STMicroelectronics STM32MP157C-DK2 Discovery Board
RAM: DDR3-DDR3L 16bits 533000Khz
WDT:   Started with servicing (32s timeout)
Trying to boot from MMC1
 
 
U-Boot 2020.01-stm32mp-r1 (Aug 09 2020 - 23:04:31 +0200)
 
CPU: STM32MP157CAC Rev.B
Model: STMicroelectronics STM32MP157C-DK2 Discovery Board
Board: stm32mp1 in basic mode (st,stm32mp157c-dk2)
Board: MB1272 Var2.0 Rev.C-01
DRAM:  512 MiB
Clocks:
- MPU : 650 MHz
- MCU : 208.878 MHz
- AXI : 266.500 MHz
- PER : 24 MHz
- DDR : 533 MHz
WDT:   Started with servicing (32s timeout)
NAND:  0 MiB
MMC:   STM32 SD/MMC: 0, STM32 SD/MMC: 1
In:    serial
Out:   serial
Err:   serial
****************************************************
*        WARNING 500mA power supply detected       *
*     Current too low, use a 3A power supply!      *
****************************************************
 
Net:   eth0: ethernet@5800a000
Hit any key to stop autoboot:  0
Boot over mmc0!
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:4...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
131 bytes read in 35 ms (2.9 KiB/s)
1:      stm32mp157c-dk2-buildroot
Retrieving file: /boot/zImage
3986960 bytes read in 203 ms (18.7 MiB/s)
append: root=/dev/mmcblk0p4 rootwait
Retrieving file: /boot/stm32mp157c-dk2.dtb
105200 bytes read in 40 ms (2.5 MiB/s)
## Flattened Device Tree blob at c4000000
   Booting using the fdt blob at 0xc4000000
   Loading Device Tree to cffe3000, end cffffaef ... OK
 
Starting kernel ...

5 REPLIES 5
Fee
Senior

Hi,

had the same problem as well:

https://community.st.com/s/question/0D53W00000CO2JOSA1/problems-booting-with-uboot-in-ecosystem-20-using-the-trusted-bootchain

For me using the .config file of the released kernel (not the one on the ST Github, I am talking about the on eyou can get here: https://wiki.st.com/stm32mpu/wiki/STM32MP1_Developer_Package#Downloading_the_Linux_kernel) fixed the problem.

Hope it helps.

Artem
Associate III

Hello,

ok, now I have also extracted the config from the "released" kernel, but it still not boot. Have you applied any patches?

Yes i applied the config fragments according to the README (till including step 5).

Artem
Associate III

Ok, I got it working now:

I have extracted and patched the kernel like explained in the README. Then I have generated the config with all fragments - also like explained in the README (till fragment 5 too). Now I have copied over the full config to buildroot and was able to compile the v5.4-stm32mp-r1 kernel from github.

The kernel now boots when using TF-A but not U-Boot SPL, but this is fine for me.

It would be good to know what piece of config is preventing the kernel from booting...

Hi @Artem​ 

>> The kernel now boots when using TF-A but not U-Boot SPL, but this is fine for me.

This is inline with the ecosystem release V2.0 in which support of basic boot chain ( start kernel from U-Boot SPL ) has been removed.

Olivier

Olivier GALLIEN
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.