iMX8 not all cores starting

[Stefan Kalkowski]

Hi Pirmin,

On Tue, Oct 06, 2020 at 06:34:02PM +0200, Pirmin Duss wrote:
> Hi Stefan,
> 
> On 06/10/2020 18:29, Stefan Kalkowski wrote:
> > Hi Pirmin,
> > 
> > On Tue, Oct 06, 2020 at 06:13:36PM +0200, Pirmin Duss wrote:
> >> Hi Stefan,
> >>
> >> On 06/10/2020 16:18, Stefan Kalkowski wrote:
> >>>
> >>> sorry, for my misleading wrong sentence. I meant it has to be _not_
> >>> below 0x40000000. And I was refering to the ARM Trusted Firmware
> >>> sources, I found are the right one for the i.MX 8MQ EVK. For your SoC,
> >>> I found the line[0] to be the relevant one for the ip checking.
> >>>
> >>> The question arises what version of the ATF are you using. Did you
> >>> compiled the bootloader chain yourself?
> >>
> >> Yes, I have compiled the bootloader according to
> >> https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8_r2.0/Documentation/imx_boot_image_build.md
> >>
> >> ATF is in the version rel_imx_5.4.24_2.1.0 plus some patches by compulab.
> >>
> >> I will try It wit the version you have listed, and give feedback on how
> >> it went.
> > 
> > I did not wanted to encourage you to use another version for the ATF,
> > but if you use other sources it would make more sense to look inside
> > those to find out why you gain the result -9.
> > So maybe you should use your compulab version for further
> > investigation.
> 
> It also ocured to me, that I juts could look, what address the ATF of
> compulab uses. I just did this, and now log run works (for the record
> the address is 0x40200000).
> 
> Many thanks for your fast support.

nice that it works now. You're welcome!

Just out of curiosity: do you find out why their ATF restricts the
entrypoint even inside the DDR memory?

Regards Stefan

> 
> Best regards,
> Pirmin
> 
> _______________________________________________
> Genode users mailing list
> users at lists.genode.org
> https://lists.genode.org/listinfo/users

-- 
Stefan Kalkowski
Genode labs

https://github.com/skalk | https://genode.org