buildrom error with M2V-MX SE

[Nathan Owens]

I'm getting the following error when using buildrom:

cp: cannot create regular file 
`/home/nate/buildrom/buildrom-devel/work/coreboot/svn/targets//asus/m2v-mx_se/m2v-mx_se/payload.elf': 
No such file or directory
make: *** 
[/home/nate/buildrom/buildrom-devel/work/coreboot/svn/targets//asus/m2v-mx_se/m2v-mx_se/payload.elf] 
Error 1

It looks like there is one too many forward slashes in the path.

Thanks,
Nate

[Patrick Georgi]

Am 20.04.2010 17:45, schrieb Nathan Owens:
> I'm getting the following error when using buildrom:
>
> cp: cannot create regular file
> `/home/nate/buildrom/buildrom-devel/work/coreboot/svn/targets//asus/m2v-mx_se/m2v-mx_se/payload.elf':
> No such file or directory
> make: ***
> [/home/nate/buildrom/buildrom-devel/work/coreboot/svn/targets//asus/m2v-mx_se/m2v-mx_se/payload.elf]
> Error 1
>
> It looks like there is one too many forward slashes in the path.

POSIX requires all multiple slashes (except at the beginning of the
path) to be eliminated, so the slashes are resolved by the system.

The issue is that we don't have "targets" anymore. buildrom probably
needs some update for the coreboot build method.

Regards,
Patrick Georgi

[Marc Jones]

On Tue, Apr 20, 2010 at 10:15 AM, Patrick Georgi  wrote:
> Am 20.04.2010 17:45, schrieb Nathan Owens:
> > I'm getting the following error when using buildrom:
> >
> > cp: cannot create regular file
> > `/home/nate/buildrom/buildrom-devel/work/coreboot/svn/targets//asus/m2v-mx_se/m2v-mx_se/payload.elf':
> > No such file or directory
> > make: ***
> > [/home/nate/buildrom/buildrom-devel/work/coreboot/svn/targets//asus/m2v-mx_se/m2v-mx_se/payload.elf]
> > Error 1
> >
> > It looks like there is one too many forward slashes in the path.
>
> POSIX requires all multiple slashes (except at the beginning of the
> path) to be eliminated, so the slashes are resolved by the system.
>
> The issue is that we don't have "targets" anymore. buildrom probably
> needs some update for the coreboot build method.

Yes, buildrom is very much out of date and kconfig does a lot of what
buildrom was doing. It may be time to drop buildrom.

Marc

[Myles Watson]

> > The issue is that we don't have "targets" anymore. buildrom probably
> > needs some update for the coreboot build method.
>
> Yes, buildrom is very much out of date and kconfig does a lot of what
> buildrom was doing. It may be time to drop buildrom.

I think buildrom is still useful for building payloads.  I agree that it
doesn't help much with coreboot any more.

Thanks,
Myles

[Cristi Magherusan]

On Tue, 2010-04-20 at 10:42 -0600, Myles Watson wrote:
> > > The issue is that we don't have "targets" anymore. buildrom probably
> > > needs some update for the coreboot build method.
> >
> > Yes, buildrom is very much out of date and kconfig does a lot of what
> > buildrom was doing. It may be time to drop buildrom.
>
> I think buildrom is still useful for building payloads.  I agree that it
> doesn't help much with coreboot any more.
>
> Thanks,
> Myles

It's just a thought, but for payloads we could switch to buildroot which
should do a much better job at that and also could integrate coreboot to
be able to create full ROM images.

Regards,
Cristi

[Stefan Reinauer]

On 4/22/10 11:54 PM, Cristi Magherusan wrote:
> On Tue, 2010-04-20 at 10:42 -0600, Myles Watson wrote:
> > > > The issue is that we don't have "targets" anymore. buildrom probably
> > > > needs some update for the coreboot build method.
> > >
> > > Yes, buildrom is very much out of date and kconfig does a lot of what
> > > buildrom was doing. It may be time to drop buildrom.
> >
> > I think buildrom is still useful for building payloads.  I agree that it
> > doesn't help much with coreboot any more.
> >
> > Thanks,
> > Myles
>
> It's just a thought, but for payloads we could switch to buildroot which
> should do a much better job at that and also could integrate coreboot to
> be able to create full ROM images.

Maybe it makes sense to import the remainder of buildrom into the
coreboot "payloads" kconfig menu?

We are hopefully going to see a GSoC project about this topic this year..!

Stefan

[Rudolf Marek]

Hi,

If you need the 1024KB image I can build it for you/test this evening which is 
just now but still not back @home.

You can use IRC #coreboot on irc.freenode.net to contact me (as ruik) too.

Thanks,
Rudolf

[Rudolf Marek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I put new image

http://assembler.cz/rom/m2v-mx_se-r5467+SeaBIOS+VGABIOS.rom

Links are on wiki:

http://www.coreboot.org/ASUS_M2V-MX_SE#Demo_image

It has the VGA BIOS from SeaBIOS so 100% free software! Please do not expect
much from VGA just a console works, I did not test anything fancy.

Bad news is that 1024KB image does not work for some reason, but you can
do:

dd if=/dev/zero of=512bin bs=1k count=512
cat 512bin m2v-mx_se-r5192+SeaBIOS+VGABIOS.rom > final.rom

and flash a final.rom (which is now 1024KB and works) I think there is something
wrong with bootblock not decoding whole flash region. I'm trying to fix it right
now.

Rudolf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvOBl0ACgkQ3J9wPJqZRNV1CwCeL3vOBV23B/OBbkHYA6aynymo
LugAoLU8cZpyGTMUtLrdTGLAl5HQAF3B
=WmDI
-----END PGP SIGNATURE-----