flamewing wrote:Ah, yes, because looking at completely unlabelled transistor-level schematics and figuring out what each transistor is doing, and what signal each wire corresponds to, is extremely easy.
Yes. For me, who is not familiar with transistor stuff is not easy to figure out what it is:
I had to google "transistor notation schema", to find something close, but closest what I've found is here:
Implying that those two types of elements on first picture corresponds to elements on this one...
I still have no idea. It makes no sense to me.
More details. I suggest two possibilities:
1) With thin line corresponds to element without circle, and element with bold line corresponds to element with circle.
Thus, in case if we have ground on pin from bottom, then bottom right element is closed, thus ground from nearest to it is opened and two other ones is closed, thus all vcc on picture is closed. it's okay.
In case if vcc on pin from bottom, then vcc at bottom right is open, thus nearest ground is closed and two other elements is opened, thus all vcc on picture is opened, but bottom left vcc opens top left ground thus top pin has ground & vcc opened at same time which is no sense to me
2) With thin line corresponds to element with circle, and element with bold line corresponds to element without circle.
This case has similar confuse.
looks like I'm mixed up vcc and vdd. :s checking.
flamewing wrote:It was made with data obtained from real hardware; so I left implied that it passed. But to be more explicit: I had a few people test it with their flashcarts on real hardware, and the ROM passes every abcd, sbcd and nbcd test. So the code I gave matches real hardware on every possible input combination.
Nice! Awaiting full source
I did kinda same but without generation, and relying on gcc.