Difference: TDCReadoutBoard (1 vs. 45)

Revision 45
Changes from r43 to r45
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Added:
>
>

Direct Link to TRBv3

New (Jan. 2011) development for TDC applications

TDCReadoutBoardV3
 

Direct Link to TRBv2

TDCReadoutBoardV2
Added:
>
>

Direct Link to TRBv2 problems handling

TDCReadoutBoardV2Beam2012
 

Important Pages

Revision 43
Changes from r41 to r43
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Direct Link to TRBv2

TDCReadoutBoardV2
Changed:
<
<

Calibration

HPTDC calibration measurements

Meetings Scheduled

No meetings schedules now. Now, most of the things are done via e-mail.
>
>

Important Pages

 
Changed:
<
<

meetings of the past

>
>
 
Changed:
<
<
List of things to be done in version 0.99 of TRB:

To be discussed on the meeting 24.05. 15:00

  • two test signals for Mambo
  • Fast DSP, large FPGA and MU-Link have to be put on (Ingo should have a look to available devices)
  • Ability to use 32-channels input for Wolfgang Koenig (jumper based?)

RPCMinutesMeeting20050524
>
>

Calibration

 
Changed:
<
<

Infos

>
>
HPTDC calibration measurements
 
Deleted:
<
<
 

Improvements for the future (new software and new TRB)

Line: 44 to 31
 

For the new TRBv2 have a look to TDCReadoutBoardV2
Deleted:
<
<

Tasks

 

RPC Documentation

Line: 63 to 48
 
  • : Question to Radek: What is the transferspeed of reading data from external memory to internal one (MBytes/s)?
  • : Answer: Average transfer speed is 1,3 MBytes/s from Etrax to an external Computer which receives the data.
Added:
>
>

Full list of Contents

 
Changed:
<
<

Patch list

Progress Reports:

TRB in the public, talks, presentations, papers

Produced boards status

Schematics

>
>
<--//treePlugin-->
 
Revision 41
Changes from r39 to r41
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Direct Link to TRBv2

TDCReadoutBoardV2
Added:
>
>

Calibration

HPTDC calibration measurements
 

Meetings Scheduled

No meetings schedules now.
Changed:
<
<
Up to now, most of the things are done via e-mail.
>
>
Now, most of the things are done via e-mail.
 

meetings of the past

Line: 77 to 80
 

Added:
>
>

Schematics

 
Revision 39
Changes from r37 to r39
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Added:
>
>

Direct Link to TRBv2

TDCReadoutBoardV2
 

Meetings Scheduled

Line: 71 to 75
 

Produced boards status

Changed:
<
<
>
>
 

Revision 37
Changes from r35 to r37
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 69 to 69
 

Added:
>
>

Produced boards status

Revision 35
Changes from r33 to r35
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 39 to 39
 

Tasks

Deleted:
<
<
Marek & Radek Team:

Next tasks (2006-05-16):
  1. prepare boards in Krakow to work (1-2 day)
  2. make jam programming faster, (1 day)
  3. prepare script, which open xterms and log on into trb done
  4. compile EPICS on trb (3 days)
  5. use standard HADES-parameter scheme (tcl variables), easiest way would be to use the allParam-library and use external perl-scripts for generating the jam-files (5 days)
  6. prepare script, which put parameters, such as search window to trb (3 days)

to Michael-> could you sort these tasks according to priorities Michael: done, but these priorities are not fixed. If you have problems with one topic, just continue with the next. If the working times, which I put at the tasks are exceeded, then please let us talk about it. Maybe then we have to change priorities. Remember: We should not aim for 100% solutions. Each task should make an significat improvement on the topic, but no revolution or perfect thing..
 

RPC Documentation

Revision 33
Changes from r31 to r33
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Changed:
<
<

Meetings

>
>

Meetings Scheduled

No meetings schedules now. Up to now, most of the things are done via e-mail.

meetings of the past

 

List of things to be done in version 0.99 of TRB:
Line: 23 to 28
 

  • Kris made the very smart remark: Why do we copy data from Dual-Ported-Ram to ETRAX RAM and then to Ethernet. We agreed that we will keep everything as it is (copy it) and change to a smarter transfer after the first
Changed:
<
<
running-TRB in the HADES-experiment (so after October)
>
>
running-TRB in the HADES-experiment (so after October 2005)
 
  • I want to ask: Why do we have a dual-ported RAM at all? We don't use it! So, in the next version of the TRB I would opt for a FIFO there.
  • The next (after October) software version of TRB should make all event-formatting to the HADES-event-standard
Line: 37 to 42
  Marek & Radek Team:

Next tasks (2006-05-16):
Changed:
<
<
  • make jam programming faster,
  • compile EPICS on trb (tcl variable)
  • prepare script, which open xterms and log on into trb
  • prepare script, which put parameters, such as search window to trb
  • prepare boards in Krakow to work
to Michael-> could you sort these tasks according to priorities
>
>
  1. prepare boards in Krakow to work (1-2 day)
  2. make jam programming faster, (1 day)
  3. prepare script, which open xterms and log on into trb done
  4. compile EPICS on trb (3 days)
  5. use standard HADES-parameter scheme (tcl variables), easiest way would be to use the allParam-library and use external perl-scripts for generating the jam-files (5 days)
  6. prepare script, which put parameters, such as search window to trb (3 days)
 
Added:
>
>
to Michael-> could you sort these tasks according to priorities Michael: done, but these priorities are not fixed. If you have problems with one topic, just continue with the next. If the working times, which I put at the tasks are exceeded, then please let us talk about it. Maybe then we have to change priorities. Remember: We should not aim for 100% solutions. Each task should make an significat improvement on the topic, but no revolution or perfect thing..
 

RPC Documentation

Line: 71 to 81
 

Added:
>
>

TRB in the public, talks, presentations, papers

Revision 31
Changes from r29 to r31
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 36 to 36
 

Marek & Radek Team:
Changed:
<
<
Next tasks (2005-07-11):
>
>
Next tasks (2006-05-16):
  • make jam programming faster,
  • compile EPICS on trb (tcl variable)
  • prepare script, which open xterms and log on into trb
  • prepare script, which put parameters, such as search window to trb
  • prepare boards in Krakow to work
to Michael-> could you sort these tasks according to priorities
 
Deleted:
<
<
  • command line tool to generate all needed .jam files to program and test HPTDC, Marek done
  • merge VHDL code from Tiago together with code witch was created by K.K, Marek done
  • creating SPI interface on Etrax, Radek done
 

RPC Documentation

Revision 29
Changes from r27 to r29
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 28 to 28
  I would opt for a FIFO there.
  • The next (after October) software version of TRB should make all event-formatting to the HADES-event-standard in the FPGA. Now we keep the C-version, because it is easier to change.
Added:
>
>
  • Add in addition the TigerSHARC TS201, a bigger XILINX (LX40) and the TLK2501 for the MU (and later also trigger-transfer)

For the new TRBv2 have a look to TDCReadoutBoardV2
 

Tasks

Line: 48 to 51
 
Added:
>
>
 

Feature List:

Revision 27
Changes from r25 to r27
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 41 to 41
 

RPC Documentation

Added:
>
>
 
Added:
>
>
 

Feature List:

Revision 25
Changes from r23 to r25
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 35 to 35
 

Next tasks (2005-07-11):
Changed:
<
<
  • command line tool to generate all needed .jam files to program and test HPTDC, Marek
  • creating code for CPLD, witch can be used to supply external trigger, Marek(CPLD)&Radek(changes on ETRAX)
  • merge VHDL code from Tiago together with code witch was created by K.K, Marek
  • creating ISP interface on Etrax, Radek
>
>
  • command line tool to generate all needed .jam files to program and test HPTDC, Marek done
  • merge VHDL code from Tiago together with code witch was created by K.K, Marek done
  • creating SPI interface on Etrax, Radek done
 

RPC Documentation

Line: 46 to 45
 
Added:
>
>
 

Feature List:

  • : Question to Radek: What is the transferspeed of reading data from external memory to internal one (MBytes/s)?
  • : Answer: Average transfer speed is 1,3 MBytes/s from Etrax to an external Computer which receives the data.
Added:
>
>

Patch list

 

Progress Reports:

Revision 23
Changes from r21 to r23
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 21 to 21
 

Improvements for the future (new software and new TRB)

Deleted:
<
<
  • It would be great to get a running TRB (with HADES-Trigger-Bus) till end of August!
 
  • Kris made the very smart remark: Why do we copy data from Dual-Ported-Ram to ETRAX RAM and then to Ethernet. We agreed that we will keep everything as it is (copy it) and change to a smarter transfer after the first running-TRB in the HADES-experiment (so after October)
Line: 46 to 45
 
Added:
>
>
 

Feature List:

  • : Question to Radek: What is the transferspeed of reading data from external memory to internal one (MBytes/s)?
Changed:
<
<
  • : Answer: Average transfer speed is 1,3 MBytes/s
>
>
  • : Answer: Average transfer speed is 1,3 MBytes/s from Etrax to an external Computer which receives the data.
 

Progress Reports:

Revision 21
Changes from r19 to r21
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 52 to 52
 
  • : Question to Radek: What is the transferspeed of reading data from external memory to internal one (MBytes/s)?
  • : Answer: Average transfer speed is 1,3 MBytes/s
Changed:
<
<
  • Segmentation fault on ETRAX -> the problem is in the 'rt' library, one cannot use shm_open(). This system function return -1.
    11:40 -> this means ''not implemented in system'' why?
    12:00 -> ''System V IPC' is NOT enabled in your kernel configuration
    15:30-> compilation of new kernel was done, above point is now enough, I have to add /dev/shm directory and mount it 17:00-> I can't change fstab on depc152, I have done it directly on hades18: memnet is working now, but I have new message: creating shared memory "subevtqueue": Function not implemented.. I have created program shm_foo and the share memory is orking for sure.
    The problem is with the sem_unlink() function ->it's system function too
    after 21:00 smile I have cut out the headers <semaphore.h>(it's system header), and now I'm using compat library.
    now the error is: opening network transport depc152.gsi.de:2222: Invalid argument, I have no idea which argument is ok.
    In friday I want to prepare evtbuider application.
  • main dir: MAIN=/home/radek/new_axis/axis/devboard_82/apps
  • compat source && library: MAIN/compat && MAIN/my_libs
  • hadaq source && library: MAIN/hadaq_lib && && MAIN/my_libs. If one prepare hadaq library then one has to read Makefile in source dir
    FRIDAY
    Problem in evtbuilder -> seg fault in functions *Param, I try see where exactly
    -> desParam()
>
>

Progress Reports:

 

Added:
>
>
 
Revision 19
Changes from r17 to r19
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 56 to 56
  11:40 -> this means ''not implemented in system'' why?
12:00 -> ''System V IPC' is NOT enabled in your kernel configuration
15:30-> compilation of new kernel was done, above point is now enough, I have to add /dev/shm directory and mount it
Changed:
<
<
17:00-> I can't change fstab on depc152, I have done it directly on hades18: memnet is working now, but I have new message: creating shared memory "subevtqueue": Function not implemented.. I have created program shm_foo and the share memory is orking for sure.
>
>
17:00-> I can't change fstab on depc152, I have done it directly on hades18: memnet is working now, but I have new message: creating shared memory "subevtqueue": Function not implemented.. I have created program shm_foo and the share memory is orking for sure.
The problem is with the sem_unlink() function ->it's system function too
after 21:00 smile I have cut out the headers <semaphore.h>(it's system header), and now I'm using compat library.
now the error is: opening network transport depc152.gsi.de:2222: Invalid argument, I have no idea which argument is ok.
In friday I want to prepare evtbuider application.
  • main dir: MAIN=/home/radek/new_axis/axis/devboard_82/apps
  • compat source && library: MAIN/compat && MAIN/my_libs
  • hadaq source && library: MAIN/hadaq_lib && && MAIN/my_libs. If one prepare hadaq library then one has to read Makefile in source dir
    FRIDAY
    Problem in evtbuilder -> seg fault in functions *Param, I try see where exactly
    -> desParam()

 
Revision 17
Changes from r15 to r17
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 56 to 56
  11:40 -> this means ''not implemented in system'' why?
12:00 -> ''System V IPC' is NOT enabled in your kernel configuration
15:30-> compilation of new kernel was done, above point is now enough, I have to add /dev/shm directory and mount it
Added:
>
>
17:00-> I can't change fstab on depc152, I have done it directly on hades18: memnet is working now, but I have new message: creating shared memory "subevtqueue": Function not implemented.. I have created program shm_foo and the share memory is orking for sure.
 
Revision 15
Changes from r13 to r15
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 52 to 52
 
  • : Question to Radek: What is the transferspeed of reading data from external memory to internal one (MBytes/s)?
  • : Answer: Average transfer speed is 1,3 MBytes/s
Changed:
<
<
  • Segmentation fault on ETRAX -> the problem is in the 'rt' library, one cannot use shm_open(). This system function return -1.
>
>
  • Segmentation fault on ETRAX -> the problem is in the 'rt' library, one cannot use shm_open(). This system function return -1.
    11:40 -> this means ''not implemented in system'' why?
    12:00 -> ''System V IPC' is NOT enabled in your kernel configuration
    15:30-> compilation of new kernel was done, above point is now enough, I have to add /dev/shm directory and mount it
 
Revision 13
Changes from r11 to r13
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 45 to 45
 

Changed:
<
<
  • TDCprogramming
>
>
 

Feature List:

  • : Question to Radek: What is the transferspeed of reading data from external memory to internal one (MBytes/s)?
  • : Answer: Average transfer speed is 1,3 MBytes/s
Added:
>
>
  • Segmentation fault on ETRAX -> the problem is in the 'rt' library, one cannot use shm_open(). This system function return -1.
Revision 11
Changes from r9 to r11
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 37 to 37
  Next tasks (2005-07-11):

  • command line tool to generate all needed .jam files to program and test HPTDC, Marek
Added:
>
>
  • creating code for CPLD, witch can be used to supply external trigger, Marek(CPLD)&Radek(changes on ETRAX)
  • merge VHDL code from Tiago together with code witch was created by K.K, Marek
  • creating ISP interface on Etrax, Radek
 

RPC Documentation

Added:
>
>
  • TDCprogramming
 

Feature List:

  • : Question to Radek: What is the transferspeed of reading data from external memory to internal one (MBytes/s)?
Added:
>
>
  • : Answer: Average transfer speed is 1,3 MBytes/s
 
Revision 9
Changes from r7 to r9
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 19 to 19
 

Added:
>
>

Improvements for the future (new software and new TRB)

  • It would be great to get a running TRB (with HADES-Trigger-Bus) till end of August!
  • Kris made the very smart remark: Why do we copy data from Dual-Ported-Ram to ETRAX RAM and then to Ethernet. We agreed that we will keep everything as it is (copy it) and change to a smarter transfer after the first running-TRB in the HADES-experiment (so after October)
  • I want to ask: Why do we have a dual-ported RAM at all? We don't use it! So, in the next version of the TRB I would opt for a FIFO there.
  • The next (after October) software version of TRB should make all event-formatting to the HADES-event-standard in the FPGA. Now we keep the C-version, because it is easier to change.
 

Tasks

Marek & Radek Team:

Next tasks (2005-07-11):
Deleted:
<
<
  • send data from Etrax to ethernet direct by TCP/IP protocol -- smile ready smile Documentation
  • webpage on Etrax to ganerate all needed .jam files to program and test HPTDC
 
Changed:
<
<
--++ RPC Documentation
>
>
  • command line tool to generate all needed .jam files to program and test HPTDC, Marek

RPC Documentation

 
Added:
>
>
  • Documentation of the Etrax->Ethernet TCP/IP programs: RamEthernet
 
Added:
>
>

Feature List:

  • : Question to Radek: What is the transferspeed of reading data from external memory to internal one (MBytes/s)?
Revision 7
Changes from r5 to r7
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 13 to 13
 
  • Ability to use 32-channels input for Wolfgang Koenig (jumper based?)
Added:
>
>
RPCMinutesMeeting20050524
 

Infos

Line: 23 to 25
  Marek & Radek Team:

Next tasks (2005-07-11):
Changed:
<
<
  • send data from Etrax to ethernet direct by TCP/IP protocol -- smile ready smile
>
>
  • send data from Etrax to ethernet direct by TCP/IP protocol -- smile ready smile Documentation
 
  • webpage on Etrax to ganerate all needed .jam files to program and test HPTDC
Added:
>
>
--++ RPC Documentation

Revision 5
Changes from r3 to r5
Line: 1 to 1
 

TRB (TDC - Readout-Board for RPC and other tasks)

Added:
>
>

Meetings

  List of things to be done in version 0.99 of TRB:

To be discussed on the meeting 24.05. 15:00
Line: 11 to 13
 
  • Ability to use 32-channels input for Wolfgang Koenig (jumper based?)
Changed:
<
<
-- MichaelTraxler - 21 Apr 2005
>
>

Infos

Tasks

 

Marek & Radek Team:
Changed:
<
<
Next tasks:
  • send data from Etrax to ethernet direct by TCP/IP protocol
>
>
Next tasks (2005-07-11):
  • send data from Etrax to ethernet direct by TCP/IP protocol -- smile ready smile
 
  • webpage on Etrax to ganerate all needed .jam files to program and test HPTDC
Revision 3
Changes from r1 to r3
Line: 1 to 1
Deleted:
<
<
 

TRB (TDC - Readout-Board for RPC and other tasks)

Line: 12 to 11
 
  • Ability to use 32-channels input for Wolfgang Koenig (jumper based?)
Added:
>
>
-- MichaelTraxler - 21 Apr 2005
 
Added:
>
>
Marek & Radek Team:
 
Added:
>
>
Next tasks:
  • send data from Etrax to ethernet direct by TCP/IP protocol
  • webpage on Etrax to ganerate all needed .jam files to program and test HPTDC
 
Deleted:
<
<
-- MichaelTraxler - 21 Apr 2005
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)