Hi all, I have created an RFC following our new procedure for proposing changes to stable APIs regarding our proposed changes to the PWM

Reminder: Zephyr Project: Dev Meeting When: Thursday, 12 December 2019, 8:00am to 9:00am, (GMT-08:00) America/Los Angeles Where:https://zoom.us/j/993312203 An RSVP is requested. Click here to

Hi Vinayak Sorry , please ignore previous message. In BT 4.2 command , we just reach -85dbm . In BT 5.0 (1M) command , we can reach -88dbm . How can we reach -93dbm forsensitivity? [BT

Vinayak Thanks for your response. From your suggestion , we can improve sensitivity from -85dbm to -88dbm. Can we improve it to -92dbm? Thanks Tommy

Hello Michael, Thanks for your prompt reply. I just open this new issue:https://github.com/zephyrproject-rtos/zephyr/issues/21328 However, I am not able to assign it to you. Really thanks

Hi, We actually encountered the same issue, not with this driver but with a different modem based upon this driver, from what I remember (it has been a long time since I last investigated) it seemed

Hello Guillaume, On 12/11/19 11:19 AM, Guillaume Paquet wrote: There could certainly be a bug in the socket offloading layer for UBLOX Sara R4 (I'm the maintainer for

Hello Zephyr Community, I found where something is wrong. Indeed in net_context_get function, I saw that I reached CONFIG_NET_MAX_CONTEXTS (equal to 10 in my prj.conf). For your information, I use

And just to add some precision, I work on zephyr 1.14.1. Rgds Guillaume De : devel@... <devel@...>De la part de Guillaume Paquet via Lists.Zephyrproject.Org Envoyé : mercredi 11 décembre

Hello Zephyr community, I contact you because I have an issue when I run mqtt_publisher example https://docs.zephyrproject.org/1.13.0/samples/net/mqtt_publisher/README.html I have the

See https://github.com/zephyrproject-rtos/zephyr/pull/13672#issuecomment-550203475 ________________________________________ Sent: Tuesday, December 10, 2019 5:58 PM To: Bøe, Sebastian Cc: Bolivar,

Hi, Is there some record of the rationale behind this? (eg PR #). I'm wondering that if its rejected from mainline zephyr for reasons like 'out of scope' etc then maybe there is some existing

Reminder: Zephyr Project: APIs When: Tuesday, 10 December 2019, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles Where:https://zoom.us/j/177647878 An RSVP is requested. Click here to

The multi-image approach in NCS will not make it's way into mainline Zephyr because it was not accepted upstream unfortunately. ________________________________________ Sent: Tuesday, December 10,

Hi Venkatesh, hciconfig uses a legacy ioctl kernel interface which is only able to retrieve the public address of a controller. nRF controllers do not come with any public address by default, which

Hi Marti, Sebastian, list Thanks for the ideas, my replies are inline below. This led me to find the "multiple images" documentation for the NCS Zephyr

Hi all, This week we will focus on API Changes and GPIO: - Changing a stable API: - https://github.com/zephyrproject-rtos/zephyr/pull/21013 - GPIO: Update on progress - Look at the PRs with

Hi, We are willing to do the LE USB controller with the nrf52840 dongle By looking into this case https://devzone.nordicsemi.com/f/nordic-q-a/46036/mac-address-ranges. I came to know that there will

Hi Marc, We faced similar problems when we had to make an IVI system that uses bare metal + FreeRTOS + Linux in one SoC and requires a consistent build for all of them. In the end we created our own

Hi Mayank, I am surprised to say this doesn't appear to be covered in the MCUboot documentation. David, did I miss it somewhere? Mayank: you need at least three pins connecting the i.MX and nRF