Olimex STMP1 SOM - Error starting up

[Gaël]

Hi!

I don't know if it's the same problem or if I have to create a new topic.

I have random boot error at starting up with SMTP1 LIME.

On thunderstorm power cuts, some boards don't restart.
On 20 STMP157-OLinuXino-LIME2H-EXT (Rev_B) boards in production approximately 5 boards remain frozen (its are distributed in several places so its do not suffer exactly the same power cuts).

I never have this problem when I reboot a board with a "shutdown -r now" (or "shutdown -r 00:00").

I did some tests and after some power cuts, the board stay frozen on :

Code Select Expand

U-Boot SPL 2021.04+olimex-1-20240312.134658 (Mar 12 2024 - 13:48:01 +0000)
Model: STM32MP1 OLinuXino-LIME
Init AXP209 PMIC
VDD Core set to: 1350 mv
When the board is frozen, the reset button don't help, the error returns.
A quick power cut doesn't help either.
For the error to disappear, the board need to be unplugged several seconds.
Quick power cuts seems to cause the problem every time.

NB : I tried with 1 A and 2 A power supply.

[LubOlimex]

It sounds like the same issue. You can easily test if it is - try the image without AXP initialization just to confirm. If these five boards that never boot, boot with it, then it is the same issue. Image is here:

https://ftp.olimex.com/TEMP/SOM-NO-AXP209/STM32MP1-OLinuXino-SOM-bullseye-minimal-20240328-133932.img.7z

Contact us at support@olimex.com about the issue with the boards that won't start when power supply is applied.

> Quick power cuts seems to cause the problem every time.

This is expected by design. All boards should fail to start if there was not enough time for the capacitors to discharge. There should be at least 2 seconds between power ups.

[Gaël]

Hi,

> This is expected by design. All boards should fail to start if there was not enough time for the capacitors to discharge. There should be at least 2 seconds between power ups.

I didn't know this limitation. I can't use LiPo battery to protect boards against micro power cuts because LiPo are not safe enough in the hot environments where boards are used (wood boiler).

After some tests, I can't reproduce the problem with this image even with quick power cuts : good news !

But I have a lot of errors during the first 100 seconds after boot :

Code Select Expand

[   83.123763] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   83.846734] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   84.570037] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   85.293739] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   86.017742] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   86.741530] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   87.465436] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   88.188899] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   88.911906] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   89.700894] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   90.422235] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   91.143840] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   91.864692] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   92.585549] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   93.307060] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   94.030435] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   94.752109] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   95.474055] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   96.196230] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   96.918255] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   97.640112] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   98.361737] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   99.082735] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   99.804734] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  100.526133] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  101.247231] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  101.968004] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  102.688578] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  103.409249] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
And I have no network :

Code Select Expand

olimex@stm32mp1-olinuxino-som:~$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
olimex@stm32mp1-olinuxino-som:~$
Edit : I understand the error messages, the kernel has been made for SOM not for LIME.

[LubOlimex]

Wait did you wrote that you have STMP LIME boards? The image and this forum thread is for STMP SOM boards, sorry my bad. It is normal to have errors since the image is suitable for only SOM boards.

We haven't noticed similar problems with LIME boards. Yours can be different problem.

[Gaël]

So, should I create a new thread ?

[LubOlimex]

Yes, better create a new thread.