You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mynewt.apache.org by Chee Wai Tang <ch...@outlook.com> on 2022/12/12 04:05:07 UTC

BSP for Fanstel LN60G840

Hi Sir,

I am new to Zephyr OS and am trying to setup proof of concept prototype using Fanstel's LN60G840 with nRF9160 to handle LTE module and separate nRF52840 for BLE and user app. I only manage to find hex/bin files on Fanstel website. I can manage to download LTE firmware into nRF9160 but has problem with trying to develop user application for the nRF52840 "BT840F". I am using VS code for IDE environment.

I see your website below has basic bsp support for fanstel-ev-bt840 under hw/bsp sun folder. I have read up on how to create custom board in nRF connect SDK documentation but have never try doing this.  I hope you can provide sufficient guidance on how to do this.

Please advise.

Best regards
Chee Wai



https://github.com/apache/mynewt-core
[https://opengraph.githubassets.com/98915fb7c86471ee1ada283c15cd44ce4f3aec0cfd0d11a5d6133d9e22225c15/apache/mynewt-core]<https://github.com/apache/mynewt-core>
GitHub - apache/mynewt-core: An OS to build, deploy and securely manage billions of devices<https://github.com/apache/mynewt-core>
Overview. Apache Mynewt is an open-source operating system for tiny embedded devices. Its goal is to make it easy to develop applications for microcontroller environments where power and cost are driving factors.
github.com


Re: Can't compile unittests

Posted by Szymon Janc <sz...@codecoup.pl>.
Hi,

`newt test` is using native target which is 32bit, so it requires support
for 32bit binaries, does WSL2 support it?
As a starter make sure you have gcc-multilib installed

On Fri, 14 Apr 2023 at 10:53, Jan Clement <ja...@cm-electronics.de>
wrote:

> Hello,
>
> > looks like WSL toolchain misconfiguration...
> anything i can do to compile on WSL? I really need the tests working.
>
> Thanks
>
>
> Am 14.04.2023 um 10:32 schrieb Szymon Janc:
> > Hi,
> >
> > OK, so we were able to reproduce this on WSL, yet all is fine on native
> > linux (including Ubuntu 22.04)
> > Not sure what is going on though, looks like WSL toolchain
> > misconfiguration...
> >
> > Also, that `newt info` output is awkward (all repos showing same
> > non-upstream sha). How did you set that up?
> >
> >
> > On Wed, 12 Apr 2023 at 15:37, Jan Clement <jan.clement@cm-electronics.de
> >
> > wrote:
> >
> >>> Which Linux is this? It looks like it is toolchain issue..Welcome to
> >> Ubuntu 22.04.2 LTS (GNU/Linux
> >> 5.15.90.1-microsoft-standard-WSL2 x86_64)
> >>
> >> i am using WSL on Win10
> >>
> >>> Also, could you do `newt info` and show result?
> >> Apache Newt 1.9.0 / 5e4874f / 2021-03-24_23:48
> >>
> >> Repository info:
> >>       * apache-mynewt-core: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> >> 0.0.1, (dirty: local changes)
> >>       * apache-mynewt-mcumgr: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> >> 0.0.0, (dirty: local changes)
> >>       * apache-mynewt-nimble: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> >> 0.0.0, (dirty: local changes)
> >>       * mcuboot: ab4c872471d65be1375f6bb49f21d58cdf389bac, 0.0.0,
> (dirty:
> >> local changes)
> >>       * my_project (project): ab4c872471d65be1375f6bb49f21d58cdf389bac
> >> (dirty: local changes)
> >>
> >>
> >> on Windows I can build for mys target with no problems, but native
> >> builds are not working due to POSIX issues..
> >>
> >> Thank you for your time.
> >>
> >>
> >>
> >> Mit freundlichen Grüßen
> >>
> >> Jan Clement
> >>
> >>
> >> Clement, Mastalerz & Partner, Elektroingenieure
> >> cm-electronics
> >> Salzstrasse 9
> >> 79098 Freiburg, Germany
> >>
> >> +49 761 45894342
> >> info@cm-electronics.de
> >> www.cm-electronics.de
> >>
> >> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
> >> Freiburg i. Br. PR700214
> >>
> >> Am 12.04.2023 um 11:48 schrieb Szymon Janc:
> >>> Hi,
> >>>
> >>> Which Linux is this? It looks like it is toolchain issue..
> >>> Also, could you do `newt info` and show result?
> >>>
> >>>
> >>> On Tue, 11 Apr 2023 at 16:26, Jan Clement <
> jan.clement@cm-electronics.de
> >>>
> >>> wrote:
> >>>
> >>>> Hi there,
> >>>>
> >>>> I am trying to compile and use mynewt unittests. I am not able to
> >>>> compile under Linux, it gets stuck at some C makros. Here is the
> compile
> >>>> output i got from newt build tool:
> >>>>
> >>>>
> >>>>> Testing package libs/xxx/selftest
> >>>>> In file included from
> >>>> /usr/lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9,
> >>>>>                    from
> >>>> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h:74,
> >>>>>                    from
> >>>> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:55:
> >>>>> /usr/include/stdint.h:276:17: error: missing binary operator before
> >>>> token "("
> >>>>>     276 | #if __GLIBC_USE (IEC_60559_BFP_EXT_C2X)
> >>>>>         |                 ^
> >>>>> In file included from
> >>>> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:57:
> >>>>> /usr/include/string.h:36:43: error: missing binary operator before
> >> token
> >>>> "("
> >>>>>      36 | #if defined __cplusplus && (__GNUC_PREREQ (4, 4) \
> >>>>>         |                                           ^
> >>>>> /usr/include/string.h:53:71: error: missing ')' after "defined"
> >>>>>      53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> >>>> (__GLIBC_USE (ISOC2X))
> >>>>>         |
> >>>>        ^
> >>>>> /usr/include/string.h:53:72: error: missing binary operator before
> >> token
> >>>> "ISOC2X"
> >>>>>      53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> >>>> (__GLIBC_USE (ISOC2X))
> >>>>>         |
> >>>>         ^~~~~~
> >>>>> /usr/include/string.h:185:30: error: missing ')' after "defined"
> >>>>>     185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined
> >> (__GLIBC_USE
> >>>> (ISOC2X)))
> >>>>>         |                              ^
> >>>>> /usr/include/string.h:185:31: error: missing binary operator before
> >>>> token "LIB_EXT2"
> >>>>>     185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined
> >> (__GLIBC_USE
> >>>> (ISOC2X)))
> >>>>>         |                               ^~~~~~~~
> >>>>> /usr/include/string.h:194:52: error: missing ')' after "defined"
> >>>>>     194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE
> (LIB_EXT2))
> >>>> || defined (__GLIBC_USE (ISOC2X))
> >>>>>         |                                                    ^
> >>>>> /usr/include/string.h:194:53: error: missing binary operator before
> >>>> token "LIB_EXT2"
> >>>>>     194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE
> (LIB_EXT2))
> >>>> || defined (__GLIBC_USE (ISOC2X))
> >>>>>         |
>  ^~~~~~~~
> >>>>> /usr/include/string.h:532:19: error: missing binary operator before
> >>>> token "("
> >>>>>     532 | #if __GNUC_PREREQ (3,4)
> >>>>>         |                   ^
> >>>>> ecc.o: repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c \
> >>>>>    repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h
> \
> >>>>>
> >>>>
> >>
> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc_platform_specific.h
> >>>>> Error: Test failure(s):
> >>>>> Passed tests: []
> >>>>
> >>>> any ideas on what i could do to get things working? Thanks in advance
> :)
> >>>>
> >>>>
> >>>> Mit freundlichen Grüßen
> >>>>
> >>>> Jan Clement
> >>>>
> >>>>
> >>>> Clement, Mastalerz & Partner, Elektroingenieure
> >>>> cm-electronics
> >>>> Salzstrasse 9
> >>>> 79098 Freiburg, Germany
> >>>>
> >>>> +49 761 45894342
> >>>> info@cm-electronics.de
> >>>> www.cm-electronics.de
> >>>>
> >>>> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
> >>>> Freiburg i. Br. PR700214
> >>>>
> >>>
> >>>
> >>
> >
> >
>


