Query Regarding DFOTA Package Generation Issue on EC200U-CN-AA

QuecPython
,
1

Dear Quectel Support,

We are working with the EC200U-CN-AA module and trying to generate a DFOTA package using QPYcom. However, every time the DFOTA generation completes, the generated output.pack file size is only around 1 KB.

We tried the following approaches:

  1. Using:

    • Base platform PAC file

    • vs merged image containing Base + Application

  2. Using:

    • app1_merged.pac

    • vs app2_merged.pac

In both cases, the generated DFOTA output.pack file remains around 1 KB.

Could you please help us understand:

  • Whether this behavior is expected?

  • If we are missing any mandatory DFOTA generation steps/configuration?

  • Whether EC200U-CN-AA has any specific DFOTA packaging requirements?

  • Any recommended tool version, merge method, or partition limitations?

It would be helpful if you could share:

  • A reference DFOTA generation procedure for EC200U-CN-AA

  • Any documentation or sample workflow related to QPYcom DFOTA package generation

Thanks in advance for your support.

Best Regards,
Surya

(Quectel)

2

Dear @Support-team,

Gentle Remainder! Waiting for your reply

3

Dear @Support-team,

Kindly please respond

4

Dear Customer

May I ask if you generated theDFota package following the steps in the link below?

Firmware OTA Delta Package Making Guide - QuecPython

It seems incorrect if the Dfota package you built is only 1KB in size.

Are you generating the Dfota package using two different firmware versions?

One point to note: for EC200U modules, DFOTA only supports firmware upgrade, not script updates. Script upgrade can only be implemented via app_fota.

5

Thanks for the update. That makes sense.

May I ask if you generated theDFota package following the steps in the link below?

Yes, Used the same steps

Currently, I am generating DFOTA packages between:

  1. 8915DM_cat1_open_EC200UCNAAR03A01M08_VOBT_OCPU_QPY_merge.pac and 8915DM_cat1_open_EC200UCNAAR03A01M08_VOBT_OCPU_QPY_merge_20260526-1215.pac (which contains the base firmware along with my Python application files). The generated DFOTA package is only about 1 KB.

  2. 8915DM_cat1_open_EC200UCNAAR03A01M08_VOBT_OCPU_QPY_merge_20260526-1215.pac and 8915DM_cat1_open_EC200UCNAAR03A01M08_VOBT_OCPU_QPY_merge_20260527-1416.pac (also containing the base firmware and Python application files). In this case as well, the generated DFOTA package is only about 1 KB.

If I switch to App FOTA for updating only the Python files, could you please help me understand:

  • How can I verify that the Python package/script has been downloaded successfully?

  • Is there any mechanism to validate the integrity of the downloaded package before applying the update?

  • Is there a backup or rollback mechanism available to retain the existing Python files in case the App FOTA process fails or the new package is corrupted?

Any guidance or recommended approach for safely updating Python application files would be greatly appreciated.

Also, with the current firmware, we have approximately 380 KB of usr space available. Is there any possibility of increasing the usr partition size or modifying the partition layout to allocate more storage for application files?

If so, could you please let me know the supported options and any limitations or considerations involved?