Re: [casper] F engine for Packetized correlator
Dear Jason, Currently we are trying the packetized correlator using Corr-0.4.0 and a modified model of F-engine (using 2 iADC) provided by Homin. But we got some problems when initializing this correlator using corr_init.py. The details are listed below: 1. When we execute the corr_init.py, the initial configuration step seems work fine, but the verifying correct operation failed. The error message is as below: == Initial configuration: == Clearing the FPGAs... done. Programming the FPGAs with r_4f_2x_16a_r322g_2010_Jan_05_2131.bof...done. Pausing 10GbE data exchange, resetting the 10GbE cores and clearing X engine TVGs... done. Configuring the 10GbE cores... done Clearing F engine TVG register... done Syncing the iBOBs, resetting F engine TVGs setting FFT shift... Armed. Expecting trigger at 17:28:20 local. Setting the accumulation length to 8192 (14.32 seconds)... done Setting the antenna indices... 0 done Setting the UDP TX data port to ... done Setting the 10GbE IP addresses... done Starting 10GbE data exchange... done. Configuring UDP output... done. Configuring EQ... done Verifying correct operation... Wait for system to stabalise... done Resetting error counters... done Checking that all XAUI links are working... FAILURES detected! Details: Missing F engine data on 140.109.176.145, XAUI port 0. Checking that all BEE FPGAs are sending 10GbE packets... FAILURES detected! 10GbE core 0 on 140.109.176.145 is stalled. Checking that all BEE FPGAs are receiving 10GbE packets... FAILURES detected! FAILURE! 10GbE core 0 on 140.109.176.145 is not receiving any packets. Checking loopback mux... FAILURES detected! FAILURE! Loopback mux on 140.109.176.145 GbE port 0 is not syncd. FAILURE! Loopback on 140.109.176.145 GbE port 0 is stalled. FAILURE! 10GbE input on 140.109.176.145 GbE port 0 is stalled. Checking that all X engines are receiving all their packets... FAILURES detected! Missing X engine data on 140.109.176.145, X engine 0 2. After tracing into ibob F engine model i28_2k_10_r306, it seems the led1 led2 of ibob are connected to armed and sys_gen which means it should be turned on if the F-engine is armed successfully. But the led is never turned on in our case. Is it possible to have something to do with the sync signal? Currently we didn't do anything on sync signal. Also, the xaui_link_down is connected to led6, but it also never turned on. 3. Although we can write registers value to F-engine by the help of X-engine, but the problem we met is that we are not sure if the F-engine operates correctly or not. Do you have any suggestion on how to verify and debug the operation of F-engine? Thank you very much for your help. Thanks and Regards, Wei-Chung
Re: [casper] F engine for Packetized correlator
wei-chung, jason is in the karoo deploying a new PAPER correlator so i'm not sure when he'll be able to read your email. do you have 1 pulse per second sync signal going into your iADC boards? you need to drive one of the two iADC boards on each iBOB with a 1 PPS signal so all the iBOB's can sync up together and time stamp the data.. best wishes, dan On 1/31/2010 8:35 PM, Wei Chung Hsieh wrote: Dear Jason, Currently we are trying the packetized correlator using Corr-0.4.0 and a modified model of F-engine (using 2 iADC) provided by Homin. But we got some problems when initializing this correlator using *corr_init.py*. The details are listed below: 1. When we execute the *corr_init.py*, the initial configuration step seems work fine, but the verifying correct operation failed. The error message is as below: == Initial configuration: == Clearing the FPGAs... done. Programming the FPGAs with r_4f_2x_16a_r322g_2010_Jan_05_2131.bof...done. Pausing 10GbE data exchange, resetting the 10GbE cores and clearing X engine TVGs... done. Configuring the 10GbE cores... done Clearing F engine TVG register... done Syncing the iBOBs, resetting F engine TVGs setting FFT shift... Armed. Expecting trigger at 17:28:20 local. Setting the accumulation length to 8192 (14.32 seconds)... done Setting the antenna indices... 0 done Setting the UDP TX data port to ... done Setting the 10GbE IP addresses... done Starting 10GbE data exchange... done. Configuring UDP output... done. Configuring EQ... done Verifying correct operation... Wait for system to stabalise... done Resetting error counters... done Checking that all XAUI links are working... FAILURES detected! Details: Missing F engine data on 140.109.176.145, XAUI port 0. Checking that all BEE FPGAs are sending 10GbE packets... FAILURES detected! 10GbE core 0 on 140.109.176.145 is stalled. Checking that all BEE FPGAs are receiving 10GbE packets... FAILURES detected! FAILURE! 10GbE core 0 on 140.109.176.145 is not receiving any packets. Checking loopback mux... FAILURES detected! FAILURE! Loopback mux on 140.109.176.145 GbE port 0 is not syncd. FAILURE! Loopback on 140.109.176.145 GbE port 0 is stalled. FAILURE! 10GbE input on 140.109.176.145 GbE port 0 is stalled. Checking that all X engines are receiving all their packets... FAILURES detected! Missing X engine data on 140.109.176.145, X engine 0 2. After tracing into ibob F engine model *i28_2k_10_r306*, it seems the *led1* *led2* of ibob are connected to *_armed_ *and *_sys_gen_* which means it should be turned on if the F-engine is armed successfully. But the led is never turned on in our case. Is it possible to have something to do with the sync signal? Currently we didn't do anything on sync signal. Also, the *xaui_link_down* is connected to *led6*, but it also never turned on. 3. Although we can write registers value to F-engine by the help of X-engine, but the problem we met is that we are not sure if the F-engine operates correctly or not. Do you have any suggestion on how to verify and debug the operation of F-engine? Thank you very much for your help. Thanks and Regards, Wei-Chung
[casper] filesystem update
I updated my usb stick to the filesystem: http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/filesystem/filesystem_etch_2009-11-30.tar.bz when I 'run usbboot' I get to: sd 1:0:0:0: [sda] 15794175 512-byte hardware sectors (8087 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Assuming drive cache: write through sd 1:0:0:0: [sda] 15794175 512-byte hardware sectors (8087 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 1:0:0:0: [sda] Attached SCSI removable disk EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 136k init Warning: unable to open an initial console. warning: `ntpd' uses 32-bit capabilities (legacy support in use) and then the boot process freezes. I've repartitioned and rebuilt the filesystem as ext3 and then simply copied (cp -rp) over the files as i've done on other working usb sticks. Any suggestions? Thanks, Mark
Re: [casper] filesystem update
Hey Mark. I would check my /dev/ entries. Remember they cannot be extracted by non-root, they might have gone missing. Cheers, David I updated my usb stick to the filesystem: http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/filesystem/filesystem_etch_2009-11-30.tar.bz when I 'run usbboot' I get to: sd 1:0:0:0: [sda] 15794175 512-byte hardware sectors (8087 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Assuming drive cache: write through sd 1:0:0:0: [sda] 15794175 512-byte hardware sectors (8087 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 1:0:0:0: [sda] Attached SCSI removable disk EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 136k init Warning: unable to open an initial console. warning: `ntpd' uses 32-bit capabilities (legacy support in use) and then the boot process freezes. I've repartitioned and rebuilt the filesystem as ext3 and then simply copied (cp -rp) over the files as i've done on other working usb sticks. Any suggestions? Thanks, Mark -- David George Digital Design Engineer Karoo Array Telescope Tel: +27 21 531-7282 Fax: +27 21 531-9761 Email: david.geo...@ska.ac.za Web: www.ska.ac.za
