You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found an issue in duplication mode of SPI expander. It occurs in situation when master wants to duplicate output data to multiple slaves. If slaves use adjacent channels like SS3 and SS4 and master decides to activate them simultaneously the first slave (SS3) is activated by SS signal one period of SCK signal prior the another slave (SS4). It means that the first slave gets first byte shifted by one pulse of SCK prior the second slave.
Here is the correct function of expander. One master transmits to one slave.
Here is incorrect function of expander. One master transmits to two adjacent slaves. The slave select signal for the slaves is not aligned ant the first slave catches a misaligned data on MOSI signal.
The solution is not to place same slaves side by side to each other.
The text was updated successfully, but these errors were encountered:
Hello,
I have found an issue in duplication mode of SPI expander. It occurs in situation when master wants to duplicate output data to multiple slaves. If slaves use adjacent channels like SS3 and SS4 and master decides to activate them simultaneously the first slave (SS3) is activated by SS signal one period of SCK signal prior the another slave (SS4). It means that the first slave gets first byte shifted by one pulse of SCK prior the second slave.
Here is the correct function of expander. One master transmits to one slave.
![SPI expander correct](https://user-images.githubusercontent.com/46750178/74919969-ac282500-53cb-11ea-9e2a-ed1de121a34c.png)
Here is incorrect function of expander. One master transmits to two adjacent slaves. The slave select signal for the slaves is not aligned ant the first slave catches a misaligned data on MOSI signal.
![SPI expander NOT correct](https://user-images.githubusercontent.com/46750178/74920126-f01b2a00-53cb-11ea-94f2-1741ebbf3bb8.png)
The solution is not to place same slaves side by side to each other.
The text was updated successfully, but these errors were encountered: