Hi Dave, Your observation looks valid. With the reworked kat_adc_iic_controller and programming the autoconfig.v registers via software, you should have the same setup as you had with ROACH 1.
Regards, Henno On Mon, Jul 1, 2013 at 7:02 PM, David MacMahon <[email protected]>wrote: > Hi, Henno, > > I think the problem is that the opb_katadccontroller pcore has an > autoconfig.v file in the ROACH1 base system, but that file (and therefore > its functionality) does not exist in the ROACH2 base system, so it's like > the "Bypass auto config" option is always checked on ROACH2. The > autoconfig.v file looks like it programs registers on the ADC chip itself > using registers inside the kat_adc_controller device (as named in > core_info.tab), so I assume anyone using KATADC with the "bypass auto > config" option checked will have an example of how to program the ADC > chip's registers from software that will be equally (if not more!) valid on > ROACH2 as on ROACH1. Maybe the autoconfig stuff only matters for > interleaved operation or maybe nobody uses KATADC with the "Bypass auto > config" option checked on ROACH1? > > FWIW, I built a test model for ROACH2 using KATADC and the data_valid > output from the ADC stays low, but I'm not exactly sure what that means. I > have the latest kat_adc_iic_controller, but what do I need to do with it to > get the card working? > > Thanks, > Dave > > On Jul 1, 2013, at 12:42 AM, Henno Kriel wrote: > > > Hi Nimish > > > > I suspect your problem is related to the KATADC I2C contoller for > ROACH2. I had to modified it to work with the EPB 32bit bus and related > byte enables access a while ago. Just check the your KAT_ADC_IIC_CONTROLLER > pcore against the in the SKA-SA repo. This might explain why your ADC is > not getting properly set up. > > > > Regards, > > Henno > > > > > > On Sat, Jun 29, 2013 at 1:43 AM, Nimish Sane <[email protected]> > wrote: > > Hi all, > > > > Resending an earlier message in case somebody who knows this missed it. > We believe (and Dave Macmahon confirms from his tests) that for using > KATADC with ROACH2, it needs to configured through software (corr package?) > to make it usable. Does anyone have any clue regarding what parameters > needs to be configured, what are the corresponding python utilities and > what are the correct settings? > > > > Thanks a lot, > > > > Nimish > > > > On Fri, Jun 21, 2013 at 4:22 PM, Nimish Sane <[email protected]> > wrote: > > Hi all, > > > > Can someone throw light on how to configure the KATADC yellow block so > that one can use some of the python wrappers in corr package to configure > it from the katcp interface? > > > > The KATADC yellow block has two fields "ADC Interleave mode" and "Bypass > auto config", which we normally leave unselected. We do not configure any > parameter from the python/katcp interface using corr package utilities. We, > however, recently learnt that some of these parameters can be (or should > be!) configured using those utilities and we would like to know if and how > that can be done. If someone could provide information on which python > utilities to use and what are the valid parameter settings, that would be > useful. Also, in order to do that, does the yellow block have to configured > in a particular way? > > > > Thanks, > > > > Nimish > > > > > > > > > > > > -- > > Henno Kriel > > > > System Architect: MeerKAT Digitiser > > > > SKA South Africa > > Third Floor > > The Park > > Park Road (off Alexandra Road) > > Pinelands > > 7405 > > Western Cape > > South Africa > > > > Latitude: -33.94329 (South); Longitude: 18.48945 (East). > > > > (p) +27 (0)21 506 7300 > > (p) +27 (0)21 506 7365 (direct) > > (f) +27 (0)21 506 7375 > > (m) +27 (0)84 504 5050 > > -- Henno Kriel System Architect: MeerKAT Digitiser SKA South Africa Third Floor The Park Park Road (off Alexandra Road) Pinelands 7405 Western Cape South Africa Latitude: -33.94329 (South); Longitude: 18.48945 (East). (p) +27 (0)21 506 7300 (p) +27 (0)21 506 7365 (direct) (f) +27 (0)21 506 7375 (m) +27 (0)84 504 5050
