Table 45. CAN Net APIs and their description (continued)
API name (type)
Description
• dataType – the data type of the specified data
• Callback – callback function
• useBlockMode – specifies whether it is a block
transmission
UNS8 writeNetworkDictCallBack (CO_Data* d, UNS8 nodeId,
UNS16 index, UNS8 subIndex, UNS32 count, UNS8 dataType,
void *data, SDOCallback_t Callback, UNS8 useBlockMode)
The master node sets the specified data to the slave node.
• d – object dictionary
• nodeId – the id value of slave node
• index – the index value of the specified data
• subIndex – the subindex value of the specified data
• count – the length of the specified data
• dataType – the data type of the specified data
• Callback – callback function
• useBlockMode – specifies whether it is a block
transmission
13.3 Running a CAN application
The following sections describe the hardware and software preparation steps for running a CAN application. The hardware
preparation is described separately for the LS1021A-IoT and LS1028ARDB, but the sections
Compiling the CANopen-app binary
Running the CANopen application
, and
Running the Socketcan commands
are applicable to both LS1021A-
IoT and LS1028A platforms.
13.3.1 Hardware preparation for LS1021-IoT
For LS1021-IoT, the list of hardware required for implementing the FlexCAN demo is as follows:
• LS1021A-IoT boards
• Two CAN hardware interfaces (for example, CAN3 and CAN4 for LS1021A-IoT)
• Two CAN transceivers (for example: TJA1050 )
NXP Semiconductors
FlexCAN
Open Industrial User Guide, Rev. 1.8, 05/2020
User's Guide
170 / 199