You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Barbiani <ba...@gmail.com> on 2021/01/29 01:17:58 UTC
PIC32 build fail
Hello,
Has anyone tested the pic32 build lately? I am using the pic32mx7mmb.
It is setting the processor as '-mprocessor=elf32pic32mx' for the xc32
compiler.
In file included from
/opt/microchip/xc32/v2.50/bin/bin/../../lib/gcc/pic32mx/4.8.3/../../../../pic32mx/lib/./crt0.S:50:0:
/opt/microchip/xc32/v2.50/pic32mx/include/xc.h:710:4: error: #error Unknown
processor!
# error Unknown processor!
^
ERROR: xc32-gcc failed: 255
command: xc32-gcc -MT
./builtin_list.home.future.nuttx.apps.builtin.o -M '-fno-builtin' '-Wall'
'-Wstrict-prototypes' '-Wshadow' '-Wundef' '-fno-strict-aliasing'
'-fno-strength-reduce' '-fomit-frame-pointer' '-mprocessor=elf32pic32mx'
'-march=m4k' ...
Marcio.
Re: PIC32 build fail
Posted by Barbiani <ba...@gmail.com>.
>
>
> Did you just use this configuration?
>
> https://www.github.com/crosstool-ng/crosstool-ng/tree/master/samples%2Fmips-unknown-elf%2Fcrosstool.config
>
>
I did. Then changed to little endian, enabled newlib and gdb.
Probably better start from mipsel-gnu.
Re: PIC32 build fail
Posted by Brennan Ashton <ba...@brennanashton.com>.
If we can get build secret by infra set we can probably just make a
pipeline that we can trigger to build and upload the CI toolchain to a blob
store like S3. I can file a ticket.
On Fri, Jan 29, 2021, 9:30 PM Xiang Xiao <xi...@gmail.com> wrote:
> How about we generate the toolchain binary and publish it on some github
> repo?
>
> > -----Original Message-----
> > From: Brennan Ashton <ba...@brennanashton.com>
> > Sent: Friday, January 29, 2021 11:49 PM
> > To: dev@nuttx.apache.org
> > Subject: Re: PIC32 build fail
> >
> > On Fri, Jan 29, 2021, 4:39 AM Barbiani <ba...@gmail.com> wrote:
> >
> > > I was able to use crosstool-ng to build gcc 10.2 (static) and Nuttx.
> > >
> > > I see that the automated test downloads a pre-built toolchain. Do I
> > > create an archive of the toolchain and upload somewhere?
> > >
> > >
> > I think this is helpful to know that it's working with with latest
> toolchain, but we should hold off on updating the ones in CI until we have a
> > better story for hosting them instead of requiring the image to build
> gcc/binutils. We are doing this for RX and it add quite a bit of time.
> >
> > Did you just use this configuration?
> >
> https://www.github.com/crosstool-ng/crosstool-ng/tree/master/samples%2Fmips-unknown-elf%2Fcrosstool.config
> >
> > Thanks!
> > --Brennan
>
>
RE: PIC32 build fail
Posted by Xiang Xiao <xi...@gmail.com>.
How about we generate the toolchain binary and publish it on some github repo?
> -----Original Message-----
> From: Brennan Ashton <ba...@brennanashton.com>
> Sent: Friday, January 29, 2021 11:49 PM
> To: dev@nuttx.apache.org
> Subject: Re: PIC32 build fail
>
> On Fri, Jan 29, 2021, 4:39 AM Barbiani <ba...@gmail.com> wrote:
>
> > I was able to use crosstool-ng to build gcc 10.2 (static) and Nuttx.
> >
> > I see that the automated test downloads a pre-built toolchain. Do I
> > create an archive of the toolchain and upload somewhere?
> >
> >
> I think this is helpful to know that it's working with with latest toolchain, but we should hold off on updating the ones in CI until we have a
> better story for hosting them instead of requiring the image to build gcc/binutils. We are doing this for RX and it add quite a bit of time.
>
> Did you just use this configuration?
> https://www.github.com/crosstool-ng/crosstool-ng/tree/master/samples%2Fmips-unknown-elf%2Fcrosstool.config
>
> Thanks!
> --Brennan
Re: PIC32 build fail
Posted by Brennan Ashton <ba...@brennanashton.com>.
On Fri, Jan 29, 2021, 4:39 AM Barbiani <ba...@gmail.com> wrote:
> I was able to use crosstool-ng to build gcc 10.2 (static) and Nuttx.
>
> I see that the automated test downloads a pre-built toolchain. Do I create
> an archive of
> the toolchain and upload somewhere?
>
>
I think this is helpful to know that it's working with with latest
toolchain, but we should hold off on updating the ones in CI until we have
a better story for hosting them instead of requiring the image to build
gcc/binutils. We are doing this for RX and it add quite a bit of time.
Did you just use this configuration?
https://www.github.com/crosstool-ng/crosstool-ng/tree/master/samples%2Fmips-unknown-elf%2Fcrosstool.config
Thanks!
--Brennan
Re: PIC32 build fail
Posted by Barbiani <ba...@gmail.com>.
I was able to use crosstool-ng to build gcc 10.2 (static) and Nuttx.
I see that the automated test downloads a pre-built toolchain. Do I create
an archive of
the toolchain and upload somewhere?
On Fri, Jan 29, 2021 at 12:08 AM Xiang Xiao <xi...@gmail.com>
wrote:
> If so, it's better to switch from Pinguino to mips-elf-gcc for daily check.
> Marcio, could you try mips-elf-gcc and send PR to
> https://github.com/apache/incubator-nuttx-testing?
>
> On Fri, Jan 29, 2021 at 11:05 AM Gregory Nutt <sp...@gmail.com> wrote:
>
> > The XC32 used to work years ago but I don't think anyone has used it in
> > the last 5 years or so. I would not recommend it. It is non-standard
> > and very likely incompatible. I would instead recommend any
> > mips-elf-gcc tool chain. There are several perbuilt MIPS toolchains
> > available. You can build a newer toolchain for yourself following
> > instructions on the internet or using the NuttX buildroot. The Pinguino
> > toolchain is a standard MIPS GCC toolchain but renames the binaries for
> > its branding. The last time I looked, the Pingquino toolchain was very
> > old and had not been updated recently.
> >
> > On 1/28/2021 8:53 PM, Barbiani wrote:
> > > Pinguino does work without a glitch.
> > >
> > >
> > > On Thu, Jan 28, 2021 at 11:29 PM Xiang Xiao <xiaoxiang781216@gmail.com
> >
> > > wrote:
> > >
> > >> On Fri, Jan 29, 2021 at 9:20 AM Barbiani <ba...@gmail.com> wrote:
> > >>
> > >>> Hello,
> > >>>
> > >>> Has anyone tested the pic32 build lately? I am using the pic32mx7mmb.
> > >>>
> > >>>
> > >> Yes, MIPS target is on the CI checklist:
> > >>
> > >>
> > >>
> >
> https://github.com/apache/incubator-nuttx-testing/blob/master/testlist/other.dat#L13-L22
> > >>
> > >> It is setting the processor as '-mprocessor=elf32pic32mx' for the xc32
> > >>> compiler.
> > >>>
> > >>> In file included from
> > >>>
> > >>>
> > >>
> >
> /opt/microchip/xc32/v2.50/bin/bin/../../lib/gcc/pic32mx/4.8.3/../../../../pic32mx/lib/./crt0.S:50:0:
> > >>> /opt/microchip/xc32/v2.50/pic32mx/include/xc.h:710:4: error: #error
> > >> Unknown
> > >>> processor!
> > >>> # error Unknown processor!
> > >>> ^
> > >>> ERROR: xc32-gcc failed: 255
> > >>> command: xc32-gcc -MT
> > >>> ./builtin_list.home.future.nuttx.apps.builtin.o -M '-fno-builtin'
> > >> '-Wall'
> > >>> '-Wstrict-prototypes' '-Wshadow' '-Wundef' '-fno-strict-aliasing'
> > >>> '-fno-strength-reduce' '-fomit-frame-pointer'
> > '-mprocessor=elf32pic32mx'
> > >>> '-march=m4k' ...
> > >>>
> > >>>
> > >> Could you try Pinguino toolchain which is used in CI build:
> > >>
> > >>
> >
> https://github.com/apache/incubator-nuttx-testing/blob/master/docker/linux/Dockerfile#L81-L89
> > >>
> > >>
> > >>> Marcio.
> > >>>
> >
>
Re: PIC32 build fail
Posted by Xiang Xiao <xi...@gmail.com>.
If so, it's better to switch from Pinguino to mips-elf-gcc for daily check.
Marcio, could you try mips-elf-gcc and send PR to
https://github.com/apache/incubator-nuttx-testing?
On Fri, Jan 29, 2021 at 11:05 AM Gregory Nutt <sp...@gmail.com> wrote:
> The XC32 used to work years ago but I don't think anyone has used it in
> the last 5 years or so. I would not recommend it. It is non-standard
> and very likely incompatible. I would instead recommend any
> mips-elf-gcc tool chain. There are several perbuilt MIPS toolchains
> available. You can build a newer toolchain for yourself following
> instructions on the internet or using the NuttX buildroot. The Pinguino
> toolchain is a standard MIPS GCC toolchain but renames the binaries for
> its branding. The last time I looked, the Pingquino toolchain was very
> old and had not been updated recently.
>
> On 1/28/2021 8:53 PM, Barbiani wrote:
> > Pinguino does work without a glitch.
> >
> >
> > On Thu, Jan 28, 2021 at 11:29 PM Xiang Xiao <xi...@gmail.com>
> > wrote:
> >
> >> On Fri, Jan 29, 2021 at 9:20 AM Barbiani <ba...@gmail.com> wrote:
> >>
> >>> Hello,
> >>>
> >>> Has anyone tested the pic32 build lately? I am using the pic32mx7mmb.
> >>>
> >>>
> >> Yes, MIPS target is on the CI checklist:
> >>
> >>
> >>
> https://github.com/apache/incubator-nuttx-testing/blob/master/testlist/other.dat#L13-L22
> >>
> >> It is setting the processor as '-mprocessor=elf32pic32mx' for the xc32
> >>> compiler.
> >>>
> >>> In file included from
> >>>
> >>>
> >>
> /opt/microchip/xc32/v2.50/bin/bin/../../lib/gcc/pic32mx/4.8.3/../../../../pic32mx/lib/./crt0.S:50:0:
> >>> /opt/microchip/xc32/v2.50/pic32mx/include/xc.h:710:4: error: #error
> >> Unknown
> >>> processor!
> >>> # error Unknown processor!
> >>> ^
> >>> ERROR: xc32-gcc failed: 255
> >>> command: xc32-gcc -MT
> >>> ./builtin_list.home.future.nuttx.apps.builtin.o -M '-fno-builtin'
> >> '-Wall'
> >>> '-Wstrict-prototypes' '-Wshadow' '-Wundef' '-fno-strict-aliasing'
> >>> '-fno-strength-reduce' '-fomit-frame-pointer'
> '-mprocessor=elf32pic32mx'
> >>> '-march=m4k' ...
> >>>
> >>>
> >> Could you try Pinguino toolchain which is used in CI build:
> >>
> >>
> https://github.com/apache/incubator-nuttx-testing/blob/master/docker/linux/Dockerfile#L81-L89
> >>
> >>
> >>> Marcio.
> >>>
>
Re: PIC32 build fail
Posted by Gregory Nutt <sp...@gmail.com>.
The XC32 used to work years ago but I don't think anyone has used it in
the last 5 years or so. I would not recommend it. It is non-standard
and very likely incompatible. I would instead recommend any
mips-elf-gcc tool chain. There are several perbuilt MIPS toolchains
available. You can build a newer toolchain for yourself following
instructions on the internet or using the NuttX buildroot. The Pinguino
toolchain is a standard MIPS GCC toolchain but renames the binaries for
its branding. The last time I looked, the Pingquino toolchain was very
old and had not been updated recently.
On 1/28/2021 8:53 PM, Barbiani wrote:
> Pinguino does work without a glitch.
>
>
> On Thu, Jan 28, 2021 at 11:29 PM Xiang Xiao <xi...@gmail.com>
> wrote:
>
>> On Fri, Jan 29, 2021 at 9:20 AM Barbiani <ba...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> Has anyone tested the pic32 build lately? I am using the pic32mx7mmb.
>>>
>>>
>> Yes, MIPS target is on the CI checklist:
>>
>>
>> https://github.com/apache/incubator-nuttx-testing/blob/master/testlist/other.dat#L13-L22
>>
>> It is setting the processor as '-mprocessor=elf32pic32mx' for the xc32
>>> compiler.
>>>
>>> In file included from
>>>
>>>
>> /opt/microchip/xc32/v2.50/bin/bin/../../lib/gcc/pic32mx/4.8.3/../../../../pic32mx/lib/./crt0.S:50:0:
>>> /opt/microchip/xc32/v2.50/pic32mx/include/xc.h:710:4: error: #error
>> Unknown
>>> processor!
>>> # error Unknown processor!
>>> ^
>>> ERROR: xc32-gcc failed: 255
>>> command: xc32-gcc -MT
>>> ./builtin_list.home.future.nuttx.apps.builtin.o -M '-fno-builtin'
>> '-Wall'
>>> '-Wstrict-prototypes' '-Wshadow' '-Wundef' '-fno-strict-aliasing'
>>> '-fno-strength-reduce' '-fomit-frame-pointer' '-mprocessor=elf32pic32mx'
>>> '-march=m4k' ...
>>>
>>>
>> Could you try Pinguino toolchain which is used in CI build:
>>
>> https://github.com/apache/incubator-nuttx-testing/blob/master/docker/linux/Dockerfile#L81-L89
>>
>>
>>> Marcio.
>>>
Re: PIC32 build fail
Posted by Barbiani <ba...@gmail.com>.
Pinguino does work without a glitch.
On Thu, Jan 28, 2021 at 11:29 PM Xiang Xiao <xi...@gmail.com>
wrote:
> On Fri, Jan 29, 2021 at 9:20 AM Barbiani <ba...@gmail.com> wrote:
>
> > Hello,
> >
> > Has anyone tested the pic32 build lately? I am using the pic32mx7mmb.
> >
> >
> Yes, MIPS target is on the CI checklist:
>
>
> https://github.com/apache/incubator-nuttx-testing/blob/master/testlist/other.dat#L13-L22
>
> It is setting the processor as '-mprocessor=elf32pic32mx' for the xc32
> > compiler.
> >
> > In file included from
> >
> >
> /opt/microchip/xc32/v2.50/bin/bin/../../lib/gcc/pic32mx/4.8.3/../../../../pic32mx/lib/./crt0.S:50:0:
> > /opt/microchip/xc32/v2.50/pic32mx/include/xc.h:710:4: error: #error
> Unknown
> > processor!
> > # error Unknown processor!
> > ^
> > ERROR: xc32-gcc failed: 255
> > command: xc32-gcc -MT
> > ./builtin_list.home.future.nuttx.apps.builtin.o -M '-fno-builtin'
> '-Wall'
> > '-Wstrict-prototypes' '-Wshadow' '-Wundef' '-fno-strict-aliasing'
> > '-fno-strength-reduce' '-fomit-frame-pointer' '-mprocessor=elf32pic32mx'
> > '-march=m4k' ...
> >
> >
> Could you try Pinguino toolchain which is used in CI build:
>
> https://github.com/apache/incubator-nuttx-testing/blob/master/docker/linux/Dockerfile#L81-L89
>
>
> > Marcio.
> >
>
Re: PIC32 build fail
Posted by Xiang Xiao <xi...@gmail.com>.
On Fri, Jan 29, 2021 at 9:20 AM Barbiani <ba...@gmail.com> wrote:
> Hello,
>
> Has anyone tested the pic32 build lately? I am using the pic32mx7mmb.
>
>
Yes, MIPS target is on the CI checklist:
https://github.com/apache/incubator-nuttx-testing/blob/master/testlist/other.dat#L13-L22
It is setting the processor as '-mprocessor=elf32pic32mx' for the xc32
> compiler.
>
> In file included from
>
> /opt/microchip/xc32/v2.50/bin/bin/../../lib/gcc/pic32mx/4.8.3/../../../../pic32mx/lib/./crt0.S:50:0:
> /opt/microchip/xc32/v2.50/pic32mx/include/xc.h:710:4: error: #error Unknown
> processor!
> # error Unknown processor!
> ^
> ERROR: xc32-gcc failed: 255
> command: xc32-gcc -MT
> ./builtin_list.home.future.nuttx.apps.builtin.o -M '-fno-builtin' '-Wall'
> '-Wstrict-prototypes' '-Wshadow' '-Wundef' '-fno-strict-aliasing'
> '-fno-strength-reduce' '-fomit-frame-pointer' '-mprocessor=elf32pic32mx'
> '-march=m4k' ...
>
>
Could you try Pinguino toolchain which is used in CI build:
https://github.com/apache/incubator-nuttx-testing/blob/master/docker/linux/Dockerfile#L81-L89
> Marcio.
>