Burn in factory data

Wireless Connectivity Matter
1

How to burn the install code, MAC address, and other factory data？

2

Modify factory data in factoryblcok.xml file

1. Windows Environment

Can use qpg6200-iot-sdk

（1） Install Vscode and install necessary tools

  • MinGW or MSYS2：provide make、bash、gcc etc tools（recommend MSYS2）
  • GNU Arm Embedded Toolchain：used in ARM build
  • Python： need
  • make sure make put in PATH，put in command line make --version to check version info

（2） Config Vscode

  1. open SDK root dir（example: qpg6200-iot-sdk-main）
  2. choose terminal MSYS2/MinGW bash（recommend MSYS2）
  • choose in VSCode terminal menu “new terminal”，choose bash。
  1. check Makefile path
  • example: Zigbee Switch Application Makefile Path：
    Applications/Zigbee/Switch/Makefile.Switch_Zigbee_qpg6200
  • example: Zigbee Switch FactoryBlock Makefile Path：
    Libraries/Qorvo/FactoryBlock/Makefile.FactoryBlock_qpg6200_Switch

Can’t use qpg6200-iot-sdk

（1） translate makefile recipts into .bat language

（2） Open Powershell

Write Command as follow:

cd .\Desktop\6414

./buildall.bat

（3） Check hex file in work folder

2. Ubuntu Environment

Can use qpg6200-iot-sdk

Enter Command in terminal as follow:

cd qpg6200-iot-sdk

source ./Scripts/activate.sh

cd Libraries/Qorvo/FactoryBlock

make -f Makefile.FactoryBlock_qpg6200_Switch

normal issue:

（1） Python version is wrong

cd qpg6200-iot-sdk

python3 --version
##if print python3.10.x is suitable
##if print python3.11 please enter follow command
sudo update-alternatives --config python3
##select python3.10.x

Can’t use qpg6200-iot-sdk

（1） Check if there is arm-none-eabi-objcopy in you path :/usr/bin/arm-none-eabi-objcopy

##if you don't have, please download from apt

（2） translate makefile recipts into python language to generate hex file separately