The problem has been addressed and the release candidate is now live. David Leach

There was a problem with how I attempted to create this release. In the process of fixing it and will send an update when ready. Sorry for any inconvenience. David Leach

Hi Zephyr developers, Zephyr 2.1.0-rc2 release candidate has been tagged. Current issue status: Priority Count Has PR High 0 - Medium 30 11 To get to an RC3 tag and eventual

Hi Johann, Could you email me a zephyr.hex of a USB app that enumerates? With it I can eliminate my nrf52 boards as the problem. Thanks, Steve

Hi Carles, This is the first time I've tried the nrf usb so I have no "working version" to compare. West version: v0.6.3 zephyr-sdk-0.10.3 The desc_section test was build with: west build -b

Can not confirm, woks fine on the latest master and on 77006e896. Johann "Cufi, Carles" <carles.cufi@...> wrote:

Hi Steve, Is this a regression? Have you tested this with an earlier Zephyr version/revision that worked? We use this board routinely to test the USB stack and haven't run into this problem. Can you

All the USB samples and tests fail to enumerate. git HEAD 77006e896 Output from the desc_sections test is below: Nov 27 09:11:57 nm-ws kernel: [520538.130145] usb 7-2: USB disconnect, device number

Reminder: Zephyr Project: APIs When: Tuesday, 26 November 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

Hi all, This week we will look at: - PWM, USB and clock_control APIs in the context of stable APIs - PR: https://github.com/zephyrproject-rtos/zephyr/pull/20657 - PR:

Finally... problem solved. I found that stack pointer was getting wrong vaule after context switch. Then I noticed that link register during pendsv interrupt indicates floating point exception. After

I’ve canceled the Nov 28th Dev Review Meeting due to holiday in the US. - k

Cancelled: Zephyr Project: Dev Meeting This event has been cancelled. When: Thursday, 28 November 2019 8:00am to 9:00am (UTC-08:00) America/Los

Hi all, As you might know there is a new GPIO API under development in the topic-gpio branch. All drivers should now be ported but the actual users of the GPIO API, which are spread all over the

I have found interesting thing. _oops event that I'm facing when running from external flash is caused by stack sentinel checking so in fact I'm getting a stack corruption - shell thread is

Hi zephyr, In case2, we also have tried -40dBm(2Mbps) and -60dBm(2Mbps) , andreceive 0 bytes. Thanks Tommy

Hi zephyr, [case 1] RF equipment send some bytes to DUT with -50dBm 1Mbps , and DUT can receive 0x2E81 bytes [case 2] RF equipment send some bytes to DUT with -50dBm 2Mbps , but DUT

Hi Tommy, To test 2M Phy please use LE Receiver Test Command [v2] with OCF 0x0033 instead of the v1 command you are using. Regards, Vinayak

I'm quite sure that content of the flash is correct. I use openocd (pending commit with stmqspi support) for flash programming and verify is ok. Moreover simple code with blinking led or even Zephyr

In the current implementation, BLE HCI_EVENT is processed on a dedicated RX_THREAD and called back in the same context. I want to handle HCI_EVENT (eg advvertise_report) directly in my thread. Is