<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Gergely,</p>
<p>Sorry, I didn´t know the PCI IDs are APU depending. I´m using an
Athlon 5350.</p>
<p>Yes, the differences are minor. Only UART used and TTYS0_BASE
address.</p>
<p>Thank you for clarifying the memory requirement. I didn´t see it
in the manual :-( .<br>
</p>
<p>Maybe you can change the defaults for CONFIG_UART_FOR_CONSOLE=1
and CONFIG_TTYS0_BASE=0x2f8.</p>
<p>Actually, I only bought this board to have this port tested and
working :-) . But, like you said, it´s the ideal system for a
HTPC.<br>
</p>
<p>I have a AM1M-A too. I think this board is (almost) identical.
"Only" it has more PCIEs slots (it´s micro-atx)<br>
</p>
<p>Thank you for your work and your valuable help.</p>
<p>Best regards,</p>
<p>Eli<br>
</p>
<br>
<div class="moz-cite-prefix">On 13/02/2018 6:57, Gergely Kiss wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAF-mK=XGfXq2TFZBA51ObQx3y-pcHtt9+fga-sFvCtNn8NYLpA@mail.gmail.com">
<div dir="ltr">
<div>
<div>Hi,<br>
<br>
</div>
taking a look at the diffs, I can't see any major difference.
CONFIG_USE_BLOBS is y by default so setting it to y is not
really useful. The only notable difference is that you used
COM1 for console output instead of COM2 (which is the port
soldered on-board). However, this does not seem to explain why
you got "slow" output on your console. If the COM port number
and the base address is specified incorrectly then you'd see
no output, at all, so I'm unsure what the real issue was in
your case and how you managed to fix it.<br>
<br>
</div>
<div>As for the PCI IDs of the VGA adapter, it can be different
depending on what APU is installed. My installation uses the
one that is set in Kconfig by default.<br>
<br>
</div>
<div>The requirement to place the DIMM to slot DIMM_A2 (the slot
closest to the edge of the board) when only one module is
present is noted in the vendor manual on page 1-7.<br>
<br>
</div>
<div>About changing the defaults in the board's Kconfig, I'm not
sure what you mean, could you please clarify? I think changing
the default VGA PCI ID does not make sense as the VGA
controller is integrated to the APU so each APU model and
revision might use different PIDs and I believe there's no
point preferring one ID over the others. The one that I have
included is for reference only which might need to be changed
to match the APU installed (my installation uses a Sempron
3850 APU).<br>
</div>
<div><br>
Anyway, I'm happy to see that you could finally make coreboot
work on your board, it's good to known I'm not the only user
of my port! :)<br>
<br>
</div>
<div>Regards,<br>
</div>
<div>Gergely<br>
</div>
<div><br>
<div>
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">On 11 February 2018 at 12:26,
Elisenda Cuadros <span dir="ltr"><<a
href="mailto:lists@e4l.es" target="_blank"
moz-do-not-send="true">lists@e4l.es</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Hi Gergely,</p>
<p>Thank you for your config. Now I have
coreboot + SeaBIOS perfectly working.<br>
</p>
<p>Console speed is now "normal" :-)</p>
<p>These are the changes between the two
configs:</p>
<p>-------------<br>
</p>
<p>diff config_original.txt config_Gergely.txt<br>
23c23<br>
< # CONFIG_USE_BLOBS is not set<br>
---<br>
> CONFIG_USE_BLOBS=y<br>
101c101<br>
< CONFIG_UART_FOR_CONSOLE=0<br>
---<br>
> CONFIG_UART_FOR_CONSOLE=1<br>
150c150<br>
< CONFIG_POST_DEVICE=y<br>
---<br>
> # CONFIG_POST_DEVICE is not set<br>
210c210<br>
< CONFIG_TTYS0_BASE=0x3f8<br>
---<br>
> CONFIG_TTYS0_BASE=0x2f8<br>
428,429d427<br>
< # CONFIG_PCI_OPTION_ROM_RUN_<wbr>REALMODE
is not set<br>
< # CONFIG_PCI_OPTION_ROM_RUN_<wbr>YABEL is
not set<br>
431d428<br>
< # CONFIG_VGA_TEXT_FRAMEBUFFER is not set<br>
556c553<br>
< # Serial port base address = 0x3f8<br>
---<br>
> # Serial port base address = 0x2f8<br>
581,583d577<br>
< CONFIG_POST_DEVICE_NONE=y<br>
< # CONFIG_POST_DEVICE_LPC is not set<br>
< # CONFIG_POST_DEVICE_PCI_PCIE is not set</p>
<p>--------------<br>
</p>
<p>I made some tweaks to the configuration,
added VGA output before payload, a nice
bootsplash, etc..</p>
<p>Other considerations:</p>
<p>VGA Device PCI IDs are 1002,9830 (The default
1002,9836 does not get output).</p>
<p>Memory has to be located firstly on second
slot (yellow DIMM_A2). If not you get
AGESA_FATAL_ERROR. I only have one module.<br>
</p>
<p>Please, find attached a working config.txt
and console.log. Coreboot revision is
4.7-294-g2db6fbc47b.<br>
</p>
<p>If you verify these changes are working for
you is it possible to change the defaults in
Kconfig?</p>
<p>Thank you very much.<br>
</p>
<p>Best regards,</p>
<p>-- Eli<br>
</p>
<div>
<div class="gmail-h5">
<p><br>
</p>
<br>
<div
class="gmail-m_5538425459714914442moz-cite-prefix">On
11/02/18 00:07, Gergely Kiss wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Strange, the log you shared
looked less verbose to me than
expected but seems like I was
wrong. Anyway, you might find an
example on a full debug log here
[1].<br>
<br>
</div>
I have a small build script I use to
build coreboot for my board, please
find it attached.<br>
<br>
</div>
<div>The version currently running on
my box is 4.6-2554-ga1b4c94.<br>
</div>
<div><br>
</div>
[1] <a
href="https://www.coreboot.org/Board:asus/am1i-a#Bootlog"
target="_blank"
moz-do-not-send="true">https://www.coreboot.org/<wbr>Board:asus/am1i-a#Bootlog</a><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 10 February
2018 at 23:18, Elisenda Cuadros <span
dir="ltr"><<a
href="mailto:lists@e4l.es"
target="_blank"
moz-do-not-send="true">lists@e4l.es</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Thank you for your kind reply
Gergely.</p>
<p>I think the cable is not the
problem, I have been using it
for years and it's intact.</p>
<p>I am using a usb dongle but not
a cheap one. Tomorrow I will try
with another cable and a real
COM port. Just to be 100% sure.</p>
<p>Console is fast at the very
first time (just the "normal")
but after two seconds it becomes
extremely slow.<br>
</p>
<p>Please, can you say me which is
the git revision you are using?</p>
<p>The console log I attached is
from a SPEW debug level, not
corresponding with the config..
I tried several configs today
:-) .</p>
<p>Is it possible to share your
config with me?</p>
<p>Best regards,</p>
<p>Eli<br>
</p>
<div>
<div
class="gmail-m_5538425459714914442h5">
<br>
<div
class="gmail-m_5538425459714914442m_-449197509072877678moz-cite-prefix">On
10/02/18 21:44, Gergely Kiss
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi Eli,<br>
<br>
</div>
I've been using
Coreboot on my
board for several
weeks, it is
serving as an HTPC
running 24/7 and
it's working
perfectly stable
which suggests the
firmware should be
free of bugs. It
is likely that you
are facing some
configuration or
hardware issue
here.<br>
<br>
</div>
<div>I didn't see
any issues with
the serial output
while working with
the board once the
SuperIO chip
started to work.
Make sure the
cable you use is
intact and try to
attach it to
another machine.
At the time I was
working with my
board, I used a
Dell Port
Replicator with a
native COM port so
I could use a
standard
null-modem cable
and it was working
flawlessly. In
case you use a USB
serial adapter,
try replacing it
or attach the
serial cable
directly to a COM
port if you have
one available.<br>
</div>
<div><br>
</div>
Also, please enable
debug_level=Spew as
it seems the console
log you attached
comes from a less
verbose setting and
therefore it's not
as useful as it
should be.<br>
<br>
Note that the VBIOS
image is executed by
SeaBIOS which means
you won't see
anything on your
display until the
payload is executed.<br>
<br>
</div>
If all else fails, you
can still attach a
POST debug module to
the LPC header of the
board [1] which can
help a lot to find out
where the boot process
hangs.<br>
<br>
</div>
<div>Feel free to
contact me if you need
some more help or
information, I'm happy
to assist!<br>
</div>
<div><br>
</div>
Regards,<br>
</div>
Gergely<br>
<br>
[1] <a
href="https://www.youtube.com/watch?v=aGGqsWx3-1c"
target="_blank"
moz-do-not-send="true">https://www.youtube.com/watch?<wbr>v=aGGqsWx3-1c</a><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On
10 February 2018 at
18:17, Elisenda
Cuadros <span
dir="ltr"><<a
href="mailto:lists@e4l.es"
target="_blank"
moz-do-not-send="true">lists@e4l.es</a>></span>
wrote:<br>
<blockquote
class="gmail_quote"
style="margin:0px
0px 0px
0.8ex;border-left:1px
solid
rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
I'm trying to use
Coreboot in an Asus
AM1I-A board
recently ported by
Gergely Kiss (thank
you!).<br>
<br>
I am using the
default config
settings and added
vga rom extracted
with UEFITool from
the vendor bios.<br>
<br>
After flashing and
booting I get no
output from vga.<br>
<br>
Serial console is
extremely slow too
(30 minutes to write
the log)<br>
<br>
I attach the
coreboot console
log, config and
cbfs.txt.<br>
<br>
Any hints?<br>
<br>
Thanks in advance.<br>
<br>
Best regards,<br>
<br>
-- Eli<br>
<br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset
class="gmail-m_5538425459714914442mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>