Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

The Z88 Flash/RAM card has been working for several years now. When OZ 4.6 was introduced, allowing applications to be run in RAM, some games failed to run.

Standard VersionModified Monitoring Version

This was thought to be due to an intermittent timing error from the decode chip CD74HCT139 which switches between the RAM and Flash chip but after the Z88 Hardware Investigation, it has been discovered to be a misunderstanding by both the hardware and software engineers on how to write faultlessly to the flash chip. This has only affected a few users, i.e. those who play games in RAM or who do repetitive writing to the flash card. The majority of users have not reported any problems.

Object

It has already been proved that if OZ 4.7 is run in a 256K EPROM card, the application runs faultlessly. This is because the code that the flash chip normally writes to the data bus is no longer written, as there is no flash chip. The OTP (One Time Programming) EPROM uses a similar footprint to the 512K Flash chip, so it was decided to try this combination and see if it improves the performance.

Two versions are considered.

  • 256K - for OZ 4.7 and
    768K of RAM
  • 256K - for OZ 4.7 and
    768K of Flash

Although the best solution would be a software upgrade to OZ 4.7 allowing users to update their cards, it has been decided to see if by changing the hardware the same result may be achieved. See Writing to Flash Chips for a full explanation of what needs to be fixed. The object of this exercise is to run OZ 4.7 in the OTP EPROM in the top 256K area, leaving the rest of the address space 768K for either RAM, using the 1M RAM chip or Flash, using the 1M Flash chip. The only disadvantage is that users will no longer be able to update their OZ themselves, but a socket may be fitted in the card, so that the OTP EPROM may be replaced.

The address decoding will be identical for both versions.

Method

The modified 512K/512K card has already been used with the modified extender card as described in the Z88 Hardware Investigation section, to test how the decoder chip may be used with different address maps. It was decided just to build a card using the knowledge gained from these previous tests.

Decoder Changes


EPROMFLASHRAM



OZ 4.7FILES
CEA19A18
Replace 512K Flash with OTP EPROM256K
768KXXX
Replace 512K Flash with OTP EPROM256K768K0KXXX

Decoder Connections

The decode chip used, is repeated twice in the same device. The first part does the 256K/768K chip select decodes the 256K EPROM. The unused decode is used to decode either the RAM or FLASH.

In all cases, the input pins of the unused part (Pins 13, 14 & 15), need to be isolated as they have been connected to GND.

EPROM/RAM or FLASH

256K OTP EPROM, 768K FLASH or RAM


CEA19A18
256K OTP EPROM011
768K FLASH or RAM010
768K FLASH or RAM001
768K FLASH or RAM000
NOT SELECTED1XX.

Choosing the output

Using the signal that we wish to control as the Enable signal, choosing which out put is used is determined by A0 and A1. In this case they are both high, which means that Y3 is used.

  • ROE to E (Pin 15)
  • Vcc to A0 (Pin 14) for A19 high
  • Vcc to A1 (Pin 13) for logic 1

The output was Y3 (Pin 9). It passed through the signal. The other 3 were high. Connecting MA19 and Vcc afterwards, the card worked perfectly.

This procedure was repeated for

  • ROE to E (Pin 15)
  • Vcc to A0 (Pin 14) for A19 high
  • GND to A1 (Pin 13) for logic 0

The output was Y1 (Pin 11).

This was the final result as it would allow the Enable signal from the Z88 to be gated into the logic as well.

512K FLASH PROTECTED & 512 RAM


CEA19LOGIC 1ROES
256K FLASH PROTECTEDX111
256K FLASH110ROE
512K RAM00

Connection List 256K


I/O
PIN
No







I/O
PIN
No





FROM Z88 SE1IE110000
FROM Z88 SE1 (0)IE1510000
FROM Z88 MA19IA02X1010
FROM FLASH CE (0)IA014X1010
FROM Z88 MA18IA13X1100
LOGIC 0 - 0v
IA113X1100

O

Y0

411110

O

Y0

1211110

O

Y1

511101

O

Y1

1111101

OY2611011
TO RAM or FLASH CEOY21011011
TO FLASH CEOY3710111

OY3910111

Connection List 1M


I/O
PIN
No







I/O
PIN
No





FROM Z88 SE1IE110000
FROM Z88 ROEIE1510000
FROM Z88 MA19IA02X1010
FROM Z88 SE1IA014X1010
LOGIC 0 - 0vIA13X1100
LOGIC 0 - 0v
IA113X1100
TO RAM CEO

Y0

411110
TO FLASH ROE_SO

Y0

1211110
TO FLASH CEO

Y1

511101

O

Y1

1111101

OY2611011

OY21011011

OY3710111

OY3910111

Conclusion

Further testing will be done before reporting that a hardware solution has been found.

What has changed?

  1. The chip select of the decoder remains unchanged.
    This selects the RAM Chip Enable when A19 is low and the FLASH Chip Enable when A19 is high.
  2. The FLASH chip only uses its Chip Enable when it is read, like a ROM.
    The second independent part of the decoder does a similar function to the FLASH chip like the first, by only enabling its Output Enable signal with ROE, when A19 is high and Card Enable is low. This means that when the on board RAM is accessed, or the card is no longer enabled, the FLASH chip is no longer able to write to the data bus.
  3. The extra circuitry does in effect the same thing as the chip enable, but gates the Output Enable signal. This prevents the flash chip from writing to the data bus when it is not selected.

POE & ROE

Splitting these two signals on the 512K/512K Flash/RAM card has made no difference. There are more cycles generated on the POE signal to refresh the RAM, but it was found that even Cambridge are using the ROE signal for their RAMs so it is proposed to leave ROE to Output Enable the FLASH and RAM as before.

Modifying Flash Cards

Some flash chips are better than others. What has been found is that it is possible to crash the Z88 consistently with one flash card and not with another one. It does not matter which size they are either. This is why not all users have experienced errors. It also depends what the user does. Just using Pipedream and saving files will not cause any errors.

New cards will be modified with these changes.

https://tinyurl.com/mkdlwv4

512K Flash Modifications


PinPinPinInstruction
Pin




Cut track (ROE) underside from pin 24U324512K FLASH
U4131415Lift up pins DO NOT CONNECT TO PCB


U413

A19 - Connect toU42
U4
14
(SE1) CE - Connect toU41
U4

15ROE - Connect to VIA


U4
10
ROE_S Connect toU137512K FLASH OE


1M Flash Modifications


PinPinPinInstruction
Pin




Cut track (ROE) on top going toU1371M FLASH
U4
45Lift up pins DO NOT CONNECT TO PCB


U4
1415Lift up pins DO NOT CONNECT TO PCB


U413

REMAINS ON GND


U4
14
(SE1) CE - Connect toU41
U4

15ROE - Connect toU324512K FLASH
U4
12
ROE_S Connect toU1371M FLASH
  • No labels