CST Ram Plus eproms - CST QDisc v4 issue
- chriskgnr
- Bent Pin Expansion Port
- Posts: 98
- Joined: Wed Jan 09, 2013 12:26 pm
- Location: Piraeus, Greece
CST Ram Plus eproms - CST QDisc v4 issue
HI to all!
Recently i purchased a 512KB CST Rom Plus card. I want to ask which eprom programs i can burn to populate the four empty rom sockets.
Secondly, i assemble a CST QDISC v4 floppy disc controller, but it is not recognized on boot screen(green letters on upper part of screen "CST 1.18" etc..).
I replaced all 74LS ics, used a wd1772 instead of 1770, burned two more different firmwares on eproms, replaced 8Mhz XTAL, tested continuity from component to solder side vias, with no avail. Any ideas for further testing?
Recently i purchased a 512KB CST Rom Plus card. I want to ask which eprom programs i can burn to populate the four empty rom sockets.
Secondly, i assemble a CST QDISC v4 floppy disc controller, but it is not recognized on boot screen(green letters on upper part of screen "CST 1.18" etc..).
I replaced all 74LS ics, used a wd1772 instead of 1770, burned two more different firmwares on eproms, replaced 8Mhz XTAL, tested continuity from component to solder side vias, with no avail. Any ideas for further testing?
Re: CST Ram Plus eproms - CST QDisc v4 issue
There is a manual for the CST RAM Plus card at https://dilwyn.qlforum.co.uk/docs/manua ... amplus.pdf (in case you didn't get one with it).
--
All things QL - https://dilwyn.qlforum.co.uk/index.html
All things QL - https://dilwyn.qlforum.co.uk/index.html
Re: CST Ram Plus eproms - CST QDisc v4 issue
Most of the "Rommable" toolkits can be put into Eprom - I am not sure what address they appear at in the QL memory map though.
Re: CST Ram Plus eproms - CST QDisc v4 issue
Hi
No real help but:
When you programmed the 27128 did you program in the correct bank ?
Are you using Minerva, don't know if they can co-exist
No real help but:
When you programmed the 27128 did you program in the correct bank ?
Are you using Minerva, don't know if they can co-exist
-
- Trump Card
- Posts: 152
- Joined: Tue Nov 30, 2021 1:19 am
Re: CST Ram Plus eproms - CST QDisc v4 issue
I would at least try a logic probe on eprom select (pin 22 /OE) to see if after a reset it is at least polled to help start narrowing problem down.
Edit: removed text about jumbled roms; V4 is jumbled
Edit2: I use 'jumbled' (not scrambled) since that is what QEP III uses.
Edit: removed text about jumbled roms; V4 is jumbled
Edit2: I use 'jumbled' (not scrambled) since that is what QEP III uses.
Last edited by ones' complement on Sat May 11, 2024 1:04 pm, edited 2 times in total.
-
- Aurora
- Posts: 947
- Joined: Sat Oct 25, 2014 9:53 am
Re: CST Ram Plus eproms - CST QDisc v4 issue
Hi all!
If indeed the v4 board uses the 'scrambled' method for data and/or address lines and if the ROM was programmed in a std programmer from a straight image, then therein would certainly lie one probable cause...
A quick check would be to PEEK_W from Basic the base address where the CST ROM is expected to lie in the memory map (0x0c000 is the first likely location) and check the returned word value, which should be the QDOS ROM flag (0x4afb, if I remember correctly.)
If it's not that, QDOS will skip that 16kB block and look elsewhere.
Then compare that against the first word of the original ROM image.
Again, the above assumes that the EPROM was programmed from a provided image as part of the self-build...
If indeed the v4 board uses the 'scrambled' method for data and/or address lines and if the ROM was programmed in a std programmer from a straight image, then therein would certainly lie one probable cause...
A quick check would be to PEEK_W from Basic the base address where the CST ROM is expected to lie in the memory map (0x0c000 is the first likely location) and check the returned word value, which should be the QDOS ROM flag (0x4afb, if I remember correctly.)
If it's not that, QDOS will skip that 16kB block and look elsewhere.
Then compare that against the first word of the original ROM image.
Again, the above assumes that the EPROM was programmed from a provided image as part of the self-build...
Re: CST Ram Plus eproms - CST QDisc v4 issue
I had problems with 2 components in the past:
The transistor, chinesse ones are slow or something and got no boot message of the card.
Also 74ls04 chinesse for the oscilator cause me problems, in this case you got boot message but not recognice the board (the board shall show boot message even without wd177x
And you shall use a 27F128, for example, if you use a EEPROM W27C512, remember that you need to Burn It 4 times, or at least in the last 16kb of the chip, because the interface only use the last 16kb o f the 64 that has a W27C512.
You shall use the file CSTQD118.ROM the other one , unscramble, not work on the interfaz
The transistor, chinesse ones are slow or something and got no boot message of the card.
Also 74ls04 chinesse for the oscilator cause me problems, in this case you got boot message but not recognice the board (the board shall show boot message even without wd177x
And you shall use a 27F128, for example, if you use a EEPROM W27C512, remember that you need to Burn It 4 times, or at least in the last 16kb of the chip, because the interface only use the last 16kb o f the 64 that has a W27C512.
You shall use the file CSTQD118.ROM the other one , unscramble, not work on the interfaz
- chriskgnr
- Bent Pin Expansion Port
- Posts: 98
- Joined: Wed Jan 09, 2013 12:26 pm
- Location: Piraeus, Greece
Re: CST Ram Plus eproms - CST QDisc v4 issue
Hello again!
I populated the CST Ram Plus card and i have some questions. I used 2N2222A instead of MPS2369. Both are NPN transistors and from the datasheets they seem to be interchangeable? Second, at the block diagram the lower right resistor is a 47KΩ or a 4.7KΩ resistor? And final, all eproms are indicated as 27256 on diagram. 27128 are not recommended?
@dilwyn
thanks for the manual.
@Pr0f
that is what i think, TK2, ICE, maybe 68K/OS, or programming languages that were partially on rom cartridge.
@Chris_68
The v1.18 bin file is a 16KB file if a remember correct. I burned two other 27C128 eproms and i am sure one file was 8KB and wrote it twice, on lower and upper bank but using first the HxD editor for doubling it.
@ones' complement
unfortunately i don't have a logic probe
@martyn_hill
and i am almost sure that i programmed the unscrambled v1.18 image.
@aalea About 2N2222A transistor, i don't know if it is a chinese the ones i have, but i used both plastic and metal case transistors with no luck.
I thought that maybe the problem has to do with the oscillator circuit, but i replaced all the XTAL parts and nothing changed.
I checked the eprom ics and the type is M27128AFI. I think it is ok.
I am quite sure that i programmed the eprom with the unscrambled file. And if the interface works correct with the CSTQD118.ROM, then that is the issue!
After the Orthodox Easter, i will program an eprom with the CSTQD118.ROM scrambled file and i'll come back for feedback.
Thank you all for your help!
I populated the CST Ram Plus card and i have some questions. I used 2N2222A instead of MPS2369. Both are NPN transistors and from the datasheets they seem to be interchangeable? Second, at the block diagram the lower right resistor is a 47KΩ or a 4.7KΩ resistor? And final, all eproms are indicated as 27256 on diagram. 27128 are not recommended?
@dilwyn
thanks for the manual.
@Pr0f
that is what i think, TK2, ICE, maybe 68K/OS, or programming languages that were partially on rom cartridge.
@Chris_68
The v1.18 bin file is a 16KB file if a remember correct. I burned two other 27C128 eproms and i am sure one file was 8KB and wrote it twice, on lower and upper bank but using first the HxD editor for doubling it.
@ones' complement
unfortunately i don't have a logic probe
@martyn_hill
and i am almost sure that i programmed the unscrambled v1.18 image.
@aalea About 2N2222A transistor, i don't know if it is a chinese the ones i have, but i used both plastic and metal case transistors with no luck.
I thought that maybe the problem has to do with the oscillator circuit, but i replaced all the XTAL parts and nothing changed.
I checked the eprom ics and the type is M27128AFI. I think it is ok.
I am quite sure that i programmed the eprom with the unscrambled file. And if the interface works correct with the CSTQD118.ROM, then that is the issue!
After the Orthodox Easter, i will program an eprom with the CSTQD118.ROM scrambled file and i'll come back for feedback.
Thank you all for your help!
Re: CST Ram Plus eproms - CST QDisc v4 issue
I think the eprom sockets decode out as 32K chunks - so you can get 2 16K ROM images per 27256 Eprom.
Not sure you'd be able to get ICE to work - I am sure I've read somewhere that it expects to be at 0C000 (ROM Socket) in the QL memory map and may not work if located elsewhere.
Not sure you'd be able to get ICE to work - I am sure I've read somewhere that it expects to be at 0C000 (ROM Socket) in the QL memory map and may not work if located elsewhere.
-
- Font of All Knowledge
- Posts: 4033
- Joined: Mon Dec 20, 2010 11:40 am
- Location: Sunny Runcorn, Cheshire, UK
Re: CST Ram Plus eproms - CST QDisc v4 issue
I have disassembled ICE rom, just tryingbto understand the assembler source code.Pr0f wrote: ↑Fri May 03, 2024 6:23 pm I think the eprom sockets decode out as 32K chunks - so you can get 2 16K ROM images per 27256 Eprom.
Not sure you'd be able to get ICE to work - I am sure I've read somewhere that it expects to be at 0C000 (ROM Socket) in the QL memory map and may not work if located elsewhere.
I did think about writing a PTR_GEN driver for the ICE mouse or is that Mice ...
Regards,
Derek
Derek