Openembedded Core Discussions
 help / color / mirror / Atom feed
* meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
@ 2012-05-29 18:20 Elvis Dowson
  2012-05-29 18:36 ` Mark Hatle
  0 siblings, 1 reply; 10+ messages in thread
From: Elvis Dowson @ 2012-05-29 18:20 UTC (permalink / raw)
  To: OpenEmbedded Core Mailing List, Adrian Alonso

[-- Attachment #1: Type: text/plain, Size: 2560 bytes --]

Hi,
      I've added the meta-xilinx layer, and modified my build/conf/local.conf file as follows:

# Set the target machine details
MACHINE ?= "virtex5"
# Set Xilinx Platform Studio hardware project path
XILINX_BSP_PATH ?= "/project/xilinx-ml507"
# Set target board
XILINX_BOARD ?= "ml507"

and when I try to build the meta-toolchain

$ cd /tool/yocto/poky
$ source oe-init-build-env build
$ bitbake meta-toolchain

I get the following errors:

ERROR: Execution of event handler 'check_sanity_eventhandler' failed
Traceback (most recent call last):
  File "/tool/yocto/poky/bitbake/lib/bb/utils.py", line 397, in better_eval(source=<code object <module> at 0x344b6b0, file "MACHINE_ARCH", line 1>, locals={'d': <bb.data_smart.DataSmart object at 0x1450050>}):
     def better_eval(source, locals):
    >    return eval(source, _context, locals)
     
  File "MACHINE_ARCH", line 1, in <module>
  File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 282, in DataSmart.getVar(var='TUNE_PKGARCH', expand=True, noweakdefault=False):
             if expand and value:
    >            return self.expand(value, var)
             return value
  File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 151, in DataSmart.expand(s='${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)}', varname='TUNE_PKGARCH'):
         def expand(self, s, varname = None):
    >        return self.expandWithRefs(s, varname).value
     
  File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 141, in DataSmart.expandWithRefs(s='${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)}', varname='TUNE_PKGARCH'):
                 except Exception as exc:
    >                raise ExpansionError(varname, s, exc)
     
ExpansionError: Failure expanding variable TUNE_PKGARCH, expression was ${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)} which triggered exception SyntaxError: EOL while scanning string literal (TUNE_PKGARCH, line 1)

ERROR: Failure expanding variable TUNE_PKGARCH, expression was ${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)} which triggered exception SyntaxError: EOL while scanning string literal (TUNE_PKGARCH, line 1)
ERROR: Command execution failed: Exited with 1

Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

Has support for the PowerPC440 processor (present in the Virtex-5 FPGA) been removed from the newer gcc-versions?

Best regards,

Elvis Dowson

[-- Attachment #2: Type: text/html, Size: 6632 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-29 18:20 meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440 Elvis Dowson
@ 2012-05-29 18:36 ` Mark Hatle
  2012-05-29 19:46   ` Elvis Dowson
  0 siblings, 1 reply; 10+ messages in thread
From: Mark Hatle @ 2012-05-29 18:36 UTC (permalink / raw)
  To: openembedded-core

On 5/29/12 1:20 PM, Elvis Dowson wrote:
> Hi,
> I've added the meta-xilinx layer, and modified my build/conf/local.conf file as
> follows:
>
> # Set the target machine details
> MACHINE ?= "virtex5"
> # Set Xilinx Platform Studio hardware project path
> XILINX_BSP_PATH ?= "/project/xilinx-ml507"
> # Set target board
> XILINX_BOARD ?= "ml507"
>
> and when I try to build the meta-toolchain
>
> $ cd /tool/yocto/poky
> $ source oe-init-build-env build
> $ bitbake meta-toolchain
>
> I get the following errors:
>
> ERROR: Execution of event handler 'check_sanity_eventhandler' failed
> Traceback (most recent call last):
> File "/tool/yocto/poky/bitbake/lib/bb/utils.py", line 397, in
> better_eval(source=<code object <module> at 0x344b6b0, file "MACHINE_ARCH", line
> 1>, locals={'d': <bb.data_smart.DataSmart object at 0x1450050>}):
> def better_eval(source, locals):
>  > return eval(source, _context, locals)
> File "MACHINE_ARCH", line 1, in <module>
> File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 282, in
> DataSmart.getVar(var='TUNE_PKGARCH', expand=True, noweakdefault=False):
> if expand and value:
>  > return self.expand(value, var)
> return value
> File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 151, in
> DataSmart.expand(s='${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440",
> "${PPCPKGARCH}", d)}', varname='TUNE_PKGARCH'):
> def expand(self, s, varname = None):
>  > return self.expandWithRefs(s, varname).value
> File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 141, in
> DataSmart.expandWithRefs(s='${@bb.utils.contains("TUNE_FEATURES", "ppc440",
> "ppc440", "${PPCPKGARCH}", d)}', varname='TUNE_PKGARCH'):
> except Exception as exc:
>  > raise ExpansionError(varname, s, exc)
> ExpansionError: Failure expanding variable TUNE_PKGARCH, expression was
> ${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)}
> which triggered exception SyntaxError: EOL while scanning string literal
> (TUNE_PKGARCH, line 1)
>
> ERROR: Failure expanding variable TUNE_PKGARCH, expression was
> ${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)}
> which triggered exception SyntaxError: EOL while scanning string literal
> (TUNE_PKGARCH, line 1)
> ERROR: Command execution failed: Exited with 1
>
> Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
>
> Has support for the PowerPC440 processor (present in the Virtex-5 FPGA) been
> removed from the newer gcc-versions?

The error above is an issue w/ the tune configuration.  In stock oe-core there 
is no 405/440 configuration.

You will need to create a new tune file, see 
meta/conf/machine/include/tune-ppc603e.inc as a reasonable example..

--Mark

> Best regards,
>
> Elvis Dowson
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-29 18:36 ` Mark Hatle
@ 2012-05-29 19:46   ` Elvis Dowson
  2012-05-30  2:56     ` Khem Raj
  0 siblings, 1 reply; 10+ messages in thread
