[eldam_fr]

Well, with the help of ST Teams,
I solved this issue:

We were using nrst signal for resetting emmc.
Emmc was powered by +3.3(PMIC_VOUT4).
During power down sequence, +3.3(PMIC_VOUT4) was shutting down, emmc was not powered and maybe driving nrst low.(maybe)
If we cut the connection between nrst(pmic) and rst(emmc), i can poweroff my board.

I have a look on an Octavo’BRK board, monitoring with a scope reset,+3V3,VDDI when poweroff command line issued.
I was surprised that there is no activity on reset, only +3V3 is shutting down.
I thinked that after a poweroff command, stpmic put stmp2MP1 in reset state(assert nrst) and then shut-off power line.
Anyway, board works now..

[eldam_fr]

Hello Mr Basu,
Thanks a lot for answering me.

I will try what you said, and hope it will work.
(my prescient menthat sense, have sensed this approach, but was not sure..).

By the way,
Does the use of the “minimal config files” are mandatory to use (due to SIP aspect or DDR param) or can i use any DK2 files from ST?

Have a nice weekend

[eldam_fr]

Well First of all, thanks a lot for guiding us in this Innsmouth fog.

Your idea to keep rootfs separated from the Uboot/Tfa seems good, but I’ve seen on ST Forum that we shouldn’t mix SDK version (V1.2 / V2.0) (tfa/uboot/kernel files within each others (…)). At this time, we won’t use Debian Distri, we are working on a embedded system, and we should keep things simple & minimal.

I will give this a try.

See you!

[Author]

Posts