Re: [coreboot] Current coreboot source tree ( revision 6084 ) for ASUS M2V-MX SE cannot boot?

[Tobias Diedrich]

That looks very unlikely to be the real rootcause I think.
For the M2V-MX SE the added code path shouldn't be taken anyway.
And given that you do get output on the serial console the bootblock
should be working just fine I think.

Fengwei:
Can you check that reverting just the bootblock.c changes from the
current revision fixes it?
I think it's more likely that the changes to
src/southbridge/via/vt8237r/vt8237r_early_smbus.c
cause the problem.

Tobias

Stefan Reinauer wrote:
> CCing author and reviewer.. Tobias, Peter, any idea?
> Fengwei Zhang  [101118 01:24]:
> > The broken version is 6062, version 6061 is good.
> > there is the diff
> >
> > http://tracker.coreboot.org/trac/coreboot/changeset?old_path=%2Ftrunk&ol...
> >
> > Best,
> > Fengwei
> >
> > On 11/17/2010 06:08 PM, Stefan Reinauer wrote:
> > > Fengwei Zhang  [101117 22:41]:
> > > > Hi all,
> > > >
> > > > I am not sure if this is true. I just tried current coreboot source
> > > > tree (revision 6084) for ASUS M2V-MX SE, it cannot boot.
> > > > It could compile successfully, and it will be dead at the beginning
> > > > when booting.
> > > > Below are the info from serial port:
> > > >
> > > > coreboot-4.0-r6070M Wed Nov 17 16:20:19 EST 2010 starting...
> > > > now booting...
> > > >
> > > > INIT detected from  --- { APICID = 00 NODEID = 00 COREID = 00} ---
> > > >
> > > > Issuing SOFT_RESET...
> > > > soft reset
> > > >
> > > > I also compiled old versions, it could boot. such as version 5555(I
> > > > just random picked up and tested it)
> > > >
> > > > I am wondering if there is anyone has some problem?
> > >
> > > Can you please find out which revision broke it?
> > >
> > > Stefan