I'm curious what burst mode was on the 68030 and
It's an extension to the 68020 bus protocol offered by the 68030. By default, all read access on a 68k takes two cycles. Cache Burst uses the same two-cycle synchronous access for the first word but reduces any of the three subsequent accesses to a single cycle, thus reducing the time for a cache line of 4 words to be loaded from 8 clocks down to 5 (*1).
Works in detail:
First of all, the bus must operate in synchronous mode, that is
DSACK0/1 is always set high from the memory control and access is always 32 Bit.
Next, when the CPU is filling the cache and a burst would be possible, it signals that by asserting
CBREQ (Cache Burst REQuest) at the beginning of the first cycle.
The memory control has to signal its ability (and acceptance) by pulling
CBACK (Cache Burst ACKnowledge) before the falling edge of the second cycle of the first word accessed.
If the CPU sees
CBACK in time, all subsequent access to fill the cache line will be done in single cycles.
To tell so,
DS stay asserted until the last word read.
The end of an burst cycle is signalled at the end of memory access by removing
AS (and of course
why wasn't it [burst access] supported on the A2630 accelerator card commonly found in the Amiga 2500/30?
Quite simply because the Amiga 2500 was (more or less) a rebadged A2000 (68000-based) with a coprocessor card. Thus its memory interface was 16-bit, not 32-bit as required for burst mode.
For what it's worth, my A2500 rig had 4MB of RAM on the A2630 card [...] I would have thought it made a difference on the accelerator card itself.
Looking at the schematics shows that they took the A2620 (68020-based) design, clipped out the MMU (68851), reduced the chip count, but left basic workings the same - meaning no support added for bus protocol extension for burst. It was up to the never-released A2631 with its new bus controller to make an upgraded A2000 really work like an A3000.
*1 - so even if all access were linear (and cached), savings could only reach 3/8th or 38.5%. In reality, with all data access mixed in and jumps out of cache before a line is exhausted and so on, a real speed up of 1-3% can be achieved - keep in mind, this is in addition to the speed up due to the cache itself.