LUT output-muxing pin-swap #12

Closed
opened 2019-06-22 16:54:40 +02:00 by markus · 6 comments
Owner

Combination BA is not possible, will be BB instead.

Swap A and B on second MUX per chip to fix.

Combination BA is not possible, will be BB instead. Swap A and B on second MUX per chip to fix.
Author
Owner

Actually, that's not quite correct. To get the LUT Output Muxing table as shown besides the MUX, pin 12 (currently B) needs to be removed from the pad and shorted to pin 13 (A) next to it. Luckily, that bodge super easy to perform.

Actually, that's not quite correct. To get the LUT Output Muxing table as shown besides the MUX, pin 12 (currently B) needs to be removed from the pad and shorted to pin 13 (A) next to it. Luckily, that bodge super easy to perform.
Author
Owner

More thoughts on this. If I do this, I can never drive B to net 1 or 3. Essentially not a big deal as we can just swap LUT3-1 and LUT3-2 in SW.

But then, look at the second MUX. If we swap and drive the now-A to net 1, we cannot drive B to net 3. So maybe leave MUX U10 net 3 as is, and change the net-2 routing.

That way, I could ONLY drive B to net 2, but thanks to the LUT-swappery described above this may be OK.

Check the following: Cut U7 pin 12 (B), connect to 13 (A). Cut U10 pin 5 (A), connect to pin 4 (B).

More thoughts on this. If I do this, I can never drive B to net 1 or 3. Essentially not a big deal as we can just swap LUT3-1 and LUT3-2 in SW. But then, look at the second MUX. If we swap and drive the now-A to net 1, we cannot drive B to net 3. So maybe leave MUX U10 net 3 as is, and change the net-2 routing. That way, I could ONLY drive B to net 2, but thanks to the LUT-swappery described above this may be OK. Check the following: Cut U7 pin 12 (B), connect to 13 (A). Cut U10 pin 5 (A), connect to pin 4 (B).
Author
Owner

Another idea: Cut U7 pin 12 (B), connect to 13 (A). Cut U10 pin 13 (A), connect to 12 (B).

This gives us full flexibility on the first unit (using LUT swapping), and it guarantees full usability of the second LUT even when driving net-1 from LUT-0 (LUT-1 can be connected to either of the nets).

Only problem: net-2 and net-3 can never have the A/B combination.

PS: Forget it, this is BS. The first change is good. The second one doesn't help with the problem at hand -- that being the B-B connection. And there actually ain't a good way to bodgefix this. So I suppose we just leave the second chip as is. (Only A can be routed to net-1, so we should be able to route B to either 3 or 4.) The only downside to this will be that the combination of A/B is impossible or net-2/net-3. Unless everything is async.....

Another idea: Cut U7 pin 12 (B), connect to 13 (A). Cut U10 pin 13 (A), connect to 12 (B). This gives us full flexibility on the first unit (using LUT swapping), and it guarantees full usability of the second LUT even when driving net-1 from LUT-0 (LUT-1 can be connected to either of the nets). Only problem: net-2 and net-3 can never have the A/B combination. PS: Forget it, this is BS. The first change is good. The second one doesn't help with the problem at hand -- that being the B-B connection. And there actually ain't a good way to bodgefix this. So I suppose we just leave the second chip as is. (Only A can be routed to net-1, so we should be able to route B to either 3 or 4.) The only downside to this will be that the combination of A/B is impossible or net-2/net-3. Unless everything is async.....
Author
Owner

The only real solution is to Cut U7 pin 12 (B), connect to 13 (A) for the upper LUT, and then modify LUT-2 to use a_async. This should give us true full flexibility.

The only real solution is to Cut U7 pin 12 (B), connect to 13 (A) for the upper LUT, and then modify LUT-2 to use a_async. This should give us true full flexibility.
Author
Owner

Updated schematic to include bodge-fix in commit 4424d762f7.

Updated schematic to include bodge-fix in commit 4424d762f795f9c86a4c5bc972bd4f7345903f07.
Author
Owner

Kousaten has the fix since commit f27c728472.

Kousaten has the fix since commit f27c7284729ba3dc4c03d112314570a7f4ffca27.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: electronics/ttl-fpga#12
No description provided.