Re: master build failed
Ok, thanks. Gonna check rsb.
On Sun 16. Feb 2020 at 20:54, Joel Sherrill wrote:
>
>
> On Sun, Feb 16, 2020, 1:44 PM Ярослав Лещинский
> wrote:
>
>> Hello,
>>
>> I decided to update master to the latest. During the build got such error:
>>
>> ../../../../../rtems/c/src/../../cpukit/libcsupport/src/posix_devctl.c:
>> In function 'posix_devctl':
>> ../../../../../rtems/c/src/../../cpukit/libcsupport/src/posix_devctl.c:81:15:
>> error: 'SOCKCLOSE' undeclared (first use in this function)
>>if (dcmd == SOCKCLOSE ) {
>>^
>> ../../../../../rtems/c/src/../../cpukit/libcsupport/src/posix_devctl.c:81:15:
>> note: each undeclared identifier is reported only once for each function it
>> appears in
>>
>> Was running as:
>> ./bootstrap && cd ../ && rm -rf build && mkdir build && cd build &&
>> ../rtems/configure --target=arm-rtems5 --prefix $HOME/workspace/rtems/build
>> && make -j8 RTEMS_BSP=stm32f4 && make RTEMS_BSP=stm32f4 install
>>
>> Did I miss some updates from sourcebuilder, for example or it's problem
>> with a build in general?
>>
>
> You missed an RSB update to get at least a newer newlib.
>
> SOCKCLOSE is required by the FACE Technical Standard, Edition 3.0 and
> later.
>
> Fwiw RTEMS with Deos passed verification and is conformant with Edition
> 3.0. RTEMS provides POSIX services and Deos provides ARINC 653.
>
> --joel
>
>
>
>> --
>> --
>> Kind regards,
>> *Yaroslav Leshchinsky*
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
> --
--
Kind regards,
*Yaroslav Leshchinsky*
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
master build failed
Hello,
I decided to update master to the latest. During the build got such error:
../../../../../rtems/c/src/../../cpukit/libcsupport/src/posix_devctl.c: In
function 'posix_devctl':
../../../../../rtems/c/src/../../cpukit/libcsupport/src/posix_devctl.c:81:15:
error: 'SOCKCLOSE' undeclared (first use in this function)
if (dcmd == SOCKCLOSE ) {
^
../../../../../rtems/c/src/../../cpukit/libcsupport/src/posix_devctl.c:81:15:
note: each undeclared identifier is reported only once for each function it
appears in
Was running as:
./bootstrap && cd ../ && rm -rf build && mkdir build && cd build &&
../rtems/configure --target=arm-rtems5 --prefix $HOME/workspace/rtems/build
&& make -j8 RTEMS_BSP=stm32f4 && make RTEMS_BSP=stm32f4 install
Did I miss some updates from sourcebuilder, for example or it's problem
with a build in general?
--
--
Kind regards,
*Yaroslav Leshchinsky*
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: fatal after a new source-builder update
sorry, my fault -- forgot to rebuild the whole project. Everything works fine with enabled FPU (-mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard) On Wed, 15 May 2019 at 17:06, Ярослав Лещинский wrote: > if change to CPU_CFLAGS = -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 > -mfloat-abi=softfp, application not responded at all. > > > > On Wed, 15 May 2019 at 16:45, Ярослав Лещинский > wrote: > >> yes, I know, I just checked that behavior is the same as before. >> >> With these flags -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 >> -mfloat-abi=hard >> >> I got error from linker: >> >> /home/midnight/rtems/toolchain/5/lib/gcc/arm-rtems5/7.4.1/../../../../arm-rtems5/bin/ld: >> error: o-optimize/test.exe uses VFP register arguments, / >> home/midnight/workspace/rtems/build/arm-rtems5/stm32l4/lib/librtemsbsp.a(bspfatal-default.o) >> does not >> /home/midnight/rtems/toolchain/5/lib/gcc/arm-rtems5/7.4.1/../../../../arm-rtems5/bin/ld: >> failed to merge target specific data of file /home/midnig >> >> ht/workspace/rtems/build/arm-rtems5/stm32l4/lib/librtemsbsp.a(bspfatal-default.o) >> >> Currently I'm trying to figure out what is a problem. >> >> On Wed, 15 May 2019 at 16:33, Sebastian Huber < >> sebastian.hu...@embedded-brains.de> wrote: >> >>> On 15/05/2019 15:31, Ярослав Лещинский wrote: >>> > problem solved after edition of CPU_FLAGS as mentioned in stm32f4.cfg: >>> > >>> > CPU_FLAGS = -mthumb -mcpu=cortex-m4 >>> >>> If you use these flags, then you don't use the floating point >>> instructions. >>> >>> -- >>> Sebastian Huber, embedded brains GmbH >>> >>> Address : Dornierstr. 4, D-82178 Puchheim, Germany >>> Phone : +49 89 189 47 41-16 >>> Fax : +49 89 189 47 41-09 >>> E-Mail : sebastian.hu...@embedded-brains.de >>> PGP : Public key available on request. >>> >>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. >>> >>> >> >> -- >> -- >> Kind regards, >> *Yaroslav Leshchinsky* >> > > > -- > -- > Kind regards, > *Yaroslav Leshchinsky* > -- -- Kind regards, *Yaroslav Leshchinsky* ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: fatal after a new source-builder update
if change to CPU_CFLAGS = -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=softfp, application not responded at all. On Wed, 15 May 2019 at 16:45, Ярослав Лещинский wrote: > yes, I know, I just checked that behavior is the same as before. > > With these flags -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard > > I got error from linker: > > /home/midnight/rtems/toolchain/5/lib/gcc/arm-rtems5/7.4.1/../../../../arm-rtems5/bin/ld: > error: o-optimize/test.exe uses VFP register arguments, / > home/midnight/workspace/rtems/build/arm-rtems5/stm32l4/lib/librtemsbsp.a(bspfatal-default.o) > does not > /home/midnight/rtems/toolchain/5/lib/gcc/arm-rtems5/7.4.1/../../../../arm-rtems5/bin/ld: > failed to merge target specific data of file /home/midnig > > ht/workspace/rtems/build/arm-rtems5/stm32l4/lib/librtemsbsp.a(bspfatal-default.o) > > Currently I'm trying to figure out what is a problem. > > On Wed, 15 May 2019 at 16:33, Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> On 15/05/2019 15:31, Ярослав Лещинский wrote: >> > problem solved after edition of CPU_FLAGS as mentioned in stm32f4.cfg: >> > >> > CPU_FLAGS = -mthumb -mcpu=cortex-m4 >> >> If you use these flags, then you don't use the floating point >> instructions. >> >> -- >> Sebastian Huber, embedded brains GmbH >> >> Address : Dornierstr. 4, D-82178 Puchheim, Germany >> Phone : +49 89 189 47 41-16 >> Fax : +49 89 189 47 41-09 >> E-Mail : sebastian.hu...@embedded-brains.de >> PGP : Public key available on request. >> >> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. >> >> > > -- > -- > Kind regards, > *Yaroslav Leshchinsky* > -- -- Kind regards, *Yaroslav Leshchinsky* ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: fatal after a new source-builder update
yes, I know, I just checked that behavior is the same as before. With these flags -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard I got error from linker: /home/midnight/rtems/toolchain/5/lib/gcc/arm-rtems5/7.4.1/../../../../arm-rtems5/bin/ld: error: o-optimize/test.exe uses VFP register arguments, / home/midnight/workspace/rtems/build/arm-rtems5/stm32l4/lib/librtemsbsp.a(bspfatal-default.o) does not /home/midnight/rtems/toolchain/5/lib/gcc/arm-rtems5/7.4.1/../../../../arm-rtems5/bin/ld: failed to merge target specific data of file /home/midnig ht/workspace/rtems/build/arm-rtems5/stm32l4/lib/librtemsbsp.a(bspfatal-default.o) Currently I'm trying to figure out what is a problem. On Wed, 15 May 2019 at 16:33, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 15/05/2019 15:31, Ярослав Лещинский wrote: > > problem solved after edition of CPU_FLAGS as mentioned in stm32f4.cfg: > > > > CPU_FLAGS = -mthumb -mcpu=cortex-m4 > > If you use these flags, then you don't use the floating point instructions. > > -- > Sebastian Huber, embedded brains GmbH > > Address : Dornierstr. 4, D-82178 Puchheim, Germany > Phone : +49 89 189 47 41-16 > Fax : +49 89 189 47 41-09 > E-Mail : sebastian.hu...@embedded-brains.de > PGP : Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > > -- -- Kind regards, *Yaroslav Leshchinsky* ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: fatal after a new source-builder update
problem solved after edition of CPU_FLAGS as mentioned in stm32f4.cfg: CPU_FLAGS = -mthumb -mcpu=cortex-m4 Thanks. On Wed, 15 May 2019 at 09:41, Ярослав Лещинский wrote: > Ok, I will check. > > Thanks. > > ср, 15 мая 2019 г. в 9:34, Sebastian Huber < > sebastian.hu...@embedded-brains.de>: > >> On 14/05/2019 20:51, Ярослав Лещинский wrote: >> > Hello Sebastian, >> > >> > I have added my own BSP for stm32l4 it based on stm32f4. If you want >> > you can take a look on it -- in attached my patch for a new >> BSP(stm32l4). >> >> Due to the multilib changes, you have to adjust the GCC options for your >> BSP: >> >> -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard >> >> See also: >> >> https://docs.rtems.org/branches/master/cpu-supplement/arm.html#multilibs >> >> -- >> Sebastian Huber, embedded brains GmbH >> >> Address : Dornierstr. 4, D-82178 Puchheim, Germany >> Phone : +49 89 189 47 41-16 >> Fax : +49 89 189 47 41-09 >> E-Mail : sebastian.hu...@embedded-brains.de >> PGP : Public key available on request. >> >> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. >> >> -- > -- > Kind regards, > *Yaroslav Leshchinsky* > -- -- Kind regards, *Yaroslav Leshchinsky* ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: fatal after a new source-builder update
Ok, I will check. Thanks. ср, 15 мая 2019 г. в 9:34, Sebastian Huber < sebastian.hu...@embedded-brains.de>: > On 14/05/2019 20:51, Ярослав Лещинский wrote: > > Hello Sebastian, > > > > I have added my own BSP for stm32l4 it based on stm32f4. If you want > > you can take a look on it -- in attached my patch for a new BSP(stm32l4). > > Due to the multilib changes, you have to adjust the GCC options for your > BSP: > > -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard > > See also: > > https://docs.rtems.org/branches/master/cpu-supplement/arm.html#multilibs > > -- > Sebastian Huber, embedded brains GmbH > > Address : Dornierstr. 4, D-82178 Puchheim, Germany > Phone : +49 89 189 47 41-16 > Fax : +49 89 189 47 41-09 > E-Mail : sebastian.hu...@embedded-brains.de > PGP : Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > > -- -- Kind regards, *Yaroslav Leshchinsky* ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH 1/4] Add stm32l476vg discovery board support
Hello, Due the size limit the first patch I'm sending as an archive. -- -- Kind regards, *Yaroslav Leshchinsky* 0001-Add-stm32l476vg-discovery-board-support.patch.tar.gz Description: application/gzip ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Stm32l4 contribution
Hello, Today I added some patches related to stm32l4 board support. As it was the first time when I’m dealing with a contribution here in RTEMS, could you please check: does this patches existed at all? I sent them via git email, so I’m not sure that I made all correct. Thanks. -- -- Kind regards, *Yaroslav Leshchinsky* ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Fwd: rtems interrupt
Hi everyone. I need help with interrupt manager for stm32f4. Here is my test project https://github.com/MiDWalkeR/try_rtems. I took example code from hello_world_c and modify it: added my own drivers for exti and gpio. Drivers was checked without rtems and working well. Board - stm32f446re. When i flash my device in terminal i see code line number from exti_event.c, that means that task is working. When i push the button all breaks down only reset can help. When i enable my own exti interrupt method without rtems_interrupt_handler_install and push the button in terminal i get the string "spurious interrupt: 40". - that means interrupt was detected. How correct should i config interrupt manager? It's looks like i'm making some stupid mistake(-s), but don't see them... Thanks for any advice. -- С уважением, Лещинский Ярослав. +79814031224 -- С уважением, Лещинский Ярослав. +79814031224 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
