Hi All,
I believe I have a version of the QDR block / software that works at
every conceivable clock frequency anyone could want. Tomorrow
(Berkeley time), I'm going to merge this into the main casper-astro
github repository. This seems like as good a time as any to ask: does
anyone have any bugfi
Dear All:
Recently i found out the locations I/O pins for qdr2/ROACH2 are not in the
same FPGA area.(from the Planahead/device map). Some of them are in the
left edge of the device, and some of them are in the middle of the device.
Is there someone experienced this problem and have constraints in
Hi, Brad,
On May 27, 2015, at 1:15 PM, Brad Dober wrote:
> Kernel command line: console=ttyS0,115200
> mtdparts=physmap-flash.0:1792k(linux),256k@0x1c(fdt),8192k@0x20(root),54656k@0xa0(usr),256k@0x3f6(env),384k@0x3fa(uboot)fdt_addr=0xfc1c
> root=192.168.40.1:/srv/roach_b
There was a very long thread about this new problem a few weeks ago.
Bottom line is that it's likely that your host isn't exporting the
filesystem correctly, there's a typo in the DHCP offer, or some other such
host problem. Look in the mail archives...
John
> So I plugged my other Roach1 that
So I plugged my other Roach1 that's in the lab into where the troubled
Roach1 was sitting and started up the netboot. The uImage transferred fine
this time, but I got another problem: *VFS: Unable to mount root fs via
NFS, trying floppy.*
*VFS: Cannot open root device "192.168.40.1:/srv/roach_boot/
Hi, Brad,
On May 27, 2015, at 9:37 AM, Brad Dober wrote:
> I have no issues with the Roach2 that is also connected to this host computer.
No issues meaning that you can tftp the uImage file from the server to the
roach2? Does tcpdump/wireshark show any clues vis a vis the ROACH1's attempted
t
I have no issues with the Roach2 that is also connected to this host
computer.
I switched the Roach1's and Roach'2 ethernet cables and still have the same
problem on the Roach1 and Roach2 is still working fine.
Which pins / voltages should I be checking on the power supply?
Brad Dober
Ph.D. Cand
Hi, Brad,
On May 27, 2015, at 8:09 AM, Brad Dober wrote:
> TFTP from server 192.168.40.1; our IP address is 192.168.100.50
> Filename 'uImage'.
> Load address: 0x40
> Loading: *\0x08###T T T #T ##T T T #T ##T T #
The 'T' characters are timeouts waiting for data from the tftp server. The
So this is new. When I rebooted to check the boot process, it took the IP
address immediately, started loading Uboot, but restarted around block 162.
Wireshark shows multiple packets of the same number being send and
acknowledged.
Yes, I'm using dnsmasq.
U-Boot 2008.10-svn3231 (Jul 15 2010 - 14:
9 matches
Mail list logo
