Date   

Re: LVGL support and more examples

Lazar Chervenkov <lazar.chervenkov@...>
 

Hi Jan,

I'm using Nordic Connect SDK with Segger Embedded Studio, maybe that's why I'm confused. There is no option to select the shield in Segger and the nordic people forwarded me to Zephyr for help. So it's a magic circle :)

I also have a custom display shield with different spi pins and from the shield documentation I cannot understand how to remap the spi signals. The display driver is also different and I have to write it (it's a Sharp MIP LCD that I use).

Many thanks!

On Tue, Aug 18, 2020 at 8:29 AM Jan Van Winkel <jan.van_winkel@...> wrote:
Hi Lazar,

Not sure if your question is about how to tell LVGL which display to use or how to select a specific display controller.

The former is done by setting CONFIG_LVGL_DISPLAY_DEV_NAME to the same name as used by the display controller. Note that in case you are using any of the supported display shields, the shields config will take care of setting the correct value for CONFIG_LVGL_DISPLAY_DEV_NAME.

The later one, display controller selection, depends on the board you are using but all in-tree nrf52 boards, to my knowledge, make use of display shields and do not have on board display controllers. So the only thing you need is to pass the correct shield name during build.
For example to use the NRF52840 DK with an adafruit 2.8" TFT shield you can use following command to build: west build -b nrf52840dk_nrf52840 samples/gui/lvgl -- -DSHIELD=adafruit_2_8_tft_touch_v2

Jan

On Mon, Aug 17, 2020 at 10:49 PM Lazar Chervenkov <lazar.chervenkov@...> wrote:
Hi Carles,

I don't understand how to select which driver is used for the current project, as all are listed in the kconfig.

Thanks!

On Tue, 4 Aug 2020, 16:59 Cufi, Carles, <Carles.Cufi@...> wrote:

Hi there,

 

LVGL has been updated to version 7 in master:

https://github.com/zephyrproject-rtos/zephyr/pull/26982

 

Changing the display driver is done in Kconfig (and I assume Devicetree):

 

https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/display/Kconfig

 

Carles

 

 

From: devel@... <devel@...> On Behalf Of lazar.chervenkov via lists.zephyrproject.org
Sent: 04 August 2020 14:27
To: devel@...
Subject: [Zephyr-devel] LVGL support and more examples

 

Hi there,

I've been using LVGL for creating GUIs together with Nordic nRF5 SDK. I have to move to nRF Connect SDK for developing with nRF53 (which is actually based on Zephyr project). I'm quite new to Zephyr and I opened the LVGL example for nRF52840. But I'm using a different display driver and I cannot find a way how to change it. The information in the documentation is quite poor for this topic. Is there a plan to also move to LVGL version 7, as the one that is used now is version 6. 

Many thanks!



--
Mag. Lazar Chervenkov
phone: +4367761600476
e-mail: lazar.chervenkov@...


Re: LVGL support and more examples

Jan Van Winkel
 

Hi Lazar,

Not sure if your question is about how to tell LVGL which display to use or how to select a specific display controller.

The former is done by setting CONFIG_LVGL_DISPLAY_DEV_NAME to the same name as used by the display controller. Note that in case you are using any of the supported display shields, the shields config will take care of setting the correct value for CONFIG_LVGL_DISPLAY_DEV_NAME.

The later one, display controller selection, depends on the board you are using but all in-tree nrf52 boards, to my knowledge, make use of display shields and do not have on board display controllers. So the only thing you need is to pass the correct shield name during build.
For example to use the NRF52840 DK with an adafruit 2.8" TFT shield you can use following command to build: west build -b nrf52840dk_nrf52840 samples/gui/lvgl -- -DSHIELD=adafruit_2_8_tft_touch_v2

Jan

On Mon, Aug 17, 2020 at 10:49 PM Lazar Chervenkov <lazar.chervenkov@...> wrote:
Hi Carles,

I don't understand how to select which driver is used for the current project, as all are listed in the kconfig.

Thanks!

On Tue, 4 Aug 2020, 16:59 Cufi, Carles, <Carles.Cufi@...> wrote:

Hi there,

 

LVGL has been updated to version 7 in master:

https://github.com/zephyrproject-rtos/zephyr/pull/26982

 

Changing the display driver is done in Kconfig (and I assume Devicetree):

 

https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/display/Kconfig

 

Carles

 

 

From: devel@... <devel@...> On Behalf Of lazar.chervenkov via lists.zephyrproject.org
Sent: 04 August 2020 14:27
To: devel@...
Subject: [Zephyr-devel] LVGL support and more examples

 

Hi there,

I've been using LVGL for creating GUIs together with Nordic nRF5 SDK. I have to move to nRF Connect SDK for developing with nRF53 (which is actually based on Zephyr project). I'm quite new to Zephyr and I opened the LVGL example for nRF52840. But I'm using a different display driver and I cannot find a way how to change it. The information in the documentation is quite poor for this topic. Is there a plan to also move to LVGL version 7, as the one that is used now is version 6. 

Many thanks!


Re: LVGL support and more examples

Lazar Chervenkov <lazar.chervenkov@...>
 

Hi Carles,

I don't understand how to select which driver is used for the current project, as all are listed in the kconfig.

Thanks!

On Tue, 4 Aug 2020, 16:59 Cufi, Carles, <Carles.Cufi@...> wrote:

Hi there,

 

LVGL has been updated to version 7 in master:

https://github.com/zephyrproject-rtos/zephyr/pull/26982

 

Changing the display driver is done in Kconfig (and I assume Devicetree):

 

https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/display/Kconfig

 

Carles

 

 

From: devel@... <devel@...> On Behalf Of lazar.chervenkov via lists.zephyrproject.org
Sent: 04 August 2020 14:27
To: devel@...
Subject: [Zephyr-devel] LVGL support and more examples

 

Hi there,

I've been using LVGL for creating GUIs together with Nordic nRF5 SDK. I have to move to nRF Connect SDK for developing with nRF53 (which is actually based on Zephyr project). I'm quite new to Zephyr and I opened the LVGL example for nRF52840. But I'm using a different display driver and I cannot find a way how to change it. The information in the documentation is quite poor for this topic. Is there a plan to also move to LVGL version 7, as the one that is used now is version 6. 

Many thanks!


API meeting agenda: 2020-08-18

Peter A. Bigot
 

Carles has asked me to stand in for him again in coordinating this week's API telecon.
 
Topics include:
 
https://github.com/zephyrproject-rtos/zephyr/pull/25049 on USB include files, which I propose to move from Triage to In Progress.
 
https://github.com/zephyrproject-rtos/zephyr/pull/27624 which records my recollection of the consensus decision on certain API design policies.  Please add comments on the PR.
 
https://github.com/zephyrproject-rtos/zephyr/pull/25851 for JEDEC Serial Flash Discoverable Parameters inspection to confirm that it will support the various QSPI driver initiatives that are ongoing.
 
A status update on those QSPI driver initiatives.
 
Any other topics requested on the #api channel on slack or at the start of the meeting.
 
If time allows, a check on the status of in-progress issues and PRs in https://github.com/zephyrproject-rtos/zephyr/projects/18.
 
We are less than three weeks away from 2.4 feature freeze.  If you have enhancements or new capabilities you want in 2.4, please mark them with the 2.4 milestone on github.
 
If you want a PR or issue to be tracked in this meeting, please add it to the GitHub project.  If it's already there and you want it discussed in the next meeting, please say so via the #api channel on slack.
 
Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d
 
https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-meeting
https://github.com/zephyrproject-rtos/zephyr/projects/18


Re: [LWM2M] Client example - QEMU x86

Guillaume PAQUET <guillaume.paquet@...>
 

Robert,

Thanks again for your help.
It works fine.
I just flush dev tap0 and it is ok now in IPv4 and IPv6.

There is just one issue in strdup allocation. Default size is too small (we need more than 4 buffers, for ref I put 100. i don't try less)
CONFIG_LOG_STRDUP_BUF_COUNT=100

Rgds,

Guillaume


On Mon, Aug 17, 2020 at 4:47 PM Guillaume PAQUET <guillaume.paquet@...> wrote:
Hi Robert,

I think I saw what is wrong for me.
I have bad configuration on tap0.
Indeed, I have not the good inet addr. Here is my output : 
tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.7.1  netmask 255.255.255.255  broadcast 192.168.7.255
        inet6 fe80::36:65ff:fe12:f27  prefixlen 64  scopeid 0x20<link>
        inet6 2001:db8::2  prefixlen 64  scopeid 0x0<global>
        ether 02:36:65:12:0f:27  txqueuelen 1000  (Ethernet)
        RX packets 33899  bytes 4153906 (4.1 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 38604  bytes 86555696 (86.5 MB)
        TX errors 0  dropped 10 overruns 0  carrier 0  collisions 0

Thanks for this. I'll let you know

Rgds,

Guillaume

On Mon, Aug 17, 2020 at 4:33 PM Lubos, Robert <Robert.Lubos@...> wrote:

Hi Guillaume,

 

I’ve just verified the sample with current master (4bd247af700a88df3d5f2cca60e46b5669b4aa71), and it works fine on my machine.

 

Please double check if:

  1. The tap0 interface is up before running the sample (for instance with `ifconfig` command, it should have 192.0.2.2 IPv4 address assigned). Perhaps there were some errors during initialization? For me the output looks like this:

$ sudo ./loop-slip-tap.sh

********SLIP started on ``/tmp/slip.dev''

slipfd and inslip reopened

ip neigh flush dev tap0

Cannot find device "tap0"

opened tap device ``/dev/tap0''

ifconfig tap0 up

ip -6 route add 2001:db8::/64 dev tap0

ip -6 addr add 2001:db8::2/64 dev tap0

ip route add 192.0.2.0/24 dev tap0

ip addr add 192.0.2.2/24 dev tap0

ifconfig tap0

 

tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.0.2.2  netmask 255.255.255.0  broadcast 0.0.0.0

        inet6 fe80::207d:e5ff:fef5:83b8  prefixlen 64  scopeid 0x20<link>

        inet6 2001:db8::2  prefixlen 64  scopeid 0x0<global>

        ether 22:7d:e5:f5:83:b8  txqueuelen 1000  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

       TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

  1. Probably you’ve overwritten the default port number somehow? ` CONFIG_LWM2M_PEER_PORT` shall be set to 5683 (default Leshan configuration).
  2. Leshan server is actually running (not sure how to verify this properly, maybe by opening its web GUI in the web browser, localhost:8080 by default).

 

You may also monitor the traffic on the tap0 interface with wireshark easily.

 

Regards,

Robert

From: devel@... [mailto:devel@...] On Behalf Of Guillaume PAQUET via lists.zephyrproject.org
Sent: Monday, August 17, 2020 11:22
To: devel@...
Subject: Re: [Zephyr-devel] [LWM2M] Client example - QEMU x86

 

Hi,

 

Sorry for bad manipulation, my previous mail was not finished ...

So to complete it, I run ./loop-socat.sh and sudo ./loop-slip-tap.sh in net-tools to be able to run QEMU x86 properly.

 

Thanks for your help

 

Rgds

 

Guillaume

 

On Mon, Aug 17, 2020 at 11:20 AM Guillaume PAQUET <guillaume.paquet@...> wrote:

Hello Zephyr Community,

 

I am Guillaume Paquet, I worked for STIMIO company and I am now working for SMILE company, specialised in Linux Open Source Embedded topics.

I tried to run LWM2M client demo on QEMU x86 target : https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/net/lwm2m_client
I tried to connect to local leshan server but I don't achieve to register. i have always the following error

[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/1, buf:0x00144373, buflen:1
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/10, buf:0x001443b2, buflen:2
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:1/0/1, buf:0x0013dea0, buflen:4
[00:00:37.230,000] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'qemu_x86' with client lifetime 30
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_parse_peerinfo: Parse url: coap://192.0.2.2
[00:00:37.230,000] <dbg> net_lwm2m_rd_client.sm_send_registration: registration sent [192.0.2.2]
[00:00:39.590,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:44.280,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:53.660,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:01:12.420,000] <wrn> net_lwm2m_rd_client: Registration Timeout
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Disconnected
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Registration failure!

 

I only activated IPv4 (I also tried IPv6 and it does not work too).

Maybe I missed something in configuration.

For information, I run ./loop-socat.sh a

--

SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET

Tech Manager

 

 

TwitterFacebookLinkedInGithub

 

ecoPour la planète, n'imprimez ce mail que si c'est nécessaire


 

--

SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET

Tech Manager

 

 

TwitterFacebookLinkedInGithub

 

ecoPour la planète, n'imprimez ce mail que si c'est nécessaire



--
SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET
Tech Manager


Twitter Facebook LinkedIn Github


eco Pour la planète, n'imprimez ce mail que si c'est nécessaire


--
SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET
Tech Manager


Twitter Facebook LinkedIn Github


eco Pour la planète, n'imprimez ce mail que si c'est nécessaire


Re: [LWM2M] Client example - QEMU x86

Guillaume PAQUET <guillaume.paquet@...>
 

Hi Robert,

I think I saw what is wrong for me.
I have bad configuration on tap0.
Indeed, I have not the good inet addr. Here is my output : 
tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.7.1  netmask 255.255.255.255  broadcast 192.168.7.255
        inet6 fe80::36:65ff:fe12:f27  prefixlen 64  scopeid 0x20<link>
        inet6 2001:db8::2  prefixlen 64  scopeid 0x0<global>
        ether 02:36:65:12:0f:27  txqueuelen 1000  (Ethernet)
        RX packets 33899  bytes 4153906 (4.1 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 38604  bytes 86555696 (86.5 MB)
        TX errors 0  dropped 10 overruns 0  carrier 0  collisions 0

Thanks for this. I'll let you know

Rgds,

Guillaume

On Mon, Aug 17, 2020 at 4:33 PM Lubos, Robert <Robert.Lubos@...> wrote:

Hi Guillaume,

 

I’ve just verified the sample with current master (4bd247af700a88df3d5f2cca60e46b5669b4aa71), and it works fine on my machine.

 

Please double check if:

  1. The tap0 interface is up before running the sample (for instance with `ifconfig` command, it should have 192.0.2.2 IPv4 address assigned). Perhaps there were some errors during initialization? For me the output looks like this:

$ sudo ./loop-slip-tap.sh

********SLIP started on ``/tmp/slip.dev''

slipfd and inslip reopened

ip neigh flush dev tap0

Cannot find device "tap0"

opened tap device ``/dev/tap0''

ifconfig tap0 up

ip -6 route add 2001:db8::/64 dev tap0

ip -6 addr add 2001:db8::2/64 dev tap0

ip route add 192.0.2.0/24 dev tap0

ip addr add 192.0.2.2/24 dev tap0

ifconfig tap0

 

tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.0.2.2  netmask 255.255.255.0  broadcast 0.0.0.0

        inet6 fe80::207d:e5ff:fef5:83b8  prefixlen 64  scopeid 0x20<link>

        inet6 2001:db8::2  prefixlen 64  scopeid 0x0<global>

        ether 22:7d:e5:f5:83:b8  txqueuelen 1000  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

       TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

  1. Probably you’ve overwritten the default port number somehow? ` CONFIG_LWM2M_PEER_PORT` shall be set to 5683 (default Leshan configuration).
  2. Leshan server is actually running (not sure how to verify this properly, maybe by opening its web GUI in the web browser, localhost:8080 by default).

 

You may also monitor the traffic on the tap0 interface with wireshark easily.

 

Regards,

Robert

From: devel@... [mailto:devel@...] On Behalf Of Guillaume PAQUET via lists.zephyrproject.org
Sent: Monday, August 17, 2020 11:22
To: devel@...
Subject: Re: [Zephyr-devel] [LWM2M] Client example - QEMU x86

 

Hi,

 

Sorry for bad manipulation, my previous mail was not finished ...

So to complete it, I run ./loop-socat.sh and sudo ./loop-slip-tap.sh in net-tools to be able to run QEMU x86 properly.

 

Thanks for your help

 

Rgds

 

Guillaume

 

On Mon, Aug 17, 2020 at 11:20 AM Guillaume PAQUET <guillaume.paquet@...> wrote:

Hello Zephyr Community,

 

I am Guillaume Paquet, I worked for STIMIO company and I am now working for SMILE company, specialised in Linux Open Source Embedded topics.

I tried to run LWM2M client demo on QEMU x86 target : https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/net/lwm2m_client
I tried to connect to local leshan server but I don't achieve to register. i have always the following error

[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/1, buf:0x00144373, buflen:1
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/10, buf:0x001443b2, buflen:2
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:1/0/1, buf:0x0013dea0, buflen:4
[00:00:37.230,000] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'qemu_x86' with client lifetime 30
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_parse_peerinfo: Parse url: coap://192.0.2.2
[00:00:37.230,000] <dbg> net_lwm2m_rd_client.sm_send_registration: registration sent [192.0.2.2]
[00:00:39.590,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:44.280,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:53.660,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:01:12.420,000] <wrn> net_lwm2m_rd_client: Registration Timeout
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Disconnected
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Registration failure!

 

I only activated IPv4 (I also tried IPv6 and it does not work too).

Maybe I missed something in configuration.

For information, I run ./loop-socat.sh a

--

SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET

Tech Manager

 

 

TwitterFacebookLinkedInGithub

 

ecoPour la planète, n'imprimez ce mail que si c'est nécessaire


 

--

SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET

Tech Manager

 

 

TwitterFacebookLinkedInGithub

 

ecoPour la planète, n'imprimez ce mail que si c'est nécessaire



--
SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET
Tech Manager


Twitter Facebook LinkedIn Github


eco Pour la planète, n'imprimez ce mail que si c'est nécessaire


Re: [LWM2M] Client example - QEMU x86

Lubos, Robert
 

Hi Guillaume,

 

I’ve just verified the sample with current master (4bd247af700a88df3d5f2cca60e46b5669b4aa71), and it works fine on my machine.

 

Please double check if:

  1. The tap0 interface is up before running the sample (for instance with `ifconfig` command, it should have 192.0.2.2 IPv4 address assigned). Perhaps there were some errors during initialization? For me the output looks like this:

$ sudo ./loop-slip-tap.sh

********SLIP started on ``/tmp/slip.dev''

slipfd and inslip reopened

ip neigh flush dev tap0

Cannot find device "tap0"

opened tap device ``/dev/tap0''

ifconfig tap0 up

ip -6 route add 2001:db8::/64 dev tap0

ip -6 addr add 2001:db8::2/64 dev tap0

ip route add 192.0.2.0/24 dev tap0

ip addr add 192.0.2.2/24 dev tap0

ifconfig tap0

 

tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.0.2.2  netmask 255.255.255.0  broadcast 0.0.0.0

        inet6 fe80::207d:e5ff:fef5:83b8  prefixlen 64  scopeid 0x20<link>

        inet6 2001:db8::2  prefixlen 64  scopeid 0x0<global>

        ether 22:7d:e5:f5:83:b8  txqueuelen 1000  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

       TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

  1. Probably you’ve overwritten the default port number somehow? ` CONFIG_LWM2M_PEER_PORT` shall be set to 5683 (default Leshan configuration).
  2. Leshan server is actually running (not sure how to verify this properly, maybe by opening its web GUI in the web browser, localhost:8080 by default).

 

You may also monitor the traffic on the tap0 interface with wireshark easily.

 

Regards,

Robert

From: devel@... [mailto:devel@...] On Behalf Of Guillaume PAQUET via lists.zephyrproject.org
Sent: Monday, August 17, 2020 11:22
To: devel@...
Subject: Re: [Zephyr-devel] [LWM2M] Client example - QEMU x86

 

Hi,

 

Sorry for bad manipulation, my previous mail was not finished ...

So to complete it, I run ./loop-socat.sh and sudo ./loop-slip-tap.sh in net-tools to be able to run QEMU x86 properly.

 

Thanks for your help

 

Rgds

 

Guillaume

 

On Mon, Aug 17, 2020 at 11:20 AM Guillaume PAQUET <guillaume.paquet@...> wrote:

Hello Zephyr Community,

 

I am Guillaume Paquet, I worked for STIMIO company and I am now working for SMILE company, specialised in Linux Open Source Embedded topics.

I tried to run LWM2M client demo on QEMU x86 target : https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/net/lwm2m_client
I tried to connect to local leshan server but I don't achieve to register. i have always the following error

[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/1, buf:0x00144373, buflen:1
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/10, buf:0x001443b2, buflen:2
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:1/0/1, buf:0x0013dea0, buflen:4
[00:00:37.230,000] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'qemu_x86' with client lifetime 30
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_parse_peerinfo: Parse url: coap://192.0.2.2
[00:00:37.230,000] <dbg> net_lwm2m_rd_client.sm_send_registration: registration sent [192.0.2.2]
[00:00:39.590,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:44.280,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:53.660,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:01:12.420,000] <wrn> net_lwm2m_rd_client: Registration Timeout
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Disconnected
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Registration failure!

 

I only activated IPv4 (I also tried IPv6 and it does not work too).

Maybe I missed something in configuration.

For information, I run ./loop-socat.sh a

--

SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET

Tech Manager

 

 

TwitterFacebookLinkedInGithub

 

ecoPour la planète, n'imprimez ce mail que si c'est nécessaire


 

--

SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET

Tech Manager

 

 

TwitterFacebookLinkedInGithub

 

ecoPour la planète, n'imprimez ce mail que si c'est nécessaire


Re: [LWM2M] Client example - QEMU x86

Guillaume PAQUET <guillaume.paquet@...>
 

Hi,

Sorry for bad manipulation, my previous mail was not finished ...
So to complete it, I run ./loop-socat.sh and sudo ./loop-slip-tap.sh in net-tools to be able to run QEMU x86 properly.

Thanks for your help

Rgds

Guillaume

On Mon, Aug 17, 2020 at 11:20 AM Guillaume PAQUET <guillaume.paquet@...> wrote:
Hello Zephyr Community,

I am Guillaume Paquet, I worked for STIMIO company and I am now working for SMILE company, specialised in Linux Open Source Embedded topics.
I tried to run LWM2M client demo on QEMU x86 target : https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/net/lwm2m_client
I tried to connect to local leshan server but I don't achieve to register. i have always the following error
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/1, buf:0x00144373, buflen:1
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/10, buf:0x001443b2, buflen:2
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:1/0/1, buf:0x0013dea0, buflen:4
[00:00:37.230,000] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'qemu_x86' with client lifetime 30
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_parse_peerinfo: Parse url: coap://192.0.2.2
[00:00:37.230,000] <dbg> net_lwm2m_rd_client.sm_send_registration: registration sent [192.0.2.2]
[00:00:39.590,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:44.280,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:53.660,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:01:12.420,000] <wrn> net_lwm2m_rd_client: Registration Timeout
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Disconnected
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Registration failure!

I only activated IPv4 (I also tried IPv6 and it does not work too).
Maybe I missed something in configuration.
For information, I run ./loop-socat.sh a
--
SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET
Tech Manager


Twitter Facebook LinkedIn Github


eco Pour la planète, n'imprimez ce mail que si c'est nécessaire


--
SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET
Tech Manager


Twitter Facebook LinkedIn Github


eco Pour la planète, n'imprimez ce mail que si c'est nécessaire


[LWM2M] Client example - QEMU x86

Guillaume PAQUET <guillaume.paquet@...>
 

Hello Zephyr Community,

I am Guillaume Paquet, I worked for STIMIO company and I am now working for SMILE company, specialised in Linux Open Source Embedded topics.
I tried to run LWM2M client demo on QEMU x86 target : https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/net/lwm2m_client
I tried to connect to local leshan server but I don't achieve to register. i have always the following error
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/1, buf:0x00144373, buflen:1
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:0/0/10, buf:0x001443b2, buflen:2
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_engine_get: path:1/0/1, buf:0x0013dea0, buflen:4
[00:00:37.230,000] <inf> net_lwm2m_rd_client: RD Client started with endpoint 'qemu_x86' with client lifetime 30
[00:00:37.230,000] <dbg> net_lwm2m_engine.lwm2m_parse_peerinfo: Parse url: coap://192.0.2.2
[00:00:37.230,000] <dbg> net_lwm2m_rd_client.sm_send_registration: registration sent [192.0.2.2]
[00:00:39.590,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:44.280,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:00:53.660,000] <inf> net_lwm2m_engine: Resending message: 0x0013b4a0
[00:01:12.420,000] <wrn> net_lwm2m_rd_client: Registration Timeout
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Disconnected
[00:01:12.420,000] <dbg> net_lwm2m_client_app.rd_client_event: Registration failure!

I only activated IPv4 (I also tried IPv6 and it does not work too).
Maybe I missed something in configuration.
For information, I run ./loop-socat.sh a
--
SMILE

10-12 rue Nicolas Appert
44100 NANTES

Guillaume PAQUET
Tech Manager


Twitter Facebook LinkedIn Github


eco Pour la planète, n'imprimez ce mail que si c'est nécessaire


Zephyr Project Code Guideline - A Couple Notes

Hibberd, Amber M <amber.m.hibberd@...>
 

Hi All,

Just wanted to send out a communication to highlight a few things regarding the Zephyr Project Coding Guideline (CG):

-The CG has been published to the Zephyrproject.org documentation, here: https://docs.zephyrproject.org/latest/guides/coding_guidelines/index.html#coding-guidelines
-There is a Github label created to use for finding / submitting PRs. It is: area: Code Guideline.
-By searching you can find some compliance activity already started.
-The Safety WG is working to publish a violation report to be used as reference in this interim time as we work to identify and integrate a scanning tool into our CI. An update will be coming in a couple weeks.

Let me know if you have any questions / would like more information.
Thank you!
-Amber


Amber Hibberd
Software Engineering Manager
Firmware & Microcontroller Operating System (FMOS)
IAGS > IPAT
Intel Corporation | OR-JF1-2 Pole B17


Zephyr Project: Dev Meeting - Thu, 08/13/2020 3:00pm-4:00pm, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>
 

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 13 August 2020, 3:00pm to 4:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Dev-Review Meeting Agenda Aug 13

Kumar Gala
 

Here’s the agenda topics for this week:

* Zephyr Testing via Emu:
- https://github.com/zephyrproject-rtos/zephyr/issues/27531
* Any PR/issues w/dev-review tag
* Any topics anyone else has.

- k


Zephyr: Toolchain Working Group - Thu, 08/13/2020 #cal-notice

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Zephyr: Toolchain Working Group

When:
Thursday, 13 August 2020
2:00pm to 3:00pm
(GMT+00:00) UTC

Where:
Microsoft Teams Meeting

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Zephyr: Toolchain Working Group - Thu, 08/13/2020 2:00pm-3:00pm, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>
 

Reminder: Zephyr: Toolchain Working Group

When: Thursday, 13 August 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: Maureen Helm

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Zephyr Toolchain Working Group Meeting – 13 August 2020

Rasmussen, Torsten
 

Let’s get started on a new round of meetings.

 

Agenda

 

  • Updates:
  • Short term goals, way forward
    • Dedicated toolchain test cases.
    • Label PR for automatic execution of CI Toolchain test cases

 

 

Feel free to send a mail, if you would like additional topics to be discussed.

 

Best regards

 

Torsten T. Rasmussen           

 

Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________

 

Join Microsoft Teams Meeting

+1 321-558-6518 United States, Orlando (Toll)

Conference ID: 682 738 030#

Local numbers | Reset PIN | Learn more about Teams | Meeting options

 

________________________________________________________________________________

 

 

        

 

 

           

 


Zephyr Project: APIs - Tue, 08/11/2020 4:00pm-5:00pm, Please RSVP #cal-reminder

devel@lists.zephyrproject.org Calendar <devel@...>
 

Reminder: Zephyr Project: APIs

When: Tuesday, 11 August 2020, 4:00pm to 5:00pm, (GMT+00:00) UTC

Where:Microsoft Teams Meeting

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description:

Meeting decisions/discussions in their respective PRs, tracked here: https://github.com/zephyrproject-rtos/zephyr/projects/18


________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Zephyr support for ARM Cortex-A7 #custom_board

emkey <apollo3344@...>
 

Hello,
I am trying to use Zephyr in my current project. Unfortunately, I can not find any sample project, which is based on a ARM Cortex A7 architecture.
Mainly, my idea was to use an already available board project as a template and port it to the needs of my custom board.

Is there anything, which I can do now? Do maybe plans from the Zephyr community exists, to support the Cortex A7 architecture in future ?

Waiting for your kind reply and many thanks in advance.

Best regards,
Mehmet


Re: SOC_DIR not populated

Rasmussen, Torsten
 

Hi,

 

Thanks for the confirmation of the patch.

And thanks for the update.

 

I was waiting for confirmation before sending update on mailing list.

 

See more comments below.

 

/Torsten

 

 

From: Dan Kalowsky <dank@...>
Sent: 11 August, 2020 0:37
To: Rasmussen, Torsten <Torsten.Rasmussen@...>
Cc: Cufi, Carles <Carles.Cufi@...>; devel@...
Subject: Re: [Zephyr-devel] SOC_DIR not populated

 

Sorry for the delay in response, got pulled into other duties and was not able to follow up on this in the immediate time frame.

 

 

 

On Thu, Aug 6, 2020 at 11:27 PM Rasmussen, Torsten <Torsten.Rasmussen@...> wrote:

Hi,

 

Find answers inline.

And for convenience, a link to the fix: https://github.com/dkalowsk/broked_zephyr/pull/1

 

Thank you for this PR.  More importantly, thank you for fixing the documentation in the follow up PR and pointing out that this is a breaking change for others.

 

One additional note that should be added here, when using the files as corrected to build, they fail to find the linker.ld file found in the soc_a in the example.

 

The fix is to change the arm/product/CMakeLists.txt file like so:

 

- add_subdirectory(${SOC_SERIES})

+ add_subdirectory(${CONFIG_SOC_SERIES})

 

This seems to allow everything to work correctly in the compile time frame.  You may want to include that detail as well if it is correct.  Note the demo repo needs to be cleaned up to compile anything at all, don't trust it.  This seems odd because I believed that Zephyr dropped the CONFIG_ prefix from everything internally before using it, yet in this case the variable has data only when prefixed.

 

No, all Kconfig settings in CMake must be accessed using `CONFIG_<name>`.
Only the `SOC_SERIES` is a little special, as that is copied into a local variable (history goes before my time).

https://github.com/zephyrproject-rtos/zephyr/blob/master/cmake/app/boilerplate.cmake#L532

I would discourage using `SOC_SERIES` directly and instead do the proper `CONFIG_SOC_SERIES` but I will not remove `SOC_SERIES` possibility without a good reason, cause users may depend on it.


But using `SOC_SERIES` should work for files included as part of Zephyr CMake boilerplate (everything that is happening as part of `find_package(Zephyr)`).

Which is the case for `SOC_ROOT/arch/soc` included CMake files.

 

For other usage, such as if a CMakeLists.txt file is included as a `add_subdirectory()` after `find_package(Zephyr)` then `SOC_SERIES` cannot be used due to CMake scoping, and `CONFIG_SOC_SERIES` must be used.

That has not changed, so I would like to know how you get those CMake files included, to understand if there is an issue hidden somewhere.

This should not have changed behavior with the changes introduced by https://github.com/zephyrproject-rtos/zephyr/pull/26715 .

 

I had no problem with linking when building for nrf52840dk_nrf52840 board, but I had to set `import:true` in the west.yml to get Nordic hal headers.

But you might be looking at code that you have not pushed to the repo.

At least I don’t see any board using the `soc_a` SoC.

 

Ok, a little bit of history.

Originally, all ROOTs where a single root only, including BOARD_ROOT.

Now, this for sure has its limitation, as people would like to be able to specify more than one root in order to support both in- and out-of-tree BOARDS, SOC, DTS, and so on.

So BOARD_ROOT was the first to be cleaned up.

https://github.com/zephyrproject-rtos/zephyr/pull/10267

 

so there has been request for other ROOTs to be extended to support multiple roots.

https://github.com/zephyrproject-rtos/zephyr/issues/25215

 

There are also several users with out-of-tree SoCs, who are using both Zephyr SoCs and out-of-tree SoCs, and everyone must make there own way of ensuring that their SOC_ROOT gets set correctly.

I have seen this as a common approach:

if(BOARD STREQUAL my_custom_soc_board)
  set(BOARD_ROOT some/out/of/tree/soc/path)
endif()

 

Thank you for the history.  From my island, I don't see this as a correct usage/behavior, but I am clearly in the minority. 

 

 

Let me know if there are still issues with the linker script location.

 

See note above.

 

 

--

"Do you expect me to talk?"
"No Mr. Bond, I expect you to die."


Re: SOC_DIR not populated

Dan Kalowsky <dank@...>
 

Sorry for the delay in response, got pulled into other duties and was not able to follow up on this in the immediate time frame.



On Thu, Aug 6, 2020 at 11:27 PM Rasmussen, Torsten <Torsten.Rasmussen@...> wrote:

Hi,

 

Find answers inline.

And for convenience, a link to the fix: https://github.com/dkalowsk/broked_zephyr/pull/1


Thank you for this PR.  More importantly, thank you for fixing the documentation in the follow up PR and pointing out that this is a breaking change for others.

One additional note that should be added here, when using the files as corrected to build, they fail to find the linker.ld file found in the soc_a in the example.

The fix is to change the arm/product/CMakeLists.txt file like so:

- add_subdirectory(${SOC_SERIES})
+ add_subdirectory(${CONFIG_SOC_SERIES})

This seems to allow everything to work correctly in the compile time frame.  You may want to include that detail as well if it is correct.  Note the demo repo needs to be cleaned up to compile anything at all, don't trust it.  This seems odd because I believed that Zephyr dropped the CONFIG_ prefix from everything internally before using it, yet in this case the variable has data only when prefixed.
 

Ok, a little bit of history.

Originally, all ROOTs where a single root only, including BOARD_ROOT.

Now, this for sure has its limitation, as people would like to be able to specify more than one root in order to support both in- and out-of-tree BOARDS, SOC, DTS, and so on.

So BOARD_ROOT was the first to be cleaned up.

https://github.com/zephyrproject-rtos/zephyr/pull/10267

 

so there has been request for other ROOTs to be extended to support multiple roots.

https://github.com/zephyrproject-rtos/zephyr/issues/25215

 

There are also several users with out-of-tree SoCs, who are using both Zephyr SoCs and out-of-tree SoCs, and everyone must make there own way of ensuring that their SOC_ROOT gets set correctly.

I have seen this as a common approach:

if(BOARD STREQUAL my_custom_soc_board)
  set(BOARD_ROOT some/out/of/tree/soc/path)
endif()


Thank you for the history.  From my island, I don't see this as a correct usage/behavior, but I am clearly in the minority. 
 
 

Let me know if there are still issues with the linker script location.


See note above.
 

--
"Do you expect me to talk?"
"No Mr. Bond, I expect you to die."


API meeting: agenda

Carles Cufi
 

921 - 940 of 8183