Hi Sebastian, I actually dusted off our old ROACH2 test machine yesterday and did exactly this. To be honest the easiest will be to set up a "roach2 test machine" as per attached instructions and then you just use the menu option to load uboot. This will load the uboot via xmodem over the ftdi USB link and you should be good to go. After that you should update the uboot to the latest 2015 version.
Have a look through the document and then we can have a quick zoom session to iron out any issues? Here is the doc: https://drive.google.com/file/d/0BzImdYPNWrAkMjJhaXlsazhYMUE/view?usp=sharing Regards Alec On Sat, Sep 12, 2020 at 11:08 PM Sebastian Antonio Jorquera Tapia <[email protected]> wrote: > > > Hi Casperiters, > When I was playing trying to make a netbooting with the ROACH2 and I issue > the command: "run tftpuboot" and making the story short I ended up with no > uboot :( > > Luckily I have access to one xilinx jtag so I was thinking in connecting via > xmd to the ppc and send the uboot with the command dow. > The jtag found 10 devices where one is the Virtex, other one is the > Coolrunner and 8 unknown devices. I think the ppc Is none of those unknown > devices, because the IR length is zero. > So now I have some doubts to how to proceed: > > 1) Looking at the roach2 diagram, the coolrunner is connected in certain > fashion with the ppc. Could I load the uboot using as target the coolrunner? > > 2) Reading the roach1 bringup memo in the old wiki, it says that one way to > upload the uboot is to use a Macraigor usbWiggler to set the ppc program > counter in a specific location in order to open a xmodem. The roach2 works in > the same way? Also, do I need that specific jtag or the Xilinx one could do > the job? > https://casper.ssl.berkeley.edu/wiki/ROACH_Bringup#PowerPC_U-Boot_Configuration > > Here are the possible targets that jtag found: > > JTAG chain configuration > -------------------------------------------------- > Device ID Code IR Length Part Name > 1 0440f1e1 0 unknown > 2 84288093 10 XC6VSX475T > 3 16d4a093 8 XC2C256 > 4 1a464069 0 unknown > 5 1a464069 0 unknown > 6 1a464069 0 unknown > 7 1a464069 0 unknown > 8 000003d3 0 unknown > 9 000003d3 0 unknown > 10 18006197 0 unknown > 11 18006197 0 unknown > > > > > > > -- > 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/134f9f9b-7141-44a6-9316-49e83dd8050fn%40lists.berkeley.edu. -- 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/CAAkZC3gwTW-3W31PGiEVzUMuQgbwkWTuKEOU_Ehizeysin86fA%40mail.gmail.com.
