Good day to you all,
Understanding how the API works with the help of the sample application and API reference only can be a bit tricky sometimes.
For example, we are currently trying unsuccessfully to set the assembly object size of our Ethernet/IP adapter.
Is there any further documentation on the Ethernet/IP stack?
I'm thinking of a how-to guide or a comprehensive explanation of how the API works.
Best regards,
Erik
Hi Nilabh,
Sorry for the delay in replying.
I am trying to add a configuration assembly to the example adpater.
I added a third assembly instance 0x66 as a config assembly and a class 0x80 for the members:
uint16_t classId_e = 0x80;
EI_API_CIP_createClass(pCip_s, classId_e);
EI_API_CIP_SService_t service;
service.getAttrAllResponseCnt = 0;
service.callback = NULL;
service.code = EI_API_CIP_eSC_GETATTRSINGLE;
EI_API_CIP_addClassService(pCip_s, classId_e, &service);
service.code = EI_API_CIP_eSC_SETATTRSINGLE;
EI_API_CIP_addClassService(pCip_s, classId_e, &service);
EI_API_CIP_createInstance(pCip_s, classId_e, instanceId);
service.code = EI_API_CIP_eSC_GETATTRSINGLE;
EI_API_CIP_addInstanceService(pCip_s, classId_e, instanceId, &service);
service.code = EI_API_CIP_eSC_SETATTRSINGLE;
EI_API_CIP_addInstanceService(pCip_s, classId_e, instanceId, &service);
uint16_t attribID = 0x300;
// USINT (uint8_t).
for (i = 0; i < 6; i++)
{
EI_API_CIP_SAttr_t attr;
memset(&attr, 0, sizeof(attr));
attr.id = attribID;
attr.edt = EI_API_CIP_eEDT_USINT;
attr.accessRule = EI_API_CIP_eAR_GET_AND_SET;
attr.pvValue = &i;
EI_API_CIP_addInstanceAttr(pCip_s, classId_e, instanceId, &attr);
EI_API_CIP_setInstanceAttr(pCip_s, classId_e, instanceId, &attr);
attribID++;
}
errCode = EI_API_CIP_createAssembly(pCipNode_p, 0x66, EI_API_CIP_eAR_GET_AND_SET); // CONFIG
for (i = 0x300; i < 0x305; i++)
{
errCode = EI_API_CIP_addAssemblyMember(pCipNode_p, 0x64, classId, instanceId, i);
if (errCode != EI_API_CIP_eERR_OK)
{
OSAL_printf("Failed to add Class ID %#x, Instance ID %#x, Attribute ID %#x to Assembly Instance 0x64: Error code: 0x%08x\n", classId, instanceId, (uint16_t)i, errCode);
}
errCode = EI_API_CIP_addAssemblyMember(pCipNode_p, 0x65, classId, instanceId, (uint16_t)(8 + i));
if (errCode != EI_API_CIP_eERR_OK) {
OSAL_printf("Failed to add Class ID %#x, Instance ID %#x, Attribute ID %#x to Assembly Instance 0x65: Error code: 0x%08x\n", classId, instanceId, (uint16_t)(8 + i), errCode);
}
errCode = EI_API_CIP_addAssemblyMember(pCipNode_p, 0x66, 0x80, instanceId, i);
if (errCode != EI_API_CIP_eERR_OK)
{
OSAL_printf("Failed to add Class ID %#x, Instance ID %#x, Attribute ID %#x to Assembly Instance 0x66: Error code: 0x%08x\n", classId, instanceId, (uint16_t)(16 + i), errCode);
}
}
errCode = EI_API_CIP_addAssemblyMember(pCipNode_p, 0x66, 0x80, instanceId, 0x305);
if (errCode != EI_API_CIP_eERR_OK)
{
OSAL_printf("OWN PARAM; Error code: 0x%08x\n", errCode);
}
The PLC sends 0x00000007 as a configuration value:
However, this has no impact on the config assembly data; these remain at their initial values:
// in EI_APP_run:
uint8_t assem_data[6]; // CONFIG ASSEM DATA BUFFER
EI_API_CIP_getAssemblyData(pCip_s, 0x66, assem_data, 6); // GET CONFIG ASSEM DATA
OSAL_printf("assemData: 0x%02x:%02x:%02x:%02x:%02x:%02x\r\n", assem_data[0],
assem_data[1], assem_data[2], assem_data[3], assem_data[4],
assem_data[5]);
// ==>
// Output is:
// assemData: 0x00:01:02:03:04:05
// But it should be:
// assemData: 0x00:00:00:00:00:07
Did I overlook something or is there something to consider when handling config data in the API?
BR
Erik
One other question:
I am trying to flash the Ethernet/IP adapter example and get the following error:
[INFO] Parsing config file ... SUCCESS. Found 3 command(s) !!! [INFO] Executing command 1 of 3 ... [INFO] Found flash writer ... sending K:/Pool/decicher/ti/mcu_plus_sdk_am243x_08_03_00_18/tools/boot/sbl_prebuilt/am243x-lp/sbl_uart.release.tiimage [INFO] Sent flashwriter K:/Pool/decicher/ti/mcu_plus_sdk_am243x_08_03_00_18/tools/boot/sbl_prebuilt/am243x-lp/sbl_uart.release.tiimage of size 257820 bytes in 26.14s. [INFO] Executing command 2 of 3 ... [INFO] Command arguments : --file=K:/Pool/decicher/ti/mcu_plus_sdk_am243x_08_03_00_18/tools/boot/sbl_prebuilt/am243x-lp/sbl_ospi.release.tiimage --operation=flash --flash-offset=0x0000 Sent K:/Pool/decicher/ti/mcu_plus_sdk_am243x_08_03_00_18/tools/boot/sbl_prebuilt/am243x-lp/sbl_ospi.release.tiimage of size 297589 bytes in 31.21s. [ERROR] Incorrect magic number in Response Header !!! [INFO] Executing command 3 of 3 ... [INFO] Command arguments : --file=C:/Users/decicher/workspace_v12/ethernetip_adapter_mii_demo_am243x-evm_r5fss0-0_freertos_ti-arm-clang/Release/ethernetip_adapter_mii_demo_am243x-evm_r5fss0-0_freertos_ti-arm-clang.appimage --operation=flash --flash-offset=0x80000
Or via terminal:
PS K:\Pool\decicher\ti\mcu_plus_sdk_am243x_08_03_00_18\tools\boot> python uart_uniflash.py -p COM6 --cfg=C:/Users/decicher/Desktop/FLASH_sbl_ospi.cfg Parsing config file ... Parsing config file ... SUCCESS. Found 3 command(s) !!! Executing command 1 of 3 ... Found flash writer ... sending sbl_prebuilt/am243x-lp/sbl_uart_uniflash.release.tiimage Sent flashwriter sbl_prebuilt/am243x-lp/sbl_uart_uniflash.release.tiimage of size 291781 bytes in 28.06s. Executing command 2 of 3 ... Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_ospi.release.tiimage --operation=flash --flash-offset=0x0 Sending sbl_prebuilt/am243x-lp/sbl_ospi.release.tiimage: 0%| | 2/297621 [01:50<9102:17:30, 110.10s/bytes] [ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user, Power cycle EVM and run this script again !!!
BR
Erik