UDF Error Codes

FLOW_FUNC_SUCCESS = 0

Execution success.

N/A

FLOW_FUNC_ERR_PARAM_INVALID = 164000

The parameter verification is invalid.

This error code is returned when parameter verification fails. A possible cause is that the input parameter is out of the range supported by the system or some parameters are not matched. When this error code is returned, invalid parameters and error causes are recorded in logs. Locate the fault based on the logs.

FLOW_FUNC_ERR_ATTR_NOT_EXITS = 164001

The attribute does not exist.

Check the name of the attribute to be obtained, and check whether the attribute is set before it is obtained.

FLOW_FUNC_ERR_ATTR_TYPE_MISMATCH = 164002

The attribute type is mismatched.

Check whether the attribute value type corresponding to the input parameter attribute name is the same as the data type of the output parameter variable when the GetAttr API is called. This error code corresponds to the data type of the actual attribute corresponding to the attribute name in the error log.

FLOW_FUNC_FAILED = 564000

UDF internal error code.

Rectify the fault based on the logs or contact engineers. (After obtaining the logs, click here to contact technical support.)

For details about logs, see the Log Reference.

FLOW_FUNC_ERR_DATA_ALIGN_FAILED = 364000

Data alignment fails.

The possible causes are as follows:

• The FlowFunc implementation is incorrect. For example, the given input does not match.
• The execution of a node times out. As a result, the data alignment waiting times out.

FLOW_FUNC_ERR_TIME_OUT_ERROR = 564001

NN execution times out.

Check whether the logs contain other errors that result in the model execution failure. If yes, locate the fault based on the actual error information. If no error log is reported and the model is in proper execution, adjust the input parameter timeout passed by the fetch data API. You can increase the value or set it to -1.

FLOW_FUNC_ERR_NOT_SUPPORT = 564002

The function is not supported.

The possible causes are as follows:

• This function is not supported by the single-func API. Replace the single-func API with a multi-func API to avoid this error.
• The corresponding API is not implemented. For example, if ResetFlowFuncState is not implemented in the fault recovery scenario, a message is returned by default, indicating that the function is not supported.

FLOW_FUNC_STATUS_REDEPLOYING = 564003

Downgraded deployment is in progress.

A recoverable error triggers downgraded deployment. As a result, no data can be obtained. After the downgraded deployment is complete, other return codes are returned. If the downgraded deployment is successful, data is returned. Otherwise, other unrecoverable error codes are returned.

FLOW_FUNC_STATUS_EXIT = 564004

The UDF process is exiting.

This error code is returned if the process receives an exit signal when FlowFunc is waiting for input data, indicating that the process is about to exit and stop input data preparation. Locate the cause why the UDF process receives the exit signal based on logs.

FLOW_FUNC_ERR_DRV_ERROR = 564100

Common driver error.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

FLOW_FUNC_ERR_MEM_BUF_ERROR = 564101

The buffer API of the driver memory is incorrect.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on error logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

FLOW_FUNC_ERR_QUEUE_ERROR = 564102

Driver queue API error.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on error logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

FLOW_FUNC_ERR_EVENT_ERROR = 564103

Driver event API error.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on error logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

FLOW_FUNC_ERR_USER_DEFINE_START = 9900000

User-defined error code, starting from the current error code.

-

FLOW_FUNC_ERR_USER_DEFINE_END = 9999999

User-defined error code, ending with the current error code.

-

int32_t AICPU_SCHEDULE_ERROR_PARAMETER_NOT_VALID = 521001

The parameter verification is invalid.

This error code is returned when parameter verification fails. A possible cause is that the input parameter is out of the range supported by the system or some parameters are not matched. When this error code is returned, invalid parameters and error causes are recorded in logs. Locate the fault based on the logs.

int32_t AICPU_SCHEDULE_ERROR_FROM_DRV = 521003

The driver API returns an error.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

int32_t AICPU_SCHEDULE_ERROR_NOT_FOUND_LOGICAL_TASK = 521005

The AI CPU task to be executed is not found.

Check whether the version of the environment driver package is compatible with that of the CANN package. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

int32_t AICPU_SCHEDULE_ERROR_INNER_ERROR = 521008

AI CPU internal error.

Check whether the version of the environment driver package is compatible with that of the CANN package. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

int32_t AICPU_SCHEDULE_ERROR_OVERFLOW = 521011

There is an overflow.

Overflow occurs in the multiplication or addition operation. Locate the fault based on the specific log.

int32_t AICPU_SCHEDULE_ERROR_MODEL_EXIT_ERR = 521104

Model execution fails.

During model execution, the return value is set to an exception flag. As a result, the model cannot be executed. Check whether other errors are reported in the logs, and locate the fault based on the logs.

int32_t AICPU_SCHEDULE_ERROR_MODEL_EXECUTE_FAILED = 521106

Model execution failure reported by the TSCH during model execution.

During model execution, an abnormal termination message is received and the model needs to be terminated (the termination cause is that the model flow fails to be executed). Check whether other errors are reported in the logs, and locate the fault based on the logs.

int32_t AICPU_SCHEDULE_ERROR_TSCH_OTHER_ERROR = 521107

Other errors reported by the TSCH during model execution.

During model execution, an abnormal termination message is received and the model needs to be terminated. Check whether other errors are reported in the logs, and locate the fault based on the logs.

int32_t AICPU_SCHEDULE_ERROR_DISCARD_DATA = 521108

Mbuf data is discarded during model execution.

During model execution, the buffered Mbuf data exceeds the threshold and needs to be discarded. To solve this problem, adjust the number of Mbufs or the time threshold.

int32_t AICPU_SCHEDULE_ERROR_DRV_ERR = 521206

The driver API returns an error.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

int32_t AICPU_SCHEDULE_ERROR_MALLOC_MEM_FAIL_THROUGH_DRV = 521207

Allocating memory using driver fails.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, check whether the device memory usage reaches the upper limit. Check the log for more information, or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

int32_t AICPU_SCHEDULE_ERROR_SAFE_FUNCTION_ERR = 521208

Executing safe functions such as memcpy_s fails.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

int32_t AICPU_SCHEDULE_ERROR_INVAILD_EVENT_SUBMIT = 521209

The AI CPU fails to submit the event.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.

int32_t AICPU_SCHEDULE_ERROR_CALL_HCCL = 521500

The AI CPU fails to call the HCCL API.

Check whether the environment driver package is properly installed and whether the device status is normal. If the current environment installation package meets the expectation and the environment status is normal, rectify the fault based on logs or contact technical support. (After obtaining the logs, click here to contact technical support.)

For details about logs, see Log Reference.