Dear all,
we have faced a strange issue - compared to the behavior expected by us ;-) Let me describe our scenario:
Our application accesses to the ball E18 via HET module set as GIO output - so acting as a simple binary output.
- Pinmux: N2HET1[08] connected to the ball E18 (default setting)
- SPI1: this peripheral is active (just the simple SPI1, not the multibuffer variant) and sends data only via one channel (MIBSPI1SIMO[0])
- The HalCoGen default setting of the SPI1 and MIBSPI1 port (MIBSPI1SIMO[1]) is FUNC input and that has not been originally modified by us.
- If the ball E18 is driven to "1" via the signal N2HET1[08] (HET register for SET operation), the communication via SPI1 channel is being corrupted!
- I am not sure whether the source of this impact is the rising edge or the high level ("1") of this signal....
- We are very surprised of this influence - our assumption was that the E18 signal is only connected to the HET module by the pinmux moduleand cannot disturb the SPI module anyhow....
- If we explicitly modify SPI1SIMO[1] pin mode within the SPI1 port as well as the MIBSPI1 port within HalCOGen, the SPI communication works properly.
- SPI1SIMO[1] is manually set as the GIO output.
Code is generated by HalCoGen version 04.05.02 (but the code generated by the previous version behaves in the same way).
Please, gentlemen, any ideas or explanation of this behavior? Have I overlooked something?
Thanks and best regards,
Jiri