RT1175: how to generate different sources for M4 and M7?

[mastupristi]

Hi,

I am doing a project in which I use both M7 and M4 of an RT1175.
How do I make config tools generate different configurations (both by pin and clock) for the two cores?
In particular I need some pins to be initialized only by M4 and not by M7 and vice versa. But especially the clocks: I need M7 to program the clocks of the peripherals that he uses but not the ones that M4 will use, so that M4 can initialize them without “tweaking” the others.

How is it possible to achieve such a thing?

regards

Max

[EdwinHz]

Hi @mastupristi,

When creating a multicore project in MCUXpresso, two different linked projects will be created (cm7 and cm4), as you can see from the multicore example projects, we provide in our RT1170 SDK.

In the case of ConfigTools, an individual .mex file can be created for each project (cm7 and cm4), which is how you can create an individual configuration for each core.

BR,
Edwin.

[mastupristi]

Hi @EdwinHz 

that was not my question.

I use Config Tool stand alone. And I know very well that I have to create two different .mex files for the two cores. My projects have this layout. Config Tool generates code to initialize the clocks for each peripheral, though. For example ENET.

The question is, how can I make Config Tool not generate the configuration for a certain device (e.g., ENET)?

I ask this because M7 starts and configures the clocks, then starts M4 which in turn configures the clocks while M7 has gone ahead in execution. By the time M4 reconfigures FlexSPI M7 can hangs (this happens often).
But then why not take the clock configuration out of M4 at all? Because in debug sessions, when we don't run M7, no one would configure the clocks.
Hence the need for each of the cores to configure pins and clocks of the peripherals they use and nothing else.

regards

Max

[EdwinHz]

Hi @mastupristi,

Thanks for clarifying. I'm afraid there isn't a way of relating two .mex files for different cores in a manner that determines only one of them to be eligible for clock setup, and the other one to be ignored.

Both configuration files for both cores will have a clock initialization configuration, and it is up to the user to determine which one will be called at booting of the i.MX RT1170.

Sorry for the inconvenience this may cause.

BR,
Edwin.