Hi, I’ve a design that was applied before on the PSoC6 platform and there were some changes in the BSP header/sources that were made. Now I use the latest modus toolbox and library manager so I just took the original BSP ...Read more
Hi,
I’ve a design that was applied before on the PSoC6 platform and there were some changes in the BSP header/sources that were made. Now I use the latest modus toolbox and library manager so I just took the original BSP and put then some changes from the previous old code base. I have noticed that the files have a notice in the header like
“This file shouldn’t be modified. It was automatically generated by.”
But I put the changes in the easiest way (I can reimplement them).
But when I issue the command make the files in the folder/ config/ GeneratedSource/ appear to be changed fully (looks like come in the original state).
So my questions here
1. Is it expected behavior? What the process of modus toolbox leads to this file change?
2. How I can be sure the BSP won’t be changed automatically coming time when I need to apply some patch for the stable figure?
What the process of modus toolbox leads to this file change?
Thank You
Read less
Hi @Vikas 1. Yes, this is the expected behavior. Whenever you do a build after making some changes in the design, Code is regenerated by a BSP Configurator and is stored in a directory named GeneratedSource, which is in the same directory as the design. modus file. 2. You can use the SKIP_CODE_GEN oRead more
Hi vikas Nagpal
1. Yes, this is the expected behavior. Whenever you do a build after making some changes in the design, Code is regenerated by a BSP Configurator and is stored in a directory named GeneratedSource, which is in the same directory as the design. modus file.
2. You can use the SKIP_CODE_GEN option in the make file to disable the code generation every time you make some changes
This information is provided in the Modus toolbox user guide Link
Thanks and Regards
See lessAlex