Can all registered uses please login, even just for a few minutes..
It helps build a picture where our "good traffic" is coming from..
Thanks :)
It helps build a picture where our "good traffic" is coming from..
Thanks :)
CURRENT PROTOTYPE STATUS (SEC 64MHz 68000)
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
Tiny update.. PCB's finally arrived
Need to do a order to mouser and get the ATF chip and some other bits next...
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
Small update.. Parts now ordered for this.. I'm going to ship the three boards and parts to a place in the UK for assembly as I just do not have time to do it. So hopefully in a few days time I can get the boards back and actually start working on the firmware.
Just as a re-cap, this board is the 68SEC000 test board, so I can see what the maximum speed of the CPU is. I am hoping to get it running at 50-64Mhz.
Even if the CPU cannot manage much more than the 68HC000 PLCC CPU, I will likely still use the SEC simply due to it is smaller, and a proper SMT package. With all the problems I am having with sockets, I have no choice but to move to a direct soldered part anyway. So moving to the 68SEC000 CPU is basically a good move anyway.
Just as a re-cap, this board is the 68SEC000 test board, so I can see what the maximum speed of the CPU is. I am hoping to get it running at 50-64Mhz.
Even if the CPU cannot manage much more than the 68HC000 PLCC CPU, I will likely still use the SEC simply due to it is smaller, and a proper SMT package. With all the problems I am having with sockets, I have no choice but to move to a direct soldered part anyway. So moving to the 68SEC000 CPU is basically a good move anyway.
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
PCBs finally arrived... next to find time to finish firmware and test it.. but likely will finish the plug in STE booster first...
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
Finally cleared my table.. Now to work on the firmware..
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
So something amiss, anyone any ideas whats going on here ?
EDIT:
I tried removing AVEC from my code just to see what happens, and diag-cart says autovector error.. so that much be working... but still no idea whats going on with the DMA errors unless some sort of bus grant issue
EDIT:
I tried removing AVEC from my code just to see what happens, and diag-cart says autovector error.. so that much be working... but still no idea whats going on with the DMA errors unless some sort of bus grant issue
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
$FFFFFC00 and $FFFFFC02 are adresses for Keyboard ACIA .. so there might be something going on with VPA/VMA there.
The 2 other one are code on the cartridge port.
The 2 other one are code on the cartridge port.
Working ones : MegaSTE (68020) / TT030 / Falcon with AB040 & Eclipse / 1040STF
Need testing : Falcon with CT2
Need testing : Falcon with CT2
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
Its odd, because I see activity on VMA, but not VPA or AVEC ... but VMA shouldn't go low without VPA being low to start with ?!
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
Is the E clock running properly ?
AVEC should definitely do something on interrupt from the keyboard. But if we can't write to the ACIA it probably doesn't trigger interrupt yet.
So it's really around VMA/VPA
AVEC should definitely do something on interrupt from the keyboard. But if we can't write to the ACIA it probably doesn't trigger interrupt yet.
So it's really around VMA/VPA
Working ones : MegaSTE (68020) / TT030 / Falcon with AB040 & Eclipse / 1040STF
Need testing : Falcon with CT2
Need testing : Falcon with CT2
Re: V2.5 BOOSTER CURRENT PROTOTYPE STATUS
Looks good on scope..
No idea, I keep trying things, but no luck..rpineau wrote: Mon May 21, 2018 9:08 pm AVEC should definitely do something on interrupt from the keyboard. But if we can't write to the ACIA it probably doesn't trigger interrupt yet.
So it's really around VMA/VPA
If I keep pressing reset, I see VMA pulse low.. though I half recall it does pulse more than VPA.. will have to re-read my notes tomorrow..
VPA I have trouble seeing any pulses.. but thats generated from GLUE anyway...
I don't get why diag-cart says DMA time out.. has nothing to do with CPU really
