Can't access "How to create a layer with device tree files generated via STM32CubeMX" page in Wiki

[j_gil]

Hi,

I'm going through the wiki to try and solve the issues I'm finding on the bring-up of our board.

I found something that could be interesting for me , so from this page I try to access the "How to create a layer with device tree files generated via STM32CubeMX" wiki page, but whe I click on it, I get a "Permission error" and can not see anything.

Is this an error or do I need some kind of special permission?

Kind regards,

j

[Olivier GALLIEN]

Hi @j_gil​ 

This page would have rather displayed "coming soon". Its content is not ready to be shared yet.

In the meantime please share your specific question/concern in order we can help

BR

Olivier

[j_gil]

Thanks for the interest Olivier,

Maybe you saw one other thread of mine where your colleague Patrick suggested me to change what's necessary in the dts so that the u-boot works with an external crystal for the 24MHz clock, instead of an oscillator, which is what the STM32MP157c-EV1 has (Our design is based on this EV1).

So I've been fiddling around the u-boot since then, among the things I've tried here's two:

1. Change the clk_hse property "st,digbypass;" to "st,css;", which didn't show any changes on the serial output of my system.
2. Delete the "st,digbypass;" line from the .dtsi, (I inferred this by comparing the generated DeviceTree files by the latest version of the STM32CubeMX from two projects; the first, was just the default configuration of the STM32MP157c-EV1 as it is, and the other one is a modification of the last where I just changed the "High Speed Clock (HSE)" to "Crystal/Ceramic Resonator" under System Core->RCC. This did also not have any effect either.

To be clear, what I've been doing, since I don't want to get deep into manually modifying all the necessary source files, is modifying specific lines of the original U-boot source files (once patched) and then substituting the generated "u-boot-stm32mp157c-ev1-trusted.stm32" for the one in the starter package and then trying to flash as if it were the EV1, with the "FlashLayout_sdcard_stm32mp157c-ev1-trusted.tsv" file.

Thus why I'm interested in the page explaining how to apply the DeviceTree generated by the STM32CubeMX.

It always stops at the same point, same thing it did when I was trying out the EV1 I had which turned out to have an Alpha version of the HW.

Is the a way to find out if the units I have assembled on my board are also Alpha version?

Here's the logs I get (both, from the STM32_Programmer_CLI, and serial communication from the board):

$ STM32_Programmer_CLI -c port=usb1 -w flashlayout_st-image-weston/FlashLayout_sdcard_stm32mp157c-ev1-trusted.tsv -tm 20000
 -------------------------------------------------------------------
 STM32CubeProgrammer v2.1.0 
 -------------------------------------------------------------------
 
 
 
Warning: Timeout is forced to 20000 ms
 
 
USB speed : High Speed (480MBit/s)
Manuf. ID : STMicroelectronics
Product ID : DFU in HS Mode @Device ID /0x500, @Revision ID /0x0000
SN : 000000000000
FW version : 0x011a
Device ID : 0x0500
Device name : STM32MPxxx
Device type : MPU
Device CPU : Cortex-A7
 
 
Start Embedded Flashing service
 
 
 
Memory Programming ...
Opening and parsing file: tf-a-stm32mp157c-ev1-trusted.stm32
 File : tf-a-stm32mp157c-ev1-trusted.stm32
 Size : 245360 Bytes
 Partition ID : 0x01 
 
Download in Progress:
[==================================================] 100% 
 
File download complete
Time elapsed during download operation: 00:00:04.027
 
RUNNING Program ... 
 PartID: :0x01 
Start operation done successfully at partition 0x01
 
Flashlayout Programming ...
[==================================================] 100% 
Running Flashlayout Partition ...
Flashlayout partition started successfully
 
 
Memory Programming ...
Opening and parsing file: u-boot-stm32mp157c-ev1-trusted.stm32
 File : u-boot-stm32mp157c-ev1-trusted.stm32
 Size : 754169 Bytes
 Partition ID : 0x03 
 
Download in Progress:
[==================================================] 100% 
 
File download complete
Time elapsed during download operation: 00:00:11.885
 
RUNNING Program ... 
 PartID: :0x03 
 
reconnecting the device ...
 
Error: unable to reconnect the target device: time out expired
 
 
Error: Start operation failed at partition 0x03
Error: TSV flashing service failed

NOTICE: CPU: STM32MP157A?? Rev.A
NOTICE: Model: STMicroelectronics STM32MP157C eval daughter on eval mother
INFO: Reset reason (0x15):
INFO: Power-on Reset (rst_por)
INFO: Using USB
INFO: Instance 2
INFO: Boot used partition fsbl1
INFO: Product_below_2v5=1: HSLVEN update is
INFO: destructive, no update as VDD>2.7V
NOTICE: BL2: v2.0(debug):
NOTICE: BL2: Built : 13:13:37, Oct 2 2018
INFO: BL2: Doing platform setup
INFO: PMIC version = 0x00
INFO: RAM: DDR3-1066/888 bin G 2x4Gb 533MHz v1.41
INFO: Memory size = 0x40000000 (1024 MB)
INFO: BL2 runs SP_MIN setup
INFO: BL2: Loading image id 4
INFO: Loading image id=4 at address 0x2fff0000
INFO: Image id=4 loaded: 0x2fff0000 - 0x30000000
INFO: BL2: Loading image id 5
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: Receive DFU abort
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 0
INFO: address 0x2ffee768
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 0
INFO: address 0x2ffee768
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: Start Download partition 0 to address 0xc0000000 length 0
INFO: USB : DFU : end of download partition : 0
INFO: Loading image id=5 at address 0xc0100000
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 3
INFO: address 0x2ffee768
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: receive request 6
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 3
INFO: address 0x2ffee768
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: usb_partition_size: partition size : 0xb80f9
INFO: Start Download partition 3 to address 0xc0100000 length 753913
INFO: USB : DFU : end of download partition : 3
WARNING: Skip signature check (header option)
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 0
INFO: address 0xffffffff
INFO: Send detach request
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: Receive Detach
INFO: Image id=5 loaded: 0xc0100000 - 0xc01b80f9
INFO: read version 0 current version 0
NOTICE: BL2: Booting BL32
INFO: Entry point address = 0x2fff0000
INFO: SPSR = 0x1d3
INFO: PMIC version = 0x00
NOTICE: SP_MIN: v2.0(debug):
NOTICE: SP_MIN: Built : 13:13:37, Oct 2 2018
INFO: ARM GICv2 driver initialized
▒ɑ▒*O@2*.▒▒▒▒▒M}qbj▒▒l▒m$J▒Α
'▒P▒▒ '▒2▒1▒"
u▒H,▒\▒▒▒%}q▒▒ٟ0▒▒b).▒:@▒1111111mdP

