Flashing and Authorization

This topic describes the common questions about firmware flashing and license authorization to help you troubleshoot problems that might occur when you flash firmware and license to the module. For more information, see Firmware Flashing and Authorization.

Incorrect COM port

• Install Universal Windows Driver on your computer.
• Check if you have connected hardware to the serial port and if the port works properly.
• Check for the port occupancy.

Flash compare failed

The flash memory size read is not consistent with the one you configured on the Tuya Developer Platform. If you have this issue, submit a service ticket.

Entering production test failed

• The device has been connected to the network for more than 15 minutes so the testing channel is shut down. You must erase corresponding data from the flash memory to initiate a test again.
• You might choose the wrong COM port or the TX and RX pins are wrongly connected. For more information, see Pin Configuration.
• Some chips such as RTL8710BN require stable 3.3V. In this case, you must use a reliable USB hub to ensure a stable voltage supply.

Getting firmware fingerprint failed

The firmware fingerprint comprises the firmware identifier and the version number. The firmware identifier and version number can be set in the SDK.

The firmware fingerprint is used to verify the production firmware. The host reads the firmware identifier and firmware version to verify the order information.

• Enter the token that matches the firmware fingerprint and then run authorization.
• Try flashing and authorization again. This method does not apply to the production certificate of Authorization Only.

Stack-up warning

In manual or automated production lines, authorization mistakes might occur in multilayer PCB assembly. In the authorization process, the stack-up test on Wi-Fi and Bluetooth modules will be performed.

• Check if the same MAC address is written to the module repeatedly.

  

• Check if the same SN and MAC address are written to the module repeatedly.

  

To fix this issue, you need to delete the token file saved in the StackedboardData folder located under the Cloud Module Burning Authorization Platform installation directory.

What is the option ‘Only Auth’ used for?

If you flash firmware by using the tool provided by your chipset platform, you must write Tuya’s license to the modules for authorization. Otherwise, your modules cannot connect to the Tuya Developer Platform.

What are GPIO Test, RSSI Test, and SN Check used for?

• GPIO Test: used to test the pin configuration of the module, which is turned on by default.
• RSSI Test: used to test the Wi-Fi signal strength, which is turned on by default.
• SN Check: used to verify the SN, which is turned off by default. You can turn it on if you use the Work Order mode.

For more information, see File Configuration.

FAQs about HomeKit flashing and authorization

Why does the software not show the Work Station options?

After you enter the work order, you must press Enter key to show the work station options. Then, choose Manual Line > RF Authorization.

What is the SN format?

The SN format is work order + XXXXX. The last five digits are in hexadecimal format, depending on the number of SNs. The high-order bits of the value are padded with zeros if they are not specified.

I have flashed firmware and license to my HomeKit device but it keeps resetting. How to fix it?

Make sure you use the Work Order mode for flashing and authorization.

If you use the Token to authorize your module in the Cloud Module Burning Authorization Platform, you only have tuya_iot authorization written to the chip, without HomeKit authorization. In this case, your HomeKit cannot be paired successfully.

The atoken (Apple Token) written to the chip will be sent to Apple for activation. Generally, the authorized module cannot be paired with the Home app until the next day.

Reference