[U-Boot] [PATCH 1/4] Reactivate the tracing feature

[Simon Glass]

Hi Masahiro,

On 12 June 2014 20:56, Masahiro Yamada <yamada.m at jp.panasonic.com> wrote:
>
> Hi Simon,
>
>
> On Wed, 11 Jun 2014 23:50:48 -0400
> Simon Glass <sjg at chromium.org> wrote:
>
> > Hi Masahiro,
> >
> > On 11 June 2014 23:42, Simon Glass <sjg at chromium.org> wrote:
> > > Hi Masahiro,
> > >
> > > Yes I should remove this otherwise it will at best bloat the code for
> > > SPL. I think it is probably best just to revert that part of the
> > > Makefile.
> >
> > Although actually I'm not sure how to have different flags for
> > everything except SPL and examples/ - any clues?
>
>
> Me neither.
>
> But one possible solution is:

[snip]

That seems to work for me, thank you. Please don't worry about
breaking it. If I was worried about the tests I would have come up
with a way of automatically running them all by now. U-Boot needs a
'make test' but the test coverage is still pretty poor, so it is not
high on my priority list.

>
> BTW,  can  FTRACE build for all boards?
>
> I checked out v2014.01 (pre-kbuild)
>
> - make sandbox_config;  make FTRACE=1
> - make snow_config;  make CROSS_COMPILE=arm-linux-gnueabi- FRACE=1
>
> succeeded. But,
>
> - make omap3_beagle_config; make CROSS_COMPILE=arm-linux-gnueabi- FRACE=1
>
> faied with lots of  undefined reference errors to __cyg_profile_func_enter/_exit.
>
>
> I don't know why.

You need to enable it - see exynos5-dt.h which has:

/* Allow tracing to be enabled */
#define CONFIG_TRACE
#define CONFIG_CMD_TRACE
#define CONFIG_TRACE_BUFFER_SIZE (16 << 20)
#define CONFIG_TRACE_EARLY_SIZE (8 << 20)
#define CONFIG_TRACE_EARLY
#define CONFIG_TRACE_EARLY_ADDR 0x50000000

It would be nice to automate these settings, but for now you must add
these settings for the board you are using. Actually I think it would
be easy except for the 'early trace' feature, which needs to have a
pre-relocation memory area to use.

Regards,
Simon