From edb36b5838633ea7fdc006a5e4055781a36c7531 Mon Sep 17 00:00:00 2001
From: Robert U <978080+urob@users.noreply.github.com>
Date: Thu, 18 Dec 2025 00:46:55 -0500
Subject: [PATCH] docs: Update native posix instructions for zephyr 4.1 (#3151)

---
 docs/docs/development/local-toolchain/posix-board.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/docs/docs/development/local-toolchain/posix-board.md b/docs/docs/development/local-toolchain/posix-board.md
index 5a809c02c..37a37076b 100644
--- a/docs/docs/development/local-toolchain/posix-board.md
+++ b/docs/docs/development/local-toolchain/posix-board.md
@@ -20,11 +20,10 @@ apt install -y gcc-multilib
 
 ## Building
 
-To do this, you can build ZMK targeting the
-`native_posix_64` board.
+To do this, you can build ZMK targeting the `native_sim` board.
 
 ```sh
-west build --pristine --board native_posix_64 -- -DZMK_CONFIG=tests/none/normal/
+west build --pristine --board native_sim/native/64 -- -DZMK_CONFIG=tests/none/normal/
 ```
 
 Once built, you can run the firmware locally:
@@ -35,4 +34,4 @@ Once built, you can run the firmware locally:
 
 ## Virtual Key Events
 
-The virtual key presses are hardcoded in `boards/native_posix_64.overlay` file, should you want to change the sequence to test various actions like Mod-Tap, etc.
+The virtual key presses are hardcoded in `boards/extensions/native_sim/native_sim_64.overlay` file, should you want to change the sequence to test various actions like Mod-Tap, etc.