mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Mauro Condarelli <mc5686@mclink.it>
Cc: barebox@lists.infradead.org
Subject: Re: barebox on VoCore2
Date: Tue, 12 Nov 2019 00:46:54 +0300	[thread overview]
Message-ID: <20191112004654.a2048136fe7d3a99994c8329@gmail.com> (raw)
In-Reply-To: <911adbc2-61ca-dd09-f42d-a656a844a2ba@mclink.it>

On Mon, 11 Nov 2019 10:48:26 +0100
Mauro Condarelli <mc5686@mclink.it> wrote:

> Hi,
> I would like to use barebox with a custom board (VoCore2, based on
> MT7628) currently running on a paleolithic version of u-boot.
> I've seen there has been some work on this board
> (http://lists.infradead.org/pipermail/barebox/2017-August/030945.html),
> but it's unclear to me if this resulted in a usable barebox and, if so,
> what's the right branch to use.
> I'm not scared about dirtying my fingers in low (register) level
> programming, if needed, but I know very little about barebox, so some
> guidance (and documentation) would be needed.

Please try this branch for your initial experiments
https://github.com/frantony/barebox/commits/20160815.mediatek

At the moment there is no PBL support for mediatek mips chips.
You can only run barebox from u-boot.

> 
> Where can I find detailed description of needed steps?

First try to run barebox for qemu-mips-malta (big endian version is simplier).

The qemu run instruction can be found in Documentation/boards/mips/qemu-malta.rst

There is an old but stil usefull barebox mips compilation demo at youtube:
https://www.youtube.com/watch?v=WWnX__5wJfg

For cross compiling I recommend to use Debian linux: just install gcc-mips-linux-gnu package.


> Note: I tried a "dumb compilation" (after rule-of-thumb configuration),
> but I got link error:
> 
> mcon@cinderella:~/vocore/prove/barebox$
> PATH=/home/mcon/vocore/prove/mipsel-buildroot-linux-uclibc_sdk-buildroot/bin:$PATH
> make ARCH=mips CROSS_COMPILE=mipsel-linux-
>   CHK     include/generated/version.h
>   CHK     include/generated/utsrelease.h 
>   ...
>   CC      common/version.o
>   LD      common/built-in.o
>   LD      barebox
> mipsel-linux-ld: arch/mips/boot/built-in.o: in function `main_entry':
> (.text_bare_init.text+0xe4): undefined reference to `glob_fdt'
> mipsel-linux-ld: (.text_bare_init.text+0xe8): undefined reference to
> `glob_fdt'
> mipsel-linux-ld: (.text_bare_init.text+0xec): undefined reference to
> `glob_fdt_size'
> mipsel-linux-ld: (.text_bare_init.text+0xf4): undefined reference to
> `glob_fdt_size'
> Unable to open input file barebox
> make: *** [Makefile:784: barebox] Error 2
> 
> ... so I'm surely missing some relevant step.
> 
> Thanks in Advance
> Mauro
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox


-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2019-11-11 21:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11  9:48 Mauro Condarelli
2019-11-11 21:46 ` Antony Pavlov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191112004654.a2048136fe7d3a99994c8329@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=mc5686@mclink.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox