jbilander github - github.com/jbilander/POC86 PS: That mouse issue is nothing to do with the POC86 as such - it's explained in a follow up video =D NOTE: The BOSS signal I believe it handled by Buster and or logic on the 2000 motherboard. If some of that was replicated, the A2630 would work! The reason the A2630 doesn't work, it needs the 68K CPU on the motherboard. It is able to switch between the stock CPU and the 030 on the A2630! NOTE: LIV2 pointed out that the A2630 has a jumper to allow it to work when the 68K is removed! This was to support the 2000B, which didn't have full implementation of BOSS.
Simplified version of how zorro config works. (from what I remember) When the system boots, the first device in the config chain receives the config in signal. This causes the device to expose its configuration bits/registers/rom to the first 64K of the zorro expansion address space. The OS reads this data and can take a few different options depending on what type of card etc... If it is ram for example, it may add the memory to the free pool and then tell the card to 'shut up' When the card is told to shut up, it stops placing its config bits into zorro config space and send its config out signal to the next card and the process repeats until no more cards respond. Some of the options that the OS can take are. Simply tell the card to 'shut up'. For example, an 8MB z2 ram card but the system has already allocated all free z2 space. The OS can also move the 64K config/rom to a fixed 64KB address slot and leave it enabled. This can be ram/rom/io custom to the card, the rom can contain boot/config/driver code. There are 7 (I think) slots for zorro ii devices, cards can have more than 1x 64K zorro device per board. Zorro iii works in a similar way but has access to the full 4GB address space. Cards that don't generate a proper config signal 'hack' the zorro mechanism by assuming they are the only zorro device in use, and just place the config bits in config space without checking.
Thats not completely true. The TF card will only let the CPU "see" its autoconfig rom until its been configured. After that other cards on the bus can be seen. Since the A500 has no buster or autoconfig "chain" logic there can only be one more in the system
So the unusual comment about the flux in the solder smelling edible - the main brand of solder I tend to use, the flux always smells like dark chocolate to me... sooooo weird. 🙂
jbilander github - github.com/jbilander/POC86
PS: That mouse issue is nothing to do with the POC86 as such - it's explained in a follow up video =D
NOTE: The BOSS signal I believe it handled by Buster and or logic on the 2000 motherboard. If some of that was replicated, the A2630 would work! The reason the A2630 doesn't work, it needs the 68K CPU on the motherboard. It is able to switch between the stock CPU and the 030 on the A2630!
NOTE: LIV2 pointed out that the A2630 has a jumper to allow it to work when the 68K is removed! This was to support the 2000B, which didn't have full implementation of BOSS.
Simplified version of how zorro config works. (from what I remember)
When the system boots, the first device in the config chain receives the config in signal.
This causes the device to expose its configuration bits/registers/rom to the first 64K of the zorro expansion address space.
The OS reads this data and can take a few different options depending on what type of card etc...
If it is ram for example, it may add the memory to the free pool and then tell the card to 'shut up'
When the card is told to shut up, it stops placing its config bits into zorro config space and send its config out signal to the next card and the process repeats until no more cards respond.
Some of the options that the OS can take are.
Simply tell the card to 'shut up'. For example, an 8MB z2 ram card but the system has already allocated all free z2 space.
The OS can also move the 64K config/rom to a fixed 64KB address slot and leave it enabled. This can be ram/rom/io custom to the card, the rom can contain boot/config/driver code.
There are 7 (I think) slots for zorro ii devices, cards can have more than 1x 64K zorro device per board. Zorro iii works in a similar way but has access to the full 4GB address space.
Cards that don't generate a proper config signal 'hack' the zorro mechanism by assuming they are the only zorro device in use, and just place the config bits in config space without checking.
Thats not completely true. The TF card will only let the CPU "see" its autoconfig rom until its been configured. After that other cards on the bus can be seen. Since the A500 has no buster or autoconfig "chain" logic there can only be one more in the system
The issue will be that even with BOSS setup correctly both CPUs emit an E clock. The B2000 does a better job of this but its not passive.
So the unusual comment about the flux in the solder smelling edible - the main brand of solder I tend to use, the flux always smells like dark chocolate to me... sooooo weird. 🙂
Here's a shot in the dark, is it a memory mapping or jumper setting issue with the accelerator card?
There is actually a jumper on the A2630 to allow it to work without the 68K I think - LIV2 reminded me about that!
@@GadgetUK164B2000 mode right?