gecko-systems:gecko3stack:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
gecko-systems:gecko3stack:start [2017/03/06 12:20] – external edit 127.0.0.1gecko-systems:gecko3stack:start [2021/12/20 10:49] (current) – external edit 127.0.0.1
Line 1: Line 1:
 <box 300px right | **Project details**> <box 300px right | **Project details**>
 ^ Name: | GECKO3EDU || ^ Name: | GECKO3EDU ||
-^ Maintainer| [[huce:microlab:projects:internal:gecko:gecko-system:gecko3stack:orphaned]]||+^ Maintainer| [[gecko-systems:gecko3stack:orphaned]]||
 ^ Revision: | unknown || ^ Revision: | unknown ||
 ^ Development status: | stable || ^ Development status: | stable ||
Line 9: Line 9:
 ====== GECKO3STACK ====== ====== GECKO3STACK ======
  
-[[http://www.tu-ilmenau.de|{{ :systems:gecko3stack:tui_logo_schwarzgruen_rgb_03.png?150| Contributed by the Ilmenau University of Technology, Ilmenau, Germany}}]]+[[http://www.tu-ilmenau.de|{{ :gecko-systems:gecko3stack:tui_logo_schwarzgruen_rgb_03.png?150| Contributed by the Ilmenau University of Technology, Ilmenau, Germany}}]]
  
-This page introduces the GECKO3STACK - a system combining several [[modules:gecko3main:start]] modules to an FPGA array.+This page introduces the GECKO3STACK - a system combining several [[gecko3:gecko3main:start]] modules to an FPGA array.
  
 ===== System ===== ===== System =====
  
-{{:huce:microlab:projects:internal:gecko:gecko3:gecko3stack:gecko3stack_3x.png?300|GECKO3STACK}} +{{gecko-systems:gecko3stack:gecko3stack_3x.png?300|GECKO3STACK}} 
-{{:huce:microlab:projects:internal:gecko:gecko3stack_3x_front.jpg?150|GECKO3STACK}}+{{gecko-systems:gecko3stack:gecko3stack_3x_front.jpg?150|GECKO3STACK}}
  
 ==== Platform and physical connection ==== ==== Platform and physical connection ====
  
-[[:platforms:gecko3_staddle|{{ :platforms:gecko3staddle:gecko3_staddle_card.jpg?100|GECKO3 staddle}}]]+[[:platforms:gecko3_staddle|{{ :gecko-platforms:gecko3_staddle:gecko3_staddle_card.jpg?100|GECKO3 staddle}}]]
  
-The GECKO3STACK is built on the [[:platforms:gecko3_staddle]] platform, which provides power supply, JTAG facilities and user interface ports. With a GECKO3 staddle a stack of up to five modules can be built.+The GECKO3STACK is built on the [[:gecko-platforms:gecko3_staddle]] platform, which provides power supply, JTAG facilities and user interface ports. With a GECKO3 staddle a stack of up to five modules can be built.
  
-Connection between the modules is realized as a physical bus over the [[standard:system_bus|system bus]] connectors. On the IO1 BUS connector the pins supporting the Altium soft-JTAG chain are reserved and an external clock pin can be utilized as a global bus clock. The unassigned pins can be used arbitrarily, or to access the user interface features of the staddle. On the connector IO2 BUS up to 116 pins are available to implement inter-module communication.+Connection between the modules is realized as a physical bus over the [[gecko3:system_bus:start|system bus]] connectors. On the IO1 BUS connector the pins supporting the Altium soft-JTAG chain are reserved and an external clock pin can be utilized as a global bus clock. The unassigned pins can be used arbitrarily, or to access the user interface features of the staddle. On the connector IO2 BUS up to 116 pins are available to implement inter-module communication.
  
-{{ :huce:microlab:projects:internal:gecko:gecko3:gecko3stack:system-bus-stack.png?400 | Pin assignment}}+{{ gecko-systems:gecko3stack:system-bus-stack.png?400 | Pin assignment}}
 ==== Setup ==== ==== Setup ====
  
 To operate a GECKO3STACK, first the required number of GECKO3main modules have to be placed on the GECKO3 stadde platform. Second, it has to be made sure, that the jumpers for the power supply are set to ''Extern'', before a 12V external power source can be connected to the front panel. To operate a GECKO3STACK, first the required number of GECKO3main modules have to be placed on the GECKO3 stadde platform. Second, it has to be made sure, that the jumpers for the power supply are set to ''Extern'', before a 12V external power source can be connected to the front panel.
  
-{{ :huce:microlab:projects:internal:gecko:gecko3:gecko3stack:jtag-cable.png?100| JTAG bridge cable}}+{{ :gecko-systems:gecko3stack:jtag-cable.png?100| JTAG bridge cable}}
  
 To prepare the JTAG connection to the stack, select the number of nodes with the slide switch and connect all the GECKO3main modules' JTAG interfaces consecutively to the 8-pin headers on the staddle. Since the GECKO3 staddle platform is laid out for both, the GECKO3STACK can be set up for development using either the Xilinx ISE or the Altium Designer tool suite. A self-tailored JTAG bridge cable can be used for both options. To prepare the JTAG connection to the stack, select the number of nodes with the slide switch and connect all the GECKO3main modules' JTAG interfaces consecutively to the 8-pin headers on the staddle. Since the GECKO3 staddle platform is laid out for both, the GECKO3STACK can be set up for development using either the Xilinx ISE or the Altium Designer tool suite. A self-tailored JTAG bridge cable can be used for both options.
Line 40: Line 40:
 Developing with the Xilinx tools requires the connection with a Xilinx Platform Cable. The number of nodes has been set by the slide switch, but the DIP-switches have to be set on ''disable'', since the Xilinx tools do not utilize the soft-JTAG feature. Therefore, also the respective pins of the JTAG bridge cable do not have to be connected to the modules RS232 header. Commonly, projects for each GECKO3main module are programmed to the FPGAs using iMPACT, the Boundary scan view of which should show all Spartan3s connected by the JTAG chain. Developing with the Xilinx tools requires the connection with a Xilinx Platform Cable. The number of nodes has been set by the slide switch, but the DIP-switches have to be set on ''disable'', since the Xilinx tools do not utilize the soft-JTAG feature. Therefore, also the respective pins of the JTAG bridge cable do not have to be connected to the modules RS232 header. Commonly, projects for each GECKO3main module are programmed to the FPGAs using iMPACT, the Boundary scan view of which should show all Spartan3s connected by the JTAG chain.
  
 +{{ :gecko-systems:gecko3stack:gecko3stack_setup_xilinx.png?400 |Xilinx iMPACT Boundary Scan view}}
  
-{{:huce:microlab:projects:internal:gecko:gecko3:gecko3stack:gecko3stack_setup_xilinx.png?400| Xilinx iMPACT Boundary Scan view}} 
  
 === Altium Designer === === Altium Designer ===
Line 48: Line 48:
 Setting up the stack for development with Altium Designer requires the connection with the [[http://wiki.altium.com/display/ADOH/USB+JTAG+Adapter|Altium USB JTAG Adapter]] using the designated port on the staddle. Additionally to selecting the number of nodes in the stack by the slide switch, the DIP switches can be used to enable the respective node for the utilization of the Altium Soft-JTAG chain. The associated pins of the JTAG bridge cable have to be connected to the (now converted) RS232 header. The [[http://wiki.altium.com/display/ADOH/Enabling+the+Soft+Devices+JTAG+Chain| soft-chain interface]] has to be included in the FPGA designs, as do the soft-JTAG instruments. These instruments, e.g. logic analysers, show up as devices on an additional JTAG chain in Altium Designer's Devices view pane, from which they can also be accessed during runtime. Setting up the stack for development with Altium Designer requires the connection with the [[http://wiki.altium.com/display/ADOH/USB+JTAG+Adapter|Altium USB JTAG Adapter]] using the designated port on the staddle. Additionally to selecting the number of nodes in the stack by the slide switch, the DIP switches can be used to enable the respective node for the utilization of the Altium Soft-JTAG chain. The associated pins of the JTAG bridge cable have to be connected to the (now converted) RS232 header. The [[http://wiki.altium.com/display/ADOH/Enabling+the+Soft+Devices+JTAG+Chain| soft-chain interface]] has to be included in the FPGA designs, as do the soft-JTAG instruments. These instruments, e.g. logic analysers, show up as devices on an additional JTAG chain in Altium Designer's Devices view pane, from which they can also be accessed during runtime.
  
-{{:huce:microlab:projects:internal:gecko:gecko3:gecko3stack:gecko3stack_setup_altium.png?400| Altium Designer Devices view with Soft-JTAG devices}}+{{gecko-systems:gecko3stack:gecko3stack_setup_altium.png?400| Altium Designer Devices view with Soft-JTAG devices}}
  
-For designs with Altium soft-JTAG devices the use of {{:huce:microlab:projects:internal:gecko:gecko3:gecko3stack:gecko3_nexus.zip|this adapted constraint file}} is required (it includes the mappings of the soft-JTAG signals to both the original RS232-header, and to GPIO-bus pins for distribution throughout the stack).+For designs with Altium soft-JTAG devices the use of {{:gecko-systems:gecko3stack:gecko3_nexus.zip|this adapted constraint file}} is required (it includes the mappings of the soft-JTAG signals to both the original RS232-header, and to GPIO-bus pins for distribution throughout the stack).
  
 ===== Inter-module communication ===== ===== Inter-module communication =====
Line 57: Line 57:
  
 ==== Shared memory communication ==== ==== Shared memory communication ====
-{{ :huce:microlab:projects:internal:gecko:gecko3:gecko3stack:shiva_concept11.png?350&nolink| Shared memory idea}}+{{ :gecko-systems:gecko3stack:shiva_concept11.png?350&nolink| Shared memory idea}}
  
 The idea of communicating via shared memory is the exchange of data over a global memory, that is equally and independently accessible by all nodes. The idea of communicating via shared memory is the exchange of data over a global memory, that is equally and independently accessible by all nodes.
Line 65: Line 65:
 SHIVA is a component to realize shared memory communication within a GECKO3STACK, without using an actual dedicated memory element. Instead, the internal resources of the FPGAs on the GECKO3main modules will be used to create a //distributed shared memory//. Central concept is to unify sections of the local BRAM on every connected Spartan3 in a global address space. This virtually global memory is established by the interface component SHIVA. The partial application on each FPGA will thus access data over a global address, independently of the actual physical memory location, and, more importantly, independently from the actual physical bus communication. SHIVA is a component to realize shared memory communication within a GECKO3STACK, without using an actual dedicated memory element. Instead, the internal resources of the FPGAs on the GECKO3main modules will be used to create a //distributed shared memory//. Central concept is to unify sections of the local BRAM on every connected Spartan3 in a global address space. This virtually global memory is established by the interface component SHIVA. The partial application on each FPGA will thus access data over a global address, independently of the actual physical memory location, and, more importantly, independently from the actual physical bus communication.
  
-{{:huce:microlab:projects:internal:gecko:gecko3:gecko3stack:shiva_concept21.png?350&nolink| Distributed shared memory concept}} +{{:gecko-systems:gecko3stack:shiva_concept21.png?350&nolink| Distributed shared memory concept}}
-{{:huce:microlab:projects:internal:gecko:gecko3:gecko3stack:shiva_concept31.png?350| SHIVA on GECKOSTACK}}+
  
-[[:systems:gecko3stack:communication_interface_shiva |Details on SHIVA]] will be discussed separately.+{{:gecko-systems:gecko3stack:shiva_concept31.png?350| SHIVA on GECKOSTACK}} 
 + 
 +FIXME 
 +[[:gecko-systems:gecko3stack:communication_interface_shiva |Details on SHIVA]] will be discussed separately.
  
  
  • gecko-systems/gecko3stack/start.1488802821.txt.gz
  • Last modified: 2021/12/20 10:49
  • (external edit)