[U-Boot] Quark compile errors

[U-Boot] Quark compile errors

[Bin Meng]

Hi Andy,

On Wed, May 20, 2015 at 6:00 PM, Andy Pont <andy.pont@sdcsystems.com> wrote:
> Hello,
>
> I am trying to create a configuration for the Silicon Motion Osprey board
> which is a Quark SoC and their SM750 graphics controller.
>
> I have cloned the Intel Galileo files and changed them accordingly and have
> defined the options for the VBIOS for the graphics controller but when I try
> to compile I get the following build failure:
>

Can you post your full configuration here?

>   CC      arch/x86/lib/bios.o
> arch/x86/lib/bios.c: In function bint_exception_handlerb:
> arch/x86/lib/bios.c:61: error: unknown field beaxb specified in initializer
> arch/x86/lib/bios.c:61: warning: missing braces around initializer
> arch/x86/lib/bios.c:61: warning: (near initialization for
> breg_info.<anonymous>b)
> arch/x86/lib/bios.c:62: error: unknown field becxb specified in initializer
> arch/x86/lib/bios.c:63: error: unknown field bedxb specified in initializer
> arch/x86/lib/bios.c:64: error: unknown field bebxb specified in initializer
> arch/x86/lib/bios.c:65: error: unknown field bespb specified in initializer
> arch/x86/lib/bios.c:66: error: unknown field bebpb specified in initializer
> arch/x86/lib/bios.c:67: error: unknown field besib specified in initializer
> arch/x86/lib/bios.c:68: error: unknown field bedib specified in initializer
> make[1]: *** [arch/x86/lib/bios.o] Error 1
>
> Could you advise what setting I have missed that is causing this build issue
> or is it the case that the bios.c file is defined for x86 capabilities
> beyond those of Quark?
>
> Also, if anyone can tell me what $TERM setting I need to get the rogue "b"
> characters to actually display bold/bright then that would be great too!
>

I am using xterm, not sure if this helps.

$ echo $TERM
xterm

Regards,
Bin

[U-Boot] Quark compile errors

[Andy Pont]

Hi Bin,

> Can you post your full configuration here?

I have attached the autoconf.mk and U-Boot .config files.  Hopefully they tell you what you need.

> > Also, if anyone can tell me what $TERM setting I need to get the rogue "b"
> > characters to actually display bold/bright then that would be great too!
> 
> I am using xterm, not sure if this helps.
> 
> $ echo $TERM
> xterm

That is what I have too.  I guess it might be down to the way SecureCRT is interpreting what it is being sent rather than the Linux machine itself.

Regards,

Andy.


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: autoconf.mk
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150520/d0320c98/attachment.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uboot.config
Type: application/xml
Size: 6406 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150520/d0320c98/attachment.wsdl>

[U-Boot] Quark compile errors

[Simon Glass]

Hi Andy,

On 20 May 2015 at 04:20, Andy Pont <andy.pont@sdcsystems.com> wrote:
> Hi Bin,
>
>> Can you post your full configuration here?
>
> I have attached the autoconf.mk and U-Boot .config files.  Hopefully they tell you what you need.
>
>> > Also, if anyone can tell me what $TERM setting I need to get the rogue "b"
>> > characters to actually display bold/bright then that would be great too!
>>
>> I am using xterm, not sure if this helps.
>>
>> $ echo $TERM
>> xterm
>
> That is what I have too.  I guess it might be down to the way SecureCRT is interpreting what it is being sent rather than the Linux machine itself.

You might be able to set that terminal program to support 'xterm'
emulation, or perhaps change TERM to whatever it does support.

Regards,
Simon

[U-Boot] Quark compile errors

[Andy Pont]

Hi Simon,

> >> I am using xterm, not sure if this helps.
> >>
> >> $ echo $TERM
> >> xterm
> >
> > That is what I have too.  I guess it might be down to the way
> SecureCRT is interpreting what it is being sent rather than the Linux
> machine itself.
> 
> You might be able to set that terminal program to support 'xterm'
> emulation, or perhaps change TERM to whatever it does support.

I have figured this bit out...  By default the terminal emulation in SecureCRT is set to strip the 8th bit of the data it receives.  Having set it to use the 8th bit and also to interpret things with UTF-8 encoding all is good with the world.

Turns out that they aren't commands for bold/bright as I thought, they are in fact the leading and trailing single quotes around the error.

Now to try and fix the issue with the code not building...

Regards,

Andy.

[U-Boot] Quark compile errors

[Bin Meng]

Hi Andy,

On Wed, May 20, 2015 at 6:20 PM, Andy Pont <andy.pont@sdcsystems.com> wrote:
> Hi Bin,
>
>> Can you post your full configuration here?
>
> I have attached the autoconf.mk and U-Boot .config files.  Hopefully they tell you what you need.
>

Looks OK. What gcc version are you using? It seems that your compiler
does not understand the macro DOWNTO8 and DOWNTO16 in
arch/x86/lib/bios.h

