the pins can be assigned from the Pins or the Peripheral Signals tab.
In the Peripheral Signals tab no warning is signalled, if the pin allready is used in another functional group.
Am I assigning the pins in a wrong way ?
first "Pins" and "Peripherals Signals" views do the same - routing pins, each one offers different look to the pins - how they are ordered.
Next, each functional group can route pins/signals the same or different. If the functional group is marked to be "Called from the initialization function", then the different settings is reported as conflict in the Problems view. If the functional group(s) are not "Called from the initialization function", then the conflict is not reported, as the tool does not know how you are calling the functions in the runtime.
thank you very much for your help.
Clears things up a lot.
How do I close this conversation and mark it as solved?
glad to hear it has been cleared. If you are logged on the community, you should see some button/link "Mark as resolved" or something like that. Probably it can be seen only by the author of the thread (I do not see it). Or it can be under "Actions" menu on my reply.
Yes, when I displays my very first message in the tread, there is a “Mark as assumed answered”
Fra: liborukropec <email@example.com>
Sendt: 27. november 2018 14:24
Til: Viggo Jørgensen <VIJO@tarp.dk>
Emne: Re: - Re: No warning if a pin is assigned in more functional groups in the pins tool
NXP Community <https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>
Re: No warning if a pin is assigned in more functional groups in the pins tool
reply from Libor Ukropec<https://community.nxp.com/people/liborukropec?et=watches.email.thread> in MCUXpresso Config Tools - View the full discussion<https://community.nxp.com/message/1084767?commentID=1084767&et=watches.email.thread#comment-1084767>
Retrieving data ...