13:13 <tnt> Mmm, in non-pipelined wishbone, can CYC ever be different from STB ?

13:33 <ZipCPU> tnt: No.

13:33 <ZipCPU> Well ... I take that back. I might have to look that up again.

13:35 <ZipCPU> According to my protocol checker, CYC must be high whenever STB is true, but STB doesn't need to be true when CYC is true

13:35 <ZipCPU> Ahh, yeah, that's right ... STB is used to select a particular slave, CYC to indicate that the bus is active

13:35 <ZipCPU> So if you have multiple slaves on a bus, CYC will go high when one of them is activated, STB will go high when the particular slave is activated.

13:36 <ZipCPU> The big purpose of CYC is for interconnects and/or arbiters. If CYC is true and master A is connected to slave B, then no other master can connect to slave B until master A lowers CYC

13:37 <ZipCPU> I've used it for locking--even though there is another bus LOCK signal

13:38 <tnt> Ah yeah, I see, if you want to prevent the arbiter to re-assign the slave to another master between two transactions ?

13:38 <ZipCPU> Yes.

13:43 <_whitenotifier-f> [whitequark/libfx2] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/Jf9B4

13:43 <_whitenotifier-f> [whitequark/libfx2] whitequark 891dbcf - Bump version.

13:43 <_whitenotifier-f> [libfx2] whitequark created tag v0.9 - https://git.io/fjAQS

13:44 <_whitenotifier-f> [whitequark/libfx2] whitequark tagged 891dbcf as v0.9 https://git.io/Jf9BB

13:45 <_whitenotifier-f> [libfx2] Success. The Travis CI build passed - https://travis-ci.org/github/whitequark/libfx2/builds/697225548?utm_source=github_status&utm_medium=notification

13:45 <_whitenotifier-f> [libfx2] Success. The Travis CI build passed - https://travis-ci.org/github/whitequark/libfx2/builds/697225543?utm_source=github_status&utm_medium=notification

13:45 <_whitenotifier-f> [libfx2] whitequark commented on pull request #4: Add standalone url field to fx2 setup.py - https://git.io/Jf9Bz