[coreboot] bios for ATOM E38XX

[Ricardo Menzer]

Sorry, I forgot to include the contents of the ROM image:

ricardo at ricardo-VirtualBox:~/BAY_TRAIL_FSP_KIT/coreboot$
build/cbfstool build/coreboot.rom print
coreboot.rom: 8192 kB, bootblocksize 1024, romsize 8388608, offset 0x600000
alignment: 64 bytes

Name                           Offset     Type         Size
cmos_layout.bin                0x600000   cmos_layout  1132
pci8086,0f31.rom               0x6004c0   optionrom    65536
fallback/romstage              0x610500   stage        26364
fallback/ramstage              0x616c40   stage        58469
fallback/payload               0x625100   payload      118456
config                         0x642000   raw          4012
(empty)                        0x643000   null         839640
cpu_microcode_blob.bin         0x710000   microcode    104448
(empty)                        0x729840   null         616280
fsp.bin                        0x7bffc0   (unknown)    229376
(empty)                        0x7f8000   null         31640



On Tue, Jul 15, 2014 at 2:45 PM, Ricardo Menzer <ricardomenzer at gmail.com> wrote:
> Hi.
> I'm also trying to use Coreboot with a COM Express Module from
> Cogatec. It is a Conga-MA3 model
> [http://www.congatec.com/products/com-express-type10/conga-ma3.html].
> Booting the original BIOS into Linux, and doing a cat /proc/cpu shows
> the processor stepping is 3, so i'm assuming it's a B3 silicon.
> I have used Intel BCT to patch the FSP so its configuration matches
> the memory chips used in this module.
> I am testing it with a base board made by Kontron, which provides a
> four digit port 80h/81h display and a SPI socket, allowing me to use
> an external flash and preserve module's flash.
> I couldn't make flashrom detect the flash memory when using this
> module from Congatec, even disabling BIOS memory write protection on
> BIOS setup, but I'm using another module to flash the external SPI and
> swapping modules after. (I plan to find out why it isn't detected
> later).
>
> I've copied
> /home/ricardo/BAY_TRAIL_FSP_KIT/Microcode/M013067331E.h
> /home/ricardo/BAY_TRAIL_FSP_KIT/Microcode/M0230672228.h
> to /home/ricardo/BAY_TRAIL_FSP_KIT/coreboot/src/soc/intel/fsp_baytrail/microcode
> so Coreboot can compile (otherwise Make fails).
>
> The first image I've burned didn't worked (.config file attached).
> There's no POST codes in the display. I think it may be a issue with
> the TXE firmware. How can I check it?
>
> I'm trying to learn about the inner workings of coreboot. How can I
> help to support this module/chipset?
>
> Thanks.
>
> On Thu, Jul 10, 2014 at 7:29 PM, ron minnich <rminnich at gmail.com> wrote:
>>
>>
>>
>> On Wed, Jun 25, 2014 at 4:11 AM, benjamin nakache <bnakache at nolam.com>
>> wrote:
>>>
>>> Hello ,
>>>
>>>
>>>
>>> When will support the new Atom E38XX
>>>
>>>
>>
>>
>>
>> Would you or someone from your company  like to help?
>>
>>>
>>>
>>>
>>> Note: This message and any attachment hereto is intended solely for the
>>> use of the designated recipient(s) and their appointed delegates and may
>>> contain confidential information. Any unauthorized use, disclosure,copying,
>>> or distribution of its contents is strictly prohibited. If you have received
>>> this message in error, please destroy it and advise Nolam Embedded Systems
>>> immediately by phone, email, or fax.Thank you for your cooperation.
>>>
>>>
>>>
>>>
>>
>>
>>
>> You should remove this Note:, else we won't be able to receive your messages
>> any more :-)
>>
>> thanks
>>
>> ron
>>
>> --
>> coreboot mailing list: coreboot at coreboot.org
>> http://www.coreboot.org/mailman/listinfo/coreboot
>
>
>
> --
>
>
> Ricardo Menzer
> ricardomenzer at gmail.com
> (32)8865-8805



-- 


Ricardo Menzer
ricardomenzer at gmail.com
(32)8865-8805