News for hackers. Stuff that matters.
Re:The KimKlone: a radical 6502 redesign by dfox on Tuesday October 04, 2011 @12:27PM (#3071644)
Which is probably the case also for this hack. It's probably possible to devise logic that would remove this limitation, but I assume that would be mentioned in the article.
Re:The KimKlone: a radical 6502 redesign by 0x12 on Tuesday October 04, 2011 @03:14PM (#3072414)
Read the article, he's thought of that. There is a trick with two registers in there that allows you to pivot from one bank to another.

More explanation in the appendix on the instruction set. The opcodes are 13, 23, eb and fb:

http://www.laughtonelectronics.com/arcana/BrideOfSon%20KK%20...

Bottom of the list.

Re:The KimKlone: a radical 6502 redesign by dfox on Tuesday October 04, 2011 @06:10PM (#3073145)
It allows you to jump between banks, but not to overflow from one bank to another without explicit jump on the boundary.
Re:The KimKlone: a radical 6502 redesign by rbanffy on Tuesday October 04, 2011 @12:46PM (#3071744)
You can always check if all address lines transitioned from 1 to 0 on an instruction fetch and increment whatever you use for PBR...
Re:The KimKlone: a radical 6502 redesign by dfox on Tuesday October 04, 2011 @06:18PM (#3073172)
It's conceptually simple, but there are two problems:

1) you have to detect near jumps that jump back inside one bank. (at least from instruction ending on 0xffff to instruction starting on 0x0000, on the other hand you can plausibly ignore this as it is very unlikely case)

2) more importantly, I understand that this coprocessor contraption does not interact in any way with lower 16 bits of address bus. You would need to actually snoop on address bus and detect the wraparound and as this thing is built from MSI logic, detecting transition 1 -> 0 on all bits of address bus - while conceptually trivial - would require significant amount of hardware. You can detect 1 -> 0 transition only on 15th bit of address, but then you really need to detect jumps in microcode and disable this logic in case of jump.