Search results

Okay! Here's 0.7d. There are three variants: 0.7d's slowdown policy does not reference SCC accesses at all. This is what I hope to ship since I think the problem was related to interrupt latency, not slowdown. 0.7d-slowscc is the same as the regular 0.7d but SCC accesses and interrupts trigger...

@ppuskari Great news!! I think the WarpSE is almost ready for release. Soon I am gonna prepare version 0.7d which will come in two variants. I want to see, what in 0.7c fixed LocalTalk? Was it the interrupt latency or was it that we don't trigger slowdown on SCC accesses? So I will have 0.7d...

Thanks!!

@Kai Robinson As long as Petar's 15.6672 MHz clock is accurate, it should work. The 4-4-4-5 thing to get the 4.25x average divide rate does reduce the baud rate tolerance a bit, but it should be fine. Baud rates can be slightly off because the serial chip does 16x oversampling and can still...

We have been investigating various possible issues impacting LocalTalk. We thought we had the cause figured out but maybe not... Basically, when the 68k CPU receives an interrupt, it executes an "interrupt acknowledge cycle" on the bus. Long story short, due to the interrupt acknowledge cycle...

@JDW @ppuskari @JTRetro Since I'm going for the final slowdown rules in version 0.7b, I think there are several things to try: Audio sounds good? Maybe James can make another recording for us to compare LocalTalk works? No crash in the sound control panel? (I have determined this was due to the...

@phipli @JDW Hahah now thinking about it, I wonder if I broke a stereo using the Mac SE. While using it on the test bench, we had the SE audio going into a particular stereo receiver we used to play music in the Garrett's Workshop lab. Then we noticed the stereo was mixing the audio from two...

@JDW I think the issue is that you're missing the Microsoft Visual C++ Runtime version 2017. This is required to run a lot of programs, so why they don't include this in Windows, I don't know... Here's the link: https://aka.ms/vs/17/release/vc_redist.x64.exe Another beta tester on our TimeDisk...

Okay, I have version 0.7b ready now which does not have any variants. I am trying to "solve the puzzle" now on 0.7b. Hope it works! The slowdown policy in 0.7b is as follows: Slowdown is triggered for 196-210 microseconds after an interrupt occurs or when the sound buffer is written to. When...

Hmm I have been working on a new build system that will let me generate all 31 or whatever versions at once, but maybe I can just "solve the puzzle" now... @ppuskari the sound issue is due to the tight software-hardware timing relationship between the sound output and generation. If the CPU is...

@JDW don’t bother with it yet if you’re not going in to work anyway. I think it would be better for to get the slowdown register fully working first.

@JDW I would keep the 74LS245s since that's the same as the original. The 74F-series parts however should not be replaced with 74ACT and instead 74FCT or 74AHCT would be better.

Just sent the power boards to fab! These will let us reflash the WarpSE prototypes outside of the Mac for greater convenience. Like I said, production versions will just be able to power themselves through USB. Now some slightly bad news regarding the previous 0.7a version. Unfortunately there...

@JDW @Kai Robinson @iPhil64 Another thing that could be an issue is the use of ACT and LVC-series parts on the Reloaded boards. I would exclusively use 74AHCT-series parts instead, because 74ACT and 74LVC series have sub-nanosecond edge rates that can lead to ringing and signal reflections. The...

Okay! I have just finished version 0.7a, which comes in an inordinate number of variants. I will explain... The purpose of the 0.6 series was to get all the subsystems working reliably, but now we have to tune the exact parameters of slowdown in order to fix some of the remaining problems. Here...

@JDW I think one of the most likely possibilities is that there is an intermittent connection somewhere on your reloaded board. I have seen this many times in the past for various reasons. For example, I have a WarpSE prototype where the CPU is socketed in a surface-mount PLCC-68 socket. The...

The Mac should clear the RAM on boot, but I think it only does this if it doesn't see a particular magic number. Like, if you reboot quickly (edit:slowly) you'll notice that the Mac repeats the RAM test routine and it takes a little bit longer before the 1/2 black/white pattern on the screen is...

What I am wondering is, why does the WarpSE lose the enablement setting after the second bong? That should not happen unless power to the WarpSE is lost or the C8M clock is consistently high or low for 120 nanoseconds (it should only be high/low for 64 nanoseconds at the most). Can you re-check...

@ppuskari Petar, thanks for your help testing the latest version! Glad to hear the address error issue has been isolated. I will try the SCSI Director 4.0 drivers myself and try to see exactly what’s triggering the address error with my logic analyzer. As for the LocalTalk issues, there have...

@JDW, the curious thing is that the WarpSE should always “listen to” the /IPL2 line from the interrupt key when starting up. If it doesn’t and starts up anyway, that means that something along the lines of the WarpSE not receiving the signal or not receiving power is occurring. And if the WarpSE...