[coreboot] Re: DIY debug Dongle

[Evgeny Zinoviev via coreboot]

On 13.10.2019 10:27, Mike Banon wrote:

With a couple of FT232H from china/aliexpress and two USB extension cables
for them
Actually, even just one FT232H plus one USB-UART (pl2303, for example) 
will work.

___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Alix2d13

[Karim El Chenawi]

Hi Mike, I actually got it to compile now with the .config from 
https://coreboot.org/status/board-status.html 
. 2018W42 was the last 
successful build for Alix2d13 and it worked!

Cheers

> On 13 Oct 2019, at 22:42, Karim El Chenawi  wrote:
> 
> Hi Mike, I’m new to coreboot so I started by following the tutorial 
> (excellent documentation btw) https://doc.coreboot.org/tutorial/part1.html 
> , built the coreboot toolchain 
> and tested with QEMU and all went well. Now, since Alix2d13 is no longer 
> supported I needed an older version of coreboot and this is where it goes 
> wrong. According to the message from Reto Rayen a few years back he got it 
> working with the following:
> 
> 1.) Clone the coreboot git -> git clone 
> http://review.coreboot.org/coreboot.git 
> 
> 2.) Revert back to the coreboot version -> git reset --hard 
> a0a3727dbbd7f3ae9f9021e0797ce2fc61d1b79e
> 3.) Download the following .config file for compiling -> 
> http://review.coreboot.org/gitweb?p=board-status.git;a=blob_plain;f=pcengines/alix2d/4.0-6723-ga0a3727-dirty/2014-08-15T23:01:34Z/config.txt;hb=HEAD
>  
> 
> 4.) Open the .config file with «make menuconfig» and close it again
> 5.) As least you do the «make» and write the coreboot bios on your «Pc 
> Engines Alix2d13».
> 
> With this is I can still build the toolchain (a few warnings) but when the I 
> get stuck at "Step 4 - Build the payload - coreinfo":
> 
> make -C payloads/coreinfo olddefconfig ==> make: *** No rule to make target 
> 'olddefconfig'.  Stop.
> 
> I guess the tutorial has changed quite a bit since the version I’m trying to 
> compile.
> 
> I think I’m way over my head here but I wanted to give it a shot and see if 
> anyone else had coreboot running on Alix2d13.
> 
>> On 13 Oct 2019, at 10:56, Mike Banon  wrote:
>> 
>>> There are some messages from a few years back from Reto Rayen but I’m not 
>>> able to reproduce his work.
>> 
>> It would be easier to help you if you can tell, what have you already
>> tried and what exactly did not work.
>> 
>> On Sun, Oct 13, 2019 at 10:59 AM Karim El Chenawi  wrote:
>>> 
>>> Hi guys,
>>> 
>>> I was wondering if anyone has a working build of coreboot for PC Engines 
>>> Alix2d13. I know that this board is old and retired but I still would like 
>>> to have coreboot on it. There are some messages from a few years back from 
>>> Reto Rayen but I’m not able to reproduce his work.
>>> 
>>> Thanks, Karim
>>> ___
>>> coreboot mailing list -- coreboot@coreboot.org
>>> To unsubscribe send an email to coreboot-le...@coreboot.org
> 

___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Alix2d13

[Karim El Chenawi]

Hi Mike, I’m new to coreboot so I started by following the tutorial (excellent 
documentation btw) https://doc.coreboot.org/tutorial/part1.html 
, built the coreboot toolchain 
and tested with QEMU and all went well. Now, since Alix2d13 is no longer 
supported I needed an older version of coreboot and this is where it goes 
wrong. According to the message from Reto Rayen a few years back he got it 
working with the following:

1.) Clone the coreboot git -> git clone http://review.coreboot.org/coreboot.git
2.) Revert back to the coreboot version -> git reset --hard 
a0a3727dbbd7f3ae9f9021e0797ce2fc61d1b79e
3.) Download the following .config file for compiling -> 
http://review.coreboot.org/gitweb?p=board-status.git;a=blob_plain;f=pcengines/alix2d/4.0-6723-ga0a3727-dirty/2014-08-15T23:01:34Z/config.txt;hb=HEAD
4.) Open the .config file with «make menuconfig» and close it again
5.) As least you do the «make» and write the coreboot bios on your «Pc Engines 
Alix2d13».

