Hi Indrajit,

I know this thread is now old, but FYI, I updated that repository with
the UC Berkeley ROACH1 and ROACH2 configurations. Apologies for being
so very very slow about it.

Cheers
Jack

On Wed, 20 Feb 2019 at 06:26, Jack Hickish <[email protected]> wrote:
>
> Oh, sorry, I completely misread your email.
>
> I don't think that link will work. I think we have a working netboot setup in 
> Berkeley. I can make sure it works and then post it to github. That'll have 
> to be next week though, currently I'm hiding in an observatory.
>
> Cheers
> Jack
>
> On Wed, 20 Feb 2019 at 16:00, indrajit <[email protected]> wrote:
>>
>> Hi Jack,
>>
>> I am looking for ROACH1 . I went through this link I thought Its for ROACH2.
>>
>> I will give a try.
>>
>> Thanks and regards
>>
>> indrajit
>>
>>
>> On Wednesday 20 February 2019 07:26 PM, Jack Hickish wrote:
>>
>> Hi Indrajit,
>>
>> Does the filesystem at https://github.com/casper-astro/roach2_nfs_uboot work 
>> for you?
>>
>> If not, let me know.
>>
>> Cheers
>> Jack
>>
>> On Wed, 20 Feb 2019 at 15:42, indrajit <[email protected]> wrote:
>>>
>>> Hello All,
>>>
>>> I am trying to make a Netboot system. I went through the "ROACH NFS guide - 
>>> Casper"
>>>
>>> Downloading the kernel and file system from the bellow link is broken(not 
>>> available ).
>>>
>>> http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/linux/
>>>
>>> http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/filesystem/
>>>
>>> anyone kindly give me a link from where I can download the same.
>>>
>>> Thanks
>>>
>>> Indrajit
>>>
>>>
>>>
>>> On Wednesday 13 February 2019 07:43 PM, indrajit wrote:
>>>
>>> Hello James,
>>>
>>> Same cable , same ROACH board with same SD card but I changed the 
>>> machine(Ubuntu 14.04) in which I initially set the boot sequences. I could 
>>> able to interrupt and select the boot order (mmcboot).
>>>
>>> The data acquisition machine is Ubuntu 18.04 which has advanced version of 
>>> gtkterm and extra baud-rates functionality  and etc... Might be some bug in 
>>> that..
>>>
>>> thanks and regards
>>>
>>> Indrajit
>>>
>>>
>>>
>>>
>>>
>>> On Wednesday 13 February 2019 05:18 PM, James Smith wrote:
>>>
>>> Hello Indrajit,
>>>
>>> Check the settings on your serial connection - did you turn off Flow 
>>> Control?
>>>
>>> Regards,
>>> James
>>>
>>>
>>> On Wed, Feb 13, 2019 at 1:47 PM indrajit <[email protected]> wrote:
>>>>
>>>> Hello James,
>>>>
>>>> I am also doing the same. I am able to see the booting sequences via the 
>>>> serial terminal counting down from 10 and I am trying to interrupt but the 
>>>> keystrokes are not interrupting the boot menu.
>>>>
>>>> Even I changed the SD card which is logically nothing to do with the 
>>>> booting sequence.
>>>>
>>>> Thanks and regards
>>>>
>>>> Indrajit
>>>>
>>>>
>>>>
>>>> On Wednesday 13 February 2019 05:07 PM, James Smith wrote:
>>>>
>>>> Hello Indrajit,
>>>>
>>>> Why were you not able to interrupt the process? Connect to the ROACH via 
>>>> the serial port then reset it - you should be able then to see the place 
>>>> to interrupt and set netboot (or whatever else you need) quite easily.
>>>>
>>>> Regards,
>>>> James
>>>>
>>>>
>>>> On Wed, Feb 13, 2019 at 1:31 PM indrajit <[email protected]> wrote:
>>>>>
>>>>> Hello all,
>>>>>
>>>>> A new ROACH1 while taking measurements stopped responding. Then via
>>>>> serial communication, found that it got booted using the flash.
>>>>> Restarted and trying to interrupt using the serial terminal and boot via
>>>>> MMC-BOOT.  I couldn't interrupt using the keyboard. I inserted another
>>>>> working SD card and tried the same. Failed to boot via the memory card.
>>>>>
>>>>> Thanks and regards
>>>>>
>>>>> indrajit
>>>>>
>>>>> --
>>>>> 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].
>>>>
>>>>
>>>> --
>>>> 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].
>>>
>>>
>>>
>>> --
>>> 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].
>>
>>
>> --
>> 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].

Reply via email to