DAQ OS: front end libraries: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 9: | Line 9: | ||
vxMemProbe((char *)addr,int,int,(char *)&data) | vxMemProbe((char *)addr,int,int,(char *)&data) | ||
usrVmeDmaShow() | usrVmeDmaShow() | ||
usrVmeDmaGetConfig(UINT32 *addrType, UINT32 *dataType, int *sstMode) | |||
usrVmeDmaConfig(UINT32 addrType, UINT32 dataType, int sstMode) | usrVmeDmaConfig(UINT32 addrType, UINT32 dataType, int sstMode) | ||
usrVme2MemDmaStart(UCHAR *vmeAddr, UCHAR *destAddr, UINT32 nbytes) - addresses in user space | usrVme2MemDmaStart(UCHAR *vmeAddr, UCHAR *destAddr, UINT32 nbytes) - addresses in user space |
Revision as of 09:48, 19 April 2011
All front end libraries are licated in $CODA/src/rol/code.s directory. To compile use gmake clean, gmake and gmake install. For vxWorks use clon10/clon00 servers only (it will work on RHEL as well, but historically we do it on sparc machines).
Generic software development rules
- All vxWorks- or UNIX-specific functions must have identical names and interfaces and must be included in kernels, BSPs or separate libraries, so board-specific library will be generic. In particular following functions must be available:
sysBusToLocalAdrs(int modifier,(char *)addr,(char **)&laddr)
vxMemProbe((char *)addr,int,int,(char *)&data)
usrVmeDmaShow() usrVmeDmaGetConfig(UINT32 *addrType, UINT32 *dataType, int *sstMode) usrVmeDmaConfig(UINT32 addrType, UINT32 dataType, int sstMode) usrVme2MemDmaStart(UCHAR *vmeAddr, UCHAR *destAddr, UINT32 nbytes) - addresses in user space usrVme2MemDmaListSet(UINT32 *vmeAddr, UINT32 *destAddr, int nbytes[], int numt) - addresses in user space usrVmeDmaListStart() usrVme2MemDmaDone()
val = vmeRead8(unsigned char *addr) vmeWrite8(unsigned char *addr, unsigned char val) val = vmeRead16(unsigned short *addr) vmeWrite16(unsigned short *addr, unsigned short val) val = vmeRead32(unsigned int *addr) vmeWrite32(unsigned int *addr, unsigned int val)
- Every board has distinctive name, for example v1495 or tdc1190. That name must be used in the files name, as well as in function names and global names to avoid duplicates. At least two files must be provided, for example v1495.c and v1495.h, where header file will be used in user readout lists.
- DMA configuration procedures must be called outside of particular boards libraries before any board's Init functions are called.
- Boards initialization function called once before any other calles. It must have at least three following arguments (as first arguments):
first board address (as it set by onboard switches) address step between boards the number of boards
It does a scan looking for all available boards and assign board IDs starting from 0. It returns the number of boards found. All individual board operations must be performed using that ID.
- Boards configuration function can be called several times, it does generic boards initiaization.