About diagnostic method of "IOM5A/IOM5B".

Hello Sazabi,

The intent of this is to use the analog loopback function to test that the pin has been configured as intended. A very basic test would be to enable the pin as GIO (non-functional) within module setup and then simply exercise the IO by toggling and check the input to insure it matches the output state.

However, many of the modules also recommend a test of function check where you would actually use the pins in functional mode in an analog loopback manner. For example, if the pin is SPIMOSI, you would send a SPI message out in analog loopback mode and check for the Rx message back. Similarly, CAN, HET and others can be checked for proper functions.

For direct answers to your questions:

Sazabi said:

(1-a) Can I implement "Analog loopback" to diagnose with "IOM5A/IOM5B" by implementing which signals are checked?

See information above. The analog loopback checks if the path through the output and input buffers is connected. If there is a mux configuration issue, the output buffers will not be connected so the loop back test will result in the same data on the input as on the output side.

Sazabi said:

(1-b) "signals traversing" is written, but as a diagnostic function of "IOM5A/IOM5B" Is there a way to check this electrical signal by mounting?

I am not certain what your question is for this. Singals traversing means the signal will pass through the configured output buffer and input buffers. What do you mean by "is there a way to check this electrical signaly by mounting?"

Sazabi said:

(2);
Although "the signal path from the module" is written, is there a way to confirm "signal path test" by implementation?

Again, I am not sure what you mean by this question? Are you asking if there is a way to test the path by a physical connection in the system other than using loop back? If this is your meaning, certainly one could implement a sequence with other devices in the system to diagnose configuration or connection issues. i.e., you could broadcast a diagnostic message(s) at power up that test the validity of the system networking. Since this would be a system level test, it is beyond the scope of the Hercules device, but you could include it as a custom diagnostic in the FMEDA to include it in your safety metrics calculations. This sort of thing would go under the Custom Diagnostics Tab.

Sazabi said:

(3);
Please tell me how to enable Analog Loopback of "IOMM". The corresponding register could not be read from the description of "IOMM Registers" of "Technical Reference Manual".

To be clear, the IO loopback is not a function of the IOMM module but rather the module(s) that you are configuring the pin access to. Once you configure the pin for SPI (as an example) you would go to the SPI module to test the SPI function in IO in loop back  mode.

Hello Chuck,

Thank you for the detailed explanation. understood.

I'm sorry I wrote a hard question to answer. I will ask questions by changing the contents of the description.

"Safety Manual" contains the following.
>> 6.13 I / O Multiplexing Module (IOMM).
>> 6.13.1 Notes
>> Software testing of the IOMM can be combined with peripheral loopback testing.
Also, Chuck wrote,
>> To be clear, the IO loopback is not a function of the IOMM module but rather the module (s) that you are configuring the pin access to.

(1) Can I satisfy the loopback test of "I / O Multiplexing Module (IOMM)" by implementing the loopback test of the peripheral module (eg SPI module)?
(Is it synonymous with "IOM 5 A / IOM 5 B" loopback test?)

Best Regards,

Sazabi

Sazabi said:

(1) Can I satisfy the loopback test of "I / O Multiplexing Module (IOMM)" by implementing the loopback test of the peripheral module (eg SPI module)?
(Is it synonymous with "IOM 5 A / IOM 5 B" loopback test?)

Absolutely, Yes! This helps drive efficiency. You will find that many of the diagnostics have overlap in the same way as these.