I had the address wrong, so upon reboot, it got stuck. I modified it
to be the last part of the RAM, and the sig seems to be 0x
always. I'd like to know how to "force" a panic, so I could check
whether it writes something or is the sig still 0x. The size
is 1M.
As I understand, whe
I think I managed to get ram_console working on the working kernel, it
gives this in kmsg:
<6>[1, swapper] [0.256378] ram_console: got buffer at 3a0,
size 4
<6>[1, swapper] [0.256408] ram_console: no valid data in buffer
(sig = 0x20008808)
<6>[1, swapper] [0.256561] console [ra
So it works in any case. Thanks, I'll check it out and post the
result.
On Feb 1, 8:55 am, jagan <402ja...@gmail.com> wrote:
> That's what, I too taking about.
>
> If your device doesn't boot, unable to see any logsSo try to enable
> RAM_CONSOLE in working & as well
> as non-working kernel [yo
That's what, I too taking about.
If your device doesn't boot, unable to see any logsSo try to enable
RAM_CONSOLE in working & as well
as non-working kernel [your case].
Boot the non-working kernel first & try to boot the working kernel & get
the crash log.
BR, Jagan.
On Mon, Jan 30, 2012 at
I said it does not boot (crashes directly on boot, does not do a
reboot), so that's not an option. But now I am thinking MMC is not
working... My device has all partitions on one MMC. And is there a way
to somehow initialize USB before anything else? To see whether it
works or not...
On Jan 25, 6:
Usually when we'r directly working on device, RAM_CONSOLE is better choice.
To setup this we have a ram_console driver at drivers/staging/android path
[enable it] & you just create a
platform device entry in BSP code.
Once you have any crash/hang happening on your device, for next the reboot
try
The ram_console is very interesting, but how should I get it, if it
does not boot? Does it matter if I boot recovery or Android?
On Jan 24, 10:01 pm, jagan <402ja...@gmail.com> wrote:
> Is there a way to save the log somewhere (like /cache or /data), so I
> could check what did not work and get a
Is there a way to save the log somewhere (like /cache or /data), so I
could check what did not work and get a start somewhere.
> there is a debug procedure called, RAM_CONSOLE, find it on google[enough
info]
Regards,
Jagan.
On Tue, Jan 24, 2012 at 9:29 PM, Rudolf Tammekivi wrote:
> It's MSM7x30,
It's MSM7x30, and when I am browsing through the manufacturer's code,
I see they have taken the msm7x30 board and simply modified for their
needs. So I am currently trying to do the same.
What do you mean by "procedural way"? I did an early build, after the
boot logo, it simply turned off/screen tu
