# Flashing QCC730 image
Source: [https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html)
You can flash images by using one of the following methods:
- Using the QCC IDE, which helps you flash images with just one click. For detailed instructions on using the QCC IDE, see [QCC IDE for QCC730 User Guide (80-Y8730-9)](doc/80-Y8730-9).
- Using the qccsdk.py or the nvm\_programmer.py script file provided in the QCC730 SDK. See [Flash command usage](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html#build_command_usage) and [Flash command examples](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html#flash_command_example) for details about using these script files.
Note:
- Usually, all images are prebuilt in the SDK downloaded from Qualcomm ChipCode™ . These images are in the .\output directory.
- To prevent errors, ensure the path to the QCC730 SDK only contains English letters and doesn't contain spaces.
- As of now, QCC730 only supports QCCIDE as the IDE. Eclipse IDE is not supported.
In QCC730 SDK, the firmware description table (FDT), secondary boot loader (SBL), board data file (BDF), firmware descriptor (FWD), FTM, and QCLI\_DEMO images can be flashed to the QCC730 EVK. Refer to the following table for more information about image files.
Table : Image file path and offset
| Image name | NVM offset | NVM location | Description | File name |
| --- | --- | --- | --- | --- |
| FDT | 0x208000 | rram | Firmware descriptor table (RRAM) | frn\_curr\_age\_default.bin for demos
frn\_curr\_age\_with\_app\_bin.bin for FTM |
| SBL\_A | 0x20a400 | rram | Secondary boot loader | FERMION\_SBL\_HASHED.elf |
| SBL\_B | 0x212400 | rram | Secondary boot loader | FERMION\_SBL\_HASHED.elf |
| FTM | 0x21A400 | rram | Factory Test Mode | FERMION\_FTM.bin |
| BDF | 0x37A000 | rram | Board Data File | mqm730i.bin for iPA QCC730M
mqm730x.bin for xPA QCC730M |
| FWD | 0x000000 | flash | Firmware descriptor (flash) | firmware\_table.bin |
| QCLI\_DEMO | 0x043000
(default address) | flash | Console image | FERMION\_IOE\_QCLI\_DEMO\_HASHED.elf |
### Prerequisites
Ensure that NVM Programmer, SBL, and one of the three demos (hello\_world, qcli\_demo, posix\_demo) have been compiled successfully before flashing.
## Flash command usage
Source: [https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html)
### Using qccsdk.py
The qccsdk.py file is in the .\qccsdk folder. You can flash all the five images (FDT, SBL\_A, SBL\_B, FWD, QCLI\_DEMO) to a QCC730 board by using the following command:
python qccsdk.py flash --flash --resetCopy to clipboard
OpenOCD is the default mode for flashing images. To use the J-Link interface, run the following command:
qccsdk.py set --jtag=jlink Copy to clipboard
Table : Flash parameters for qccsdk.py
| Parameter | Description |
| --- | --- |
| --help | Print help messages |
| --flash
(default) | Flash images |
| --reset | Reset the board after flash |
| --erase | Erase all RRAM and flash |
| --verbose | Enable output debug info on console |
| --bdf | Flash board data |
### Using nvm\_programmer.py
The nvm\_programmer.py file is in the .\qccsdk\tools\nvm\_programmer\script folder. The syntax for programming an image to the flash is as follows:
python nvm_programmer.py -b -f -s Copy to clipboard
## Flash command examples
Source: [https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html)
Before flashing images, ensure the development environment has been set up according to Section 2.
On Linux, you also need to add rules for the USB interface that connects to the QCC730 EVK. To do this, follow these steps:
1. Check device ID information (`idVendor` and `idProduct`) by using the `lsusb` command.
In the example output of the `lsusb` command, `1a86` is `idVendor` and `55de` is `idProduct`.
Bus 003 Device 004: ID 1a86:55de QinHeng Electronics UART+SPI+I2C+JTAGCopy to clipboard
2. Create a new file named 99-usb.rules in the etc/udev/rules.d/ directory and add the following lines into the file.
SUBSYSTEM=="usb", ATTR{idVendor}=="1a86", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1a86", ATTR{idProduct}=="55de", MODE="0666"Copy to clipboard
Note: `1a86` and `55de` are only example values, replace them with your actual `idVendor` and `idProduct` values.
### qccsdk.py examples
Source: [https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html)
You can use the qccsdk.py script on both Windows and Linux.
Flash all the five necessary images (FDT, SBL\_A, SBL\_B, FWD, QCLI\_DEMO) into the board and reset in one command:
python qccsdk.py set -S=demo/qcli_demo flash --flash --resetCopy to clipboard
Flash the BDF into the board and reset (flash it only if the board doesn't have the BDF):
python qccsdk.py flash --bdf --resetCopy to clipboard
### nvm\_programmer.py examples for Windows
Source: [https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html)
The following examples show how to flash a single image at a time on Windows. To prevent run failures, ensure that you flash all the mentioned images in either of the following groups.
Note: Image addresses (except for QCLI\_DEMO) are fixed. Don't change these addresses. The QCLI\_DEMO address may be modified if the configuration is different.
**Commands for flashing FDT, SBL\_A, SBL\_B, and QCLI\_DEMO**
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x208000 -f ..\..\storage\firmware_desc_table\curr_age_fdt\frn_curr_age_default.bin
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x20a400 -f ..\..\..\output\mqm730i\FERMION_SBL\DEBUG\bin\FERMION_SBL_HASHED.elf
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x212400 -f ..\..\..\output\mqm730i\FERMION_SBL\DEBUG\bin\FERMION_SBL_HASHED.elf
python nvm_programmer.py -s ch347 --nvm-name flash -b 0x043000 -P -f ..\..\..\output\mqm730i\FERMION_IOE_QCLI_DEMO\DEBUG\bin\FERMION_IOE_QCLI_DEMO_HASHED.elfCopy to clipboard
**Commands for flashing FDT, SBL\_A, SBL\_B, and FTM**
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x208000 -f ..\..\storage\firmware_desc_table\curr_age_fdt\frn_curr_age_with_app_bin.bin
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x20a400 -f ..\..\..\output\mqm730i\FERMION_SBL\DEBUG\bin\FERMION_SBL_HASHED.elf
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x212400 -f ..\..\..\output\mqm730i\FERMION_SBL\DEBUG\bin\FERMION_SBL_HASHED.elf
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x21A400 -f ..\..\..\output\mqm730i\FERMION_FTM\DEBUG\bin\FERMION_FTM.binCopy to clipboard
### nvm\_programmer.py examples for Linux
Source: [https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html)
The following examples show how to flash a single image at a time on Linux. To prevent run failures, ensure that you flash all the mentioned images.
Note: Image addresses (except for QCLI\_DEMO) are fixed. Don't change these addresses. The QCLI\_DEMO address may be modified if the configuration is different.
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x208000 -f ../../storage/firmware_desc_table/curr_age_fdt/frn_curr_age_with_app_bin.bin
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x37a000 -f ../../../modules/wifi/bin/mqm730i.bin
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x20a400 -f ../../../output/mqm730i/FERMION_SBL/DEBUG/bin/FERMION_SBL_HASHED.elf
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x212400 -f ../../../output/mqm730i/FERMION_SBL/DEBUG/bin/FERMION_SBL_HASHED.elf
python nvm_programmer.py -s ch347 --nvm-name rram -b 0x21a400 -f ../../../output/mqm730i/FERMION_IOE_QCLI_DEMO/DEBUG/bin/FERMION_IOE_QCLI_DEMO.bin --resetCopy to clipboard
## Autoboot and run the application
Source: [https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html](https://docs.qualcomm.com/doc/80-Y8730-1/topic/flash_image.html)
Ensure that you connect the QCC730M EVK using UART and the serial console is active with a port configuration as shown in the following figure.
Figure : UART settings
A command line interface (CLI) menu appears in the console after QCC730M powers up. You can then type commands to test the system features.
The following image shows the console log:
Figure : QCLI\_DEMO console log
QCC IDE also provides a console that can communicate with the QCC730M EVK. For detailed instructions on using the QCC IDE, see [QCC IDE for QCC730 User Guide (80-Y8730-9)](doc/80-Y8730-9).
Last Published: Mar 18, 2026
[Previous Topic
Build sample demo application](https://docs.qualcomm.com/bundle/publicresource/80-Y8730-1/topics/build_fermion_qcli_demo.md) [Next Topic
Program Wi-Fi MAC address](https://docs.qualcomm.com/bundle/publicresource/80-Y8730-1/topics/program_wi_fi_mac_address.md)