|
Zephyr Toolchain Working Group Meeting – 14 May 2020
*******************************
NOTE: We will be using Microsoft Teams for this meeting instead of zoom. The link is found below.
*******************************
Hi,
Due to lack of
*******************************
NOTE: We will be using Microsoft Teams for this meeting instead of zoom. The link is found below.
*******************************
Hi,
Due to lack of
|
By
Rasmussen, Torsten
·
#7011
·
|
|
Dev-Review Meeting Agenda May 14
Here’s the agenda topics for this week:
* Review PR/issues’s tagged with dev-review:
* Support for buildtesting SoCs w/o boards
https://github.com/zephyrproject-rtos/zephyr/issues/25153
*
Here’s the agenda topics for this week:
* Review PR/issues’s tagged with dev-review:
* Support for buildtesting SoCs w/o boards
https://github.com/zephyrproject-rtos/zephyr/issues/25153
*
|
By
Kumar Gala
·
#7010
·
|
|
Re: Unable to run USB samples on STM32F411E-DISCO
#samples
Thanks for the feedback. I will go ahead and create an issue on github to describe the issue and show what I have tried so far.
Thanks!
Brian
Thanks for the feedback. I will go ahead and create an issue on github to describe the issue and show what I have tried so far.
Thanks!
Brian
|
By
bbradley@...
·
#7009
·
|
|
Re: Unable to run USB samples on STM32F411E-DISCO
#samples
Hi Brian,
Raising an issue would indeed help to provide support.
Don't hesitate to share the work you've already done to ease things.
BR
Erwan
Hi Brian,
Raising an issue would indeed help to provide support.
Don't hesitate to share the work you've already done to ease things.
BR
Erwan
|
By
Erwan Gouriou
·
#7008
·
|
|
Unable to run USB samples on STM32F411E-DISCO
#samples
So I think there are a few things going on here, and have begun to unravel it but I might need some guidance on how to proceed.
I intend to utilize the STM32F411E MCU on an upcoming board, but I
So I think there are a few things going on here, and have begun to unravel it but I might need some guidance on how to proceed.
I intend to utilize the STM32F411E MCU on an upcoming board, but I
|
By
bbradley@...
·
#7007
·
|
|
Zephyr SDK 0.11.x and Python support query
As part of the SDK 0.11.x SDK we moved from python2.7 to python3.6 as the version of python that GDB is linked against, partially due to the deprecation of python2.7.
There have been several issues
As part of the SDK 0.11.x SDK we moved from python2.7 to python3.6 as the version of python that GDB is linked against, partially due to the deprecation of python2.7.
There have been several issues
|
By
Kumar Gala
·
#7006
·
|
|
Upcoming Event: Zephyr Project: APIs - Tue, 05/12/2020 9:00am-10:00am, Please RSVP
#cal-reminder
Reminder: Zephyr Project: APIs
When: Tuesday, 12 May 2020, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles
Where:Microsoft Teams Meeting
An RSVP is requested. Click here to
Reminder: Zephyr Project: APIs
When: Tuesday, 12 May 2020, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles
Where:Microsoft Teams Meeting
An RSVP is requested. Click here to
|
By
devel@lists.zephyrproject.org Calendar <devel@...>
·
#7005
·
|
|
API meeting: agenda
Hi all,
*************************************************
We will be using Teams instead of
Hi all,
*************************************************
We will be using Teams instead of
|
By
Carles Cufi
·
#7004
·
|
|
[Zephyr 2.3] Please set the 2.3.0 milestone on all relevant PRs
Hi all,
I'd like to ask you to set the milestone in all Pull Requests that need to be merged during the stabilization period (be them bugfix and documentation or special cases, in which case they
Hi all,
I'd like to ask you to set the milestone in all Pull Requests that need to be merged during the stabilization period (be them bugfix and documentation or special cases, in which case they
|
By
Carles Cufi
·
#7003
·
|
|
Re: #networking #ppp #gsm_modem #mbedtls
#ppp
#gsm_modem
#mbedtls
#networking
Hi Jukka
And thank you very much for your very quick answer.
I am sorry I haven't repsonded before, but we had a national Holiday in Denmark Friday the 8th.
I will try to answer on your
Hi Jukka
And thank you very much for your very quick answer.
I am sorry I haven't repsonded before, but we had a national Holiday in Denmark Friday the 8th.
I will try to answer on your
|
By
Bo.Kragelund@...
·
#7002
·
|
|
Re: Thread Scheduling question
> I'm not quite sure what you are trying to mitigate, exactly. This is the desired behavior. You WANT your two custom threads to run instead of your main thread, that's why they're higher
> I'm not quite sure what you are trying to mitigate, exactly. This is the desired behavior. You WANT your two custom threads to run instead of your main thread, that's why they're higher
|
By
Peter A. Bigot
·
#7001
·
|
|
Re: Thread Scheduling question
This will help, Andy. Thanks for your inputs!
Regards,
Raj
This will help, Andy. Thanks for your inputs!
Regards,
Raj
|
By
Raj Gundi
·
#7000
·
|
|
Re: Thread Scheduling question
Your understanding is correct. If a higher priority thread is available to run, then a preemptible thread will yield to that thread at every scheduling point.
I'm not quite sure what
Your understanding is correct. If a higher priority thread is available to run, then a preemptible thread will yield to that thread at every scheduling point.
I'm not quite sure what
|
By
Andy Ross
·
#6999
·
|
|
Thread Scheduling question
Hi,
This is a question related to thread scheduling. Imagine you have 2 custom threads in addition to the “main thread”. The custom threads are created static (K_THREAD_DEFINE) and are
Hi,
This is a question related to thread scheduling. Imagine you have 2 custom threads in addition to the “main thread”. The custom threads are created static (K_THREAD_DEFINE) and are
|
By
Raj Gundi
·
#6998
·
|
|
Re: 回复:[Zephyr-devel] How to compile riscv64 program with 0.10.3 sdk "riscv64-zephyr-elf-gcc" toolchain?
Sure, that was why “riscv32-zephyr-elf-“ toolchain was removed in the SDK 0.11.0 release:
https://github.com/zephyrproject-rtos/sdk-ng/commit/5997df8e3dc78184543f05ccbbc425c2d3c2818b
Sure, that was why “riscv32-zephyr-elf-“ toolchain was removed in the SDK 0.11.0 release:
https://github.com/zephyrproject-rtos/sdk-ng/commit/5997df8e3dc78184543f05ccbbc425c2d3c2818b
|
By
Stephanos Ioannidis
·
#6997
·
|
|
回复:[Zephyr-devel] How to compile riscv64 program with 0.10.3 sdk "riscv64-zephyr-elf-gcc" toolchain?
Thank you!
if so,it seems riscv32 toolchain also can take this flag and generate the 64 bit program.
riscv32-zephyr-elf-gcc -march=rv64i -mabi=lp64 -c main.c -o
Thank you!
if so,it seems riscv32 toolchain also can take this flag and generate the 64 bit program.
riscv32-zephyr-elf-gcc -march=rv64i -mabi=lp64 -c main.c -o
|
By
"曹子龙
·
#6996
·
|
|
Re: How to compile riscv64 program with 0.10.3 sdk "riscv64-zephyr-elf-gcc" toolchain?
Hi,
You need to specify the correct ABI type through `-mabi` alongside the `-march` flag.
Try `-march=rv64i -mabi=lp64` for instance.
Regards,
Stephanos
Hi,
You need to specify the correct ABI type through `-mabi` alongside the `-march` flag.
Try `-march=rv64i -mabi=lp64` for instance.
Regards,
Stephanos
|
By
Stephanos Ioannidis
·
#6995
·
|
|
Zephyr 2.3.0-rc1 tagged
Hi all,
The first release candidate for Zephyr 2.3.0 has now been tagged (v2.3.0-rc1).
The merge window for features and enhancements is now closed for this release, and it will remain closed until
Hi all,
The first release candidate for Zephyr 2.3.0 has now been tagged (v2.3.0-rc1).
The merge window for features and enhancements is now closed for this release, and it will remain closed until
|
By
Carles Cufi
·
#6994
·
|
|
How to compile riscv64 program with 0.10.3 sdk "riscv64-zephyr-elf-gcc" toolchain?
I try to compile program with "zephyr-sdk-0.10.3/riscv64-zephyr-elf/bin/riscv64-zephyr-elf-gcc " to compile my program,
but it seems the result still be 32 bit
I try to compile program with "zephyr-sdk-0.10.3/riscv64-zephyr-elf/bin/riscv64-zephyr-elf-gcc " to compile my program,
but it seems the result still be 32 bit
|
By
"曹子龙
·
#6993
·
|
|
API Change: video
Hi all,
A recent stable API has been modified to adapt it to the recent kernel timeout change.
video_dequeue() now takes a k_timeout_t instead of a u32_t for the type of the timeout parameter.
Note
Hi all,
A recent stable API has been modified to adapt it to the recent kernel timeout change.
video_dequeue() now takes a k_timeout_t instead of a u32_t for the type of the timeout parameter.
Note
|
By
Carles Cufi
·
#6992
·
|