is the Roach2 test machine bring up manual of any help?
https://docs.google.com/document/d/1tqw4C6uZ6EULl1OykTFL_vQTnK52UBr0aYqTg44E5wg/edit
this link is found at
https://casper.ssl.berkeley.edu/wiki/ROACH-2_Revision_2

On Sat, 12 Sep 2020, Matt Dexter wrote:

Date: Sat, 12 Sep 2020 15:26:16 -0700 (Pacific Daylight Time (Mexico))
From: Matt Dexter <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [casper] ROACH2 jtag booting

I don't know enough to help with loading uboot.  Perhaps the
following bits of low level information on the Roach2 Rev2
might be of use.

In the Roach2 rev2 schematics U77 (page 26 of 27) drives the JTAG TCK
signals.  There are 11 loads:
V6, CPLD, PPC, PPCNET, V6NET, QDR0, QDR1, QDR2, QDR3, VMON, CMON

The 4 QDR are the same devices so the JTAG IDCODE is probably the same.
The voltage and current monitor ICs are both MAX16071 and will have
matching IDCODEs.
The 2 network devices are both Marvel 88E1111 GbE transceivers
so will have matching IDCODES.

The series resistors to the right of U77 and U79 show the sequence
of the JTAG input/output bits.
PPC, V6, CPLD, QDR0, QDR1, QDR2, QDR3, PPCNET, V6NET, CMON, VMON
So my guess is

Device   ID Code    IR Length  Part Name         Guess from TDI/O
 1       0440f1e1       0      PPC440EPX-NUA667T    PPC
 2       84288093      10      XC6VSX475T            V6
 3       16d4a093       8      XC2C256             CPLD
 4       1a464069       0      CY7C2565KV18        QDR0
 5       1a464069       0      CY7C2565KV18        QDR1
 6       1a464069       0      CY7C2565KV18        QDR2
 7       1a464069       0      CY7C2565KV18        QDR3
 8       000003d3       0      88E1111           PPCNET
 9       000003d3       0      88E1111            V6NET
10       18006197       0      MAX16071            CMON
11       18006197       0      MAX16071            VMON

I've only heard of the usbWiggler being used with the Roach1.

Matt

On Sat, 12 Sep 2020, Sebastian Antonio Jorquera Tapia wrote:

Date: Sat, 12 Sep 2020 14:08:54 -0700 (PDT)
From: Sebastian Antonio Jorquera Tapia <[email protected]>
Reply-To: [email protected]
To: "[email protected]" <[email protected]>
Subject: [casper] ROACH2 jtag booting


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 visithttps://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/134f9f9b-7141-44a6-9316-49e83dd8050fn%40
lists.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/alpine.WNT.2.20.2009121526570.9336%40DESKTOP-LM78PCL.

Reply via email to