[rishi@smufsbio.com]

Hi Neeraj,
Thanks for your response. I saw these links, but i still can not find a way to add a gpio as wakeup source in CubeMX tool. Even when i add new wakeup sources in CubeMX i do not see any changes in the device tree files generated.

See another issue is when i am trying to wake up through PONKey,my build blocks at
“INFO: SP_MIN: Preparing exit to normal world”.

But the same thing (waking up through Ponkey) works just fine in your demo build “OSD32MP1_BRK_OpenSTLinux_Trusted_RELEASE_V2.0”.
I tried to compare my device trees with OSD-brk device trees, but i can not find the difference.
Can you please point me to right direction where should i look for the issue, i mean its tfa ,uboot or kernel issue ?

Please see the full logs.
# echo mem > /sys/power/state
[ 52.990628] PM: suspend entry (deep)
[ 53.032482] Filesystems sync: 0.039 seconds
[ 53.036337] Freezing user space processes … (elapsed 0.001 seconds) done.
[ 53.043048] OOM killer disabled.
[ 53.046219] Freezing remaining freezable tasks … (elapsed 0.001 seconds) done.
[ 53.053667] printk: Suspending console(s) (use no_console_suspend to debug)
————– I wakeup by PON Key here ——————————
NOTICE: CPU: STM32MP157C?? Rev.Z
NOTICE: Model: Custom board
INFO: Reset reason (0x810):
INFO: System exits from STANDBY
NOTICE: BL2: v2.2-r2.0(release):
NOTICE: BL2: Built : 06:55:06, Apr 15 2021
INFO: Using crypto library ‘stm32_crypto_lib’
INFO: BL2: Doing platform setup
INFO: RAM: DDR3-DDR3L 16bits 533000Khz
INFO: BL2 runs SP_MIN setup
INFO: BL2: Skip loading image id 4
INFO: BL2: Skip loading image id 5
NOTICE: BL2: Booting BL32
INFO: Entry point address = 0x2ffeb000
INFO: SPSR = 0x1d3
NOTICE: SP_MIN: v2.2-r2.0(release):
NOTICE: SP_MIN: Built : 06:55:10, Apr 15 2021
INFO: ARM GICv2 driver initialized
INFO: Set calibration timer to 60 sec
INFO: ETZPC: UART1 (3) could be non secure
INFO: ETZPC: SPI6 (4) could be non secure
INFO: ETZPC: I2C6 (12) could be non secure
INFO: SP_MIN: Initializing runtime services
INFO: SP_MIN: Preparing exit to normal world <—— It blocks here for around 20 seconds before watchdog kicks in and resets the board.

Thanks, Rishi

[rishi@smufsbio.com]

Hi Neeraj,
Thanks, After some load testing we decided to use our external power supply in our initial prototype.
Yes you are right we will use VDD 1.8 but we still need 5 and 3.3 lines.

As our 5V load is around 400mA and our 3.3 load is USB hub and emmc chips which is around 250mA.

So after testing for like 20-30 minutes voltage was dropping a lot, 5.2 V was going down to 4.8~4.9V from BST_OUT and 3.3V was going down to 2.7~2.8V from LDO2.

So to be on safer side we decided to have our own external supply.

Thanks, Rishi

[rishi@smufsbio.com]

Hi All,
I am sorry probably i posted my question as soon as it came to my mind….
Reading further clarified i think 7.6.11 table clearly shows what should NOT be modified.

Thanks, Rishi

[rishi@smufsbio.com]

Neeraj,
Thanks for your response, i was able to start it by modifying the device tree.
Now i can see 5.2V on PMIC_BSTOUT.

Thanks, Rishi

[rishi@smufsbio.com]

Hi there,
Thanks everyone, Just an update, i was able to build my image using ST distribution package “openstlinux-5.4-dunfell-mp1-20-11-12”.

Just seeing few messages in kernel log like :
….
– [0.003383] /cpus/cpu@0 missing clock-frequency property
– [0.003420] /cpus/cpu@1 missing clock-frequency property
– [ 1.540689] Unable to get STM32 DDR PMU clock
…
– [1.613845] stm32-ddr-pmu: probed (ID=0x00140061 VER=0x00000010), DDR@533MHz
– [2.940962] VREF_DDR: supplied by vin
…

Anyways, thanks for support! But i guess need to test more thoroughly for stability and will see if i can fix these Cpu clock frequency properties.

Thanks, Rishi

[rishi@smufsbio.com]

Hi bduke,
Thanks a lot! I will give it a shot now.

[rishi@smufsbio.com]

Hi mlarkin,
Thanks for your response!
May be because of my lack of understanding but i thought working device tree blobs for osd32mp1-brk board are provided by octova systems at https://github.com/octavosystems/OSD32MP1-BRK-device-tree. So i tried using these device trees as it is. I did not regenerated with there cubemx app note.
If this is the case then today i will try to generate device tree from basic cube-mx project and will see how it goes.

Octova Team: Now i understand officially Octova systems is currently working on distribution package support for brk board, just wondering is this targeted in near future?

[rishi@smufsbio.com]

Hi bduke,
I am struggling from the last few days to build bootable image from distribution package using OSD32MP1-BRK devicetree.

While trying with repo TAG= openstlinux-5.4-dunfell-mp1-20-11-12 build always failed with :
Error: /stm32mp151/build-openstlinuxweston-stm32mp1-smufs/tmp-glibc/work-shared/stm32mp1-smufs/kernel-source/arch/arm/boot/#dts/ stm32mp157c-smufs.dts:1017.1-7 Label or path optee not found | FATAL ERROR: Syntax error parsing input tree

Using repo TAG= openstlinux-5.4-dunfell-mp1-20-06-24, everything builds fine but does n’t boot 🙁
Warning i got during build was :
WARNING: st-initrd-1.0-r0 do_package: Manifest /home/rishiosd/osd32mp1/build-openstlinuxweston-stm32mp1-smufs/tmp-glibc/sstate-control/manifest-x86_64_x86_64-nativesdk-st-image-resize-initrd.packagedata not found in stm32mp1_smufs cortexa7t2hf-neon-vfpv4 cortexa7t2hf-neon cortexa7t2hf-vfp cortexa7hf-neon-vfpv4 cortexa7hf-neon cortexa7hf-vfp armv7vet2hf-neon-vfpv4 armv7vehf-neon-vfpv4 armv7vet2hf-neon armv7vehf-neon armv7vet2hf-vfp armv7vehf-vfp armv7at2hf-vfp armv7ahf-vfp armv6thf-vfp armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp allarch x86_64_x86_64-nativesdk (variant ”)?

After building the sdcard booting stops at INFO: SP_MIN: Preparing exit to normal world.

Would you like to suggest any ideas or sharing your know know.
Thanks in advance.

[Author]

Posts