dma_ip_drivers issueshttps://gitlab.mpcdf.mpg.de/bcar/dma_ip_drivers/-/issues2021-12-02T11:46:24Zhttps://gitlab.mpcdf.mpg.de/bcar/dma_ip_drivers/-/issues/18Add support to read interlock data2021-12-02T11:46:24ZNejc Smrkolj KozeljAdd support to read interlock dataAt the moment we can set all the necessary interlock values but are unable to read any results.At the moment we can set all the necessary interlock values but are unable to read any results.https://gitlab.mpcdf.mpg.de/bcar/dma_ip_drivers/-/issues/12IPMC Module - FPGA Integration2021-09-24T11:33:52ZBernardo CarvalhoIPMC Module - FPGA IntegrationIt would be nicw to test communication beteenw the uProcessor on the IPMC module and the FPGA
using the I2C interface. Namelly the FPGA could read the Board physical slot and some temperatures.
The present address of the slave core is 0x...It would be nicw to test communication beteenw the uProcessor on the IPMC module and the FPGA
using the I2C interface. Namelly the FPGA could read the Board physical slot and some temperatures.
The present address of the slave core is 0x3c (7 bit)
The I2C slave protocol is described bellow
```verilog
Perform device address matching
//// Handle arbitrary length I2C reads terminated by NAK
//// from host, and arbitrary length I2C writes terminated
//// by STOP from host
//// The first byte of a I2C is always Address
//// The second byte of a I2C write is always interpreted
//// as a register address, and becomes the base register address
//// for all read and write transactions.
//// I2C WRITE: devAddr, regAddr, data[regAddr], data[regAddr+1], ..... data[regAddr+N]
//// I2C READ: data[regAddr], data[regAddr+1], ..... data[regAddr+N]
```Manfred M. ZilkerManfred M. Zilkerhttps://gitlab.mpcdf.mpg.de/bcar/dma_ip_drivers/-/issues/11New features planned for upcoming versions2021-09-22T11:45:55ZManfred M. ZilkerNew features planned for upcoming versionsHere is a list of planned features for the next versions of firmware/software:
1) Firmware version information available in API:
In the Standard Hardware API (SHAPI)-structure used in the device driver the entries for the correct firmwa...Here is a list of planned features for the next versions of firmware/software:
1) Firmware version information available in API:
In the Standard Hardware API (SHAPI)-structure used in the device driver the entries for the correct firmware identification (name, version, timestamp) can be readout with a new API call.https://gitlab.mpcdf.mpg.de/bcar/dma_ip_drivers/-/issues/10Library files and headers should be self containing2021-10-27T10:57:50ZNejc Smrkolj KozeljLibrary files and headers should be self containingLibrary files, especially headers should be self contained. They should include all libraries they need for their proper working. One such example is the need for import of stdint.h in atca-v2-daq.h for datatype uint32_t.Library files, especially headers should be self contained. They should include all libraries they need for their proper working. One such example is the need for import of stdint.h in atca-v2-daq.h for datatype uint32_t.https://gitlab.mpcdf.mpg.de/bcar/dma_ip_drivers/-/issues/8Add to library for various board values2021-09-29T17:36:50ZNejc Smrkolj KozeljAdd to library for various board valuesLibrary provides an entry point towards the hardware. Due to that it can access registers and through them a detailed board information. Any information that can potentially be useful towards higher levels should be exposed through libra...Library provides an entry point towards the hardware. Due to that it can access registers and through them a detailed board information. Any information that can potentially be useful towards higher levels should be exposed through library functions. This should also span the configuration we do on the board such as is device open, is 32 bit acquisition selected, are interlocks configured, etc.https://gitlab.mpcdf.mpg.de/bcar/dma_ip_drivers/-/issues/6Device name should be configurable2021-09-22T16:54:12ZNejc Smrkolj KozeljDevice name should be configurableAt the moment the device name is hardcoded via define and only device number can be changed. While in the current setup this works great this is not sustainable long term if underlying OS setup changes. Library should contain a possibili...At the moment the device name is hardcoded via define and only device number can be changed. While in the current setup this works great this is not sustainable long term if underlying OS setup changes. Library should contain a possibility to specify a full device name.