[coreboot] Samsung 550 Chromebook own Coreboot

[Aaron Durbin]

John,

Are you checking out the blobs repo into 3rdparty? In that repo there
are the following blobs for lumpy:

http://review.coreboot.org/gitweb?p=blobs.git;a=tree;f=mainboard/samsung/lumpy;h=b4c159f20789c0eacdf5a25135a3275d277cf256;hb=refs/heads/master

The descriptor and me blobs don't live in cbfs. They live in the rom
but not as cbfs files.

Offset 0:
descriptor.bin
Offset 0 + sizeof(descriptor.bin):
me.bin
Offset 0 + sizeof(descriptor.bin) + sizeof(me.bin):
Usable rom space for corebot. This should be 6MiB. i.e. descriptor +
me.bin take 2MiB (there is some rounding).

The mrc.bin needs to be at a fixed location in the address space (and
fixed location in rom) in order to work correctly.

You will need adjust the CONFIG_ paths in  your .config for the build
to work. Looking at src/southbridge/intel/bd82x6x/Makefile.inc I see
CONFIG_HAVE_ME_BIN needs to be set to y and CONFIG_ME_BIN_PATH needs
to be set accordingly like I provided my previous example for mrc.bin.

Could you provide more details of your .config and the location of the
blobs on your local file system? This sounds like a simple build issue
in that the pieces aren't being placed in the proper places. I'm
guessing the default path locations in the Kconfigs just don't line up
correctly -- thus leading to some manual intervention.

-Aaron

On Wed, Jul 24, 2013 at 6:30 AM, John Lewis <jlewis at johnlewis.ie> wrote:
> Well, that didn't work, although the fan briefly span up, which I didn't
> notice before.
>
> I also tried building your beloved Parrot, and that is missing me.bin too.
>
>
> On 24/07/2013 11:26, John Lewis wrote:
>
>> I realise that this may well not work for reasons I don't understand,
>> but I have manually added the me.bin file to coreboot.rom using
>> cbfstool. Worth a try, I thought.
>>
>> On 24/07/2013 07:38, ron minnich wrote:
>>
>>> On Tue, Jul 23, 2013 at 9:44 PM, Peter Stuge <peter at stuge.se [1]>
>>>
>>> wrote:
>>>
>>>> I guess eliminating that deployment/release process completely is the
>>>> reason to just always work directly upstream.
>>>
>>> well, that deploy/release process is not going to be eliminated. I'm
>>> just working on some ideas to make things better in the context of that
>>> process, which I think is doable. I'm just grateful John is a patient
>>> and reasonable guy :-) ron
>
>
> --
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot