EB software MCAL does not have a license

[Embedded_novice]

HI.

I installed MCAL in the EB software and imported other people's projects. However, when I tried to open CAN, it didn't prompt me that I didn't have a license. But my ADC and other components were the same version as CAN, and the ADC could be opened normally without any error reports. Not only CAN, but also EEP,FEE and other modules have the same problem. I want to know what's going on here? The EB version I'm using is 29.0, and the MCAL version is as shown in the figure

[petervlna · Accepted solution]

Hello,

This means EB tresos detected that the CAN module you are trying to open requires a license that is not available in your current EB license configuration.

Here’s why this happens and why ADC works but CAN, EEP, FEE do not:

Possible Reasons

1. License Scope Difference

   • EB licenses are module-specific. You might have a license for ADC but not for CAN, EEP, or FEE.
   • Even if all modules belong to the same MCAL version, EB checks licenses per module.

2. Imported Project References Different Targets

   • The imported project may use a CAN module variant (e.g., Can_TS_T40D2M1012R0) that your license does not cover.
   • ADC might match your licensed variant, so it opens fine.

3. License File Not Activated or Missing

   • If you recently installed EB 29.0, the license file might not have been properly activated for all modules.

4. MCAL Package Includes Modules, But EB Needs Separate Licenses

   • Installing MCAL does not automatically grant EB licenses for all modules. EB requires separate license keys for each module.

You can check the license in your EB license admin: ClientLicenseAdministrator.exe by doublke click on license.

How to Check:

• In EB tresos, go to Help → About → License Information and verify which modules are licensed.
• Compare the module name in the error (Can_TS_T40D2M1012R0) with your license list.
• Check if EEP and FEE also show similar missing license messages when opened.

Best regards,

Peter