From: Jens Maus <mail@jens-maus.de>
To: "Ivan T. Ivanov" <iivanov@suse.de>
Cc: Stefan Wahren <wahrenst@gmx.net>, u-boot@lists.denx.de
Subject: Re: [PATCH v4 0/6] rpi5: initial support
Date: Fri, 19 Jan 2024 17:53:03 +0100 [thread overview]
Message-ID: <489FBAE5-501A-49F6-894D-58BE5C5429CC@jens-maus.de> (raw)
In-Reply-To: <dvpwizpui6a52dfmy57ghv4zmplvgqvow6oec7x5opwzh63zzl@jehyglofr6yh>
> Am 19.01.2024 um 17:29 schrieb Ivan T. Ivanov <iivanov@suse.de>:
>
>> So you say with your own u-boot.bin you see serial U-Boot output after that „NOTICE: BL31: …“ lines? On that special UART port on the rpi5 or on the UART on the GPIO header?
>>
>
> Yes :-) See attached log file.
Really strange that in your case U-Boot seems to come up nicely and outputs something on the debug UART. Here definitely not. And the only difference in the rpi boot loader log outputs I could spot between yours and mine is:
— cut here —
--- uboot2.log 2024-01-19 17:36:18.099674743 +0100
+++ uboot1.log 2024-01-19 17:33:06.794258533 +0100
@@ -1,13 +1,13 @@
-RPi: BOOTSYS release VERSION:30cc5f37 DATE: 2024/01/05 TIME: 15:57:40
-BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1704470260 serial 9127ae99 boardrev d04170 stc 930201
+RPi: BOOTSYS release VERSION:30de0ba5 DATE: 2023/10/30 TIME: 16:45:10
+BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1698684310 serial 3c533ede boardrev c04170 stc 815886
AON_RESET: 00000003 PM_RSTS 00001000
RP1_BOOT chip ID: 0x20001927
PM_RSTS: 0x00001000
part 00000000 reset_info 00000000
PMIC reset-event 00000000 rtc 00000000 alarm 00000000 enabled 0
uSD voltage 3.3V
-Initialising SDRAM 'Micron' 32Gb x2 total-size: 64 Gbit 4267
-DDR 4267 1 0 64 152
+Initialising SDRAM 'Samsung' 16Gb x2 total-size: 32 Gbit 4267
+DDR 4267 1 0 32 152
RP1_BOOT chip ID: 0x20001927
RP1_BOOT chip ID: 0x20001927
@@ -17,18 +17,17 @@
PCIe scan 00001de4:00000001
RP1_CHIP_INFO 20001927
-RPi: BOOTLOADER release VERSION:30cc5f37 DATE: 2024/01/05 TIME: 15:57:40
-BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1704470260 serial 9127ae99 boardrev d04170 stc 3949421
+RPi: BOOTLOADER release VERSION:30de0ba5 DATE: 2023/10/30 TIME: 16:45:10
+BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1698684310 serial 3c533ede boardrev c04170 stc 3726990
AON_RESET: 00000003 PM_RSTS 00001000
-M.2 PCIe HAT not detected.
usb_pd_init status 1
Boot mode: SD (01) order f4
SD HOST: 200000000 CTL0: 0x00800000 BUS: 400000 Hz actual: 390625 HZ div: 512 (256) status: 0x1fff0000 delay: 276
SD HOST: 200000000 CTL0: 0x00800f00 BUS: 400000 Hz actual: 390625 HZ div: 512 (256) status: 0x1fff0000 delay: 276
-OCR c0ff8000 [310]
-CID: 00035344534536344780519441cb0123
-CSD: 400e00325b590001dbd37f800a404000
-SD: bus-width: 4 spec: 2 SCR: 0x02458443 0x00000000
+OCR c0ff8000 [118]
+CID: 00035344534e33324780fa570bda0169
+CSD: 400e00325b590000edb07f800a400000
+SD: bus-width: 4 spec: 2 SCR: 0x02358483 0x00000000
SD HOST: 200000000 CTL0: 0x00800f04 BUS: 50000000 Hz actual: 50000000 HZ div: 4 (2) status: 0x1fff0000 delay: 2
MBR: 0x00002000, 131072 type: 0x0c
MBR: 0x00022000, 1024000 type: 0x82
@@ -39,7 +38,6 @@
rsc 4 fat-sectors 128 root dir cluster 1 sectors 32 entries 512
FAT16 clusters 32695
[sdcard] autoboot.txt not found
-Select partition rsts 0 C(boot_partition) 0 EEPROM config 0 result 0
Trying partition: 0
type: 16 lba: 8192 'mkfs.fat' ' V ^ ' clusters 32695 (4)
rsc 4 fat-sectors 128 root dir cluster 1 sectors 32 entries 512
@@ -52,6 +50,7 @@
Read bcm2712-rpi-5-b.dtb bytes 79357 hnd 0x139f
dt-match: compatible: raspberrypi,5-model-b match: brcm,bcm2712
dt-match: compatible: brcm,bcm2712 match: brcm,bcm2712
+PM_RSTS 00001000
Selecting USB low current limit
NOTICE: BL31: v2.6(release):v2.6-239-g2a9ede0bd
— cut here —
So lets see if after you updated to a more recent rpi eeprom U-boot is still able to boot…
regards,
jens
--
Jens Maus, Dresden/Germany
http://jens-maus.de/
next prev parent reply other threads:[~2024-01-19 16:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 13:10 [PATCH v4 0/6] rpi5: initial support Jens Maus
2024-01-17 15:07 ` Ivan T. Ivanov
2024-01-17 15:13 ` Jens Maus
2024-01-17 15:23 ` Ivan T. Ivanov
2024-01-17 15:30 ` Jens Maus
2024-01-17 16:45 ` Ivan T. Ivanov
2024-01-17 23:06 ` Jens Maus
2024-01-18 8:33 ` Ivan T. Ivanov
2024-01-18 17:18 ` Jens Maus
2024-01-19 5:29 ` Ivan T. Ivanov
2024-01-19 7:21 ` Jens Maus
2024-01-19 9:20 ` Stefan Wahren
2024-01-19 10:49 ` Jens Maus
[not found] ` <sjmi6dftbgx56isfyjtaryehzq2iollwxm2etlspiygehh3n6v@k4ws56nsbgfn>
[not found] ` <6C9E5E0C-9C27-45A4-886F-8B8C641EF7A3@jens-maus.de>
2024-01-19 13:46 ` Ivan T. Ivanov
2024-01-19 13:54 ` Jens Maus
2024-01-19 14:06 ` Ivan T. Ivanov
2024-01-19 14:08 ` Jens Maus
2024-01-19 14:24 ` Ivan T. Ivanov
2024-01-19 16:12 ` Jens Maus
2024-01-19 16:29 ` Ivan T. Ivanov
2024-01-19 16:53 ` Jens Maus [this message]
2024-01-19 21:26 ` Jens Maus
2024-01-20 9:22 ` Stefan Wahren
2024-01-20 9:48 ` Jens Maus
2024-01-20 10:50 ` Stefan Wahren
2024-01-22 11:57 ` Ivan T. Ivanov
2024-01-22 14:16 ` Ivan T. Ivanov
2024-01-22 14:30 ` Mark Kettenis
2024-01-22 18:01 ` Tom Rini
2024-01-23 11:11 ` Jens Maus
2024-01-23 12:09 ` Stefan Wahren
-- strict thread matches above, loose matches on Subject: below --
2024-01-10 12:29 Ivan T. Ivanov
2024-01-22 13:46 ` Matthias Brugger
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=489FBAE5-501A-49F6-894D-58BE5C5429CC@jens-maus.de \
--to=mail@jens-maus.de \
--cc=iivanov@suse.de \
--cc=u-boot@lists.denx.de \
--cc=wahrenst@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).