Dear all,
I would like to ask you for clarifying a few issues regarding pinmux setting.
1) Preliminary question
Is it possible to change the pinmux setting more times (e.g. periodically) during the run-time?
- I guess that is allowed - only the locking mechanism must be applied (to write 2 lock values - magic constants).
- Anyway I have in my mind this procedure is not allowed and the pinmux can be set only once during the run-time (e.g. at the start-up). But I have not found any restriction like this within the Safety Manual SPNU540 May 2014.
According to the TRM SPNU563 May 2014 (chapter 6.6.1 Locking Mechanism for Memory-Mapped Registers), the answer seems to be YES...
2) Scenario
Our intention is to use the BGA balls (terminals):
- V2: for both signals N2HET1[1] as well as eQEP2A - both as input ones
- U1: for both signals N2HET1[3] as well as eQEP2B - both as input ones
During the run-time the both signals from the terminal V2 will be processed (by NHET and eQEP module) - in the sequence (periodically "switched" or switching based on the Condition A - see below), not simultaneously.
If the Condition A is true, the input signal on the terminal V2 will be "connected" to (processed by) NHET module.
If the Condition A is false, the input signal on the terminal V2 will be "connected" to (processed by) eQEP module.
Similar situation is applied for the terminal U1.
3) Alternative solution
According to the TRM SPNU563 May 2014 (the NOTE below Table 6-2. Input Multiplexing and Control on 337ZWT Package):
Inputs are broadcast to all multiplexed functions
The input signals are broadcast to all modules hooked up to a terminal.
So does this NOTE mean that the periodical pinmux switching (discussed in 1)) is NOT necessary? An application must decide (e.g. according to the mentioned Condition A) whether the input signal on the terminal V2 will be processed by NHET module or by eQEP module?
Thanks for your explanation,
Best regards, Jiri
