I stand corrected, but I believe Brian Bradford fixed this in the new
JASPER toolflow i.e. there is no reference to ROACH1 or ROACH2? Just
checked - seems this is the case.

Glad all is sorted.

Kind regards,

Adam Isaacson
South African Radio Astronomy Observatory (SARAO)
Hardware Manager
Cell: (+27) 825639602
Tel:  (+27) 215067300
email: aisaac...@ska.ac.za



On Mon, Mar 11, 2019 at 7:26 PM Jack Hickish <jackhick...@gmail.com> wrote:

> Heh. See this bug report that after 6 years I guess I decided it was time
> to give up on.
>
> https://github.com/casper-astro/mlib_devel/issues/7
>
> Reopened. Check back in 6 years to see if it's fixed!
>
> Thanks for the report back.
>
> On Mon, 11 Mar 2019 at 06:20, Heystek Grobler <heystekgrob...@gmail.com>
> wrote:
>
>> Hey Adam and Jack
>>
>> I mannaged to solve the problem. The GPIO block for was set for the wrong
>> platform. It was set on ROACH1 and not ROACH2.
>>
>> Thanks for all the help!
>>
>> Heystek
>>
>> On Sat, Mar 9, 2019 at 12:27 AM Jack Hickish <jackhick...@gmail.com>
>> wrote:
>>
>>> Hi Heystek,
>>>
>>> Adam's right. I think this is potentially a bug in the tool flow's
>>> auto-generated ROACH2 UCF file. Which is weird. Either that or your GPIO
>>> block is misconfigured, though I'm not sure off the top of my head what
>>> this would be. Can you send me your model (preferably a GitHub link) and an
>>> mlib_devel git hash for the version of the library you're using?
>>>
>>> Cheers
>>> Jack
>>>
>>> On Fri, 8 Mar 2019 at 01:15, Heystek Grobler <heystekgrob...@gmail.com>
>>> wrote:
>>>
>>>> Hey Franco and Jack
>>>>
>>>> I have cheked that I have done the post install "fixes"
>>>>
>>>> I have traced the error to these:
>>>>
>>>> ERROR:NgdBuild:488 - Attribute value "LVCMOS33" is not an accepted
>>>> value for
>>>>    attribute "IOSTANDARD" on
>>>> "r2wb640mhz_roach_gpio_a_enable_not_ext<0>".
>>>> ERROR:NgdBuild:488 - Attribute value "LVCMOS33" is not an accepted
>>>> value for
>>>>    attribute "IOSTANDARD" on
>>>> "r2wb640mhz_roach_gpio_b_enable_not_ext<0>".
>>>>
>>>> Do you perhaps know how I can fix this?
>>>>
>>>> Heystek
>>>>
>>>>
>>>> On Thu, Mar 7, 2019 at 2:12 AM Jack Hickish <jackhick...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Heystek,
>>>>>
>>>>> In addition to Franco's point about post-installation tweaks, you
>>>>> might find more information if you look up above the "Number of errors: 
>>>>> 2",
>>>>> where [hopefully] there will be more specific error messages.
>>>>>
>>>>> Cheers
>>>>> Jack
>>>>>
>>>>> On Wed, 6 Mar 2019 at 09:47, Franco <francocuro...@gmail.com> wrote:
>>>>>
>>>>>> I'm not sure but did you make the modifications required
>>>>>> post-installation:
>>>>>> https://github.com/casper-astro/tutorials_devel/wiki#modifications-to-be-run-after-installs
>>>>>> ?
>>>>>>
>>>>>> I remember having a similar error for not having the make -> gmake
>>>>>> link.
>>>>>>
>>>>>> Franco
>>>>>>
>>>>>> On Tue, Mar 5, 2019 at 10:24 AM Heystek Grobler <
>>>>>> heystekgrob...@gmail.com> wrote:
>>>>>>
>>>>>>> Good day CASPERites
>>>>>>>
>>>>>>> I am trying to compile a deign for a ROACH2 but I get the
>>>>>>> following error:
>>>>>>>
>>>>>>> NGDBUILD Design Results Summary:
>>>>>>>   Number of errors:     2
>>>>>>>   Number of warnings: 10272
>>>>>>>
>>>>>>> Total REAL time to NGDBUILD completion: 2 min  48 sec
>>>>>>> Total CPU time to NGDBUILD completion:  2 min  41 sec
>>>>>>>
>>>>>>> One or more errors were found during NGDBUILD.  No NGD file will be
>>>>>>> written.
>>>>>>>
>>>>>>> Writing NGDBUILD log file "system.bld"...
>>>>>>> ERROR:Xflow - Program ngdbuild returned error code 2. Aborting flow
>>>>>>> execution...
>>>>>>> gmake: *** [__xps/system_routed] Error 1
>>>>>>> ERROR:EDK -
>>>>>>>    Error while running "gmake -f system.make bits".
>>>>>>> Error using gen_xps_files (line 688)
>>>>>>> XPS failed.
>>>>>>>
>>>>>>> Does anyone perhaps know how to fix it?
>>>>>>>
>>>>>>> Thanks for the help
>>>>>>>
>>>>>>> Heystek
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "casper@lists.berkeley.edu" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to casper+unsubscr...@lists.berkeley.edu.
>>>>>>> To post to this group, send email to casper@lists.berkeley.edu.
>>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "casper@lists.berkeley.edu" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to casper+unsubscr...@lists.berkeley.edu.
>>>>>> To post to this group, send email to casper@lists.berkeley.edu.
>>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "casper@lists.berkeley.edu" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to casper+unsubscr...@lists.berkeley.edu.
>>>>> To post to this group, send email to casper@lists.berkeley.edu.
>>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "casper@lists.berkeley.edu" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to casper+unsubscr...@lists.berkeley.edu.
>>>> To post to this group, send email to casper@lists.berkeley.edu.
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "casper@lists.berkeley.edu" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to casper+unsubscr...@lists.berkeley.edu.
>>> To post to this group, send email to casper@lists.berkeley.edu.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To post to this group, send email to casper@lists.berkeley.edu.
>>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To post to this group, send email to casper@lists.berkeley.edu.
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To post to this group, send email to casper@lists.berkeley.edu.

Reply via email to