public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] imx8: add sc_misc_seco_build_info()
Date: Thu, 24 Oct 2019 15:54:09 +0200	[thread overview]
Message-ID: <20191024155409.6d64a7ae@crub> (raw)
In-Reply-To: <DB7PR04MB4490AF1FD72C9A263ED3E44388680@DB7PR04MB4490.eurprd04.prod.outlook.com>

Hi Peng,

On Tue, 22 Oct 2019 02:47:28 +0000
Peng Fan peng.fan at nxp.com wrote:
...
> > Subject: [PATCH 2/3] imx8: add sc_misc_seco_build_info()  
> 
> sc_seco_build_info already in Stefano's tree.

sc_seco_build_info() in current git master works on i.MX8QXP MEK board,
but it doesn't work on my custom board with different blobs. Here U-Boot
triggers system reset somewhere in sc_seco_build_info()->misc_call().

With sc_misc_seco_build_info() in this patch getting the IDs works,
I've following IDs on this board:
SCFW 65afe5f6, SECO-FW 9d71fd5b, ATF d6451cc

The differences:
sc_seco_build_info() uses SC_RPC_SVC_SECO/SECO_FUNC_BUILD_INFO,
sc_misc_seco_build_info() uses SC_RPC_SVC_MISC/MISC_FUNC_SECO_BUILD_INFO.

Any idea why sc_seco_build_info() ends in system reset?

Thanks,

--
Anatolij

  parent reply	other threads:[~2019-10-24 13:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 15:58 [U-Boot] [PATCH 1/3] mach-imx: Adding new argument for SIP call interface Anatolij Gustschin
2019-10-21 15:58 ` [U-Boot] [PATCH 2/3] imx8: add sc_misc_seco_build_info() Anatolij Gustschin
2019-10-22  2:47   ` Peng Fan
2019-10-22  7:40     ` Anatolij Gustschin
2019-10-24 13:54     ` Anatolij Gustschin [this message]
2019-10-25  1:45       ` Peng Fan
2019-10-21 15:58 ` [U-Boot] [PATCH 3/3] imx8: output SECO-FW, ATF and imx-mkimage commit IDs Anatolij Gustschin
2019-10-22  2:49   ` Peng Fan
2019-10-22  7:57     ` Anatolij Gustschin
2019-10-21 17:12 ` [U-Boot] [PATCH 1/3] mach-imx: Adding new argument for SIP call interface Patrick Wildt
2019-10-22  7:53 ` Anatolij Gustschin

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=20191024155409.6d64a7ae@crub \
    --to=agust@denx.de \
    --cc=u-boot@lists.denx.de \
    /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