FMC ADC 100M 14b 4cha - Software issueshttps://ohwr.org/project/fmc-adc-100m14b4cha-sw/issues2019-02-18T13:17:23Zhttps://ohwr.org/project/fmc-adc-100m14b4cha-sw/issues/116 Bit Offset2019-02-18T13:17:23ZTim Mottram16 Bit OffsetCurrently the offset is passed by applications to the driver in mV.
However the DAC has a maximum resolution of 16 bits. Allowing the user
to provide a 16 bit value will improve the offset resolution.https://ohwr.org/project/fmc-adc-100m14b4cha-sw/issues/4Allocation bug2019-02-12T10:41:28ZJuan David González CobasAllocation bugBy repeating several multishot acquisitions like the following command
pcgw23:fmc-adc$ sudo /usr/local/bin/fald-simple-acq -c 0 -t 0 -n 10 -p 0
-P 2000 0x500
Open ADC fmcadc\_100MS\_4ch\_14bit dev\_id 0x0500 ...
Configuring trigger ...
Configuring acquisition ...
Start Acquisition ...
Cannot apply acquisition configuration: (1) Operation not permitted
we arrive at the error above which comes from an allocation failure
(dmesg follows):
spec 0000:05:00.0: Start DMA transfer
spec 0000:05:00.0: irq status = 0x0 multi = 0x0
spec 0000:05:00.0: irq status = 0x1 multi = 0x0
spec 0000:05:00.0: Handle ADC interrupts
spec 0000:05:00.0: unmap DMA
cset0: Data done
cset0: Store Block 1/10
cset0: Store Block 2/10
cset0: Store Block 3/10
cset0: Store Block 4/10
cset0: Store Block 5/10
cset0: Store Block 6/10
cset0: Store Block 7/10
cset0: Store Block 8/10
cset0: Store Block 9/10
cset0: Free un-acquired block 10/10 (received 9 shots)
spec 0000:05:00.0: 0 blocks transfered
spec 0000:05:00.0: irq status = 0x0 multi = 0x0
trigger: Writing 0 in the sysfs attribute external
trigger: Writing 0 in the sysfs attribute int-channel
trigger: Writing 0 in the sysfs attribute int-threshold
trigger: Writing 0 in the sysfs attribute polarity
trigger: Writing 10 in the sysfs attribute nshots
trigger: Writing 2000 in the sysfs attribute post-samples
trigger: Writing 0 in the sysfs attribute pre-samples
cset0: Writing 1 in the sysfs attribute fsm-command
trigger: Arming trigger
trigger: programmed shot 10
cset0: Allocating block 0 ...
cset0: next dev\_mem\_ptr 0x3e80 (+16000) cset0: Allocating block 1
...
cset0: next dev\_mem\_ptr 0x7d00 (+16000) cset0: Allocating block 2
...
cset0: next dev\_mem\_ptr 0xbb80 (+16000) cset0: Allocating block 3
...
cset0: next dev\_mem\_ptr 0xfa00 (+16000) cset0: Allocating block 4
...
cset0: next dev\_mem\_ptr 0x13880 (+16000) cset0: Allocating block 5
...
cset0: next dev\_mem\_ptr 0x17700 (+16000) cset0: Allocating block 6
...
cset0: next dev\_mem\_ptr 0x1b580 (+16000) cset0: Allocating block 7
...
cset0: next dev\_mem\_ptr 0x1f400 (+16000) cset0: Allocating block 8
...
cset0: arm trigger fail, cannot allocate block
spec 0000:05:00.0: Trigger not armed, cannot start acquisition
### Files
* [dmesg7](/uploads/4dfab64f8c67efab9d044d4115c4c75e/dmesg7)Alessandro RubiniAlessandro Rubinihttps://ohwr.org/project/fmc-adc-100m14b4cha-sw/issues/3busid parameter absent2019-02-12T10:41:27ZJuan David González Cobasbusid parameter absentNot having a busid insmod parameter makes **very** hard to install two
SPECs with different mezzanines in the same system.
Actually, fmc-adc tries to program both boards if the fine-delay is not
programmed first; this is dangerous and, worse,
it will not scale.Federico VagaFederico Vagahttps://ohwr.org/project/fmc-adc-100m14b4cha-sw/issues/2can not access dummy image2019-02-12T10:41:26ZPiotr Miedzikcan not access dummy imageCan not download dummy image mentioned on
https://www.ohwr.org/project/fmc-adc-100m14b4cha-sw/wikis/Frequently_Asked_Questions
page
https://www.ohwr.org/project/fmc-adc-100m14b4cha/uploads/1711cbd4515984d6bbf51eb14d0117d6/fmc-adc_dummy_eeprom_image.out