Hi Insatman,
I'm the designer of this replacement. I figured I would give some insight of things I've run across having built a number of these now.
a) you did mention that you had solder bridges that you fixed after already testing them. You likely already fried the chips at this point. I can't say for sure which pins would or wouldn't cause the chip to die but my first build I also had a solder bridge and the chip was dead.
I also had an issue earlier this year with some flux that was highly conductive without me realizing it, and fried a number of chips during testing because I've usually tested before washing to avoid having to wash twice if I have to do any rework.
b)Ever since I switched to a solder paste workflow I've had none of the aformentioned issues and I highly suggest if people have the tools to use solder paste with standard QFP and TSSOP stencils. If you're using external flux, you have to make sure that the board is absolutely spotless. This is hard to do with flux that gets under the chips unless you have an ultrasonic cleaner.
c)Lastly I'm not sure how you're programming these, but I've found the TL866 (which is most people's go-to cheap programmer) extremely unreliable with the DS1486 in DS1245 mode. I really don't know what the cause is of the issue but I find often that data at the beginning of the chip is unable to be read correctly meaning if you try to make a binary dump of the data, you better be sure you don't have a bunch of FF in the first 0-100 rows. Each read tends to give me a different amount of data, yet the chips work fine in my scope, including the clock which is the first row of data. I have a theory that the TL866 might be trying to read the data too quickly after applying power. It looks like the DS1245 has a startup time of 125ms while the DS1486 is 200ms. I need to see if I can apply 5V externally without damaging the programmer to test this theory. I suppose I could lift the power pin to try that.
I recommend using the tektool or tekfwtool process that has been documented on this forum reasonably well.
Hope this helps you and anyone else working on this.
Yes I had heard that the 784D should have booted even without the DS1486 replica being programmed. So something must be wrong. I built two examples and both exhibit the same behavior, both in the programmer and the 784D. Note when I attempt to boot the 784 the numeric display oscillates between 6 and 8, if that means anything.
That sounds like the DS1486 is in test mode. This causes one of the pins to oscillate at a frequency, 512hz IIRC to allow you to measure the frequency of the internal crystal. This will of course result in unpredictable behavior of whatever device it is installed in. I ran into this some time back when I was trying to program a similar Dallas RTC in a regular EPROM/flash programmer. Read the datasheet and it explains how to enable and disable test mode, I ended up using an arduino mega and wrote a little program to do it.
The replica DS1486 is based on the DS1384G. Looking at the datasheet of the DS1384G, I cannot find any mention of a test mode.
From the DS1384 datasheet: "SQW - Square Wave (output): This pin can be programmed to output a 1024 Hz square wave signal.
When the signal is turned off, the pin is high Z."
On the DS1486 this is shared with the /INTA pin. Have you tried scoping the pins to see if one has a square wave on it?
I have checked pin 30 on the DS1486 replica and got nothing but a little noise. I do see 32kHz on the crystal, so at least that is working.