>> > Also, if anyone can tell me what $TERM setting I need to get the rogue "b"
>> > characters to actually display bold/bright then that would be great too!
>>
>> I am using xterm, not sure if this helps.
>>
>> $ echo $TERM
>> xterm
>
> That is what I have too.  I guess it might be down to the way SecureCRT is interpreting what it is being sent rather than the Linux machine itself.
>

Regards,
Bin

[U-Boot] Quark compile errors

[Andy Pont]

Hi Bin,

> >> Can you post your full configuration here?
> >
> > I have attached the autoconf.mk and U-Boot .config files.  Hopefully they tell you what you need.
> >
> 
> Looks OK. What gcc version are you using? It seems that your compiler
> does not understand the macro DOWNTO8 and DOWNTO16 in
> arch/x86/lib/bios.h

It is using the standard version of gcc that comes as part of the CentOS 6.6 installation which is 4.4.7.

Regards,

Andy.

[U-Boot] Quark compile errors

[Bin Meng]

Hi Andy,

On Wed, May 20, 2015 at 10:50 PM, Andy Pont <andy.pont@sdcsystems.com> wrote:
> Hi Bin,
>
>> >> Can you post your full configuration here?
>> >
>> > I have attached the autoconf.mk and U-Boot .config files.  Hopefully they tell you what you need.
>> >
>>
>> Looks OK. What gcc version are you using? It seems that your compiler
>> does not understand the macro DOWNTO8 and DOWNTO16 in
>> arch/x86/lib/bios.h
>
> It is using the standard version of gcc that comes as part of the CentOS 6.6 installation which is 4.4.7.
>

I have been using 4.6.1 and 4.7.2, and both work. Can you please try
some newer gcc?

Regards,
Bin

[U-Boot] Quark compile errors

[Andy Pont]

Hi Bin,

> > It is using the standard version of gcc that comes as part of the 
> > CentOS 6.6 installation which is 4.4.7.
> >
> 
> I have been using 4.6.1 and 4.7.2, and both work. Can you please try
> some newer gcc?

Good call.  Having found a gcc version 4.8.4 then it has all compiled successfully!

Thanks for your help!

Regards,

Andy.

[U-Boot] Quark compile errors

[Bin Meng]

Hi Andy,

On Wed, May 20, 2015 at 10:58 PM, Andy Pont <andy.pont@sdcsystems.com> wrote:
> Hi Bin,
>
>> > It is using the standard version of gcc that comes as part of the
>> > CentOS 6.6 installation which is 4.4.7.
>> >
>>
>> I have been using 4.6.1 and 4.7.2, and both work. Can you please try
>> some newer gcc?
>
> Good call.  Having found a gcc version 4.8.4 then it has all compiled successfully!
>
> Thanks for your help!
>

Good to know.

BTW, so you are working on this board?
http://www.siliconmotion.com/EW_Pages/Osprey.html
Looks like a quark based board with graphics support! Are you planning
to submit patches to enable it?

Regards,
Bin

[U-Boot] Quark compile errors

[Andy Pont]

Hi Bin,

> BTW, so you are working on this board?
> http://www.siliconmotion.com/EW_Pages/Osprey.html
> Looks like a quark based board with graphics support! Are you planning
> to submit patches to enable it?

It is indeed for one of those boards, as an off-radar task to get my head back into x86 after lots of time spent playing with ARM!

At the moment I am still waiting for some physical hardware but once I have some and have tested everything then yes, I will submit the patches for it.

Regards,

Andy.

[U-Boot] Quark compile errors

[Andy Pont]

Hello,

I am trying to create a configuration for the Silicon Motion Osprey board
which is a Quark SoC and their SM750 graphics controller.

I have cloned the Intel Galileo files and changed them accordingly and have
defined the options for the VBIOS for the graphics controller but when I try
to compile I get the following build failure:

  CC      arch/x86/lib/bios.o
arch/x86/lib/bios.c: In function bint_exception_handlerb:
arch/x86/lib/bios.c:61: error: unknown field beaxb specified in initializer
arch/x86/lib/bios.c:61: warning: missing braces around initializer
arch/x86/lib/bios.c:61: warning: (near initialization for
breg_info.<anonymous>b)
arch/x86/lib/bios.c:62: error: unknown field becxb specified in initializer
arch/x86/lib/bios.c:63: error: unknown field bedxb specified in initializer
arch/x86/lib/bios.c:64: error: unknown field bebxb specified in initializer
arch/x86/lib/bios.c:65: error: unknown field bespb specified in initializer
arch/x86/lib/bios.c:66: error: unknown field bebpb specified in initializer
arch/x86/lib/bios.c:67: error: unknown field besib specified in initializer
arch/x86/lib/bios.c:68: error: unknown field bedib specified in initializer
make[1]: *** [arch/x86/lib/bios.o] Error 1

Could you advise what setting I have missed that is causing this build issue
or is it the case that the bios.c file is defined for x86 capabilities
beyond those of Quark?

Also, if anyone can tell me what $TERM setting I need to get the rogue "b"
characters to actually display bold/bright then that would be great too!

Thanks,

Andy.