MCUXpresso IDE creating readonly files?

[netstv73]

Hello.

I'm using MCUXpresso IDE v10.1.1 [Build 606] [2018-01-02] and I have two issues.  One of them is the fact that read only files are getting created, so when you commit something into github for example and then you make changes (Using the Peripheral tool or the Pins tool) and you want to back out those changes, you get an error.

Maybe I'm just missing something obvious when you install a new project.

I created a new project using the "New Project" Quick start panel.

I create a project for my FRDM-K28F

I pull in many fsl modules.

and I create a baremetal with a shell and debug_console etc.  

I pull in essentially everything but FreeRTOS stuff.

I build it and then I created a github repo and committed everything.

I then screw up my build and it doesn't work.

So I go to revert my changes (ie using `git checkout `)

And on OSX I get the error...

error: unable to unlink old 'board/peripherals.c': Operation not permitted

error: unable to unlink old 'board/peripherals.h': Operation not permitted

error: unable to unlink old 'board/pin_mux.c': Operation not permitted

error: unable to unlink old 'board/pin_mux.h': Operation not permitted

So on OSX I need to go and change the rights.  (ie chflags nouchg board/*)

I'm SURE I'm missing a preference somewhere... 

Thanks in advance.

Steve

[netstv73]

Thanks Marek.  

I was hoping to get around that.  I usually work with a hardware engineer and he usually sets stuff up like this and then I will take the generated code and make tweaks to it later.  Looks like I'm gonna have to find a new way of doing it.

Thanks for the info.

-stv

[marek-trmac · Accepted solution]

Hi Steve,

pin_mux.*, clock_config.* and peripherals.* might be generated from Config Tools (Pins, Clocks, Peripherals). These tools regenerate the files completelly and to avoid any manuall changes, the files are generated read-only. You do not need to put these files into GIT as they can be re-generated any times later (settings is stored in .mex file).

Hope this clarified your problem,

regards

Marek