Hello,
I'm experiencing an issue with RTD 5 when configuring the LCU module. Specifically, when I select Instance -> 1 in LCU, it throws an error (please refer to the image below). There are no other changes made, and this configuration works fine in RTD 4.
Additionally, after pressing "OK," it does not allow adding more than one LCU Output Physical — the "+" button in the peripherals section becomes unresponsive.
I’ve verified this behavior in both S32 Design Studio v3.5 and v3.6, and the issue persists in both versions.
Could you please look into this?
Thank you.
Yeah, this is the same workaround I was using as well. I keep LCU_IP_HW_INST_0 in the configuration while setting everything up, even though it is not used, and then remove Instance 0 at the end.
NXP did suggest updating/reinstalling the RTD, but that did not resolve this particular issue. The post was eventually closed, so I’m not sure if this was fixed in a later S32DS/RTD version. I saw the issue in both S32DS 3.5 and 3.6.
Thanks for adding this to the community @Micha4566465
. It’s useful to have the workaround here so others can refer to it if they run into the same issue.
Hi,
I have this issue, too.
The issue only appears, when using LCU Hardware Instance LCU_IP_HW_INST_1 as only instance in "LCU Logic Instance"-Item.
If you keep the LCU_IP_HW_INST_0 beside the LCU_IP_HW_INST_1, although it will not be used, there is no problem.
Hello,
here is what i see when configure Instance 1:
I do not see any issue.
Best regards,
Peter
Thanks for the responses! I tried the suggestions you provided — things are working better now. I'm able to add the LCU instance, which is good progress.
However, I the issue only occurs when selecting hardware instance 1(as mentioned before). In the image you shared, it shows instance 0, which doesn't seem to have the same problem.
Occasionally, an error still pops up when working with instance 1, but it's not a blocker since I can exit it without any functional impact.
Could you please confirm if this is a known issue in RTD v5, or if it might be related to something else? Also, if there's a fix or recommended workaround, that would be helpful.
Hello,
I have just tried it in S32DS 3.5. with RTD 5.0.0. and I do not see such issue:
The error seem to be tied to your installation.
Since the issue is also present in S32DS 3.6 I suggest to reinstall the RTD pluggin and intall the latest update of RTD 5..0.0.HF1
But the fact is that I am using much older release and do not see the issues.
It can also be linked to S32DS GUI. Maybe it is somehow corrupted or has restricted access to the configuration in LPC.
Best regards,
Peter