Hello all,
I have an issue when using Keil uVision (v5.43.0.0) where the .ini files that are generated upon loading a CMSIS Toolbox project (e.g. a .csolution.yml file) are dictating the files that should be programmed to my device, when what I actually want to do is program my device from a file I create during a postbuild step.
I've tried modifying the generated .ini files both before and after opening the project to point to the desired file from my postbuild, but it seems that any changes I make are discarded by uVision. Furthermore, it appears that, although I can specify a custom .ini file to use instead (via Options for Target -> Utilities -> Init File), this file is completely ignored in favor of the files uVision generates from the info in the CMSIS Toolbox project. I've also verified that specifying a custom .ini file via target options in an equivalent .cprj project works as expected.
Is there a preferred way to go about programming files generated by a postbuild in Keil uVision?