Hi.
Now you have coreboot running.
coreboot searches for FSP, finds it and executes the first call into it.
FSP returns with an error and what you see is this (taken from
src/drivers/intel/fsp/cache_as_ram.inc):
/*
* Failures for postcode 0xBB - failed in the FSP:
*
* 0x00 - FSP_SUCCESS: Temp RAM was initialized successfully.
* 0x02 - FSP_INVALID_PARAMETER: Input parameters are invalid.
* 0x0E - FSP_NOT_FOUND: No valid microcode was found in the
microcode region.
* 0x03 - FSP_UNSUPPORTED: The FSP calling conditions were not met.
* 0x07 - FSP_DEVICE_ERROR: Temp RAM initialization failed
* 0x14 - FSP_ALREADY_STARTED: Temp RAM initialization has been invoked
*/
So what you actually see is error code 0x07 from FSP. This can mean that
your CPU is not supported by this FSP version.
If you use GOLD1 or GOLD2, then a D0 stepping is not supported and if
you have in advance a D0 stepping installed on your board,
than you have to use GOLD3 FSP release as it was already mentioned.
I had the same issue and it was due to missing D0-Support in GOLD1
release. So, I would suggest to try the right FSP-release from Intel.
Bye
Werner
Am 03.11.2014 um 17:23 schrieb Gailu Singh via coreboot:
With the changed TXE/descriptor, it moved ahead but now toggling
between POST codes 0x66 and 0x07. I checked
./src/include/console/post_codes.h and these POST codes are not
defined there so I doubt that these are coming from coreboot code. Are
these post codes coming from FSP code? If yes, How do I interpret
them? Do I need to ask Intel? Any pointers please?
On Sun, Nov 2, 2014 at 6:50 PM, Sean McNeil <seanmcne...@gmail.com
<mailto:seanmcne...@gmail.com>> wrote:
You mentioned just copying the .fd file, so I assumed it was being
used directly in your coreboot image. FSP needs to be incorporated
into flash, yes. It should, however, be patched with the BCT
program as what is provided in the .fd is usually not patched with
the a configuration that you desire. Thus you should run bct and
configure/patch the .fd and generate a .bin to include into coreboot.
I am a little confused by your email below. You state that you are
not using the .fd directly then contradict yourself in the next
sentence. Bottom line is I would not include any .fd file from the
FSP archive directly. Use BCT to patch it and do not name it .fd.
This avoids any confusion regarding whether you are including a
patched FSP or not. Just because there is a bsf file included in
the GOLD release doesn't mean that the .fd was patched with those
settings and that it is valid.
Best of luck to you. There are many issues you will have to
resolve dealing with new hardware. I've gone through the process
with a lot of support from Intel and it is not that easy.
Especially when certain components found on the CRB are not
provided on custom hardware.
Cheers,
Sean
On 11/02/2014 08:01 PM, Gailu Singh wrote:
Hi Sean,
1. This is not for a real project and we are trying to understand
FSP interaction with coreboot to look at feasibility for
considering coreboot in our future projects. Unfortunately I do
not have board documentation so was not able to determine which
one is serial port 0 though I know that port 0 is specified in
coreboot config. That was the reason I was trying on all 3
available ports.
2. I am not using .fd directly. I believe that FSP need to be
included in bootloader (coreboot in this case) and we are
providing path to coreboot so that it can be included in
coreboot. In my original post I only said that I copied .fd to a
path expected by coreboot configuration. May I know how did you
conclude that I am using it directly? May be that can give me
some pointer.
3. I had checked the bsf file in the FSP kit with BCT tool and it
is configured for non-ECC RAM, so I believe that no change is
required in .fd. Am I wrong?
4. Yes, I agree that there is no documentation available on how
to create entire 8MB binary with Firmware Description, TXE,
coreboot etc so for safe route I only touched upper 2 MB as
recommended in one of the initial commit for baytrail FSP
integration and some posts related to similar discussion.
On Sun, Nov 2, 2014 at 3:49 PM, Sean McNeil
<seanmcne...@gmail.com <mailto:seanmcne...@gmail.com>> wrote:
Coreboot and FSP are not as easy to understand as you can
see. I also would suggest that you seek assistance from
either Sage (who has good experience that I understand serves
the USA and Europe markets and contributed the current
Coreboot+FSP code) or perhaps a company in Asia such as Zien
Solutions (of Vietnam). There are a number of issues that you
are failing to understand:
1) As stated, the first serial port is actually connected to
a USB->Serial converter and delivered out of the microUSB
connector on the CRB.
2) You need to configure the FSP with Intels program to
create a ROMable image and not use the .fd file directly.
3) BayleyBay needs to be configured for non-ECC RAM whereas
Bakersport needs to be configured for ECC.
4) You don't necessarily need the TXE security module, but
you could very well cause problems if it is partially
overwritten. Best is to create a correct 8MB image to flash
that has the proper Intel Firmware Description block at the
beginning.
Regards,
Sean
On 11/02/2014 02:25 AM, Gaumless via coreboot wrote:
First, the serial ports: The serial console is on the
first serial port on the micro-USB connection.
The 0x0000 on the post code display means that it's not
actually starting to boot - it's probably hanging in the
TXE. There are known issues with upgrading to coreboot
from some of the bayleybay roms. I thought Intel was
going to document that, but I don't know if they did.
The Gold 2 FSP doesn't support D0 parts, so if you have a
D0, you need the Gold 3. Also, the FSP is targeted at
the embedded sku Baytrail-I. It might work with M/D
parts, I haven't tested that.
Assuming all that is ok, you probably need to start from
a different rom. It might be failing because of the TXE
security. You'll probably need to talk to your Intel
contact to get that update.
Finally, if this is not a personal project, you might be
interested in contacting Sage and look at purchasing a
BSP to get up and running. Either way, let us know
whether you make progress or need more help.
Martin
On Nov 1, 2014, at 11:48 AM, Gailu Singh via coreboot
<coreboot@coreboot.org
<mailto:coreboot@coreboot.org>> wrote:
Hi Experts,
I am trying to boot BayleyBay CRB Rev 3 using
coreboot and have no success so far. I have serial
port (DB9) connected and using 115200 Baud Rate. No
message comes on serial at all. Here is the procedure
I followed.
1. Pulled latest coreboot from git.
2. Pulled following from BAY_TRAIL_FSP_KIT. The
reason for doing it is that BAYTRAIL_FSP.fd is not
in git and .config refers to it. Also .config refers
to ../intel/cpu/baytrail/microcode
a) created intel directory parallel to coreboot
and copied BAYTRAIL_FSP_GOLD_002_10-JANUARY-2014.fd
in to intel/fsp/baytrail/BAYTRAIL_FSP.fd
b) Copied *.h from Microcode folder in the kit
to intel/cpu/baytrail/microcode.
3. Configured the coreboot for mainboard as intel
bayleybay. My .config is attached.
4. Build Coreboot. Below is the prints from cbfstool.
cmos_layout.bin 0x0 cmos_layout 1132
fallback/romstage 0x4c0 stage
27813
fallback/ramstage 0x71c0 stage
67431
fallback/payload 0x17980 payload 268859
config 0x59400 raw 4363
(empty) 0x5a540 null 744088
cpu_microcode_blob.bin 0x110000 microcode 104448
(empty) 0x129840 null 157528
mrc.cache 0x14ffc0 (unknown) 65536
(empty) 0x160000 null 393112
fsp.bin 0x1bffc0 (unknown) 229376
(empty) 0x1f8000 null 31640
5. Flashed the coreboot.rom in upper 2MB
(0X0600000-0x07FFFFF)
6. Reboot the board
7. Nothing comes on Serial Console (DB9). Also tried
to connect Micro usb cable which detects two serial
ports but no output to any of them as well.
8. Before flashing coreboot.rom, 4 digit display was
displaying something on two digits and rest two were
zero. Now all 4 digits stays at zeros.
Looking for help to get at least serial working so
that I can get some logs to debug it. I do not have
copy of original BIOS that was there in Flash and
forgot to make a copy using programmer though I
ensured that I only touch upper 2MB. I am stuck and
have no logs to debug it.
Thanks in advance.
<my.config>
--
coreboot mailing list: coreboot@coreboot.org
<mailto:coreboot@coreboot.org>
http://www.coreboot.org/mailman/listinfo/coreboot
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