[Olivier GALLIEN]

Hi @j_gil​ 

Your substitution method is correct but you need also to recompile and update the tf-a in the same way.

Your traces clearly shows you crash during HSE initialization in tf-a

Olivier

[j_gil]

Hi Olivier,

I just tried recompiling TF-A also (with the same changes as the U-boot) and still get the same result.

I tried this both, deleting the "st,digbypass" parameter and modifying it to "st,css".

Some values are different but that must be because of the file size variation due to file modifications:

INFO: usb_partition_size: partition size : 0xb80e0
INFO: Start Download partition 3 to address 0xc0100000 length 753888
INFO: USB : DFU : end of download partition : 3
WARNING: Skip signature check (header option)
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 0
INFO: address 0xffffffff
INFO: Send detach request
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: Receive Detach
INFO: Image id=5 loaded: 0xc0100000 - 0xc01b80e0

[Bernard PUEL]

Hello,

I see from your trace:

CPU: STM32MP157A?? Rev.A

Public STM32mp1 release is only supporting Rev.B. So I guess you need to update your EV1 board with a new one (MB1262C and MB1263C) or take an hold non public SW release (Beta1 Release).

rgs,

[Bernard PUEL]

I red all the thread, even if it is on your own design (I did not realized first) the comment above is still valid.

[j_gil]

Thank you Bernard.

While we try to get ahold of release units of the MPU and have them assembled onto a new batch of our boards, can you point out who should I get in touch with in order to have access to he non public Beta1 SW Release?

Kind regards,

j

[Bernard PUEL]

​As it is not public versions of HW and SW. I would propose to answer offline.