Contents

• For all permission issues
• Software Developer Portal News
  • Roaming test report
• NHX-SDK-ODM code repository
• Software module
• NHX SDK software framework
• Framework Process Icon Description
• NHX-PACKAGES-OPEN framework
• pipelines
  • NHX-SDK pipelines
  • NHX-PACKAGES-BIN pipelines
  • NHX-PACKAGES-OPEN pipelines
• Git Repositories
  • Git Usage Examples
    • 1. Clone Main Repository
    • 2. Pull Latest Code
    • 3. View Repository Status
    • 4. Switch Branches
    • 5. View Remote Repository Information
    • 6. Common Problem Resolution
  • Token Expiration: Update and Handling
• Firmware Release

For all permission issues

• For access to developer resources, please contact sales or technical support for approval.
  • README

Software Developer Portal News

Roaming test report

---

NHX-SDK-ODM code repository

Note:

• For access to code repositories, please contact sales or technical support for approval.
  • README

Apply for permission group link	code repository	openwrt	Driver	Kernel	SDK	Supported Models	Remarks
FAE-NHX-QSDK-11.5-ODM	NHX-QSDK -11.5-ODM	15.05	qsdk-11.5	v4.4	Source code for nhxwrt sdk kit excluding vendor-restricted binaries (e.g. the QSDK driver)	NHX4019 NHX5018 NHX6018	LTS Recommended
FAE-NHX-QSDK-12.2-ODM	NHX-QSDK-12.2-ODM	19.07	qsdk-12.2	v5.4	Source code for nhxwrt sdk kit excluding vendor-restricted binaries (e.g. the QSDK driver)	NHX5018 NHX6018 NHX53X2-V01 NHX53X2-V03	LTS
FAE-NHX-QSDK-12.5-ODM	NHX-QSDK-12.5-ODM	23.05	qsdk-12.5	v5.4	Source code for nhxwrt sdk kit excluding vendor-restricted binaries (e.g. the QSDK driver)	NHX5018 NHX6018 NHX53X2	LTS
Requires project permission group	NHX-ATH11K-ODM	21.02	ath11k	v5.4	Open-source wireless drivers (ath11k)	NHX4019 NHX5018 NHX6018

Software module

Note:

• Software module permissions inherit repository access permissions.
  • README

Project Wiki	Git Repository	code delivery	supported models	remarks	Performance pk advantage level
NHX-STAROAM-BIN	NHX-STAROAM	pkg-bin	NHX4019, NHX5018, NHX6018, NHX53X2	Wireless roaming application	A
NHX-API-BIN	NHX-API	pkg-bin	NHX4019, NHX5018, NHX6018, NHX53X2	API Application
NHX-IAC-BIN	NHX-IAC	pkg-bin	NHX4019, NHX5018, NHX6018, NHX53X2	Wireless Controller Application
NHX-MESH-BIN	NHX-MESH	pkg-bin	NHX4019, NHX5018, NHX6018, NHX53X2	Mesh Application	A
NHX-VUE-ODM	NHX-VUE	pkg-src	NHX4019、NHX5018、NHX6018、NHX53X2	vue source code
nhxweb	nhxweb	pkg-bin	NHX4019、NHX5018、NHX6018、NHX53X2	vue binary web file
NHX-PACKAGES-OPEN	NHX-PACKAGES-OPEN	pkg-src	NHX4019、NHX5018、NHX6018、NHX53X2	Open Source Applications
NHX-DL	NHX-DL	—	NHX4019、NHX5018、NHX6018、NHX53X2	Compile dependency cache library
NHX__-SDK	NHX-SDK	src	NHX4019、NHX5018、NHX6018、NHX53X2	Model file; dts file
nhx_longbridge	nhx_longbridge	nhxwifiko	NHX5018、NHX6018、NHX53X2	Long distance transmission NHX-QSDK-12.2-ODM support	A
nhxpcf	nhxpcf	nhxwifiko	NHX4019, NHX5018, NHX6018, NHX53X2	802.11 PCF	A
nhxhcf	nhxhcf	nhxwifiko	NHX4019, NHX5018, NHX6018, NHX53X2	802.11 HCF	A
nhxant	nhxant	nhxwifiko	NHX4019、NHX5018、NHX6018、NHX53X2	Smart antenna
nhxtdma	nhxtdma	nhxwifiko	NHX5018、NHX6018、NHX53X2	TDMA	A

---

NHX SDK software framework

1. master branch: Source code for qsdk sdk kit excluding vendor-restricted binaries (e.g. the QSDK driver)

• master_nhx4019
• master_nhx5018
• master_nhx6018

1. nhxwrt branch: Source code for nhxwrt sdk kit excluding vendor-restricted binaries (e.g. the nhxwifiko driver); Deeply optimized driver; supports nhx applications

• nhxwrt_NHX53X2
• nhxwrt_NHX6018
• nhxwrt_nhx6018 4g
• nhxwrt_nhx6018-64bit
• nhxwrt_nhx6018-64bit-4g
• nhxwrt_NHX5018
• nhxwrt_NHX4019

---

Framework Process Icon Description

graph LR
1>Project Node]
2[code repository node]
3[[Developer feeds node]]
4{{code repository branch node}}
5((public feeds node))

---

NHX-PACKAGES-OPEN framework

graph LR
A>NHX-PACKAGES-OPEN]-.Repos..->B[[NHX-PACKAGES-OPEN]]
B ---> B1[network]
B ---> B2[firmware]

B1 ---> B101[iperf]
B1 ---> B102[iperf3]

