froyo build not booting on sapphire

[Earlence]

Hi,

I have downloaded the froyo code using the "-b froyo" branch.
I lunched a full sapphire userdebug build.
I tested the build on the emulator and it works fine.
I flashed the build to an HTC sapphire (after erasing cache and
userdata).
It just hangs at the google I/O screen. I cannot run adb -> it just
tells me "waiting for device"
Help!

Cheers,
Earlence

[Jean-Baptiste Queru]

I'll need to do a build to double-check.

My guess is that you might have a mismatch between the radio image and
the boot image. The layout of physical RAM in sapphire was changed for
froyo (to squeeze a bit of space out).

The radio image and the kernel in the boot image must match so that
they agree on the layout of physical memory. Otherwise different chips
stomp on one another's toes and things go bad very quickly.

JBQ

> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Jean-Baptiste Queru]

I've had a look, the answer is that "it's complicated". On my side,
flashing the images from the AOSP froyo on the donut radio
(2.22.19.26I) also doesn't work.

The trickiness is that the froyo branch is more or less build FRG83
(i.e. 2.2.1_r1), which is neither the same as donut-based builds nor
the same as FRG83D (which are what shipped on sapphire).

JBQ

[Jan]

Earlence,
I have an ADP1 with a tweaked radio (2.22.19.26I), and for the most
part installed the SPL from the Sapphire. I had the same issue, but
when I built and installed a custom kernel (2.6.35) it booted fine.

~ Jan

On Jan 4, 2:05 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> I've had a look, the answer is that "it's complicated". On my side,
> flashing the images from the AOSP froyo on the donut radio
> (2.22.19.26I) also doesn't work.
>
> The trickiness is that the froyo branch is more or less build FRG83
> (i.e. 2.2.1_r1), which is neither the same as donut-based builds nor
> the same as FRG83D (which are what shipped on sapphire).
>
> JBQ
>
>
>
>
>
>
>
>
>
> On Tue, Jan 4, 2011 at 10:03 AM, Jean-Baptiste Queru <j...@android.com> wrote:
> > I'll need to do a build to double-check.
>
> > My guess is that you might have a mismatch between the radio image and
> > the boot image. The layout of physical RAM in sapphire was changed for
> > froyo (to squeeze a bit of space out).
>
> > The radio image and the kernel in the boot image must match so that
> > they agree on the layout of physical memory. Otherwise different chips
> > stomp on one another's toes and things go bad very quickly.
>
> > JBQ
>