What target are you trying to compile for? From the stack overflow thread I find Target: x86_64-pc-linux-gnu Then some references to the Nordic HAL. So I’m just going to assume you are trying to

Hello, We are currently running zephyr on M7 and linux on A72. The base M7 support has been upstreamed

Hi, I don't know if this is the proper place to ask technical question about zephyr but I have tried stackoverflow and started github issue with no help. I am new to zephyr so I followed the getting

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

NOTE: The cal invite has gotten messed up and might show the meeting starting a hour earlier than normal. This is NOT correct, we are working on trying to correct the issue. The meeting time is the

Hi! This is my first message to the Zephyr forum. Well, I started to work with zephyr a few days ago. I followed the steps from the Getting Started Guide and I'd like to perform the debugging of the

On Wed, Jan 29, 2020 at 7:08 AM devel@... Calendar <devel@...> wrote: Zephyr Project: Dev Meeting When: Thursday, 2 May 2019 8:00am to 9:00am (UTC-07:00) America/Los Angeles Repeats: Weekly on

Zephyr Project: Dev Meeting When: Thursday, 2 May 2019 8:00am to 9:00am (UTC-07:00) America/Los Angeles Repeats: Weekly on Thursday Where: https://zoom.us/j/993312203 Organizer:

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

+ Andrew, Stephanos Hi Phil, Thanks for reporting this. I need to do a more careful looking into it, but it is likely that you have spotted a bug in the Cortex-M implementation. The

Hi all, I cannot attend today so Peter Bigot will kindly chair the meeting instead. The discussion will be centered exclusively around the completion of the GPIO transition into its new API. -

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