XCP Seed & Key dll

[Madottati]

Hello,

I have an ECU using XCP, and I got an A2L file and a seedkey.dll for it. Calling the MC ECU Connect.vi Returns an error -301021, which means, the seed & key dll could not be located. The dll is in the same Folder as the A2L file. The dll works with other Software (Vector).

Can anybody give me a hint?

I use LV2015 and ECUMC Toolkit 15.0. Attached you can find

- screenshot of A2L file (see seed & key dll Name)

- screenshot of an XCP trace

- A2L file

- SeedKey.dll

[JefeL · Accepted solution]

Your A2L file is telling ECUMC to look for a seedkey DLL called SeedAndKeySeedKey.skb while your actual DLL is named Skb.dll. Make sure the file referenced in the A2L matches the name of the DLL.

[jrfarre]

I am getting a similar issue (error code -301021) when attempting to connect to my controller via XCP on CAN using "XCP or CCP Master" custom device. I have verified the .dll is named the same as the file referenced in the database. Both the database and the checksum are in the same directory on the windows PC that is running VeriStand. I have also compiled with checksum as a shared object file and placed directly on the Linux target with an edited database that references a .so checksum instead of a .dll in usr/local/lib. I also set up a remote seed and key server using "Remote Seedkey.lvproj" in example finder and cannot seem to unlock my ecu using a tried and true checksum. 

Does anyone have screenshots of how they configured this custom device in VeriStand? It would be nice to compare to something that is working.

[ZYOng]

---

@jrfarre wrote:

I am getting a similar issue (error code -301021) when attempting to connect to my controller via XCP on CAN using "XCP or CCP Master" custom device. I have verified the .dll is named the same as the file referenced in the database. Both the database and the checksum are in the same directory on the windows PC that is running VeriStand. I have also compiled with checksum as a shared object file and placed directly on the Linux target with an edited database that references a .so checksum instead of a .dll in usr/local/lib. I also set up a remote seed and key server using "Remote Seedkey.lvproj" in example finder and cannot seem to unlock my ecu using a tried and true checksum. 

Does anyone have screenshots of how they configured this custom device in VeriStand? It would be nice to compare to something that is working.

---

Please start a new post for a different question.

Usually seedkey is only compiled in the form of DLL for Windows. Remote seedkey is recommended. Make sure you enable the Remote Seedkey and configure the correct IP and Port settings in XCP Master Custom Device.

[jrfarre]

Thank you for your response, unfortunately the remote seed and key .vi has been attempted while on a video call with NI support and it did not work. I also only have access to that .vi for a short time as I only have an evaluation license. So my question remains, does anyone have a working example of XCP on CAN using VeriStand and ECUMC toolkit only. Is it possible to connect to a controller via VeriStand custom device, XCP on CAN, without LabVIEW or remote seed and key. 

[ZYOng]

I have helped many customers resolve the seedkey issue in the past, with or without remote seedkey. Since you are using the real-time controller, most likely you will need the remote seedkey. Please start a new thread and let me know your VeriStand version. I can provide you with the executable of the remote seedkey and guide you throught the troubleshooting process using ECUMC trace log.

[jrfarre]

https://forums.ni.com/t5/Automotive-and-Embedded-Networks/Unable-to-connect-to-ECU-using-XCP-on-CAN-...