Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Applied links to related System Call API's

...

This system call is regarded as internal operating system usage but may be used by applicationsThis system call is used by the File Eprom Management Interface, OS_Epr, but is well suited for other application purposes.

The routine can be told which programming algorithm to use (by specifying the FE_28F or FE_29F mnemonic in C); these parameters can be fetched when investigating which Flash Memory chip is available in the slot, using the OS_Fep, A = FEP_CDID that reports these constants.

However, if neither of the constants are provided in A, the routine can be specified with C = 0 which internally polls the Flash Memory for identification and intelligently use the correct programming algorithm. The identified FE_28F or FE_29F constant is returned to the caller in C for future reference (when the block was successfully programmed to the card).

Uses the segment mask of HL (where BHL memory will be bound into the Z80 address space to blow the block of bytes (MM_S0 - MM_S3), which has to be in a different segment than DE is referring.

BHL points to an absolute bank (which is part of the slot that the Flash Memory Card have been inserted into). Further, the local buffer must be available in local address space and not part of the segment used for blowing bytes.

Important:
Third generation AMD Flash Memory chips may be programmed in all available slots (0-3). Only INTEL I28Fxxxx series Flash chips require the 12V VPP pin in slot 3 to successfully blow data on the memory chip. If the Intel Flash Eprom card is inserted in slot 1 or 2, this routine will report a programming failure.

It is the responsibility of the application (before using this call) to evaluate the Flash Memory (using the OS_Fep, FEP_CDID routine) and warn the user that an INTEL Flash Memory Card requires the Z88 slot 3 hardware, so this type of unnecessary error can be avoided.

...