Hi Jack,

The bof was not a executable, and this seemed to be the problem.
Once I changed it to an executable, then the ROACH got programmed.

Thank to you and James :)

Regards,

Mugundhan

On Fri, Oct 13, 2017 at 10:34 AM, Jack Hickish <[email protected]>
wrote:

> Hi Mugundhan,
>
> Is the boffile that fails to program executable? I.e., if you log into the
> roach and run "ls -la /boffiles/" do the working and not-working boffiles
> have the asme permissions.
> (I don't actually know if roach1 still requires boffiles to be executable,
> but it used to, so maybe it's worth checking).
>
> Cheers
> Jack
>
> On Thu, 12 Oct 2017 at 20:58 Mugundhan vijayaraghavan <
> [email protected]> wrote:
>
>> Hi James,
>>
>> I tried it using the version of casperfpga you suggested. The same error
>> is returned.
>>
>> I'm attaching the python code that I'm using for programming the board.
>>
>> -
>> Regards,
>>
>> Mugundhan V.
>>
>> On Thu, Oct 12, 2017 at 5:24 PM, James Smith <[email protected]> wrote:
>>
>>> Hello Mugundhan,
>>>
>>> Casperfpga is a work in progress and unfortunately some of the more
>>> recent developments will have broken compatibility with ROACH1. Its main
>>> focus at the moment is SKARAB / ROACH2.
>>>
>>> I use the following commit to work on ROACH1:
>>> avnuser@planck:~/SKASoftware/casperfpga$ git show
>>> commit 475ed6826b893230d62da8c7dcdcc2541bea83cf
>>> Merge: 9835009 7402b29
>>> Author: Paul Prozesky <[email protected]>
>>> Date:   Fri Mar 4 17:27:09 2016 +0200
>>>
>>>     Merge branch 'devel' of github.com:ska-sa/casperfpga into devel
>>>
>>> Try installing casperfpga from that particular git commit and you'll
>>> likely be more successful.
>>>
>>> Also, before you use the fpga.program() function, you need to set the
>>> bof file in the system information - I think I have mentioned how to do
>>> this in the history of the mailing list somewhere before.
>>>
>>> Let me know if it works.
>>>
>>> Regards,
>>> James
>>>
>>>
>>> On Thu, Oct 12, 2017 at 12:35 PM, Mugundhan vijayaraghavan <
>>> [email protected]> wrote:
>>>
>>>> And I'm using the latest version of casperfpga library and katcp
>>>> version.
>>>>
>>>> On Thu, Oct 12, 2017 at 3:56 PM, Mugundhan vijayaraghavan <
>>>> [email protected]> wrote:
>>>>
>>>>> Hello James,
>>>>>
>>>>> I'm attaching the model files of the first and the second designs,
>>>>> along with the bof and the fga files. I used the ipython terminal for
>>>>> programming the fpga in both cases. The error I obtained is attached in a
>>>>> text file.
>>>>>
>>>>> Hope this helps,
>>>>>
>>>>> Thank you,
>>>>>
>>>>> Mugundhan V.
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Oct 12, 2017 at 3:49 PM, James Smith <[email protected]> wrote:
>>>>>
>>>>>> Hello Mugundhan,
>>>>>>
>>>>>> Please describe your context a bit more - what libraries are you
>>>>>> using? Please also paste the error that you get? (and perhaps the code 
>>>>>> you
>>>>>> used to generate the error.)
>>>>>>
>>>>>> Regards,
>>>>>> James
>>>>>>
>>>>>>
>>>>>> On Thu, Oct 12, 2017 at 12:17 PM, Mugundhan vijayaraghavan <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I'm facing a strange problem. I have an iADC, which I've connected
>>>>>>> to roach1 and have compiled a program to acquire raw samples from it. 
>>>>>>> The
>>>>>>> simulation, compilation and generation works fine and I get the bof and 
>>>>>>> the
>>>>>>> fpg files, which i place in their respective locations, and the ROACH 
>>>>>>> gets
>>>>>>> programmed well.
>>>>>>>
>>>>>>> I also developed a iADC spectropolarimeter and generated the fpg and
>>>>>>> bof files and placed them in their locations, but now when I try
>>>>>>> programming the ROACH, i get Katcp request time out error. If i 
>>>>>>> reprogram
>>>>>>> the first bof file, it works fine, but repeated compilation and program
>>>>>>> cycles have failed for hte second model, with the same katcp request 
>>>>>>> failed
>>>>>>> error.
>>>>>>>
>>>>>>> Can someone kindly guide me solving it ?
>>>>>>>
>>>>>>> Thank you,
>>>>>>>
>>>>>>> --
>>>>>>> V. Mugundhan
>>>>>>> SRF, IIA
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "[email protected]" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to [email protected].
>>>>>>> To post to this group, send email to [email protected].
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "[email protected]" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to [email protected].
>>>>>> To post to this group, send email to [email protected].
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> V. Mugundhan
>>>>> SRF, IIA
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> V. Mugundhan
>>>> SRF, IIA
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "[email protected]" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>>
>>
>>
>>
>> --
>> V. Mugundhan
>> SRF, IIA
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "[email protected]" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>>
> --
> You received this message because you are subscribed to the Google Groups "
> [email protected]" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
>



-- 
V. Mugundhan
SRF, IIA

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].

Reply via email to