Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14006] New: op-tee not start on imx8mm_evk
Date: Sat, 15 Jun 2024 14:59:12 +0000	[thread overview]
Message-ID: <bug-14006-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=14006

            Bug ID: 14006
           Summary: op-tee not start on imx8mm_evk
           Product: buildroot
           Version: 2021.05
          Hardware: Other
                OS: Other
            Status: RESOLVED
          Severity: major
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: v9sd@yandex.ru
                CC: buildroot@uclibc.org, yann.morin.1998@free.fr
  Target Milestone: ---
                CC: yann.morin.1998@free.fr
        Resolution: MOVED
            Status: RESOLVED

Hello!
I have a problem with op-tee start on imx8mm_evk
(https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/evaluation-kit-for-the-i-mx-8m-mini-applications-processor:8MMINILPD4-EVK).

My .config file is attached.


I write output/images/sdcard.img on sdcadr, connect terminal emultaion with
serial port and start imx8.

After below output imx8mm_evk is output nothing.
U-Boot SPL 2020.04 (Jul 12 2021 - 16:19:50 +0300)
Can't find PMIC:PCA9450
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC1
NOTICE:  BL31: v2.4(release):2021.05-393-gb928074e2d
NOTICE:  BL31: Built : 16:16:43, Jul 12 2021


Problem arises after jump execution on op-tee entry point address (0xbe000000)


After reaching the above address breakpoint, we have content in memory: 

(gdb) x/10i $pc
=> [34m0xbe000000[m <[33m_start[m>:     .inst   0x00150000 ; undefined
   [34m0xbe000004[m <[33m_start[m+4>:   .inst   0x00000000 ; undefined
   [34m0xbe000008[m <[33m_start[m+8>:   .inst   0x00000000 ; undefined
   [34m0xbe00000c[m <[33m_start[m+12>:  .inst   0x00000000 ; undefined
   [34m0xbe000010[m <[33m_start[m+16>:  .inst   0x00000000 ; undefined
   [34m0xbe000014[m <[33m_start[m+20>:  .inst   0x00000000 ; undefined
   [34m0xbe000018[m <[33m_start[m+24>:  .inst   0x00000000 ; undefined
   [34m0xbe00001c[m <[33m_start[m+28>:  .inst   0x00000000 ; undefined
   [34m0xbe000020[m <[33m_start[m+32>:  .inst   0x00000000 ; undefined
   [34m0xbe000024[m <[33m_start[m+36>:  .inst   0x00400000 ; undefined

As we look, it is not valid instructions opcode.

After continue execution, imx8 freezes.

Guess that the op-tee was not load in memory in uboot-spl.

--- Comment #1 from v9sd@yandex.ru ---
Created attachment 9061
  --> https://bugs.busybox.net/attachment.cgi?id=9061&action=edit
My config (without comments and empty lines)

--- Comment #2 from v9sd@yandex.ru ---
*** Bug 14001 has been marked as a duplicate of this bug. ***

--- Comment #3 from v9sd@yandex.ru ---
*** Bug 14011 has been marked as a duplicate of this bug. ***

--- Comment #4 from v9sd@yandex.ru ---
*** Bug 14016 has been marked as a duplicate of this bug. ***

--- Comment #5 from v9sd@yandex.ru ---
*** Bug 14021 has been marked as a duplicate of this bug. ***

--- Comment #6 from v9sd@yandex.ru ---
Data from  op-tee entry point address without service info:
(gdb) x/10i $pc
=> 0xbe000000 <_start>:     .inst   0x00150000 ; undefined
   0xbe000004 <_start+4>:   .inst   0x00000000 ; undefined
   0xbe000008 <_start+8>:   .inst   0x00000000 ; undefined
   0xbe00000c <_start+12>:  .inst   0x00000000 ; undefined
   0xbe000010 <_start+16>:  .inst   0x00000000 ; undefined
   0xbe000014 <_start+20>:  .inst   0x00000000 ; undefined
   0xbe000018 <_start+24>:  .inst   0x00000000 ; undefined
   0xbe00001c <_start+28>:  .inst   0x00000000 ; undefined
   0xbe000020 <_start+32>:  .inst   0x00000000 ; undefined
   0xbe000024 <_start+36>:  .inst   0x00400000 ; undefined

--- Comment #7 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Thank you for your report.

The issue tracker for the Buildroot project has been moved to
the Gitlab.com issue tracker:
    https://gitlab.com/buildroot.org/buildroot/-/issues

We are taking this opportunity to close old issues in this old
tracker. If you believe your issue is still relevant, please
open one in the new issue tracker.

Thank you!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

                 reply	other threads:[~2024-06-15 14:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14006-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox