Hi, I'm new to Zephyr, just starting to investigate it. I suspect I'm either missing something or doing something silly. When I run the following command in the

"Cufi, Carles" <Carles.Cufi@...> wrote: Good to know, thanks! -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro:

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

Hi Paul, This one seems to have been renamed "picolibc": https://salsa.debian.org/electronics-team/toolchains/picolibc Carles

Hello, Kumar Gala <kumar.gala@...> wrote: [] Right, those are useful options to keep in mind and explore. But given that they require more development effort, IMHO they should be treated as

Hi, I've verified basic OT functionality using the echo_client/server samples with the openthread overlays. That's nice, but it's not obvious to me how I proceed after this. A few things that had me

Hi all, This week we will look at: Agenda: - Sensor API: Update on progress - GPIO: Update on https://github.com/zephyrproject-rtos/zephyr/pull/16648 and possibly merging it Additional items in

Indeed, that looks like a bug in the driver when SMP and !TICKLESS are set. Can you file an issue on github? Andy On 8/24/2019 3:23 AM, "曹子龙 wrote:

There are some other options, but they require more development effort. 1. Add support for newlib nano for long long. 2. Add support to crosstool-ng to build multiple newlib variants. And build 2

Dear Sir/Madam, Hope you will be fine and in best of health. I am a beginner and done with the Zephyr BLE Beacon example with NRF52840 Dongle. It is requested if i can be helped to run the Bluetooth

Hello, We have a patch to enable format specifiers %lld, %llu (i.e. dealing with "long long" C types) for Newlib libc in the next Zephyr SDK release:

Hi andrew: i find the place you said laste emai, it seems only xtensa and x84 arch supports the SMP mode, so take xtensa for exmaple. it seems the mechanism you said in the laste email only

It's still not clear to me what you're looking for but maybe this git command will help: git log --decorate --no-walk --oneline $(git tag -l v1.14*) upstream/v1.14-branch 5ad3f4a6930d (tag:

Thanks Anas, I should have been clearer in my question, apologies. It looks like there is a 1.14.1 brewing, I presume that is bug fixes on the 1.14 release. When it is released, I will probably want

v1.14-branch is the branch, all others are tags on the branch. Anas From:<devel@...> on behalf of Manu R <manu@...> Date: Friday, 23 August 2019 at 18:38 To: "devel@..." <devel@...> Subject:

I still cant understand this flow after read the code. take cortex-m arch for exmaple, z_clock_isr, is hooked for NVIC vector table, so each cores would call this following the frequency. so, there

when I do a zephyr (v1.14-branch) $ git checkout v1.14<tab> v1.14-branch v1.14.0 v1.14.0-rc1 v1.14.0-rc2 v1.14.0-rc3 v1.14.1-rc1 Thanks Manu

could you show me where the logic you said locates? i still cant catches it, thank you

This is the responsibility of the timer driver. The ticks announced needs to be globally correct. The existing drivers do this by locking a "last count" state variable and updating it, so

Hi friends: a puzzle in the timer tick interrupt handler in SMP mode. look at below, the SMP mult cores share the same "cur_tick" object to remeber the current time, each cpu would increment