Hi Marc, Thanks for the rapid response. Here's the log-lvl info.
Trying 192.168.4.20... Connected to 192.168.4.20. Escape character is '^]'. #version memcpy-88-g38ad77a-dirty #build-state 2013-04-11T11:50:43 ?log-level debug !log-level ok debug #log info 1133318717282 raw new\_client\_connection\_192.168.4.1:38120 #client-connected 192.168.4.1:38120 #log info 1133318717284 raw received\_end\_of\_file\_from\_192.168.4.1:38120 #client-disconnected 192.168.4.1:38120 #log info 1133318717286 raw new\_client\_connection\_192.168.4.1:38128 #client-connected 192.168.4.1:38128 #log debug 1133318717287 raw client\_message\_<?watchdog> #log debug 1133318717289 raw client\_message\_<?read\_sys_board_id\_0\_4> #log error 1133318717289 raw fpga\_not\_programmed #log debug 1133318717291 raw client\_message\_<?read\_sys_board_id\_0\_4> #log error 1133318717291 raw fpga\_not\_programmed #log debug 1133318718295 raw client\_message\_<?progremote\_2477> #log info 1133318718356 raw received\_end\_of\_file\_from\_192.168.4.1:38128 #client-disconnected 192.168.4.1:38128 Austin ________________________________ From: [email protected] <[email protected]> on behalf of Marc <[email protected]> Sent: Friday, March 31, 2023 2:25 PM To: [email protected] <[email protected]> Subject: Re: [casper] Roach2 progremote error & CASPER slack account On Fri, Mar 31, 2023 at 6:38 PM Austin Dymont <[email protected]<mailto:[email protected]>> wrote: Hello, Hi 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://urldefense.com/v3/__https://casper-toolflow.readthedocs.io/projects/tutorials/en/latest/tutorials/roach/tut_intro.html__;!!BpyFHLRN4TMTrA!8OYiZDPnURC6x21rOpZx_aDihMamA4soZmByl42UEXnkDB_XfGaMSBHzm-LdlGx7fRtZ8miLhlOICYWTGg$>. 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',)) If you telnet (or nc) to the roach on port 7147 while you do this, there might be some messages telling us a bit more. And if you type ?log-level debug on that connection, you might get more detailed feedback. Let us know what you see and hopefully we can point you in the right direction. On that connection you could also try to program fpg files by hand, though that will involve a second netcat - it works in a similar way to ftp. Regarding the uboot prompt: There are standalone tftp servers as well as one part of dnsmasq, and if you do a printenv at the uboot prompt you can see what those run macros expand to, so you could run the tftp get by hand too... I'd put off reflashing uboot until later, if that goes wrong then it becomes quite a bit more tricky to recover regards marc Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website. -- 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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGrhWaQwk7K13uhoT%3DTbnuc26%3DjWMZU6Ybe-wcO3zhzhjQ5oyw%40mail.gmail.com<https://urldefense.com/v3/__https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGrhWaQwk7K13uhoT*3DTbnuc26*3DjWMZU6Ybe-wcO3zhzhjQ5oyw*40mail.gmail.com?utm_medium=email&utm_source=footer__;JSUl!!BpyFHLRN4TMTrA!8OYiZDPnURC6x21rOpZx_aDihMamA4soZmByl42UEXnkDB_XfGaMSBHzm-LdlGx7fRtZ8miLhlPQaHR0fw$>. -- 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/IA1PR11MB649223A91ACB0955D1A018ABD98C9%40IA1PR11MB6492.namprd11.prod.outlook.com.