-- 
pozdrawiam
Szymon K. Janc

Re: Can't compile unittests

Posted by Jan Clement <ja...@cm-electronics.de>.
Hello,

> looks like WSL toolchain misconfiguration...
anything i can do to compile on WSL? I really need the tests working.

Thanks


Am 14.04.2023 um 10:32 schrieb Szymon Janc:
> Hi,
> 
> OK, so we were able to reproduce this on WSL, yet all is fine on native
> linux (including Ubuntu 22.04)
> Not sure what is going on though, looks like WSL toolchain
> misconfiguration...
> 
> Also, that `newt info` output is awkward (all repos showing same
> non-upstream sha). How did you set that up?
> 
> 
> On Wed, 12 Apr 2023 at 15:37, Jan Clement <ja...@cm-electronics.de>
> wrote:
> 
>>> Which Linux is this? It looks like it is toolchain issue..Welcome to
>> Ubuntu 22.04.2 LTS (GNU/Linux
>> 5.15.90.1-microsoft-standard-WSL2 x86_64)
>>
>> i am using WSL on Win10
>>
>>> Also, could you do `newt info` and show result?
>> Apache Newt 1.9.0 / 5e4874f / 2021-03-24_23:48
>>
>> Repository info:
>>       * apache-mynewt-core: ab4c872471d65be1375f6bb49f21d58cdf389bac,
>> 0.0.1, (dirty: local changes)
>>       * apache-mynewt-mcumgr: ab4c872471d65be1375f6bb49f21d58cdf389bac,
>> 0.0.0, (dirty: local changes)
>>       * apache-mynewt-nimble: ab4c872471d65be1375f6bb49f21d58cdf389bac,
>> 0.0.0, (dirty: local changes)
>>       * mcuboot: ab4c872471d65be1375f6bb49f21d58cdf389bac, 0.0.0, (dirty:
>> local changes)
>>       * my_project (project): ab4c872471d65be1375f6bb49f21d58cdf389bac
>> (dirty: local changes)
>>
>>
>> on Windows I can build for mys target with no problems, but native
>> builds are not working due to POSIX issues..
>>
>> Thank you for your time.
>>
>>
>>
>> Mit freundlichen Grüßen
>>
>> Jan Clement
>>
>>
>> Clement, Mastalerz & Partner, Elektroingenieure
>> cm-electronics
>> Salzstrasse 9
>> 79098 Freiburg, Germany
>>
>> +49 761 45894342
>> info@cm-electronics.de
>> www.cm-electronics.de
>>
>> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
>> Freiburg i. Br. PR700214
>>
>> Am 12.04.2023 um 11:48 schrieb Szymon Janc:
>>> Hi,
>>>
>>> Which Linux is this? It looks like it is toolchain issue..
>>> Also, could you do `newt info` and show result?
>>>
>>>
>>> On Tue, 11 Apr 2023 at 16:26, Jan Clement <jan.clement@cm-electronics.de
>>>
>>> wrote:
>>>
>>>> Hi there,
>>>>
>>>> I am trying to compile and use mynewt unittests. I am not able to
>>>> compile under Linux, it gets stuck at some C makros. Here is the compile
>>>> output i got from newt build tool:
>>>>
>>>>
>>>>> Testing package libs/xxx/selftest
>>>>> In file included from
>>>> /usr/lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9,
>>>>>                    from
>>>> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h:74,
>>>>>                    from
>>>> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:55:
>>>>> /usr/include/stdint.h:276:17: error: missing binary operator before
>>>> token "("
>>>>>     276 | #if __GLIBC_USE (IEC_60559_BFP_EXT_C2X)
>>>>>         |                 ^
>>>>> In file included from
>>>> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:57:
>>>>> /usr/include/string.h:36:43: error: missing binary operator before
>> token
>>>> "("
>>>>>      36 | #if defined __cplusplus && (__GNUC_PREREQ (4, 4) \
>>>>>         |                                           ^
>>>>> /usr/include/string.h:53:71: error: missing ')' after "defined"
>>>>>      53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
>>>> (__GLIBC_USE (ISOC2X))
>>>>>         |
>>>>        ^
>>>>> /usr/include/string.h:53:72: error: missing binary operator before
>> token
>>>> "ISOC2X"
>>>>>      53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
>>>> (__GLIBC_USE (ISOC2X))
>>>>>         |
>>>>         ^~~~~~
>>>>> /usr/include/string.h:185:30: error: missing ')' after "defined"
>>>>>     185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined
>> (__GLIBC_USE
>>>> (ISOC2X)))
>>>>>         |                              ^
>>>>> /usr/include/string.h:185:31: error: missing binary operator before
>>>> token "LIB_EXT2"
>>>>>     185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined
>> (__GLIBC_USE
>>>> (ISOC2X)))
>>>>>         |                               ^~~~~~~~
>>>>> /usr/include/string.h:194:52: error: missing ')' after "defined"
>>>>>     194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
>>>> || defined (__GLIBC_USE (ISOC2X))
>>>>>         |                                                    ^
>>>>> /usr/include/string.h:194:53: error: missing binary operator before
>>>> token "LIB_EXT2"
>>>>>     194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
>>>> || defined (__GLIBC_USE (ISOC2X))
>>>>>         |                                                     ^~~~~~~~
>>>>> /usr/include/string.h:532:19: error: missing binary operator before
>>>> token "("
>>>>>     532 | #if __GNUC_PREREQ (3,4)
>>>>>         |                   ^
>>>>> ecc.o: repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c \
>>>>>    repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h \
>>>>>
>>>>
>> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc_platform_specific.h
>>>>> Error: Test failure(s):
>>>>> Passed tests: []
>>>>
>>>> any ideas on what i could do to get things working? Thanks in advance :)
>>>>
>>>>
>>>> Mit freundlichen Grüßen
>>>>
>>>> Jan Clement
>>>>
>>>>
>>>> Clement, Mastalerz & Partner, Elektroingenieure
>>>> cm-electronics
>>>> Salzstrasse 9
>>>> 79098 Freiburg, Germany
>>>>
>>>> +49 761 45894342
>>>> info@cm-electronics.de
>>>> www.cm-electronics.de
>>>>
>>>> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
>>>> Freiburg i. Br. PR700214
>>>>
>>>
>>>
>>
> 
> 