With this is I can still build the toolchain (a few warnings) but when the I 
get stuck at "Step 4 - Build the payload - coreinfo":

make -C payloads/coreinfo olddefconfig ==> make: *** No rule to make target 
'olddefconfig'.  Stop.

I guess the tutorial has changed quite a bit since the version I’m trying to 
compile.

I think I’m way over my head here but I wanted to give it a shot and see if 
anyone else had coreboot running on Alix2d13.

> On 13 Oct 2019, at 10:56, Mike Banon  wrote:
> 
>> There are some messages from a few years back from Reto Rayen but I’m not 
>> able to reproduce his work.
> 
> It would be easier to help you if you can tell, what have you already
> tried and what exactly did not work.
> 
> On Sun, Oct 13, 2019 at 10:59 AM Karim El Chenawi  wrote:
>> 
>> Hi guys,
>> 
>> I was wondering if anyone has a working build of coreboot for PC Engines 
>> Alix2d13. I know that this board is old and retired but I still would like 
>> to have coreboot on it. There are some messages from a few years back from 
>> Reto Rayen but I’m not able to reproduce his work.
>> 
>> Thanks, Karim
>> ___
>> coreboot mailing list -- coreboot@coreboot.org
>> To unsubscribe send an email to coreboot-le...@coreboot.org

___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: GRUB2 payload build error

[Merlin Büge]

On Sun, 13 Oct 2019 17:17:23 +
Naveen Chaudhary  wrote:

...

> Has anyone seen this error? I tried searching on google and few related but 
> different posts suggested that it maybe related to incorrect automake 
> files/headers being picked up, but I couldn't make it working. While I am 
> still searching on it, has anyone seen and fixed this earlier before?

You're probably missing the pkg-config package, as suggested by:
https://stackoverflow.com/questions/8811381/possibly-undefined-macro-ac-msg-error

For reference, when building GRUB2 I had to additionally install the
following packages (on Debian):

autoconf automake gettext autopoint pkg-config grub-common libfreetype6-dev 
unifont


Regards,

Merlin



-- 
Merlin Büge
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] GRUB2 payload build error

[Naveen Chaudhary]

I am able to successfully build with SeaBIOS as payload and also able to boot 
it on MinnowBoard Max. But when I change the payload to GRUB2, it fails with 
the following build error :

Copying file m4/time_h.m4
Copying file m4/unistd-safer.m4
Copying file m4/unistd_h.m4
Copying file m4/vasnprintf.m4
Copying file m4/vsnprintf.m4
Copying file m4/warn-on-use.m4
Copying file m4/wchar_h.m4
Replacing file m4/wchar_t.m4 (non-gnulib code backed up in m4/wchar_t.m4~) !!
Copying file m4/wcrtomb.m4
Copying file m4/wctype_h.m4
Copying file m4/wcwidth.m4
Replacing file m4/wint_t.m4 (non-gnulib code backed up in m4/wint_t.m4~) !!
Replacing file m4/xsize.m4 (non-gnulib code backed up in m4/xsize.m4~) !!
Creating grub-core/lib/gnulib/Makefile.am
Creating m4/gnulib-cache.m4
Creating m4/gnulib-comp.m4
Finished.

You may need to add #include directives for the following .h files.
  #include 
  #include 
  #include 
  #include 
  #include "argp.h"
  #include "error.h"
  #include "gettext.h"
  #include "mbswidth.h"
  #include "progname.h"
  #include "save-cwd.h"

You may need to use the following Makefile variables when linking.
Use them in _LDADD when linking a program, or
in _a_LDFLAGS or _la_LDFLAGS when linking a library.
  $(LTLIBINTL) when linking with libtool, $(LIBINTL) otherwise
  $(LTLIBTHREAD) when linking with libtool, $(LIBTHREAD) otherwise

Don't forget to
  - add "grub-core/lib/gnulib/Makefile" to AC_CONFIG_FILES in ./configure.ac,
  - mention "gnulib" in SUBDIRS in grub-core/lib/Makefile.am,
  - mention "-I m4" in ACLOCAL_AMFLAGS in Makefile.am,
  - mention "m4/gnulib-cache.m4" in EXTRA_DIST in Makefile.am,
  - invoke gl_EARLY in ./configure.ac, right after AC_PROG_CC,
  - invoke gl_INIT in ./configure.ac.
