Parent: ECB Documentation

Folder: older files

Page: N8VEM on the ECB bus

File: Wed Dec 3 23:03:10 2014 ECB-06.jpg (380090 bytes)
File: Wed Nov 16 04:18:34 2011 ECB-Standard-Basic.xls (32256 bytes)
Wolfgang Kabatzke at 5:57 pm on Nov 16, 2011:

This is an idea to describe the Bus as common element for interoperarbility in this group. We have one basisc bus, the ECB, and we have fixed signals which are not allowed to change, and we have a fix number of signal for free using in special projects, I call them "project specific signals".
I put the standard and the project specific modifications into different files. I think that this is not to 100% complete because I was not the developer of SBC188, M68k, MF-PIC etc. So the developers have the chance to complete the configurations. I hope this is an usable way to come to an acceptabtable definition what our bus-system is.

This knowledge is important to create the correct sub-configuration for specific CPU. For example: I have an SBC188 and define the basic unchangable signals, I have the project specific signals on the free pins (for this project free) and then I can decide which other boards are interoperable in my specific configuration (for example DISK-IO, RAM-Floppy etc.)

This way is one model which is used in industry with big success.

File: Wed Nov 16 04:18:37 2011 ECB-Standard-N8VEM-Address-Expansion.xls (33280 bytes)
Wolfgang Kabatzke at 5:58 pm on Nov 16, 2011:

This is an idea to describe the Bus as common element for interoperarbility in this group. We have one basisc bus, the ECB, and we have fixed signals which are not allowed to change, and we have a fix number of signal for free using in special projects, I call them "project specific signals".
I put the standard and the project specific modifications into different files. I think that this is not to 100% complete because I was not the developer of SBC188, M68k, MF-PIC etc. So the developers have the chance to complete the configurations. I hope this is an usable way to come to an acceptabtable definition what our bus-system is.

This knowledge is important to create the correct sub-configuration for specific CPU. For example: I have an SBC188 and define the basic unchangable signals, I have the project specific signals on the free pins (for this project free) and then I can decide which other boards are interoperable in my specific configuration (for example DISK-IO, RAM-Floppy etc.)

This way is one model which is used in industry with big success.

File: Wed Nov 16 04:18:38 2011 ECB-Standard-N8VEM-M68k.xls (33280 bytes)
Wolfgang Kabatzke at 5:58 pm on Nov 16, 2011:

This is an idea to describe the Bus as common element for interoperarbility in this group. We have one basisc bus, the ECB, and we have fixed signals which are not allowed to change, and we have a fix number of signal for free using in special projects, I call them "project specific signals".
I put the standard and the project specific modifications into different files. I think that this is not to 100% complete because I was not the developer of SBC188, M68k, MF-PIC etc. So the developers have the chance to complete the configurations. I hope this is an usable way to come to an acceptabtable definition what our bus-system is.

This knowledge is important to create the correct sub-configuration for specific CPU. For example: I have an SBC188 and define the basic unchangable signals, I have the project specific signals on the free pins (for this project free) and then I can decide which other boards are interoperable in my specific configuration (for example DISK-IO, RAM-Floppy etc.)

This way is one model which is used in industry with big success.

File: Wed Nov 16 04:18:40 2011 ECB-Standard-N8VEM-MF-PIC.xls (32768 bytes)
Wolfgang Kabatzke at 5:58 pm on Nov 16, 2011:

This is an idea to describe the Bus as common element for interoperarbility in this group. We have one basisc bus, the ECB, and we have fixed signals which are not allowed to change, and we have a fix number of signal for free using in special projects, I call them "project specific signals".
I put the standard and the project specific modifications into different files. I think that this is not to 100% complete because I was not the developer of SBC188, M68k, MF-PIC etc. So the developers have the chance to complete the configurations. I hope this is an usable way to come to an acceptabtable definition what our bus-system is.

This knowledge is important to create the correct sub-configuration for specific CPU. For example: I have an SBC188 and define the basic unchangable signals, I have the project specific signals on the free pins (for this project free) and then I can decide which other boards are interoperable in my specific configuration (for example DISK-IO, RAM-Floppy etc.)

This way is one model which is used in industry with big success.

File: Wed Nov 16 04:18:33 2011 ECB-Standard-N8VEM-SBC188.xls (32768 bytes)
File: Wed Nov 16 04:18:36 2011 ECB-Standard-N8VEM.xls (32768 bytes)
Wolfgang Kabatzke at 5:59 pm on Nov 16, 2011:

This is an idea to describe the Bus as common element for interoperarbility in this group. We have one basisc bus, the ECB, and we have fixed signals which are not allowed to change, and we have a fix number of signal for free using in special projects, I call them "project specific signals".
I put the standard and the project specific modifications into different files. I think that this is not to 100% complete because I was not the developer of SBC188, M68k, MF-PIC etc. So the developers have the chance to complete the configurations. I hope this is an usable way to come to an acceptabtable definition what our bus-system is.

This knowledge is important to create the correct sub-configuration for specific CPU. For example: I have an SBC188 and define the basic unchangable signals, I have the project specific signals on the free pins (for this project free) and then I can decide which other boards are interoperable in my specific configuration (for example DISK-IO, RAM-Floppy etc.)

This way is one model which is used in industry with big success.