add support SA8397 SoC (automotive) in executorch Qualcomm backend

[ares89]

🚀 The feature, motivation and pitch

Request: add support for SA8397 in executorch's Qualcomm backend so scripts accept -m SA8397 and generate correct QNN/HTP artifacts.
Current problem: using -m SA8397 fails.
Desired: add SA8397 to QcomChipset enum and to the soc->chipset map, and update any chipset-specific compiler/runtime options (can mirror SA8295 defaults initially). Add a basic CI/integration test that compiles a small model with -m SA8397.

Alternatives

No response

Additional context

No response

RFC (Optional)

No response

cc @cccclai @winskuo-quic @shewu-quic @haowhsu-quic @DannyYuyang-quic @cbilgin

[cccclai]

That should be easy - will you be willing to add the SoC? There are some other similar PRs contributed from external users like #16331 and #16332

[ares89]

I'll give it a try. If it works, I'll submit a pull request.

[cccclai]

Sounds good! Once you have it, feel free to tag me to review. If you run into issues, let us know

[ares89]

I made some change like these (SA8397 is the same as SA8797):

diff --git a/backends/qualcomm/serialization/qc_compiler_spec.fbs b/backends/qualcomm/serialization/qc_compiler_spec.fbs
index 7b81711b58..0d66d7d683 100644
--- a/backends/qualcomm/serialization/qc_compiler_spec.fbs
+++ b/backends/qualcomm/serialization/qc_compiler_spec.fbs
@@ -18,6 +18,7 @@ enum HtpArch: int {
   V73 = 73,
   V75 = 75,
   V79 = 79,
+  V81 = 81,
 }
 
 table HtpInfo {
@@ -42,7 +43,7 @@ enum QcomChipset: int {
   SSG2125P = 58,
   SXR1230P = 45,
   SXR2230P = 53,
-  SA8797 =72,
+  SA8797 = 72,
   SXR2330P = 75,
 }
 

commit 5d48672a7ee956315e9e32569538fe59fa4b7923
Author: ares89 <ares89@126.com>
Date:   Tue Jan 13 03:41:50 2026 +0000

    add support for SA8797(SA8397)

diff --git a/backends/qualcomm/serialization/qc_compiler_spec.fbs b/backends/qualcomm/serialization/qc_compiler_spec.fbs
index 8aeaa060a5..7b81711b58 100644
--- a/backends/qualcomm/serialization/qc_compiler_spec.fbs
+++ b/backends/qualcomm/serialization/qc_compiler_spec.fbs
@@ -42,6 +42,7 @@ enum QcomChipset: int {
   SSG2125P = 58,
   SXR1230P = 45,
   SXR2230P = 53,
+  SA8797 =72,
   SXR2330P = 75,
 }
 
diff --git a/backends/qualcomm/serialization/qc_schema.py b/backends/qualcomm/serialization/qc_schema.py
index f3b9e2cc1a..fabee6f6d5 100644
--- a/backends/qualcomm/serialization/qc_schema.py
+++ b/backends/qualcomm/serialization/qc_schema.py
@@ -27,6 +27,7 @@ class HtpArch(IntEnum):
     V73 = 73
     V75 = 75
     V79 = 79
+    V81 = 81
 
 
 @dataclass
@@ -48,6 +49,7 @@ class QcomChipset(IntEnum):
     SSG2125P = 58  # v73
     SXR1230P = 45  # v73
     SXR2230P = 53  # v69
+    SA8797 = 72  # v81
     SXR2330P = 75  # v79
 
 
@@ -69,6 +71,7 @@ _soc_info_table = {
     QcomChipset.SXR1230P: SocInfo(QcomChipset.SXR1230P, HtpInfo(HtpArch.V73, 2)),
     QcomChipset.SXR2230P: SocInfo(QcomChipset.SXR2230P, HtpInfo(HtpArch.V69, 8)),
     QcomChipset.SXR2330P: SocInfo(QcomChipset.SXR2330P, HtpInfo(HtpArch.V79, 8)),
+    QcomChipset.SA8797: SocInfo(QcomChipset.SA8797, HtpInfo(HtpArch.V81, 16)),
 }
 
 
diff --git a/backends/qualcomm/utils/utils.py b/backends/qualcomm/utils/utils.py
index be4e86de50..0204fab178 100644
--- a/backends/qualcomm/utils/utils.py
+++ b/backends/qualcomm/utils/utils.py
@@ -1089,6 +1089,7 @@ def generate_qnn_executorch_compiler_spec(
 def get_soc_to_arch_map():
     return {
         "SA8295": HtpArch.V68,
+        "SA8797": HtpArch.V81,
         "SM8450": HtpArch.V69,
         "SM8475": HtpArch.V69,
         "SM8550": HtpArch.V73,
@@ -1105,6 +1106,7 @@ def get_soc_to_arch_map():
 def get_soc_to_chipset_map():
     return {
         "SA8295": QcomChipset.SA8295,
+        "SA8797": QcomChipset.SA8797,
         "SM8450": QcomChipset.SM8450,
         "SM8475": QcomChipset.SM8475,
         "SM8550": QcomChipset.SM8550,

when i run like this:
nohup python -m examples.qualcomm.oss_scripts.qwen2_5.qwen2_5 -b build-android -m SA8797 --compile_only --decoder_model qwen2.5_0.5B --prompt 你好啊 1>logs/qwen25_8797.log 2>&1 &

the log is full of this:

[ERROR] [Qnn ExecuTorch]: The SocModel doesn't support FP16
[ERROR] [Qnn ExecuTorch]: QnnBackend_validateOpConfig failed 3110
[ERROR] [Qnn ExecuTorch]: Failed to validate op aten_rms_norm_default_48 with error 0xc26
[WARNING] [Qnn ExecuTorch]: Qnn Backend op validation failed with error: 3110

qwen25_8797.log

[ares89]

Also in this file，

executorch/backends/qualcomm/README.md

Line 38 in 064ef7c

Currently, users cannot add additional chipset models because the chipset ID is not accessible to community users. If you have specific chipset models you wish to add, please contact one of the authors in the `Code Reviews` section at the bottom of this page.

Are there differences between QNN(for mobile phone) and QNN(for autoware)?

[shewu-quic]

qwen2_5

Hi @ares89 ,
This device seems not support FP16 graph based on the log. Could you please try to add --ptq 16a8w in your command?
BTW, if you would like to get the better performance, you could try static llama. https://github.com/pytorch/executorch/tree/064ef7ca0049d483429412e55d1be53e1835d525/examples/qualcomm/oss_scripts/llama

End to End Commanad:

python examples/qualcomm/oss_scripts/llama/llama.py -b build-android -s ${SERIAL_NUM} -m ${SOC_MODEL} --temperature 0 --model_mode hybrid --max_seq_len 1024 --prefill_ar_len 128 --decoder_model qwen2_5-0_5b --prompt "I would like to learn python, could you teach me with a simple example?" --tasks wikitext --limit 1

[ares89]

Hi @shewu-quic,
I tried this command,
python examples/qualcomm/oss_scripts/llama/llama.py -b build-android -m **SA8797** --temperature 0 --model_mode hybrid --max_seq_len 1024 --prefill_ar_len 128 --decoder_model qwen3-0_6b --compile_only --prompt "你好啊"
and there were some errors in the log.

qwen3_8797_0115_04.log

[WARNING] [Qnn ExecuTorch]: Qnn Backend op validation failed with error: 3110
[ERROR] [Qnn ExecuTorch]: [4294967295] has incorrect Value 0, expected >= 69.
[ERROR] [Qnn ExecuTorch]: QnnBackend_validateOpConfig failed 3110
[ERROR] [Qnn ExecuTorch]: Failed to validate op aten_convolution_default_1005 with error 0xc26

[WARNING] [Qnn ExecuTorch]: Qnn Backend op validation failed with error: 3110
[ERROR] [Qnn ExecuTorch]: [4294967295] has incorrect Value 0, expected >= 73.
[ERROR] [Qnn ExecuTorch]: QnnBackend_validateOpConfig failed 3110
[ERROR] [Qnn ExecuTorch]: Failed to validate op aten_matmul_default_894 with error 0xc26

compare with the log from this command SA8295
python examples/qualcomm/oss_scripts/llama/llama.py -b build-android -m **SA8295** --temperature 0 --model_mode hybrid --max_seq_len 1024 --prefill_ar_len 128 --decoder_model qwen3-0_6b --compile_only --prompt "你好啊"

qwen3_8295_0115_03.log

[WARNING] [Qnn ExecuTorch]: Qnn Backend op validation failed with error: 3110
[ERROR] [Qnn ExecuTorch]: [4294967295] has incorrect Value 68, expected >= 69.
[ERROR] [Qnn ExecuTorch]: QnnBackend_validateOpConfig failed 3110
[ERROR] [Qnn ExecuTorch]: Failed to validate op aten_convolution_default_11 with error 0xc26

[WARNING] [Qnn ExecuTorch]: Qnn Backend op validation failed with error: 3110
[ERROR] [Qnn ExecuTorch]: [4294967295] has incorrect Value 68, expected >= 73.
[ERROR] [Qnn ExecuTorch]: QnnBackend_validateOpConfig failed 3110
[ERROR] [Qnn ExecuTorch]: Failed to validate op aten_matmul_default_479 with error 0xc26

I had set the soc info to
QcomChipset.SA8797: SocInfo(QcomChipset.SA8797, HtpInfo(HtpArch.V81, 16))

[shewu-quic]

Hi @ares89 ,
Based on the below error message, it can not identify htp_arch of SA8797 in QAIRT SDK. Could you please use QAIRT SDK v2.42.0?
You can set QNN_SDK_ROOT to change the sdk be used.
https://softwarecenter.qualcomm.com/api/download/software/sdks/Qualcomm_AI_Runtime_Community/All/2.42.0.251225/v2.42.0.251225.zip

[ERROR] [Qnn ExecuTorch]: [4294967295] has incorrect Value 0 (should be 81), expected >= 73 (htp_arch).