Pixie-32 User Manual
Version 0.2
Boot_Pattern
is an unsigned 16-bit integer that represents a bit mask used to control the boot
pattern of the Pixie-32 modules:
Bit 0:
ignored
Bit 1: Boot signal processing FPGA (
using file path from configuration file)
Bit 2:
ignored
Bit 3: Load parameters
. (reads parameters from Fip_Regs_m##.txt file, checks parameter
ranges)
Bit 4: Apply parameters
(reads parameters from Fip_Regs_m##.txt file, writes to
hardware)
Bit 5:
ignored
ModNum
is an unsigned 8-bit integer that represents module number intended to receive the
Pixie32_Boot_System command. If ModNum == the number of modules present in system, this
function will loop over each module and boot all. Module numbering is 0-based, so to address a
single module, 0 <= ModNum < number of modules.
Return Parameters:
status:
is a 32-bit integer indicating the status of the function call. 0---success, negative--error.
API Function: Pixie_Acquire_Data
Syntax
S32 status Pixie_Acquire_Data (uint16 Run_Type,
uint32 *User_Data,
char *file_name,
uint8 ModNum);
Description:
Use this function to start/stop a run, acquire run data, and other run control functions.
Calling Parameters:
Run_Type
is a 16-bit word whose lower 12-bit specifies the type of either data run or control task
run and whose upper 4-bit specifies actions (start\stop\poll) as described below.
User_Data
is a pointer to either:
a) pre-allocated array of unsigned integers of arbitrary size (caller ensures that User_ptr has the
correct size and data type before reading out statistics).
b) a function pointer to a user supplied callback function that is attached to the interrupt service
routine for that module. The main purpose of this function will be to retrieve the 2MB of data that
is ready on the interrupting module.
If no data is returned to user, User_Data would be NULL pointer.
© 2017 XIA LLC
25
