marko wrote:
floobydust wrote:
I've been using WDC Tools for over 7 years now... TIDE has it's issues, but I've managed to use it as part of my dev environment. As for the WDC SXB, I'd just yank the EEPROM and reprogram it to use the ACIA port with a Serial to usb adapter as a console. Granted, the W65C51 has the Xmit bug, but you can work around that as well. You should be able to add a newer UART to it via the expansion port.
I've got the 65C02 and 65C816 SXBs, but haven't gotten around to porting my BIOS/Monitor over yet... but the source is on my Github page. They are decent boards, but as Andrew noted, they only software is to interface to their debug code, which I don't care for.
Floobydust - Can you help with this please?
Can I program the eeprom without an adaptor? I have a TL866 programmer but no PLCC adaptors.
The other question I have is re: TIDE...It looks like a grown up way to consolidate all the command line stuff etc except almost every option kicks up 'Failed to set data for version'. I gave up after an hour of adjusting windows for compatibility issues.
I'd like to persevere with everyones help on here...
Hi Marko,
Well, if you pull the EEPROM out of the SXB, you will need some way to get it connected to any programmer, hence an adapter. Granted, you could likely make your own adapter and get it working that way.
Alternately, looking at the schematic for the SXB, the WE (write enable) line for the EEPROM is connected to the WE signal (same as the RAM). Looking at the Datasheet for the EEPROM, you can program it insitu. However... this can be a challenge. You do need to be able to download code to the SXB (using the WDC tools) which will program the EEPROM, but you also need to ensure you're loading code that will function on the board. If you overwrite the main code and your's doesn't work, the board becomes nonfunctional.
As for TIDE, I'm using WDC Tools under Win7 running in a VM under Fusion. The WDC Tools were written back in the WinXP (or earlier era)... so I'm not sure how well it will run on the latest release of Windows. As a simple test, you might want to try using the attached monitor/BIOS source code. All of my code was assembled/linked using WDC Tools using TIDE, hence there is a .wdc file which you can load, then click on the assemble/link icon at the top. If it doesn't work, you might have to change the location of the source code (to match the path info in the .wdc file), or edit the .wdc file for path information.
Attachment:
V104.zip [116.8 KiB]
Downloaded 143 times
If you can't get this code to work with WDC Tools using TIDE, then you likely have a system issue, i.e, DLL, Path info, incompatible code , etc. NOTE: The Monitor code has a routine which will program the Atmel 28Cxxx EEPROMs insitu, which I believe is similar to how the SST EEPROMs are programmed. Let me know if the above works for you.