mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: SCHNEIDER Johannes <johannes.schneider@leica-geosystems.com>
To: Marco Felsch <m.felsch@pengutronix.de>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH master] i.MX: HAB: fix i.MX8MP field-return fuse
Date: Mon, 10 Mar 2025 16:36:37 +0000	[thread overview]
Message-ID: <AM8PR06MB7521AE5766581B704671ECB8BCD62@AM8PR06MB7521.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <20250310135154.bw6awpkjydcf32zp@pengutronix.de>

Hoi,

>
> On 25-03-10, Ahmad Fatoum wrote:
> > Hello Marco,
> >
> > On 3/10/25 12:36, Marco Felsch wrote:
> > > Current tests showed that fusing just the single field-return bit(0) on
> > > i.MX8MP SoCs brick the device.
> >
> > So such a device is bricked permanently with no way to upload
> > a bootloader again to fuse the remainder of the bits?
>
> Yes, as written here [3], the device isnow in "device asserts security
> violation" state, what ever this means but maybe: "I refuse to power
> up".

The imx does consume power, but does "nothing", e.g. does not boot from emmc,
say anything on the hardware serial or even enumerate the usb side.
And pulling the boot-mode pins to serial-download mode does also nothing,
even though the serial-dl is usually the one last and common fallback.

>
> [3] https://lore.kernel.org/all/a9ebece9-4ab6-4bca-bebe-985e0bf95278@oss.nxp.com/
>
> > Interesting thing to not document :/
>
> Took us 2 devices to figure it out :/ We also don't know why NXP doesn't
> care and don't update the (S)TRM since the v1 of [3] is 9months old.
>
> Regards,
>   Marco
>

gruß
Johannes



  reply	other threads:[~2025-03-10 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 11:36 Marco Felsch
2025-03-10 13:31 ` Ahmad Fatoum
2025-03-10 13:51   ` Marco Felsch
2025-03-10 16:36     ` SCHNEIDER Johannes [this message]
2025-03-12 10:22 ` Sascha Hauer

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=AM8PR06MB7521AE5766581B704671ECB8BCD62@AM8PR06MB7521.eurprd06.prod.outlook.com \
    --to=johannes.schneider@leica-geosystems.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=m.felsch@pengutronix.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