patching file argp-parse.c
patching file argp-fmtstream.c
patching file argp-help.c
patching file mbswidth.c
patching file mbswidth.h
patching file regcomp.c
Importing unicode...
Importing libgcrypt...
Generating Automake input...
Saving timestamps...
running: AUTOPOINT=true LIBTOOLIZE=true autoreconf --verbose --install --force 
-I m4  --no-recursive
autoreconf: Entering directory `.'
autoreconf: running: true --force
autoreconf: running: aclocal -I m4 --force -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --include=m4 --force
configure.ac:414: error: possibly undefined macro: AC_CHECK_HEADERS
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
configure.ac:505: error: possibly undefined macro: AC_LINK_IFELSE
configure.ac:1550: error: possibly undefined macro: AC_LANG_CALL
autoreconf: /usr/bin/autoconf failed with exit status: 1
./bootstrap: autoreconf failed
Importing unicode...
Importing libgcrypt...
WARNING: grub-core/lib/libgcrypt-grub already exists
WARNING: grub-core/lib/libgcrypt-grub/cipher already exists
WARNING: grub-core/lib/libgcrypt-grub/mpi already exists
WARNING: grub-core/lib/libgcrypt-grub/src already exists
Generating Automake input...
Saving timestamps...
Running autoreconf...
autoreconf: Entering directory `.'
autoreconf: running: autopoint --force
Copying file build-aux/config.rpath
Copying file m4/extern-inline.m4
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
configure.ac:414: error: possibly undefined macro: AC_CHECK_HEADERS
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
configure.ac:505: error: possibly undefined macro: AC_LINK_IFELSE
configure.ac:1550: error: possibly undefined macro: AC_LANG_CALL
autoreconf: /usr/bin/autoconf failed with exit status: 1
Makefile:28: recipe for target 'grub2/build/config.h' failed
make[1]: *** [grub2/build/config.h] Error 1
payloads/external/Makefile.inc:171: recipe for target 'grub2' failed
make: *** [grub2] Error 2


Has anyone seen this error? I tried searching on google and few related but 
different posts suggested that it maybe related to incorrect automake 
files/headers being picked up, but I couldn't make it working. While I am still 
searching on it, has anyone seen and fixed this earlier before?
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: OpenBMC on KGPE-D16, somebody has it working?

[ron minnich]

On Sun, Oct 13, 2019 at 6:42 AM Merlin Büge  wrote:

>
> ... as far as I can see, u-bmc doesn't support the AST2050 yet (the BMC
> chip used by the KGPE-D16).

This is the kind of challenge people on this list live for :-)

The cool thing about u-bmc is that is has only about 1000 lines of
assembly. It turns on dram, loads linux from flash, starts it. It's
not u-boot, or coreboot, or anything. In fact it's a lot like
linuxbios v0.

ron
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: DIY debug Dongle

[Tom Hiller]

I do not mean to hijack the question but is a hardware usb to serial 
device required?



The wiki briefly mentions "usb_debug_io.c" with a link to an old trac 
ticket.  Could a second device connected via usb only read the logs?  I 
am curious on the feasibility of attaching an Android phone/tablet with 
an app that could easily read coreboot debug information.


On 10/13/19 3:27 AM, Mike Banon wrote:

Know I'm a bit late, but for me it was much easier to use FT232H-based
USB board as a debug dongle. Initially I also wanted to build that
FX2LP sandwich, but some confusion regarding the revisions (it's a bit
tiresome to ask many sellers for a board revision in advance) and the
need for revision-dependent soldering have scared me off. With a
couple of FT232H from china/aliexpress and two USB extension cables
for them, I didn't need to solder anything except their pin headers,
so it was quite easy for me to get it working with coreboot - just by
enabling CONFIG_USBDEBUG_DONGLE_FTDI_FT232H at its' config. But I
haven't compared what is easier to use from a software side, for
coreboot : FX2LP (which seems to have its' own firmware) or FT232H. It
seems that you don't have a coreboot-supporting board, but maybe you
could still use the sources from /coreboot/src/drivers/usb/gadget.c
for your OS.

On Sun, Oct 13, 2019 at 1:28 AM  wrote:

Hi
I’ve seen an EHCI debug dongle in the old wiki. I’m trying to build one for 2 
purposes: debug a homebrew os/Shell and make it a new UEFI bootloader. However 
I don’t know where to find further documentation or comments about this. I also 
dont’ know what is the current or most up to date schematic to build the 
“sandwich” and what tracks cut and what not. I have bought those blue cypress 
FX2LP boards and I don’t know how to check revisions. Also, I’dont know exactly 
what software can be used to control it. It would be desirable if one can send 
stop or install some breakpoints with Visual studio’s debugger or WinDBG or GDB 
or something like that.
thanks in advance for your advice.

___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: OpenBMC on KGPE-D16, somebody has it working?

[Merlin Büge]

On Sat, 12 Oct 2019 22:11:02 -0700
ron minnich  wrote:

> If you like running systemd on your bmc, the minimum 60 seconds
> openbmc takes to boot, the complex, fragile, and long time it takes to
> build from source, and the openbmc stack's need for giant memory
> footprint and lots of nvme, stop reading.

I don't like that, but...

> IF, OTOH, you like the idea of a very lightweight stack, which builds
> in minutes not hours, and needs maybe 32M of memory to run, and boots
> much faster, well, you might want to checkout u-bmc.
> 
> https://github.com/u-root/u-bmc

... as far as I can see, u-bmc doesn't support the AST2050 yet (the BMC
chip used by the KGPE-D16).


Merlin




-- 
Merlin Büge
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Alix2d13

[Mike Banon]

> There are some messages from a few years back from Reto Rayen but I’m not 
> able to reproduce his work.

It would be easier to help you if you can tell, what have you already
tried and what exactly did not work.

On Sun, Oct 13, 2019 at 10:59 AM Karim El Chenawi  wrote:
>
> Hi guys,
>
> I was wondering if anyone has a working build of coreboot for PC Engines 
> Alix2d13. I know that this board is old and retired but I still would like to 
> have coreboot on it. There are some messages from a few years back from Reto 
> Rayen but I’m not able to reproduce his work.
>
> Thanks, Karim
> ___
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-le...@coreboot.org
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Alix2d13

[Karim El Chenawi]

Hi guys,

I was wondering if anyone has a working build of coreboot for PC Engines 
Alix2d13. I know that this board is old and retired but I still would like to 
have coreboot on it. There are some messages from a few years back from Reto 
Rayen but I’m not able to reproduce his work.

Thanks, Karim
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: DIY debug Dongle

[Mike Banon]

Know I'm a bit late, but for me it was much easier to use FT232H-based
USB board as a debug dongle. Initially I also wanted to build that
FX2LP sandwich, but some confusion regarding the revisions (it's a bit
tiresome to ask many sellers for a board revision in advance) and the
need for revision-dependent soldering have scared me off. With a
couple of FT232H from china/aliexpress and two USB extension cables
for them, I didn't need to solder anything except their pin headers,
so it was quite easy for me to get it working with coreboot - just by
enabling CONFIG_USBDEBUG_DONGLE_FTDI_FT232H at its' config. But I
haven't compared what is easier to use from a software side, for
coreboot : FX2LP (which seems to have its' own firmware) or FT232H. It
seems that you don't have a coreboot-supporting board, but maybe you
could still use the sources from /coreboot/src/drivers/usb/gadget.c
for your OS.

On Sun, Oct 13, 2019 at 1:28 AM  wrote:
>
> Hi
> I’ve seen an EHCI debug dongle in the old wiki. I’m trying to build one for 2 
> purposes: debug a homebrew os/Shell and make it a new UEFI bootloader. 
> However I don’t know where to find further documentation or comments about 
> this. I also dont’ know what is the current or most up to date schematic to 
> build the “sandwich” and what tracks cut and what not. I have bought those 
> blue cypress FX2LP boards and I don’t know how to check revisions. Also, 
> I’dont know exactly what software can be used to control it. It would be 
> desirable if one can send stop or install some breakpoints with Visual 
> studio’s debugger or WinDBG or GDB or something like that.
> thanks in advance for your advice.
>
> ___
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-le...@coreboot.org
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org