B101-.ipk..->Z((docs.bitswrt.com))
B102-.ipk..->Z
B2-.ipk..->Z

subgraph all package-open repos
B
end

subgraph all package-open ipk
Z
end

click Z "http://docs.bitswrt.com"
click A "https://dev.azure.com/lede/NHX-PACKAGES-OPEN"

---

pipelines

NHX-SDK pipelines

• Publish firmware to docs.bitswrt.com azure-build/NHX6018-Product model.yml azure-build/NHX5018-Product model.yml azure-build/NHX4019-Product model.yml azure-build/CPE7621-Product model.yml

---

NHX-PACKAGES-BIN pipelines

• Publish to Repos [packages name] Naming rules for pipelines:qca-packages name-bin.yml mtk-packages name-bin.yml PKG naming rules:qca-packages name-bin mtk-packages name-bin Note: each private PKG corresponds to a PKG feed warehouse

NHX-PACKAGES-OPEN pipelines

• Publish to docs.bitswrt.com (ipk file) Naming rules for pipelines:mtk-package-bin.yml mtk-package-bin.yml PKG naming rules:packages name

---

Git Repositories

Usage:

• Access project: https://dev.bitswrt.com/devs/projects/project-name
• Click “Copy Clone Link” to get the complete repository address with token
• Use the provided token for code cloning

Git Credential Helper Configuration (Recommended, only for bitswrt-clients repositories):

1. Install Git Credential Manager

   • macOS:

     brew install git-credential-manager

   • Windows: Included with Git for Windows, no separate installation required.
   • Linux (Debian/Ubuntu):

     sudo apt-get update
     sudo apt-get install git-credential-manager

   • Linux (CentOS/RHEL):

     sudo yum install git-credential-manager

2. Configure credential helper only for bitswrt-clients repositories

   Execute in terminal:

   git config --global credential.https://github.com/bitswrt-clients.helper manager

3. Verify configuration

   Execute:

   git config --global --list | grep credential

   You should see:

   credential.https://github.com/bitswrt-clients.helper=manager

4. Automatic effect when cloning repositories

   When you clone or operate any repository under https://github.com/bitswrt-clients/, Git Credential Manager will be used automatically, and you do not need to enter your username and token every time.

5. Remove/reset configuration (if needed)

   git config --global --unset credential.https://github.com/bitswrt-clients.helper

Git Usage Examples

After configuration, you can perform the following Git operations:

1. Clone Main Repository

# Clone NHX-QSDK-11.5-ODM main repository
# Username: bitswrt
# Project link already contains repository token and git link, copy and use directly
git clone https://github.com/bitswrt-clients/NHX-QSDK-11.5-ODM.git

# Use complete link format (recommended)
git clone https://bitswrt:[email protected]/bitswrt-clients/NHX-QSDK-11.5-ODM.git

# Clone to specified directory
git clone https://bitswrt:[email protected]/bitswrt-clients/NHX-QSDK-11.5-ODM.git nhx-sdk-project

Get Complete Clone Link:

1. Visit project page: https://dev.bitswrt.com/devs/projects/NHX-QSDK-11.5-ODM
2. Click “Copy Clone Link” button
3. The copied link already contains username(bitswrt), token and repository address, can be used directly

2. Pull Latest Code

# Enter project directory
cd NHX-QSDK-11.5-ODM

# Pull latest code
git pull origin master

# Or specify branch
git pull origin nhxwrt

3. View Repository Status

# View current status
git status

# View branch information
git branch -a

# View commit history
git log --oneline -10

4. Switch Branches

# Switch to nhxwrt branch
git checkout nhxwrt

# Create and switch to new branch
git checkout -b feature/new-feature

# Switch to specific model branch
git checkout nhxwrt_nhx6018

5. View Remote Repository Information

# View remote repositories
git remote -v

# Add remote repository
git remote add upstream https://github.com/bitswrt-clients/NHX-QSDK-11.5-ODM.git

6. Common Problem Resolution

# If authentication issues occur, clear credentials
git credential-manager reject https://github.com/bitswrt-clients/NHX-QSDK-11.5-ODM.git

# Force pull (overwrite local changes)
git fetch origin
git reset --hard origin/master

# View Git configuration
git config --list | grep credential

Note: On first operation, Git Credential Manager will pop up an authentication window. Enter your username and access token. After successful authentication, subsequent operations will automatically use saved credentials.

---

Token Expiration: Update and Handling

If your access token has a limited validity period due to security policies, please follow these steps after expiration:

1. Obtain a new access token
   Go to the project page (e.g., https://dev.bitswrt.com/devs/projects/project-name ) to generate and copy a new access token.

2. Clear locally saved old credentials
   It is recommended to use Git Credential Manager to clear credentials for the specific repository:

   git credential-manager reject https://github.com/bitswrt-clients/NHX-QSDK-11.5-ODM.git

   Or use the following command to clear all credentials for the bitswrt-clients organization:

   printf "protocol=https\nhost=github.com\npath=bitswrt-clients\n" | git credential-manager erase

   To erase credentials for a specific repository (optional):

   printf "protocol=https\nhost=github.com\npath=bitswrt-clients/NHX-QSDK-11.5-ODM.git\n" | git credential-manager erase

   Note: protocol specifies the protocol, host specifies the host, and path specifies the bitswrt-clients organization or specific repository.

3. Re-authenticate
   When you perform git pull, git push, or git clone, the system will prompt for your username (e.g., bitswrt) and the new access token.
   After successful authentication, Git Credential Manager will automatically save the new credentials until the token expires again.

For automated credential cleanup and update, you may write scripts as needed.

---

Firmware Release