Hi Zahra, Yes, I used the 6-pin serial port header. Also, make sure the microcode header(s) you include correspond to the CPUID of your processor. The E3825 and E3826 use different microcode headers, so M0130679901.h will not work for you.
Please keep the coreboot mailing list CC'd. I haven't done anything with Minnowboard in several months and others may be able to help.
On Thu, Aug 2, 2018 at 5:01 PM, zahra rahimkhani zrahimkhani2014@gmail.com wrote:
Hi David
Thank you for your help. I extract your file and got M0130679901.h as Microcode but my board does not work it did not show anything. I use E3825. In previous notes, you told "My guess is that you don't have CONFIG_ENABLE_BUILTIN_COM1 selected (under "Chipset"), which is an option you have to set in addition to the stuff under "Console." but in your config, you had not enabled this option. Could you help me with this and Did you use 6 pins that are separated on board for console port? I do not know what is my problem .it did not show anything log.
Thank you for your time. Zahra
On Wed, Aug 1, 2018 at 2:04 AM David Hendricks david.hendricks@gmail.com wrote:
Hi Zahra, That header may be out of date (https://mail.coreboot.org/pipermail/coreboot/2017-August/084800.html).
I had to manually download the microcode file corresponding to my processor SKU from Intel. Use the link I sent you earlier to download Baytrail_FSP_Gold4.tgz and see if the microcode headers included in that tarball match your processor. The Atom on my Minnowboard Turbot has a CPUID of 30679, so I needed to use M0130679901.h.
(note that the Minnowboard Max uses an Atom E3825, while the Turbot uses an E3826 dual-core SoC or E3845 quad-core SoC)
On Mon, Jul 30, 2018 at 2:36 AM, zahra rahimkhani zrahimkhani2014@gmail.com wrote:
Dear David
for Microcode file I just it from coreboot source from this path coreboot/3rdparty/blobs/soc/intel/baytrail/microcode_blob.h
Is that good ?
Thanks ,
On Sun, Jul 29, 2018 at 1:18 PM zahra rahimkhani <
zrahimkhani2014@gmail.com>
wrote:
Hi David,
Thank you very much for your guide.
I got this comments on my config and changes it based on your config. But I can not see any thing on output. Could you tell me which Uart pins do you use on Minnowboard max
I used it 6 pin that are separately on board .
I would be grateful if you guide me . I got my new config here . https://paste.flashrom.org/view.php?id=3097
Also , Could you tell me what is this parameter CONFIG_UART_FOR_CONSOLE=0 and CONFIG_DRIVERS_UART_8250IO
Cheers! Zahra
On Fri, Jul 27, 2018 at 11:06 AM David Hendricks david.hendricks@gmail.com wrote:
Hi Zahra,
I got my config file here https://paste.flashrom.org/view.php?id=3096
Thanks, that helps a lot!
The last config that I tested is https://review.coreboot.org/cgit/board-status.git/plain/
intel/minnowmax/4.6-1358-g49d117c69f/2017-09-06T06_53_39Z/config.txt
If you diff my config and yours, it seems you have several options disabled which I think you should try enabling: CONFIG_HAVE_IFD_BIN CONFIG_HAVE_ME_BIN CONFIG_TTYS0_LCS CONFIG_DRIVERS_UART_8250IO CONFIG_IFD_BIN_PATH CONFIG_ME_BIN_PATH CONFIG_LOCK_MANAGEMENT_ENGINE CONFIG_DRIVERS_UART CONFIG_CONSOLE_SERIAL CONFIG_CONSOLE_SERIAL_115200
You can find these by using the search function in `make menuconfig`. Press '/' and type a Kconfig option.
I would be grateful if you check my config and tell me what is
ifdtool
in Coreboot and how I use it. and How I find Intel ME file for my board and GBE for a network on
my
board.
ifdtool is a tool for viewing and manipulating an Intel Flash
Descriptor
binary. The flash descriptor is a 4KB data structure at the start of
the
ROM's address space (offset 0x000000-0x000fff).
To build it: `make -C util/ifdtool` To run it: `util/ifdtool/ifdtool`
You'll probably want to use the '-x' option to extract the individual modules from an existing Minnowboard Max firmware image (e.g. the
UEFI image
that comes with the board). That will give you the ME and GBE files.
-
David Hendricks