[FAQ] AM625 / AM623 / AM62A / AM62P / AM62D-Q1 / AM64x / AM243x Design Recommendations / Custom board hardware design - Queries related to SysConfig-PinMux IOSET and Voltage Conflict

Hi Board designers 

Refer below inputs:

Voltage Conflict 

Signals a grouped by function/domain, not power domain. It is therefore possible to encounter voltage conflict warnings with some peripherals. This is a warning to highlight a difference between the preferred voltage and the actual pin voltage so you can take any necessary action should there be a real conflict.  Most useful when grouping GPIO signals from different voltage domains. 

This is because the current tool configuration only allows one preferred voltage per peripheral. Where peripherals that include pins with different voltages, a warning will be present.

The warning shows because the preferred voltage is a different level than the pin voltage (eg. Preferred voltage is 3.3V V while the pin voltage is 1.8 V) .This warning can be suppressed as long as 1.8 V is the intended voltage for selected pins.

This is not a hardware issue or a tool bug, its a notification for the preferred voltage is different than pin voltage configured. 

These warning are there simply to highlight the conflict between preferred voltage and power rail voltage selection. A long as you understand this, the warnings can be suppressed.

Example:

MCU_PORz, MCU_ERRORn are referenced to VDDS_OSC0 IO supply rail, and such operate at 1.8V.  There is no option to operate these IO at 3.3V.

The tool may be warning that these IO cannot operate at the 'preferred voltage setting of 3.3V'.  There is not issue if your design understands these IO are 1.8v and other IOs can be set to 3.3V

Note: MCU_PORz is 3.3V tolerant and fail-safe

IOSET 

IOSets define groups of pin that can be used together for a peripheral interface. In most cases this is a timing restriction in order to meeting the datasheet timing and switching characteristics.  Only a few peripherals have such restrictions.. 

You can see the list of IOSets from within the tool by selecting "IO Sets" from the 3-dot menu on the top right of the tool.

You can use the "Use Cases" menu  to select functional collections of pins for the interface.   

The device is timing closed using IOSets.  These are a collation signals specific to an interfaces that a timed as a set. Any interface that has IO sets must select all interface signals from the same IO set.  Some interface signals may be shared over multiple IO Sets. 
The tool enforces these IO set requirements

You can view which pins/balls are in an IOSet be enabling the IOset view:

You can see the reason for a conflict by hovering the mouse pointer over the "Resource conflict" message. for example:

Regards,

Sreenivasa