When a Source core is configured in slave clocking mode, the GUI allows me to select "global clocking" or "regional clocking" for the clock implementation option. However, regardless of the selection I make, the delivered example clock module implements "global clocking" when the core is generated. Regional clocking should not be a valid clock implementation option when the Source core is in slave clocking mode.
You must select "Global Clocking" implementation when the Source core is in slave clocking mode. No error message will appear if you select "Regional Clocking"; however, the design will be implemented using "Global Clocking".
The SPI-4.2 CORE Generator GUI will be updated to fix this problem in the next release.