Re: Can't compile unittests

Posted by Szymon Janc <sz...@codecoup.pl>.
Hi,

OK, so we were able to reproduce this on WSL, yet all is fine on native
linux (including Ubuntu 22.04)
Not sure what is going on though, looks like WSL toolchain
misconfiguration...

Also, that `newt info` output is awkward (all repos showing same
non-upstream sha). How did you set that up?


On Wed, 12 Apr 2023 at 15:37, Jan Clement <ja...@cm-electronics.de>
wrote:

> > Which Linux is this? It looks like it is toolchain issue..Welcome to
> Ubuntu 22.04.2 LTS (GNU/Linux
> 5.15.90.1-microsoft-standard-WSL2 x86_64)
>
> i am using WSL on Win10
>
> > Also, could you do `newt info` and show result?
> Apache Newt 1.9.0 / 5e4874f / 2021-03-24_23:48
>
> Repository info:
>      * apache-mynewt-core: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> 0.0.1, (dirty: local changes)
>      * apache-mynewt-mcumgr: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> 0.0.0, (dirty: local changes)
>      * apache-mynewt-nimble: ab4c872471d65be1375f6bb49f21d58cdf389bac,
> 0.0.0, (dirty: local changes)
>      * mcuboot: ab4c872471d65be1375f6bb49f21d58cdf389bac, 0.0.0, (dirty:
> local changes)
>      * my_project (project): ab4c872471d65be1375f6bb49f21d58cdf389bac
> (dirty: local changes)
>
>
> on Windows I can build for mys target with no problems, but native
> builds are not working due to POSIX issues..
>
> Thank you for your time.
>
>
>
> Mit freundlichen Grüßen
>
> Jan Clement
>
>
> Clement, Mastalerz & Partner, Elektroingenieure
> cm-electronics
> Salzstrasse 9
> 79098 Freiburg, Germany
>
> +49 761 45894342
> info@cm-electronics.de
> www.cm-electronics.de
>
> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
> Freiburg i. Br. PR700214
>
> Am 12.04.2023 um 11:48 schrieb Szymon Janc:
> > Hi,
> >
> > Which Linux is this? It looks like it is toolchain issue..
> > Also, could you do `newt info` and show result?
> >
> >
> > On Tue, 11 Apr 2023 at 16:26, Jan Clement <jan.clement@cm-electronics.de
> >
> > wrote:
> >
> >> Hi there,
> >>
> >> I am trying to compile and use mynewt unittests. I am not able to
> >> compile under Linux, it gets stuck at some C makros. Here is the compile
> >> output i got from newt build tool:
> >>
> >>
> >>> Testing package libs/xxx/selftest
> >>> In file included from
> >> /usr/lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9,
> >>>                   from
> >> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h:74,
> >>>                   from
> >> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:55:
> >>> /usr/include/stdint.h:276:17: error: missing binary operator before
> >> token "("
> >>>    276 | #if __GLIBC_USE (IEC_60559_BFP_EXT_C2X)
> >>>        |                 ^
> >>> In file included from
> >> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:57:
> >>> /usr/include/string.h:36:43: error: missing binary operator before
> token
> >> "("
> >>>     36 | #if defined __cplusplus && (__GNUC_PREREQ (4, 4) \
> >>>        |                                           ^
> >>> /usr/include/string.h:53:71: error: missing ')' after "defined"
> >>>     53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> >> (__GLIBC_USE (ISOC2X))
> >>>        |
> >>       ^
> >>> /usr/include/string.h:53:72: error: missing binary operator before
> token
> >> "ISOC2X"
> >>>     53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> >> (__GLIBC_USE (ISOC2X))
> >>>        |
> >>        ^~~~~~
> >>> /usr/include/string.h:185:30: error: missing ')' after "defined"
> >>>    185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined
> (__GLIBC_USE
> >> (ISOC2X)))
> >>>        |                              ^
> >>> /usr/include/string.h:185:31: error: missing binary operator before
> >> token "LIB_EXT2"
> >>>    185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined
> (__GLIBC_USE
> >> (ISOC2X)))
> >>>        |                               ^~~~~~~~
> >>> /usr/include/string.h:194:52: error: missing ')' after "defined"
> >>>    194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
> >> || defined (__GLIBC_USE (ISOC2X))
> >>>        |                                                    ^
> >>> /usr/include/string.h:194:53: error: missing binary operator before
> >> token "LIB_EXT2"
> >>>    194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
> >> || defined (__GLIBC_USE (ISOC2X))
> >>>        |                                                     ^~~~~~~~
> >>> /usr/include/string.h:532:19: error: missing binary operator before
> >> token "("
> >>>    532 | #if __GNUC_PREREQ (3,4)
> >>>        |                   ^
> >>> ecc.o: repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c \
> >>>   repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h \
> >>>
> >>
> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc_platform_specific.h
> >>> Error: Test failure(s):
> >>> Passed tests: []
> >>
> >> any ideas on what i could do to get things working? Thanks in advance :)
> >>
> >>
> >> Mit freundlichen Grüßen
> >>
> >> Jan Clement
> >>
> >>
> >> Clement, Mastalerz & Partner, Elektroingenieure
> >> cm-electronics
> >> Salzstrasse 9
> >> 79098 Freiburg, Germany
> >>
> >> +49 761 45894342
> >> info@cm-electronics.de
> >> www.cm-electronics.de
> >>
> >> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
> >> Freiburg i. Br. PR700214
> >>
> >
> >
>


-- 
pozdrawiam
Szymon K. Janc

Re: Can't compile unittests

Posted by Jan Clement <ja...@cm-electronics.de>.
> Which Linux is this? It looks like it is toolchain issue..Welcome to Ubuntu 22.04.2 LTS (GNU/Linux 
5.15.90.1-microsoft-standard-WSL2 x86_64)

i am using WSL on Win10

> Also, could you do `newt info` and show result?
Apache Newt 1.9.0 / 5e4874f / 2021-03-24_23:48

Repository info:
     * apache-mynewt-core: ab4c872471d65be1375f6bb49f21d58cdf389bac, 
0.0.1, (dirty: local changes)
     * apache-mynewt-mcumgr: ab4c872471d65be1375f6bb49f21d58cdf389bac, 
0.0.0, (dirty: local changes)
     * apache-mynewt-nimble: ab4c872471d65be1375f6bb49f21d58cdf389bac, 
0.0.0, (dirty: local changes)
     * mcuboot: ab4c872471d65be1375f6bb49f21d58cdf389bac, 0.0.0, (dirty: 
local changes)
     * my_project (project): ab4c872471d65be1375f6bb49f21d58cdf389bac 
(dirty: local changes)


on Windows I can build for mys target with no problems, but native 
builds are not working due to POSIX issues..

Thank you for your time.



Mit freundlichen Grüßen

Jan Clement


Clement, Mastalerz & Partner, Elektroingenieure
cm-electronics
Salzstrasse 9
79098 Freiburg, Germany

+49 761 45894342
info@cm-electronics.de
www.cm-electronics.de

Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister: 
Freiburg i. Br. PR700214

Am 12.04.2023 um 11:48 schrieb Szymon Janc:
> Hi,
> 
> Which Linux is this? It looks like it is toolchain issue..
> Also, could you do `newt info` and show result?
> 
> 
> On Tue, 11 Apr 2023 at 16:26, Jan Clement <ja...@cm-electronics.de>
> wrote:
> 
>> Hi there,
>>
>> I am trying to compile and use mynewt unittests. I am not able to
>> compile under Linux, it gets stuck at some C makros. Here is the compile
>> output i got from newt build tool:
>>
>>
>>> Testing package libs/xxx/selftest
>>> In file included from
>> /usr/lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9,
>>>                   from
>> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h:74,
>>>                   from
>> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:55:
>>> /usr/include/stdint.h:276:17: error: missing binary operator before
>> token "("
>>>    276 | #if __GLIBC_USE (IEC_60559_BFP_EXT_C2X)
>>>        |                 ^
>>> In file included from
>> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:57:
>>> /usr/include/string.h:36:43: error: missing binary operator before token
>> "("
>>>     36 | #if defined __cplusplus && (__GNUC_PREREQ (4, 4) \
>>>        |                                           ^
>>> /usr/include/string.h:53:71: error: missing ')' after "defined"
>>>     53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
>> (__GLIBC_USE (ISOC2X))
>>>        |
>>       ^
>>> /usr/include/string.h:53:72: error: missing binary operator before token
>> "ISOC2X"
>>>     53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
>> (__GLIBC_USE (ISOC2X))
>>>        |
>>        ^~~~~~
>>> /usr/include/string.h:185:30: error: missing ')' after "defined"
>>>    185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined (__GLIBC_USE
>> (ISOC2X)))
>>>        |                              ^
>>> /usr/include/string.h:185:31: error: missing binary operator before
>> token "LIB_EXT2"
>>>    185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined (__GLIBC_USE
>> (ISOC2X)))
>>>        |                               ^~~~~~~~
>>> /usr/include/string.h:194:52: error: missing ')' after "defined"
>>>    194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
>> || defined (__GLIBC_USE (ISOC2X))
>>>        |                                                    ^
>>> /usr/include/string.h:194:53: error: missing binary operator before
>> token "LIB_EXT2"
>>>    194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
>> || defined (__GLIBC_USE (ISOC2X))
>>>        |                                                     ^~~~~~~~
>>> /usr/include/string.h:532:19: error: missing binary operator before
>> token "("
>>>    532 | #if __GNUC_PREREQ (3,4)
>>>        |                   ^
>>> ecc.o: repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c \
>>>   repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h \
>>>
>> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc_platform_specific.h
>>> Error: Test failure(s):
>>> Passed tests: []
>>
>> any ideas on what i could do to get things working? Thanks in advance :)
>>
>>
>> Mit freundlichen Grüßen
>>
>> Jan Clement
>>
>>
>> Clement, Mastalerz & Partner, Elektroingenieure
>> cm-electronics
>> Salzstrasse 9
>> 79098 Freiburg, Germany
>>
>> +49 761 45894342
>> info@cm-electronics.de
>> www.cm-electronics.de
>>
>> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
>> Freiburg i. Br. PR700214
>>
> 
> 

Re: Can't compile unittests

Posted by Szymon Janc <sz...@codecoup.pl>.
Hi,

Which Linux is this? It looks like it is toolchain issue..
Also, could you do `newt info` and show result?


On Tue, 11 Apr 2023 at 16:26, Jan Clement <ja...@cm-electronics.de>
wrote:

> Hi there,
>
> I am trying to compile and use mynewt unittests. I am not able to
> compile under Linux, it gets stuck at some C makros. Here is the compile
> output i got from newt build tool:
>
>
> > Testing package libs/xxx/selftest
> > In file included from
> /usr/lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9,
> >                  from
> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h:74,
> >                  from
> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:55:
> > /usr/include/stdint.h:276:17: error: missing binary operator before
> token "("
> >   276 | #if __GLIBC_USE (IEC_60559_BFP_EXT_C2X)
> >       |                 ^
> > In file included from
> repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:57:
> > /usr/include/string.h:36:43: error: missing binary operator before token
> "("
> >    36 | #if defined __cplusplus && (__GNUC_PREREQ (4, 4) \
> >       |                                           ^
> > /usr/include/string.h:53:71: error: missing ')' after "defined"
> >    53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> (__GLIBC_USE (ISOC2X))
> >       |
>      ^
> > /usr/include/string.h:53:72: error: missing binary operator before token
> "ISOC2X"
> >    53 | #if defined __USE_MISC || defined __USE_XOPEN || defined
> (__GLIBC_USE (ISOC2X))
> >       |
>       ^~~~~~
> > /usr/include/string.h:185:30: error: missing ')' after "defined"
> >   185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined (__GLIBC_USE
> (ISOC2X)))
> >       |                              ^
> > /usr/include/string.h:185:31: error: missing binary operator before
> token "LIB_EXT2"
> >   185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined (__GLIBC_USE
> (ISOC2X)))
> >       |                               ^~~~~~~~
> > /usr/include/string.h:194:52: error: missing ')' after "defined"
> >   194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
> || defined (__GLIBC_USE (ISOC2X))
> >       |                                                    ^
> > /usr/include/string.h:194:53: error: missing binary operator before
> token "LIB_EXT2"
> >   194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2))
> || defined (__GLIBC_USE (ISOC2X))
> >       |                                                     ^~~~~~~~
> > /usr/include/string.h:532:19: error: missing binary operator before
> token "("
> >   532 | #if __GNUC_PREREQ (3,4)
> >       |                   ^
> > ecc.o: repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c \
> >  repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h \
> >
> repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc_platform_specific.h
> > Error: Test failure(s):
> > Passed tests: []
>
> any ideas on what i could do to get things working? Thanks in advance :)
>
>
> Mit freundlichen Grüßen
>
> Jan Clement
>
>
> Clement, Mastalerz & Partner, Elektroingenieure
> cm-electronics
> Salzstrasse 9
> 79098 Freiburg, Germany
>
> +49 761 45894342
> info@cm-electronics.de
> www.cm-electronics.de
>
> Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister:
> Freiburg i. Br. PR700214
>


-- 
pozdrawiam
Szymon K. Janc

Can't compile unittests

Posted by Jan Clement <ja...@cm-electronics.de>.
Hi there,

I am trying to compile and use mynewt unittests. I am not able to 
compile under Linux, it gets stuck at some C makros. Here is the compile 
output i got from newt build tool:


> Testing package libs/xxx/selftest
> In file included from /usr/lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9,
>                  from repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h:74,
>                  from repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:55:
> /usr/include/stdint.h:276:17: error: missing binary operator before token "("
>   276 | #if __GLIBC_USE (IEC_60559_BFP_EXT_C2X)
>       |                 ^
> In file included from repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c:57:
> /usr/include/string.h:36:43: error: missing binary operator before token "("
>    36 | #if defined __cplusplus && (__GNUC_PREREQ (4, 4) \
>       |                                           ^
> /usr/include/string.h:53:71: error: missing ')' after "defined"
>    53 | #if defined __USE_MISC || defined __USE_XOPEN || defined (__GLIBC_USE (ISOC2X))
>       |                                                                       ^
> /usr/include/string.h:53:72: error: missing binary operator before token "ISOC2X"
>    53 | #if defined __USE_MISC || defined __USE_XOPEN || defined (__GLIBC_USE (ISOC2X))
>       |                                                                        ^~~~~~
> /usr/include/string.h:185:30: error: missing ')' after "defined"
>   185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined (__GLIBC_USE (ISOC2X)))
>       |                              ^
> /usr/include/string.h:185:31: error: missing binary operator before token "LIB_EXT2"
>   185 |      || defined (__GLIBC_USE (LIB_EXT2)) || defined (__GLIBC_USE (ISOC2X)))
>       |                               ^~~~~~~~
> /usr/include/string.h:194:52: error: missing ')' after "defined"
>   194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2)) || defined (__GLIBC_USE (ISOC2X))
>       |                                                    ^
> /usr/include/string.h:194:53: error: missing binary operator before token "LIB_EXT2"
>   194 | #if defined __USE_XOPEN2K8 || defined (__GLIBC_USE (LIB_EXT2)) || defined (__GLIBC_USE (ISOC2X))
>       |                                                     ^~~~~~~~
> /usr/include/string.h:532:19: error: missing binary operator before token "("
>   532 | #if __GNUC_PREREQ (3,4)
>       |                   ^
> ecc.o: repos/apache-mynewt-core/crypto/tinycrypt/src/ecc.c \
>  repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc.h \
>  repos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/ecc_platform_specific.h
> Error: Test failure(s):
> Passed tests: []

