Return Codes

HIVA_SUCCESS=0x00

Success

None

HIVA_FAILED=0x01

Failure

Possible cause: common error code

Solution: Analyze the error based on the context. Currently, there is no clear error description.

HIVA_INPUT_NODE_NAME_ERROR=0xF20004

The node name is abnormal.

Possible cause: The entered node name is incorrect.

Solution: Check the entered node name.

HIVA_NNENGINE_PARAMCHECK_FAILED=0xF20350

Parameter verification fails.

Possible cause: The input parameter is incorrect.

Solution: Check the parameter range, model path, and model file permission.

HIVA_NNENGINE_ACLINIT_FAILED=0xF20351

AscendCL initialization fails.

Possible cause: An internal error occurs in the AscendCL module.

Solution: Restart the process and try again.

HIVA_NNENGINE_ACLSETDEVICE_FAILED=0xF20352

AscendCL setDevice fails.

Possible cause: An internal error occurs in the AscendCL module.

Solution: Restart the process and try again.

HIVA_SERVICE_SUB_NULL=0xF20401

Sub initialization fails.

Possible causes:

• The specified blockNum or dataSize is abnormal.
• Failed to initialize the corresponding shared memory.

Solution: Restart the node.

HIVA_SERVICE_CALL_REQ_NULL=0xF20402

The request data pointer is null.

Possible cause: The data pointer input for the request is abnormal.

Solution: Check the parameter value and send the request again.

HIVA_SERVICE_CALL_RES_NULL=0xF20403

The response data pointer is null.

Possible cause: The data pointer input for the request is abnormal.

Solution: Check the parameter value and send the request again.

HIVA_SERVICE_CALL_RESULT_FAILED=0xF20404

The server returns a failure message.

Possible cause: The callback processing on the server fails.

Solution: Send the request again.

HIVA_SERVICE_CALL_TIMEOUT=0xF20405

Request timed out.

Possible cause: The waiting times out after the request is sent.

Solution: Send the request again.

HIVA_NODE_PARAM_INVALID=0xF20500

The initialization parameter of the publish node is invalid (for example, the serialization parameter is empty or the message size is incorrect).

Possible causes:

• The value of the serialization function is null.
• The size of the standard message to be published is greater than the maximum value or less than the minimum value.
• The mbuf pointer of the BufferMessage message is null.

Solution: Check the parameter value.

HIVA_INPUT_NODE_NAME_ERROR=0xF20501

The node name is invalid.

Possible causes: The node name is too long. Or the node name is too long after remap.

Solution: Check the parameter value.

HIVA_NODE_STRCPY_ERROR=0xF20502

Failed to copy the node name during DataMaster registration.

Possible cause: The character string fails to be copied when the registration message is constructed during queue creation.

Solution: Restart the node.

HIVA_NODE_SERIALIZE_FAILED=0xF20510

Failed to serialize the publisher.

Possible cause: The data does not match the message type, and the mbuf data is damaged.

Solution: The publisher checks the code and intercept points.

HIVA_NODE_MSG_SIZE_INVALID=0xF20511

The size of a BufferMessage message or a management-plane message is not within the normal range.

Possible cause: The size of BufferMessage messages or management plane messages is not within the normal range.

Solution: Check the parameter value.

HIVA_NODE_CONNECT_DataMaster_FAILED=0xF20517

Failed to register the DataMaster during node initialization.

Possible causes: The DataMaster exits or the communication with the DataMaster fails.

Solution: Restart the node.

HIVA_NODE_GENERA_MSG_FAILED=0xF20518

Failed to generate a registration message during node initialization.

Possible causes:

• Failed to concatenate character strings in the registration message.
• The environment variable for plane selection is incorrect.
• /proc/self/exe link read error.

Solution: Restart the node.

HIVA_NODE_HAL_CREAT_GROUP_FAILED=0xF20520

Failed to create a group during node initialization.

Possible cause: The driver fails to be loaded.

Solution: The permission is incorrect or the process exits.

HIVA_NODE_BIND_CPU_FAILED=0xF20521

Failed to bind CPUs during the node initialization.

Possible causes: hardware initialization error, detach device error, or OS CPU binding error.

Solution: Restart the node.

HIVA_CORE_SERIALIZE_FUN_EMPTY=0xF20A05

The serialization function is empty when a message is published.

Possible cause: The serialization function is empty.

Solution: Restart the node.

HIVA_CORE_BUFF_PTR_EMPTY=0xF20A06

The start address of the buffer is empty when a message is published.

Possible cause: The buffer is empty.

Solution: Restart the node.

HIVA_TRANSPORT_MSG_TYPE_INVALID=0xF20B07

The message type is incorrect.

Possible cause: The message type is incorrect.

Solution: Check whether the BufferMessage message is correct.

HIVA_TRANSPORT_QUEUE_INVALID=0xF20B08

Failed to obtain queue info.

Possible cause: hiva not OK

Solution: Restart the node.

HIVA_TRANSPORT_VFS_NOT_SUPPORT_BUFF_MSG=0xF20B09

The VFS does not support BufferMessage.

Possible cause: The VFS does not support BufferMessage.

Solution: Reconfigure the communication mode or message type.

HIVA_SERVICE_CLIENT_PTR_EMPTY=0xF20D00

The client pointer of the service is null.

Possible cause: The client pointer of the service is null.

Solution: Restart the node.

HIVA_SERVICE_SEVER_PTR_EMPTY=0xF20D01

The server pointer of the service is null.

Possible cause: The server pointer of the service is null.

Solution: Restart the node.

HIVA_SERVICE_STATE_INVALID=0xF20D02

The service status is incorrect.

Possible cause: The service status is incorrect.

Solution: Check whether the status change process is correct.

HIVA_SERVICE_NODEPTR_EMPTY=0xF20D03

The node pointer is null.

Possible cause: The node pointer is null.

Solution: Restart the node.