From: Elvis Dowson @ 2012-05-29 19:46 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

Hi Mark,

On May 29, 2012, at 8:36 PM, Mark Hatle wrote:
> 
> The error above is an issue w/ the tune configuration.  In stock oe-core there is no 405/440 configuration.
> 
> You will need to create a new tune file, see meta/conf/machine/include/tune-ppc603e.inc as a reasonable example..


I modified the poky/meta/conf/machine/include/tune-ppc440.inc as follows:

DEFAULTTUNE ?= "ppc440"

require conf/machine/include/powerpc/arch-powerpc.inc

TUNEVALID[ppc440] = "Enable ppc440 specific processor optimizations"
TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "ppc440", "-mcpu=440", "", d)}"

AVAILTUNES += "ppc440"
TUNE_FEATURES_tune-ppc440 = "m32 fpu-soft ppc440"
TUNE_PKGARCH_tune-ppc603e = "ppc440"
PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppc440"

# glibc configure options to get 440 specific library (for sqrt)
GLIBC_EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppc440", "-with-cpu=440", "", d)}"

This is for the embedded PowerPC440 processor on the Virtex-5 FX70T FPGA chip, which doesn't have a hardware FPU. Do the options look okay: "m32 fpu-soft ppc440" ?

Is there a resource I can refer to see a full list of applicable PowerPC440 gcc-4.x compiler options?

Best regards,

Elvis Dowson


[-- Attachment #2: Type: text/html, Size: 1840 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-29 19:46   ` Elvis Dowson
@ 2012-05-30  2:56     ` Khem Raj
  2012-05-30 14:36       ` Adrian Alonso
  0 siblings, 1 reply; 10+ messages in thread
From: Khem Raj @ 2012-05-30  2:56 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

On Tue, May 29, 2012 at 12:46 PM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
> PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc}
> ppc440"

may be this should be be

 PACKAGE_EXTRA_ARCHS_tune-ppc440 =
"${PACKAGE_EXTRA_ARCHS_tune-powerpc-nf} ppc440"

other pieces look good

