|
API meeting: agenda
Hi all,
Tomorrow we will discuss an RFC that is ready to be merged, two items that were raised in last week's TSC and we will check on progress with the GPIO porting.
- RFC (ready to merge): on-off
Hi all,
Tomorrow we will discuss an RFC that is ready to be merged, two items that were raised in last week's TSC and we will check on progress with the GPIO porting.
- RFC (ready to merge): on-off
|
By
Carles Cufi
·
#1859
·
|
|
Re: Signaling/Messaging Userspace from Kernel
I see some examples using callback functions, but wonder if that is a good practice: it is generally a security risk to run a function provided by a userspace application in the supervisor mode.
I see some examples using callback functions, but wonder if that is a good practice: it is generally a security risk to run a function provided by a userspace application in the supervisor mode.
|
By
Boie, Andrew P
·
#1858
·
|
|
Signaling/Messaging Userspace from Kernel
Hi,
Could someone shed some light on ways in Zephyr for Kernel to signal, or send a message to, threads running in the userspace?
I see some examples using callback functions, but wonder if that is a
Hi,
Could someone shed some light on ways in Zephyr for Kernel to signal, or send a message to, threads running in the userspace?
I see some examples using callback functions, but wonder if that is a
|
By
Justin Huang
·
#1857
·
|
|
Re: Removing an item from the Device tree
Excellent solution. Thank you.
Lawrence King
Principal Developer
+1(416)627-7302
Excellent solution. Thank you.
Lawrence King
Principal Developer
+1(416)627-7302
|
By
Lawrence King
·
#1856
·
|
|
Re: Removing an item from the Device tree
You can use /delete-property/, something like:
&uart0 {
/delete-property/ rts-pin;
/delete-property/ cts-pin;
};
In your overlay should work.
- k
You can use /delete-property/, something like:
&uart0 {
/delete-property/ rts-pin;
/delete-property/ cts-pin;
};
In your overlay should work.
- k
|
By
Kumar Gala
·
#1855
·
|
|
Removing an item from the Device tree
I have a little problem with the device tree
In zephyrproject/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk.dts the uart is defined as:
&uart0 {
compatible = "nordic,nrf-uart";
I have a little problem with the device tree
In zephyrproject/zephyr/boards/arm/nrf52840_mdk/nrf52840_mdk.dts the uart is defined as:
&uart0 {
compatible = "nordic,nrf-uart";
|
By
Lawrence King
·
#1854
·
|
|
Re: NVS on flash with erase page size 64k or larger
#nvs
NVS on flash with erase page size 64k or larger #nvs
Marco
Jan 2 #1824
Hi there
> In my application I try to use NVS on an external SPI flash (M25P16) which has an erase page size of 64k.
>
NVS on flash with erase page size 64k or larger #nvs
Marco
Jan 2 #1824
Hi there
> In my application I try to use NVS on an external SPI flash (M25P16) which has an erase page size of 64k.
>
|
By
Puzdrowski, Andrzej <Andrzej.Puzdrowski@...>
·
#1853
·
|
|
Re: Feedback requested on west manifest imports
Just had a read through your documentation; it looks nice. Have not
tested the code, but judging from the documentation, it looks useful.
Thank you :-)
~Jørn
Just had a read through your documentation; it looks nice. Have not
tested the code, but judging from the documentation, it looks useful.
Thank you :-)
~Jørn
|
By
Jørn Villesen Christensen <jvc@...>
·
#1852
·
|
|
DTS/Binding Issue migrating from 2.0.0 to 2.1.0
#nrf52832
Hello Zephyr Users,
I have inherited a Zephyr project using nRF52832 from another developer and am having an issue migrating from 2.0.0 to 2.1.0. Its probably something simple but I'm fairly new to
Hello Zephyr Users,
I have inherited a Zephyr project using nRF52832 from another developer and am having an issue migrating from 2.0.0 to 2.1.0. Its probably something simple but I'm fairly new to
|
By
matt@...
·
#1851
·
|
|
Feedback requested on west manifest imports
Hello Zephyr users and developers,
We've just uploaded a pre-release version of west to PyPI with a new
feature: manifest imports. We would like your feedback!
For a short README you can follow to
Hello Zephyr users and developers,
We've just uploaded a pre-release version of west to PyPI with a new
feature: manifest imports. We would like your feedback!
For a short README you can follow to
|
By
Bolivar, Marti
·
#1850
·
|
|
API meeting: Agenda
Hi all,
This week we will focus on a new RFC and GPIO.
- RFC: New counter_get_value() API call
- https://github.com/zephyrproject-rtos/zephyr/issues/21846
- GPIO: Update on progress
- Proposal
Hi all,
This week we will focus on a new RFC and GPIO.
- RFC: New counter_get_value() API call
- https://github.com/zephyrproject-rtos/zephyr/issues/21846
- GPIO: Update on progress
- Proposal
|
By
Carles Cufi
·
#1849
·
|
|
Re: NXP RT1064 board and JLink Debugging
For what it's worth 8 months later, I was able to use PyOCD and the the built-in debugger on RT1064-EVK board to flash the Zephyr blinky program using MCUXpresso's flash programmer. Thus avoiding (for
For what it's worth 8 months later, I was able to use PyOCD and the the built-in debugger on RT1064-EVK board to flash the Zephyr blinky program using MCUXpresso's flash programmer. Thus avoiding (for
|
By
langrind@...
·
#1848
·
|
|
Upgrade pyocd requested version to 0.24.0
Hi Zephyr users,
In order to benefit from a wider range of user options [1], I'm proposing in PR 21791 to upgrade requirement for pyocd to version 0.24.0.
Change should not have impact for most users,
Hi Zephyr users,
In order to benefit from a wider range of user options [1], I'm proposing in PR 21791 to upgrade requirement for pyocd to version 0.24.0.
Change should not have impact for most users,
|
By
Erwan Gouriou
·
#1847
·
|
|
Re: DHCPV4 and CONFIG_NET_SOCKETS_SOCKOPT_TLS
Hi,
the DHCPv4 code does not really timeout, there is exponential backoff so the system will try to get the IP address as long as needed.
For the socket TLS error, you need to enable also mbedTLS as
Hi,
the DHCPv4 code does not really timeout, there is exponential backoff so the system will try to get the IP address as long as needed.
For the socket TLS error, you need to enable also mbedTLS as
|
By
Jukka Rissanen
·
#1846
·
|
|
Re: I2C on nRF5340 Issues
#i2c
#driver
#nrf5340
After further testing, I found that if I step through each instruction with the debugger the individual messages send correctly, but not if I let the program run regularly. In neither case does the
After further testing, I found that if I step through each instruction with the debugger the individual messages send correctly, but not if I let the program run regularly. In neither case does the
|
By
Marciano
·
#1845
·
|
|
I2C on nRF5340 Issues
#i2c
#driver
#nrf5340
I am attempting to write a basic I2C program using Zephyr, but I am currently unable to sent a single byte over I2C. The program hangs after the first clock falling & rising edge.
I'm using external
I am attempting to write a basic I2C program using Zephyr, but I am currently unable to sent a single byte over I2C. The program hangs after the first clock falling & rising edge.
I'm using external
|
By
Marciano
·
#1844
·
|
|
DHCPV4 and CONFIG_NET_SOCKETS_SOCKOPT_TLS
Hi,
using zephyr-v2.1.0
I have build the mqtt_publisher sample application for the stm32f746g_disco and it works fine.
I have build the dhcpv4_client sample application for the stm32f746g_disco and it
Hi,
using zephyr-v2.1.0
I have build the mqtt_publisher sample application for the stm32f746g_disco and it works fine.
I have build the dhcpv4_client sample application for the stm32f746g_disco and it
|
By
Denv E
·
#1843
·
|
|
API meeting: agenda
Hi all,
This week we will focus on RFCs and GPIO:
- RFC: API Change: PWM: add support for inverted PWM signals. We will try to close on this today.
-
Hi all,
This week we will focus on RFCs and GPIO:
- RFC: API Change: PWM: add support for inverted PWM signals. We will try to close on this today.
-
|
By
Carles Cufi
·
#1842
·
|
|
Re: NRF52 and timing - actual state and what functions to use?
#nrf52-pca10040
Hi Martin,
Nrf52832 has 3 RTC's. RTC0 is used for Bluetooth, RTC1 for system clock and RTC2 is usually available for application. You can use RTC2 with counter driver API (see counter.h). Then you
Hi Martin,
Nrf52832 has 3 RTC's. RTC0 is used for Bluetooth, RTC1 for system clock and RTC2 is usually available for application. You can use RTC2 with counter driver API (see counter.h). Then you
|
By
Chruściński, Krzysztof
·
#1841
·
|
|
Re: NRF 802.15.4 driver without networking?
Hi Axel,
I've found the following configuration to be the minimal needed to use the Zephyr ieee802154 radio driver w/o the networking stack:
CONFIG_IEEE802154=y
CONFIG_NETWORKING=y
Hi Axel,
I've found the following configuration to be the minimal needed to use the Zephyr ieee802154 radio driver w/o the networking stack:
CONFIG_IEEE802154=y
CONFIG_NETWORKING=y
|
By
Lubos, Robert
·
#1840
·
|