Hi all, We are very close to finalizing the port of users to the new GPIO API. There are only 4 Pull Requests that need to be reviewed, reworked and merged in order to complete the process. If you

I'm getting intermittent run-time failures such as: syscall z_hdlr_k_uptime_get failed check: Memory region 0x0002ff70 (size 8) write access denied ***** Hardware exception *****

Hello, I've cut a new west pre-release today (0.6.99.dev5) which is feature complete for manifest imports. The main new feature since 0.6.99.dev4 is you can now use whitelists and blacklists to

Try this instead, this is what I do every day, I never use west as it doesn’t properly support emulators. For x86-64 the host GDB works great: . zephyr-env.sh cd samples/hello_world mkdir

Thank you！ It seems work seeing the source code, but still has problem on connection: (gdb) target remote localhost:1234 Remote debugging using localhost:1234 warning: Selected architecture

Hi all, Peter Bigot is currently working on rebasing the topic-gpio branch against master. The highest risk right now is the current set of users without a PR, since existing PRs with requested

Hi there, You are right, I made a mistake. Here’s the updated instructions that work for me: $ cd ~/zephyrproject/zephyr $ source zephyr-env.sh $ west build -b qemu_x86_64

Hello, Skip the 'CONFIG_' prefix when searching for symbols in menuconfig. 'CONFIG_' is just added on output. Can also search for e.g. "thread name" btw. The search function isn't case-sensitive, and

See blow picture, i try to enable the flag "CONFIG_THREAD_NAME" because it was disabled by default, but still cant see the configuration items in menuconfig, can anyone tell me

Thank you! But it seems cant load the symbol, so how to compile the debug elf files? BTW: there are two elf files exist in build dir, zephyr.elf and zepyhr-qemu.elf, what is the difference? Thread 1

[resending this email with the mailing list included to increase distribution] Hi all, This is the current status of GPIO user porting as of today (24th January): Remaining users without a

$ cd ~/zephyrproject/zephyr $ source zephyr-env.sh $ west build-b qemu_x86_64 samples/hello_world/ $ cd build/ $ ninja debugserver and then in another terminal $ gdb (gdb) target remote

Hi, I’d like to remind everyone of the current release schedule for the next Zephyr release, i.e. version 2.2: - The feature merge window is open for roughly two more weeks, closing on February

Thanks Can it be debuged by GDB? how to with west? 曹子龙 珠海全志科技股份有限公司

In version 1.14.1, there appears to be a race condition when updating an indication value. It results in a BUS FAULT, which occurs because a pointer becomes null. Here are the Zephyr ATT print

Hi, Latest version of the SDK can be found here: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.11.0 Please download and try things out and report any issues. General: • Replaced

This is a bug. I’ll spend some time on this today and get a GH issue opened. Andrew

The qemu_x86_64 target is configured to use two cores and SMP by default. Regards, Andrew

I have a work Q that will run in user state and attempting to send work to it. This results in intermittent failures. The issue I see in my current test is that I have taken an interrupt while

Now SMP only supported on xtensa, arc and x86 arch, but it seems more diffculte to run on xtensa and arc becasue of no boards. so anybody can tell me how to launch a smp run environment on x86 arch?