[casper] PowerPC C code modified to automate the transmission of the shared BRAM / IBOB

2014-07-04 Thread Rolando Paz
Hi again everyone! I do not know if some one still remember this ... :-) but I will do the question: I'm trying to modify the PowerPC code which interacts with LWIP in order to automate the transmission of the shared BRAM from my correlator, but I was unable accomplish it. I'm using CMD

Re: [casper] PowerPC C code modified to automate the transmission of the shared BRAM / IBOB

2014-07-04 Thread G Jones
Hi Rolando, I think you mentioned that you are able to communicate with the IBOB over ethernet. Is that correct? Can you read and set registers using the UDP interface? If so, then the communication is working and the problem is not the communication itself. Glenn On Fri, Jul 4, 2014 at 9:59

Re: [casper] PowerPC C code modified to automate the transmission of the shared BRAM / IBOB

2014-07-04 Thread G Jones
Yeah, somehow it looks like the new main.c you are trying to use is not getting included. Where are you putting the main.c? One thing you can try is instead of putting your new main.c in there, try just deleting the main.c that is there and try the run init_bram. If it does not fail, then that

Re: [casper] PowerPC C code modified to automate the transmission of the shared BRAM / IBOB

2014-07-04 Thread Rolando Paz
When the design is compiled, several folders are created. The XPS_IBOB_base folder is one of them, and inside this folder is created the Software folder, and inside this folder is created the main.c file. I remove this main.c file created by the compilation, and I copy the new main.c in the same

Re: [casper] PowerPC C code modified to automate the transmission of the shared BRAM / IBOB

2014-07-04 Thread G Jones
I think that's the wrong place. You want something in the implementation directory if i recall correctly. Glenn On Jul 4, 2014 11:05 AM, Rolando Paz flx...@gmail.com wrote: When the design is compiled, several folders are created. The XPS_IBOB_base folder is one of them, and inside this folder

Re: [casper] PowerPC C code modified to automate the transmission of the shared BRAM / IBOB

2014-07-04 Thread Rolando Paz
https://casper.berkeley.edu/svn/trunk/projects/pocketcorrelator/poco-0.1.1/docs/poco_user_guide This is the Griffin guide : 2: PowerPC Code --- The embedded PowerPC C code which interacts with LWIP needs to be modified

Re: [casper] ADC 5GS error in ROACH2

2014-07-04 Thread Geelen, T.F.G.
Hi, I've been helping Andres and applied the patch you send to the system files using git-apply. Double checked the system files to see if it worked correctly. After that we tries recompiling the program but the error remains. Constructing platform-level connectivity ... ERROR:EDK:4072 -

Re: [casper] ADC 5GS error in ROACH2

2014-07-04 Thread Jack Hickish
Hi, Just a thought - Is it possible that the zdok you've selected for the ADC doesn't match the clock selected in the mssge block? I.e., if you're ADC is on zdok0, are you clocking off adc0 and not adc1? Cheers, Jack On 4 Jul 2014 09:46, Geelen, T.F.G. t.f.g.gee...@student.tue.nl wrote: Hi,

Re: [casper] ADC 5GS error in ROACH2

2014-07-04 Thread Geelen, T.F.G.
Hi Jack, That solved almost all the problems. We were indeed trying to use the wrong clock for the wrong ADC. Stupid mistake. However I still have three of these error left... Constructing platform-level connectivity ... ERROR:EDK:4072 - INSTANCE: spec_roach2_1200_asiaa_adc5g, PORT: datain_pin

Re: [casper] ADC 5GS error in ROACH2

2014-07-04 Thread Primiani, Rurik
Are you sure you applied the patch? Can you send your system.mhs from your design's XPS_ROACH2_base directory? On Fri, Jul 4, 2014 at 1:53 PM, Geelen, T.F.G. t.f.g.gee...@student.tue.nl wrote: Hi Jack, That solved almost all the problems. We were indeed trying to use the wrong clock for

Re: [casper] ADC 5GS error in ROACH2

2014-07-04 Thread Primiani, Rurik
That is the pre-parsed system.mhs from your mlib_devel working copy. When you compile a design the toolflow copies over the mlib_devel/XPS_ROACH2_base to a new directory at the same location of your design's MDL file and then it parses system.mhs. Can you please send that parsed version from your