After typing sys1024 and m9000 9000 here is what I seeThe value in the accumulator does match the rom dump for sure. So with the rom installed, type sys 1024 to enter TIM and then m 9000 9000 to display the first 8 bytes at that memory location. It maybe still pointing to the SP ram.
Yes, that's correct, u11/12 are blank, what kind of emprom should be there and what kind of rom image should be burned into it? This week I will be preparing the missing pair of switches responsible for running the ram/rom u11/12That usually indicates that there is no EPROM in the socket $9000 UD12 socket. Is the UD12 switch hooked up correctly?
No EPROMs are needed. The switch is just to allow one to be used if wanted. The NOROM signal is not compatible with EPROMs so the switch is a kind of work-around.Yes, that's correct, u11/12 are blank, what kind of emprom should be there and what kind of rom image should be burned into it? This week I will be preparing the missing pair of switches responsible for running the ram/rom u11/12
If I understand correctly the u11/12 slots should contain an emprom 2532 along with a rom image of whatever we want to have "at hand" in my case I care about "Waterloo structured basic" addon to basic 4 for 6502No EPROMs are needed. The switch is just to allow one to be used if wanted. The NOROM signal is not compatible with EPROMs so the switch is a kind of work-around.
If I understand correctly the u11/12 slots should contain an emprom 2532 along with a rom image of whatever we want to have "at hand" in my case I care about "Waterloo structured basic" addon to basic 4 for 6502
If I understand correctly the switch allows to choose if the emprom code or the extra ram should be active? The question is if it adds +4kb or +64kb?
Could the lack of this switch cause the error seen in earlier posts? On the screen
Thank you very much for all the answers.Yes. You can try EPROM anytime in 6502 mode only. If you want to go to 6809 mode without crashing, you will need UD11/12 switch in place.
in 6502, you get 4K EPROM data or 4K paged RAM data at $9000.
Since you had no EPROM installed, no I don't think so.
Unfortunately I'm still looking for a suitable programmer for rom 2532First thing, have you used my PETTESTER ROM to test out the 6502 PET itself?
Second thing, I did ask a question back in post #5 about how you are loading programs into the 6809.
If I remember correctly, there are some diagnostics for the SuperPET. I can’t quite remember at the moment where they are though...
I am currently writing a SuperPET memory tester for use in a 6502 ROM socket. But this is a longer term project than your timescales though!
With this method I successfully loaded any program up to 20kB, including the floppy tester, the aforementioned PIP for copying data from server to floppy, com-master and other programs>>> Programs for the 6809 are loaded in the following way
I connect my laptop with Linux to monitor in P mode and load files to SuperPET memory directly via rs232 cable.
Are you sure that works? I am not...
I use hostcmYou go into the Waterloo Monitor and type 'p'.
You log into your remote machine.
What do you then type to perform the load?
This is why I am suggesting using HOSTCM on your remote machine, that is guaranteed to work (he says)...
I'm not sure but I think you're looking in the wrong place. If any of the connection steps were wrong no program would load properly.OK - I understand more now...
So, I am not sure what you are using the waterlooMonitor 'p' command for?
It looks like you are trying to start HOSTCM on the remote machine via the SuperPET using the serial port. Is this correct? If so, you are trying to use the serial port for two different (and potentially incompatible) things - the serial terminal and the HOSTCM protocol - concurrently.
The other possibility is you are overrunning the serial port at the baudrate you are using - either due to missing hardware handshake lines or something is not setup to use the hardware handshake lines. How is the serial cable constructed (pinouts)?
I am just throwing out a few ideas for you to consider.
Don't be misled by the errors in the earlier screenshots. These were the only photos I had at hand. It took me two days to configure everything so that it does not generate any errors. Everything is working now, programs are uploading without any problems. I still have problems with Waterloo software and programs larger than 20kB, as if ram expansion board is not working properly or one of chips translating ram address.I am looking at your posted photographs and seeing the duplicated text and error messages that are displayed. This is indicative that something is clearly amiss between the SP9000 and HOSTCM to me.
I am sure you have read this http://mikenaberezny.com/wp-content/uploads/2015/03/hostcm_tutorial.pdf but, unfortunately, it is not for the Linux/Windows variant of HOSTCM.
You shouldn't be getting the error messages etc. that you appear to be getting if things are setup correctly.
Actually, if the connection steps were wrong, this is exactly the behaviour you could observe - that of working with small programs and not larger programs.
Just my ten pence/cents. Please ignore if you wish.