-Khem



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-30  2:56     ` Khem Raj
@ 2012-05-30 14:36       ` Adrian Alonso
  2012-05-30 14:47         ` Elvis Dowson
  0 siblings, 1 reply; 10+ messages in thread
From: Adrian Alonso @ 2012-05-30 14:36 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

Push fixes for this error.

Regards

On Tue, May 29, 2012 at 9:56 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Tue, May 29, 2012 at 12:46 PM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>> PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc}
>> ppc440"
>
> may be this should be be
>
>  PACKAGE_EXTRA_ARCHS_tune-ppc440 =
> "${PACKAGE_EXTRA_ARCHS_tune-powerpc-nf} ppc440"
>
> other pieces look good
>
> -Khem
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



-- 
Saludos
Adrian Alonso
http://aalonso.wordpress.com



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-30 14:36       ` Adrian Alonso
@ 2012-05-30 14:47         ` Elvis Dowson
  2012-05-30 15:00           ` Khem Raj
  2012-05-30 15:00           ` Mark Hatle
  0 siblings, 2 replies; 10+ messages in thread
From: Elvis Dowson @ 2012-05-30 14:47 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

Hi Khem,

> On Tue, May 29, 2012 at 9:56 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> On Tue, May 29, 2012 at 12:46 PM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>>> PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppc440"
>> 
>> may be this should be be
>> 
>>  PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc-nf} ppc440"
>> 
>> other pieces look good


What does the -nf suffix do ?

Best regards,

Elvis Dowson


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-30 14:47         ` Elvis Dowson
@ 2012-05-30 15:00           ` Khem Raj
  2012-05-30 15:34             ` Elvis Dowson
  2012-05-30 15:00           ` Mark Hatle
  1 sibling, 1 reply; 10+ messages in thread
From: Khem Raj @ 2012-05-30 15:00 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

On Wed, May 30, 2012 at 7:47 AM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>
> What does the -nf suffix do ?
>

indicates no float



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-30 14:47         ` Elvis Dowson
  2012-05-30 15:00           ` Khem Raj
@ 2012-05-30 15:00           ` Mark Hatle
  1 sibling, 0 replies; 10+ messages in thread
From: Mark Hatle @ 2012-05-30 15:00 UTC (permalink / raw)
  To: openembedded-core

On 5/30/12 9:47 AM, Elvis Dowson wrote:
> Hi Khem,
>
>> On Tue, May 29, 2012 at 9:56 PM, Khem Raj<raj.khem@gmail.com>  wrote:
>>> On Tue, May 29, 2012 at 12:46 PM, Elvis Dowson<elvis.dowson@gmail.com>  wrote:
>>>> PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppc440"
>>>
>>> may be this should be be
>>>
>>>   PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc-nf} ppc440"
>>>
>>> other pieces look good
>
>
> What does the -nf suffix do ?

-nf means "no floating" point math.

There are variants of the ppc4xx lines with and without classic Power floating 
point units.

--Mark

> Best regards,
>
> Elvis Dowson
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-30 15:00           ` Khem Raj
@ 2012-05-30 15:34             ` Elvis Dowson
  2012-05-30 16:04               ` Khem Raj
  0 siblings, 1 reply; 10+ messages in thread
From: Elvis Dowson @ 2012-05-30 15:34 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

Hi,

On May 30, 2012, at 5:00 PM, Khem Raj wrote:

> On Wed, May 30, 2012 at 7:47 AM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>> 
>> What does the -nf suffix do ?
>> 
> 
> indicates no float

What should I call the tune configuration file: tune-ppc440.inc or tune-ppc440-nf.inc ?

For the initial build tests, I will first try to get this running without a hardware FPU. By default the embedded PowerPC 440 processor on the Xilinx Virtex-5 doesn't have a hardware FPU. But one can configure a LogiCORE IP Virtex-5 APU Floating-Point Unit (v1.01a) to get single or double precision FPU support. 

How would I handle file naming and configuration for these 3 possible variants (i.e. software floating point emulation, hardware FPU single precision & hardware FPU double precision)?

Best regards,

Elvis Dowson




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
  2012-05-30 15:34             ` Elvis Dowson
@ 2012-05-30 16:04               ` Khem Raj
  0 siblings, 0 replies; 10+ messages in thread
From: Khem Raj @ 2012-05-30 16:04 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer

On Wed, May 30, 2012 at 8:34 AM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>
>
> On May 30, 2012, at 5:00 PM, Khem Raj wrote:
>
>> On Wed, May 30, 2012 at 7:47 AM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>>>
>>> What does the -nf suffix do ?
>>>
>>
>> indicates no float
>
> What should I call the tune configuration file: tune-ppc440.inc or tune-ppc440-nf.inc ?

I dont have strong opinion on it but I think 440 with fpu are denoted
as ppc440fp or somesuch so I default 440 core is nofp
unline other powerpc cores.



^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2012-05-30 16:15 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-29 18:20 meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440 Elvis Dowson
2012-05-29 18:36 ` Mark Hatle
2012-05-29 19:46   ` Elvis Dowson
2012-05-30  2:56     ` Khem Raj
2012-05-30 14:36       ` Adrian Alonso
2012-05-30 14:47         ` Elvis Dowson
2012-05-30 15:00           ` Khem Raj
2012-05-30 15:34             ` Elvis Dowson
2012-05-30 16:04               ` Khem Raj
2012-05-30 15:00           ` Mark Hatle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox