1. devel@lists.zephyrproject.org
  2. Messages
   Date   
API meeting cancelled today

Carles Cufi
 

Hi all,

Due to a conflict I have had to cancel the API meeting today.
Next week we will have the meeting as usual.

Regards,

Carles
Cancelled Event: Zephyr Project: APIs - Tuesday, 17 November 2020 #cal-cancelled

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

Cancelled: Zephyr Project: APIs

This event has been cancelled.

When:
Tuesday, 17 November 2020
5:00pm to 6:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

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
 
 
________________________________________________________________________________

Calendar
Calendar

Zephyr: Toolchain Working Group - Mon, 11/16/2020 #cal-notice

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

Zephyr: Toolchain Working Group

When:
Monday, 16 November 2020
4:00pm to 5: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 - Mon, 11/16/2020 4:00pm-5:00pm, Please RSVP #cal-reminder

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

Reminder: Zephyr: Toolchain Working Group

When: Monday, 16 November 2020, 4:00pm to 5: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 – 16 November 2020

Rasmussen, Torsten
 

Call for today’s Toolchain WG.

 

Agenda

 

  • Updates:
    • Thomas: IAR: Updates ?
    • Zephyr SDK.
      • LLVM support
        • compiler-rt.
    • LLVM toolchain – arm updates
    • Milestones for 2.5, news.

 

 

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

 

           

 
Re: RISC-V maintainers and collaborators

Katsuhiro Suzuki
 

Hello Maureen-san,

Sorry for late, I created PR 30033 that just adds
myself to collaborators.

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

Best Regards,
Katsuhiro Suzuki

On 2020/11/12 5:28, Maureen Helm (OSS) wrote:
Hi Suzuki-san,
Yes, please create a pull request. MAINTAINERS.yml is at the top of the main zephyr tree.
Maureen
-----Original Message-----
From: devel@... <devel@...> On Behalf Of Katsuhiro Suzuki via lists.zephyrproject.org
Sent: Wednesday, November 11, 2020 9:41 AM
To: Maureen Helm (OSS) <maureen.helm@...>; devel@...
Subject: Re: [Zephyr-devel] RISC-V maintainers and collaborators
Hello Maureen,
I want to join as collaborators.
Would you tell me how to add? By pull request?
Best Regards,
Katsuhiro Suzuki
On 2020/11/10 5:52, Maureen Helm wrote:
Hi everyone,
We are looking for collaborators and maintainers to help maintain the RISC-V architecture in Zephyr, and have several major RISC-V pull requests (SMP and memory protection) in acute need of code review. If you are interested in taking on one of these important roles and helping to advance RISC-V support in Zephyr, I encourage you to review the TSC Project Roles [1], start reviewing RISC-V pull requests [2], and consider adding yourself as a collaborator in MAINTAINERS.yml. Active collaborators are encouraged to become maintainers with TSC approval.

[1] https://docs.zephyrproject.org/latest/contribute/project_roles.html
[2] https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+is%3Aopen+label%3A%22area%3A+RISCv32%2F64%22

Maureen
new facility for formatted output

Peter A. Bigot
 

With the merge of https://github.com/zephyrproject-rtos/zephyr/pull/29876 Zephyr printk, shell_printf, minimal libc sprintf, and some other in-tree facilities use a common formatting functionality that supports almost everything in C18 *printf, with Kconfig options to reduce the code size impact based on controlling feature availability.

That PR added a C99 stdio value formatter capability named cbprintf() (plus related variants) where generated text is emitted through a callback. This allows generation of arbitrarily long output without a buffer, functionality that is core to printk, logging, and other system and application needs.

The formater supports most C99 specifications, excluding:
  • %L[aefg] long double conversion
  • wide character output
The new solution is derived from z_prf(), which had the most complete functionality available. Format parsing has been reimplemented, while floating point conversion has been retained and enhanced.

Kconfig options allow disabling features like floating-point conversion if they are not necessary.

Benefits include:No more inconsistencies between printk, logging, and shell formatting capabilities.
  • Reduced inconsistencies due to toolchain libc capabilities.
  • Simplified (toolchain-independent) formatting feature selection via Kconfig.
  • Core infrastructure can avoid duplication with libc printf by using cbprintf variants.
  • Potentially a path to resolving #18351 and related issues, as the infrastructure can tell a caller the total size of arguments to the conversion string.
  • Fixed bugs with several specifications.
Costs include:
  • Applications that used only printk with no extra features consume more code space than the previous implementation.
More information is available at: https://docs.zephyrproject.org/latest/reference/misc/formatted_output.html

You may see either an increase or a decrease in code size depending on what your application uses.  Some code size can be reduced by switching in-tree use of snprintf to snprintfcb to avoid pulling in libc formatters.

I expect there'll be a burn-in period while we identify Kconfig settings that have to change to maintain compatibility.  Please mention me (@pabigot) in any issues or slack questions that you have about this.

Peter

Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 12 November 2020 #cal-cancelled

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

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, 12 November 2020
4:00pm to 5:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

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
 
 
________________________________________________________________________________

Calendar
Calendar

Re: RISC-V maintainers and collaborators

Maureen Helm
 

Hi Suzuki-san,
Yes, please create a pull request. MAINTAINERS.yml is at the top of the main zephyr tree.

Maureen

-----Original Message-----
From: devel@... <devel@...> On Behalf Of Katsuhiro Suzuki via lists.zephyrproject.org
Sent: Wednesday, November 11, 2020 9:41 AM
To: Maureen Helm (OSS) <maureen.helm@...>; devel@...
Subject: Re: [Zephyr-devel] RISC-V maintainers and collaborators

Hello Maureen,

I want to join as collaborators.
Would you tell me how to add? By pull request?

Best Regards,
Katsuhiro Suzuki

On 2020/11/10 5:52, Maureen Helm wrote:
Hi everyone,
We are looking for collaborators and maintainers to help maintain the RISC-V architecture in Zephyr, and have several major RISC-V pull requests (SMP and memory protection) in acute need of code review. If you are interested in taking on one of these important roles and helping to advance RISC-V support in Zephyr, I encourage you to review the TSC Project Roles [1], start reviewing RISC-V pull requests [2], and consider adding yourself as a collaborator in MAINTAINERS.yml. Active collaborators are encouraged to become maintainers with TSC approval.

[1] https://docs.zephyrproject.org/latest/contribute/project_roles.html
[2] https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+is%3Aopen+label%3A%22area%3A+RISCv32%2F64%22

Maureen
Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 26 November 2020 #cal-cancelled

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

Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, 26 November 2020
4:00pm to 5:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

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
 
 
________________________________________________________________________________

Calendar
Calendar

Re: RISC-V maintainers and collaborators

Katsuhiro Suzuki
 

Hello Maureen,

I want to join as collaborators.
Would you tell me how to add? By pull request?

Best Regards,
Katsuhiro Suzuki

On 2020/11/10 5:52, Maureen Helm wrote:
Hi everyone,
We are looking for collaborators and maintainers to help maintain the RISC-V architecture in Zephyr, and have several major RISC-V pull requests (SMP and memory protection) in acute need of code review. If you are interested in taking on one of these important roles and helping to advance RISC-V support in Zephyr, I encourage you to review the TSC Project Roles [1], start reviewing RISC-V pull requests [2], and consider adding yourself as a collaborator in MAINTAINERS.yml. Active collaborators are encouraged to become maintainers with TSC approval.
[1] https://docs.zephyrproject.org/latest/contribute/project_roles.html
[2] https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+is%3Aopen+label%3A%22area%3A+RISCv32%2F64%22
Maureen
Re: #LWM2M #Leshan #QEMU #Networking #lwm2m #leshan #qemu #networking

Khaled Elsayed <khaled.elsayed@...>
 

Seems like a problem in the local host 192.168.0.20. Could you route any traffic from another local machine (not Qemu) via that host, i.e. set 192.168.0.20 as their G/W? Also are you able to ping from Qemu to 192.168.0.1 (I assume not, but just trying to localize where the problem is). 

Also make sure you issue these commands as root on  192.168.0.20. 

On Tue, Nov 10, 2020 at 7:13 PM Thomas LE ROUX <thomas.leroux@...> wrote:

Hi everybody !

I'm trying to build a projet using Zephyr & LWM2M (& Leshan).

For now, I’m prototyping on QEMU.

TL;DR before explaining more precisely my issue : There must be a way to connect a QEMU instance to a remote server, but I’m stuck trying to do this.


—

I have made my small application to test things out, and except Firmware Update (my previous mail), everything is working fine on a local scale.

Running my client & Leshan server on the server along with the loop-socat and loop-slip-tap scripts given on /tools/net-tools/ causes no issue.

(Procedure followed here : https://docs.zephyrproject.org/latest/guides/networking/qemu_setup.html).

I’d like to connect my client to a Leshan server running on an AWS EC2 Instance.

I have made a small schematic. The goal would be to connect my Client (aka QEMU) to the Leshan server running on the Instance.


image.png

From the QEMU instance, I am able to run small commands. One of them is « net ping xxx ». From my client, I am able to ping the local Leshan and my computer. The ping request direct to other peripherals (other computers, my Internet modem, remote Leshan …) all end up in a timeout.

From my computer, I am able to ping basically anyone on the network.

I have followed the tutorial (given here : https://docs.zephyrproject.org/latest/guides/networking/qemu_setup.html#setting-up-zephyr-and-nat-masquerading-on-host-to-access-internet), and added to my prj.conf : CONFIG_NET_CONFIG_MY_IPV4_GW="192.168.0.20".

Running the following commands didn’t raise any error message, so I assume that eveything went right :

  • iptables -t nat -A POSTROUTING -j MASQUERADE -s 192.0.2.1

  • sysctl -w net.ipv4.ip_forward=1

I used Zenmap, a GUI tool for Nmap and here is my network’s map. Center point is my internet modem (choose this for a viewing perspective.) The long blue line going up is the route for reaching my EC2 instance. It confirms that my computer can reach anything, but only my computer can reach 192.0.2.1.

image.png

I used Wireshark on the tap0 interface generated by loop-slip-tap.sh and it seems that the registration’s frame sent to the EC2 instance stays on the tap0 interface and never leaves my computer.

I think the issue might be related to the use of those 2 scripts but I’m not sure and I’m (clearly) not the best in terms of networking.

My problem is pretty much described, if needed, I can send some logs.

Thank you for your help !

Best regards,

Thomas





--

Khaled Elsayed

Technical Fellow


Si-Vision LLC

Square 1142, Al Ezaei Salah Zaki St.,

Sheraton Heliopolis,

Cairo, 11361 EGYPT

Mob. +(20)100 1649292



The information contained in this message is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying or dissemination of this message or the taking of any action in reliance on its contents, or other use is strictly prohibited.  If you received this message in error, please notify us immediately by replying to the message and deleting it from your computer.  Thank you.
Si-Vision, LLC.
#LWM2M #Leshan #QEMU #Networking #lwm2m #leshan #qemu #networking

Thomas LE ROUX
 

Hi everybody !

I'm trying to build a projet using Zephyr & LWM2M (& Leshan).

For now, I’m prototyping on QEMU.

TL;DR before explaining more precisely my issue : There must be a way to connect a QEMU instance to a remote server, but I’m stuck trying to do this.


—

I have made my small application to test things out, and except Firmware Update (my previous mail), everything is working fine on a local scale.

Running my client & Leshan server on the server along with the loop-socat and loop-slip-tap scripts given on /tools/net-tools/ causes no issue.

(Procedure followed here : https://docs.zephyrproject.org/latest/guides/networking/qemu_setup.html).

I’d like to connect my client to a Leshan server running on an AWS EC2 Instance.

I have made a small schematic. The goal would be to connect my Client (aka QEMU) to the Leshan server running on the Instance.


image.png

From the QEMU instance, I am able to run small commands. One of them is « net ping xxx ». From my client, I am able to ping the local Leshan and my computer. The ping request direct to other peripherals (other computers, my Internet modem, remote Leshan …) all end up in a timeout.

From my computer, I am able to ping basically anyone on the network.

I have followed the tutorial (given here : https://docs.zephyrproject.org/latest/guides/networking/qemu_setup.html#setting-up-zephyr-and-nat-masquerading-on-host-to-access-internet), and added to my prj.conf : CONFIG_NET_CONFIG_MY_IPV4_GW="192.168.0.20".

Running the following commands didn’t raise any error message, so I assume that eveything went right :

  • iptables -t nat -A POSTROUTING -j MASQUERADE -s 192.0.2.1

  • sysctl -w net.ipv4.ip_forward=1

I used Zenmap, a GUI tool for Nmap and here is my network’s map. Center point is my internet modem (choose this for a viewing perspective.) The long blue line going up is the route for reaching my EC2 instance. It confirms that my computer can reach anything, but only my computer can reach 192.0.2.1.

image.png

I used Wireshark on the tap0 interface generated by loop-slip-tap.sh and it seems that the registration’s frame sent to the EC2 instance stays on the tap0 interface and never leaves my computer.

I think the issue might be related to the use of those 2 scripts but I’m not sure and I’m (clearly) not the best in terms of networking.

My problem is pretty much described, if needed, I can send some logs.

Thank you for your help !

Best regards,

Thomas



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

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

Reminder: Zephyr Project: APIs

When: Tuesday, 10 November 2020, 5:00pm to 6: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
 
 
________________________________________________________________________________
RISC-V maintainers and collaborators

Maureen Helm
 

Hi everyone,

We are looking for collaborators and maintainers to help maintain the RISC-V architecture in Zephyr, and have several major RISC-V pull requests (SMP and memory protection) in acute need of code review. If you are interested in taking on one of these important roles and helping to advance RISC-V support in Zephyr, I encourage you to review the TSC Project Roles [1], start reviewing RISC-V pull requests [2], and consider adding yourself as a collaborator in MAINTAINERS.yml. Active collaborators are encouraged to become maintainers with TSC approval.

 

[1] https://docs.zephyrproject.org/latest/contribute/project_roles.html

[2] https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+is%3Aopen+label%3A%22area%3A+RISCv32%2F64%22

 

Maureen

 
API meeting: agenda

Carles Cufi
 

Re: Question about the sanitycheck for SMP

Katsuhiro Suzuki
 

Hello Andrew,

Thanks for comments.

On 2020/11/09 16:08, Boie, Andrew P wrote:
- Sometimes success/fault on my RISC-V SMP environment
At first, I think it's bug of my patches, but...
- Also same tests sometimes success/fault on qemu_x86_64
There are known issues with SMP and Zephyr's scheduler:
https://github.com/zephyrproject-rtos/zephyr/issues/28105
Andrew
I understand you are fixing the problem.

Currently we cannot trust sanitycheck results for SMP.
And in last month, you told me there are no active maintainer
in RISC-V area.

So I wonder how to proceed merging SMP support for RISC-V...

Best Regards,
Katsuhiro Suzuki
Re: Question about the sanitycheck for SMP

Boie, Andrew P
 

- Sometimes success/fault on my RISC-V SMP environment
At first, I think it's bug of my patches, but...
- Also same tests sometimes success/fault on qemu_x86_64
There are known issues with SMP and Zephyr's scheduler:

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

Andrew
Question about the sanitycheck for SMP

Katsuhiro Suzuki
 

Hello,

I'm continuing to try and fix bugs of SMP support for RISC-V.
My first target is my patches pass the 'sanitycheck' and 'buildkite'
tests.

I'm facing strange behavior of sanitycheck currently:

- Sometimes success/fault on my RISC-V SMP environment
At first, I think it's bug of my patches, but...
- Also same tests sometimes success/fault on qemu_x86_64

For example this is result of tests/kernel/mem_protect/sys_sem/
(Using SDK-0.11.4)

----------------------------------------
$ cmake -G Ninja -DBOARD=qemu_x86_64 ../tests/kernel/mem_protect/sys_sem/

$ ninja run
[3/4] To exit from QEMU enter: 'CTRL+a, x'[QEMU] CPU: qemu64,+x2apic
qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:EC
X.x2apic [bit 21]
qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]
SeaBIOS (version rel-1.12.1-0-ga5cab58-dirty-20200625_115407-9426dddc0a1f-zephyr
)
Booting from ROM..*** Booting Zephyr OS build zephyr-v2.4.0-1318-g73e8cadbb398 ***
Running test suite test_sys_sem
===================================================================
START - test_basic_sem_test
PASS - test_basic_sem_test
===================================================================
START - test_simple_sem_from_isr
PASS - test_simple_sem_from_isr
===================================================================
START - test_sem_take_timeout_isr
PASS - test_sem_take_timeout_isr
===================================================================
START - test_sem_give_take_from_isr
PASS - test_sem_give_take_from_isr
===================================================================
START - test_simple_sem_from_task
PASS - test_simple_sem_from_task
===================================================================
START - test_sem_take_no_wait
PASS - test_sem_take_no_wait
===================================================================
START - test_sem_take_no_wait_fails
PASS - test_sem_take_no_wait_fails
===================================================================
START - test_sem_take_timeout_fails
PASS - test_sem_take_timeout_fails
===================================================================
START - test_sem_take_timeout

Assertion failed at ZEPHYR_BASE/tests/kernel/mem_protect/sys_sem/src/main.c:277: test_sem_take_timeout: (ret_value == 0 is false)
sys_sem_take failed when its shouldn't have
FAIL - test_sem_take_timeout
===================================================================
START - test_sem_take_timeout_forever
PASS - test_sem_take_timeout_forever
===================================================================
START - test_sem_take_multiple
PASS - test_sem_take_multiple
===================================================================
START - test_sem_give_limit
PASS - test_sem_give_limit
===================================================================
START - test_sem_multiple_threads_wait
PASS - test_sem_multiple_threads_wait
===================================================================
Test suite test_sys_sem failed.
----------------------------------------

Current test set and results are correct? Or is there any bugs or
limitations of current sanitycheck? I'm not sure. If you have any
ideas or reasons, please tell me.

Best Regards,
Katsuhiro Suzuki
Zephyr Project: Dev Meeting - Thu, 11/05/2020 4:00pm-5:00pm, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 5 November 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:

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