On 05.09.17 15:02, Matwey V. Kornilov wrote:
2017-09-05 16:00 GMT+03:00 Alexander Graf <ag...@suse.de>:
On 05.09.17 14:58, Matwey V. Kornilov wrote:
Still no luck. No signal at video, no text in console after EFI stub.
Any ideas why?
Can you try to make earlycon work? I'm sure someone has the magic parameters
for it somewhere...
Indeed. But they don't work either. Ones which should is
earlycon=uart8250,mmio32,0xff130000
That is very odd. Usually earlycon works. The only case I've found where
it was unintuitively broken was when U-Boot ran in EL3, but I assume you
do have ATF running somewhere, right?
What you can still try is to recover the kernel log from RAM. For that,
boot up the system, then reset (don't power cycle, use the reset button
if available, otherwise use the reset line on the jtag port if
available). After reset, you should get back to U-Boot. There, run
"bdinfo" to find out the base offset of RAM.
Then do "nm vmlinux | grep log_buf" on the vmlinux file to the kernel
you executed. You may have to extract it first, as it comes gzip'ed by
default. In there you will find Linux virtual addresses for log_buf
locations. IIRC __log_buf is the one you want. Remove the high 1-bits
from that address, then add the RAM offset to it. That *should*
hopefully be the offset into RAM for the dmesg buffer.
With that address, try to "md.b" its contents from the U-Boot command
line. With a bit of luck you can spot something. If not we either had
kASLR hit or didn't get as far as writing a dmesg buffer...
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
