From: Renaud Barbier <Renaud.Barbier@ametek.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: RE: NVME o nLS1046A-RDB
Date: Tue, 12 Nov 2024 11:48:45 +0000 [thread overview]
Message-ID: <BYAPR07MB435804EEFB6FF352E07CF9F9EC592@BYAPR07MB4358.namprd07.prod.outlook.com> (raw)
In-Reply-To: <ZzMKUugcLKGY4aq-@pengutronix.de>
>
> Ok, 0x00000000 could be correct or not. Try md -s /dev/nvme0n1 0+512, it
> should give you the protective MBR at the end. Or use some other non-empty
> area and verify with Linux the data is correct.
barebox@LS1046A RDB Board:/ md -s /dev/nvme0n1 512
00000200: 20494645 54524150 00010000 0000005c EFI PART....\...
00000210: 40c45fac 00000000 00000001 00000000 ._.@............
00000220: 37e436af 00000000 00000022 00000000 .6.7....".......
00000230: 37e4368e 00000000 1fc28552 4ef94807 .6.7....R....H.N
00000240: c1d791b1 f9f74875 00000002 00000000 ....uH..........
00000250: 00000080 00000080 a95c01c9 00000000 ..........\.....
00000260: 00000000 00000000 00000000 00000000 ................
>
> DMA issues as Ahmad mentioned is a good guess.
I will go for the newer barebox .
Thanks.
>
> Sascha
>
> --
> Pengutronix e.K. | |
> Steuerwalder Str. 21 |
> https://urldefense.com/v3/__http://www.pengutronix.de/__;!!HKOSU0g!GiA
> 4jHEWr6erg1nQ8tci8dnGc7rYsIO3FriXc_wSiCDkgfIBsd0hF8nKRgPCdzAIlVSVij
> 8yeGe2rvSrR63YJ_bzAQ$ |
> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-11-12 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 13:42 Renaud Barbier
2024-11-08 11:05 ` Sascha Hauer
2024-11-11 11:15 ` Renaud Barbier
2024-11-12 7:57 ` Sascha Hauer
2024-11-12 11:48 ` Renaud Barbier [this message]
2024-11-11 11:30 ` Ahmad Fatoum
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=BYAPR07MB435804EEFB6FF352E07CF9F9EC592@BYAPR07MB4358.namprd07.prod.outlook.com \
--to=renaud.barbier@ametek.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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