Thanks Alec, That worked! I'm used to always having a minicom terminal up at start. When I didn't, it successfully reloaded u-boot. We're up and running now.
Really appreciate the help! --Tony Goodson R On Tue, Jun 13, 2017 at 12:47 AM, Alec Rust <a...@ska.ac.za> wrote: > Hi Tony, the initial u-boot is transferred using x-modem. This is done via > serial link. If you have a minicom session open there will be a com port > clash. Try again with minicom closed. > > Regards > Alec > > PS. I'll go take a look at the code and see what else could be wrong but I > think it's just a com port clash. > > On Mon, Jun 12, 2017 at 6:09 AM, Tony Goodson <aggoods...@gmail.com> > wrote: > >> Hello, >> >> New member here. >> >> At the University of Washington, we've been running a pair of ROACH2's >> successfully for several years. >> >> However, today I was restarting one of them through the roach2_ats.py >> utility, and u-boot appears to be failing. I inadvertently unloaded U-boot >> (option m), and subsequently tried to load u-boot. (option 0). >> >> The symptoms/behavior: >> I can turn the board on and off via roach2_ats.py, but uboot doesn't >> start - I see no traffic across my minicom terminal associated with the >> u-boot. >> >> I can succesfully run an unload U-boot (or at least no errors are >> reported back from roach2_ats.py). When I try to run a "load U-boot, >> kernel, and filesystem", I get an error that says "device reports readiness >> to read but returned no data (device disconnected or multiple access on >> port?)". While doing this, I get some odd symbols on the minicom >> terminal. Also, if I run option 9 ("Test FLASH and PPC DDR2 memory"), I >> see the following on the minicom terminal: >> >> "start >> eeeeeeeeee >> wwwwwwwwww >> rrrrrrrrrr >> pass" >> >> Any help would be greatly appreciated. >> >> Also, if you could please add me to the list server - when I try to join >> via the link at the casper site, I get to a Berkeley Calnet login. >> >> Thanks in advance, >> >> --Tony Goodson >> >> -- >> 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.