Issue with IOC File Changes Not Reflecting in Code (CUBEIDE)

[User.72]

Hello,

I am currently working on a project using CUBEIDE.

However, I encountered an issue where modifications made in the IOC file do not reflect in the generated code. I would appreciate any advice or suggestions on how to resolve this problem.

Project Copying Process:
Created and worked on the project on Computer A.
Copied the project to Computer B.
The project folder was copied entirely via USB from A to B.
Opened the project on Computer B using "Open Project from File System..." → Directory.
Has anyone experienced a similar issue? How can I make the IOC file modifications apply correctly to the code?

Thank you in advance for your help!

[Mahmoud Ben Romdhane]

Hello @User.72 ,

First let me thank you for posing and welcome to the ST Community.

For more investigation, I suggest that you provide your Ioc.File.

Thanks.

Mahmoud

[User.72]

The problem is that when I open the IOC file in CUBEIDE and enable UART2, it is not reflected in the code.

[Mahmoud Ben Romdhane]

Hello @User.72 ,

Further to your comment, and through STM32CubeIDE 1.18, I am able to enable UART2 and the code is generated successfully.

After enabling UART2, I suggest that you click [Ctrl+S] to generate the code.

Thanks.

Mahmoud

[User.72]

The attached video shows the issue that occurs when I run the project on Computer B.

1. When UART2 is deactivated after being activated, the change is not applied to the code.

[User.72]

When can I expect to receive an answer to my question?

[Mahmoud Ben Romdhane]

Hello @User.72 ,

You can notice through this video that if you disable USART2, changes are well applied into the main.c.

Thanks.

Mahmoud

[User.72]

Thank you for your response.

In the video you uploaded, I can see that the code is applied correctly.

However, what I’m curious about is why the changes are not reflected in my code.

When I copy the entire project folder and run it on another computer, the same issue occurs as shown in the video I uploaded. (The issue occurs consistently on all computers – tested on five different devices.)