any ideas on what i could do to get things working? Thanks in advance :)


Mit freundlichen Grüßen

Jan Clement


Clement, Mastalerz & Partner, Elektroingenieure
cm-electronics
Salzstrasse 9
79098 Freiburg, Germany

+49 761 45894342
info@cm-electronics.de
www.cm-electronics.de

Clement, Mastalerz & Partner, Elektroingenieure - Handelsregister: 
Freiburg i. Br. PR700214

RE: BSP for Fanstel LN60G840

Posted by "Cufí, Carles" <Ca...@nordicsemi.no.INVALID>.
Hi there,

I think you have the wrong mailing list.

This is the Mynewt mailing list, the Zephyr mailing list is here:
https://lists.zephyrproject.org/g/devel

and the Zephyr Discord is here:
https://chat.zephyrproject.org/

Carles

> -----Original Message-----
> From: Chee Wai Tang <ch...@outlook.com>
> Sent: 12 December 2022 05:05
> To: dev@mynewt.apache.org
> Subject: BSP for Fanstel LN60G840
> Importance: High
> 
> Caution: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
> 
> 
> Hi Sir,
> 
> I am new to Zephyr OS and am trying to setup proof of concept prototype
> using Fanstel's LN60G840 with nRF9160 to handle LTE module and separate
> nRF52840 for BLE and user app. I only manage to find hex/bin files on
> Fanstel website. I can manage to download LTE firmware into nRF9160 but
> has problem with trying to develop user application for the nRF52840
> "BT840F". I am using VS code for IDE environment.
> 
> I see your website below has basic bsp support for fanstel-ev-bt840
> under hw/bsp sun folder. I have read up on how to create custom board in
> nRF connect SDK documentation but have never try doing this.  I hope you
> can provide sufficient guidance on how to do this.
> 
> Please advise.
> 
> Best regards
> Chee Wai
> 
> 
> 
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub
> .com%2Fapache%2Fmynewt-
> core&amp;data=05%7C01%7CCarles.Cufi%40nordicsemi.no%7Cbb7ddb5998a54da27f
> d708dadc04598d%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C638064208504
> 073067%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> iI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=MN0oFqRsFNgyIuyiMPQY
> VtSOjoHGCy7MJXNZfLJ8Yf8%3D&amp;reserved=0
> [https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopeng
> raph.githubassets.com%2F98915fb7c86471ee1ada283c15cd44ce4f3aec0cfd0d11a5
> d6133d9e22225c15%2Fapache%2Fmynewt-
> core&amp;data=05%7C01%7CCarles.Cufi%40nordicsemi.no%7Cbb7ddb5998a54da27f
> d708dadc04598d%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C638064208504
> 073067%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> iI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=fqmVH9rURkq%2F%2Bukb
> KsIV1JW9bcsUt9eAjaHru51JoeU%3D&amp;reserved=0]<https://eur03.safelinks.p
> rotection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmynewt-
> core&amp;data=05%7C01%7CCarles.Cufi%40nordicsemi.no%7Cbb7ddb5998a54da27f
> d708dadc04598d%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C638064208504
> 073067%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> iI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=MN0oFqRsFNgyIuyiMPQY
> VtSOjoHGCy7MJXNZfLJ8Yf8%3D&amp;reserved=0>
> GitHub - apache/mynewt-core: An OS to build, deploy and securely manage
> billions of
> devices<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
> 2Fgithub.com%2Fapache%2Fmynewt-
> core&amp;data=05%7C01%7CCarles.Cufi%40nordicsemi.no%7Cbb7ddb5998a54da27f
> d708dadc04598d%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C638064208504
> 073067%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> iI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=MN0oFqRsFNgyIuyiMPQY
> VtSOjoHGCy7MJXNZfLJ8Yf8%3D&amp;reserved=0>
> Overview. Apache Mynewt is an open-source operating system for tiny
> embedded devices. Its goal is to make it easy to develop applications
> for microcontroller environments where power and cost are driving
> factors.
> github.com