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:41 pm, jagan <402ja...@gmail.com> wrote: > 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 to dump the log from > /proc/last_kmsg [where you can get the previous crash log]...debug it > > Regards, > Jagan. > > On Wed, Jan 25, 2012 at 7:26 PM, Rudolf Tammekivi <rtammek...@gmail.com>wrote: > > > > > > > > > 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 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 <rtammek...@gmail.com > > >wrote: > > > > > 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 turned off, USB did not work. I > > > > did try this on the recovery, because that should not need all things > > > > Android needs, right? > > > > > 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. > > > > > On Jan 24, 8:41 am, jagan <402ja...@gmail.com> wrote: > > > > > What is your device QC Chipset? > > > > > -If you your phone chipset supports the downloaded msm kernel, try to > > > > > download msm-2.6.35[chipset supportable]. > > > > > do the diff b/w msm-2.6.35 to your device kernel, identify the > > device > > > > > spec changes & apply them on msm-3.0. > > > > > > Be-careful you need to do it in a procedural way. > > > > > > Regards, > > > > > Jagan. > > > > > > On Sat, Jan 21, 2012 at 11:46 PM, Rudolf Tammekivi < > > rtammek...@gmail.com > > > > >wrote: > > > > > > > My device has 2.6.35.7 source code provided, but I want to upgrade > > it > > > > to > > > > > > 3.0. Most of the 2.6.35.7 sources are from CodeAurora, which are > > > > modifed by > > > > > > manufacturer, and I have already downloaded the 3.0 base for msm. > > What > > > > are > > > > > > the mandatory things I need to modify in order to make it boot? > > Like > > > > CPU, > > > > > > display, memory. > > > > > > > -- > > > > > > unsubscribe: android-kernel+unsubscr...@googlegroups.com > > > > > > website:http://groups.google.com/group/android-kernel > > > > > -- > > > > unsubscribe: android-kernel+unsubscr...@googlegroups.com > > > > website:http://groups.google.com/group/android-kernel > > > -- > > unsubscribe: android-kernel+unsubscr...@googlegroups.com > > website:http://groups.google.com/group/android-kernel -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
