As many of the Dragon and Coco community will be aware, the Dragon MSX 2+ board has been in development for around a year now. This evolution of the WordPak 2+ board by CocoDemus features three main ICs for audio and video supported by a CPLD.
It has been working flawlessly with real disk drives, the DragonDrive and the DragonMMC. With workarounds it has also been working well with the Coco SDC. By workarounds I mean that the VDK image would need to be selected using Pere Serrat’s extended DOSPLUS (which is how the Coco SDC usually boots for Dragon machines), but then a BANK command would need to be issued which would retain the VDK image, but reboot into another DOS – typically SUPERDOS E8 or Eurohard DOS 4.2.
After much head-scratching and experimentation between myself and Pere, Darren Atkinson (the designer of the Coco SDC) came up with a suggestion as to what might be wrong. He suggested that the 6809 SYNC command used in the various DOS versions might be susceptible to all of the additional circuitry that was connected (with the Coco SDC and the Dragon MSX 2+, there is a lot!).
Essentially the SYNC command is designed to put the 6809 busses and R/W lines into an open-collector or high-impedance state, whilst the 6809 waits for an external interrupt to be fired. The theory as to what was causing the issue was that the additional circuitry could be causing stray capacitance to trigger spurious activity within the CocoSDC – and essentially crash the device. The solution – which is fitted to all Coco 3s by default, is to connect 4k7 pull-up resistors between +5V and R/W and each of the address lines.
I originally modified an Oojamaflip 2020, as this was the simplest and safest way to test this out, and lo and behold, it worked. The Dragon MSX 2+ and Coco SDC were now able to operate in perfect harmony with no DOS banking required.
Of course there is absolutely no reason why you cannot modify your own Dragon to add these resistors somewhere else. Underneath the motherboard is a possibility if you are feeling brave – though do watch for areas where the solder mask is not protecting adjacent tracks properly.
Update – 27th June 2020: I have now restarted shipments for most items, though I am trying to limit physical visits to the post office. This is being done in several ways, including using pre-paid tracking, collection services and still on occasion, necessary visits to the post office.
Update – 1st May 2020: I have restarted shipments for just one line today. I hope to be able to re-commence shipments across the wider range soon.
Regrettably I have made the decision to temporarily stop selling anything which cannot simply be dropped into a postbox. This essentially means only selected electronic components will continue to be available for the foreseeable future. I have also restricted multiple purchases of the same item, in order that package values remain lower, and thus do not necessitate so many trips to the postal office.
At the same time, I have decided only to ship within the United Kingdom for the foreseeable future.
I do hope that you understand my reasons for these changes. It’s a worrying time – and I have a family to safeguard. Please stay safe everyone.
One of my Dragon 64s is set up so that I can test RAM easily. I’ve made some little PCBs up, which allow me to plug in a mounted ZIF socket into a standard DIL socket on the lower four RAM positions, as per the image below:
Whilst I was undertaking this testing, it became apparent to me, that before even getting to the memory test program, a RAM fault would generally appear on the boot screen. In fact, faulty RAM would fill the majority of the screen with a single character.
Through a bit of trial and error I discovered that the single character shown could be used to work out which chip(s) had failed.
Another way to reproduce this fault was simply to leave one or more sockets empty, with the populated sockets containing known good chips.
I’ve not replicated the testing on the upper row of four DRAM chips, but I have worked out what symbol corresponds to which of the lower sockets are faulty, as presented in the table below. RAM A-D are the bottom row of RAM, from left to right respectively. If anyone knows how faults would show in the upper row of RAM chips, please do let me know.
A new online store dedicated to the 1980s’ Dragon computer? Well yes, for now. It may branch out into supporting other computers/spares in time, but for now, this is pretty much all Dragon.
Those of you who follow the Facebook Dragon 32 group will know that I’ve sold a couple of types of add-on board for the Dragon 32/64/200 both on that group, and via eBay. This was the very successful lower case device (the Dragon 200E replica daughter-board), and the far more complex DragonPlus board – after which this site takes its name.
I’ve enjoyed making and selling these boards directly on the group, and via eBay – however, I decided the time was right to put together a proper store to group things together, as sometimes selling on Facebook felt like I was blatantly spamming the group. eBay can feel decidedly dodgy at the best of times – but when the item price is higher, this being the case with the DragonPlus boards, so too does the element of risk involved.
I also plan to upload some technical findings on here too – like oscilloscope traces, or logic analyser outputs that I’ve performed – which may be used later as a baseline for other people’s fault finding.
Notice to EU Customers: We are not yet using IOSS - so if you order directly from us you will incur import VAT & duty at point of entry to your country. Dismiss