Please note again that this question pertains to S32DS for ARM v 2.2
The code auto generated by the IDE in the directory 'Generated_Code' seems to be re-generated (possibly with updates) *after* it is compiled. This seems wrong and the way I find is that if I delete the files in this directory the project fails to build because of missing header files. But if I include these files in a git repo, then after each project rebuild these files are shown as modified with a different date/time stamp; i.e. a line like
** Date/Time : 2025-08-29, 11:06, # CodeGen: 54
Is there a way that this code can be generated *before* it is used?
Hi,
the generated code is done by Processor Expert if you click on Generate Code icon in Processor Expert tab. Normally the existing generated code should remain. Can you please share more details about your setup and which SDK version are you using?
Hello @jiri_kral
I am using S32 DS for ARM v 2.2, please see the screenshot:
The SDK version is 3.0.0, please see the screenshot below:
The hardware for this project is mature and I am not (explicitly) updating the code from Processor Expert (the tool may be invoking it behind the scene).
After any non-trivial code change (involving the application logic, not the hardware), I click on 'Clean...' in the project menu which does a full project rebuild.
With this, sometimes I see a large number of warnings from all over the project (including the auto generated code) and other times I see only a small number of warnings only in the application logic, which seems to imply that the autogenerated code is recompiled sometime but not always. To add to this, sometimes all the autogenerated code show up as modified it git and other times only a few or none. When a modification *does* happen, it is only in the timestamp of the file, as shown in the screen shot below:
It does not impact the validity of the code, but it does affect our CI/CD pipeline. I'd like to either:
1. Put the autogenerated code *outside* of version control (less preferable since this is a safety critical product and all the code that is in the image should be traceable), but this does not work because the code is not (always) regenerated as part of the build.
Or
2. Keep the code in version control (preferred method) but not have the build tool change it every time with a timestamp update.
I could try committing the changed autogenerated code once if that would fix the issue, but if a timestamp is updated at every build, I don't see how that will work.