Hello,

My name is Austin Dymont, a new graduate student at the University of Chicago. 
I'm in need some help regarding the setup of a ROACH2. I'm running into an 
issue with programming the roach with a new .fpg file. I followed through with 
some of the intro tutorial from the 
toolflow<https://casper-toolflow.readthedocs.io/projects/tutorials/en/latest/tutorials/roach/tut_intro.html>.
 The tutorial was able to connect to the ROACH2 and begin talking to it, 
checked by pinging and the is_connected() returned true. It errored when it 
tried to run progremote.

INFO:192.168.X.XX:192.168.X.XX: uploading 
tutorial/roach2/tut_intro/roach2_tut_intro.fpg, programming when done
<class 'RuntimeError'>
('progremote request(Request to client 192.168.X.XX failed.) on host 
192.168.X.XX failed',))

I've found some discussion in the 
wiki<https://casper.astro.berkeley.edu/wiki/Getting_Started_with_ROACH2>, setup 
guide, and on the mail archive about this issue being related to needing to 
update the ROACH2's romf/kernel/boot.
Given this is the solution, which one do I need to update? Is the run tftproot 
or run tftpkernel command still the correct way to update those two, unlike the 
uboot which seems to need some modification?

I'm uncertain how to go about this fix from the steps given between the wiki 
pages. I was unable to set up a DHCP (and so the built-in TFTP) server but have 
set up a direct IP connection. Is there a simple way to setup the TFTP server 
to transfer the romf/kernel file?

If it would help, would it be possible to get a CASPER account to join the 
slack, as I have some more smaller questions about hardware restrictions?

Any help is appreciated,
Austin Dymont

-- 
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 view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/IA1PR11MB649230598F1228BFFD9E4378D98F9%40IA1PR11MB6492.namprd11.prod.outlook.com.

Reply via email to