Hi Marc,
/dev/roach/mem exists but I'm not sure what the correct numbers are.
Brad Dober
Ph.D. Candidate
Department of Physics and Astronomy
University of Pennsylvania
Cell: 262-949-4668
On Wed, Mar 18, 2015 at 3:31 AM, Marc Welz m...@ska.ac.za wrote:
On Tue, Mar 17, 2015 at 8:54 PM, Brad
On Wed, Mar 18, 2015 at 1:40 PM, Brad Dober do...@sas.upenn.edu wrote:
Hi Marc,
/dev/roach/mem exists but I'm not sure what the correct numbers are.
So if you go cat /proc/devices there should be an entry for the roach
driver which should tell you the major number, if there isn't such a line
This is what comes up.
Character devices:
1 mem
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
10 misc
13 input
21 sg
89 i2c
90 mtd
108 ppp
128 ptm
136 pts
252 roach2_fpga
253 bsg
254 rtc
Block devices:
1 ramdisk
259 blkext
8 sd
11 sr
31 mtdblock
65 sd
66 sd
67 sd
68 sd
On Wed, Mar 18, 2015 at 2:10 PM, Brad Dober do...@sas.upenn.edu wrote:
This is what comes up.
Character devices:
...
252 roach2_fpga
Ok, so then /dev/roach/config should be c 252 0 and mem c 252 1. When the
programming
fails, does dmesg tell you anything interesting ?
regards
I do that by running tftpkernel at the R2 bootup instead of tftproot,
correct?
Is there any cleanup I need to do after the reset like when updating
tcpborphserver3?
Brad Dober
Ph.D. Candidate
Department of Physics and Astronomy
University of Pennsylvania
Cell: 262-949-4668
On Wed, Mar 18, 2015
I am now running the newest kernel on github.
I tried again with progdev and it failed, but I tried
fpga.upload_to_ram_and_program('qdr_err_check_2015_Mar_16_1247.fpg') and it
succeeded.
Could fpga.upload_to_flash('qdr_err_check_2015_Mar_16_1247.fpg') be
exhibiting errors?
I'm using
On Wed, Mar 18, 2015 at 2:29 PM, Brad Dober do...@sas.upenn.edu wrote:
Hi Marc. Thanks for the help.
I'm not exactly sure what I'm supposed to be looking for, but here's the
dmesg dump:
roach2: claiming matching platform
Using PowerPC 44x Platform machine description
Linux version
On Wed, Mar 18, 2015 at 2:53 PM, Brad Dober do...@sas.upenn.edu wrote:
I do that by running tftpkernel at the R2 bootup instead of tftproot,
correct?
yep - printenv will show you what these macros do in case you want to know
more
Is there any cleanup I need to do after the reset like when
On Wed, Mar 18, 2015 at 3:11 PM, Brad Dober do...@sas.upenn.edu wrote:
I tried again with progdev and it failed, but I tried
fpga.upload_to_ram_and_program('qdr_err_check_2015_Mar_16_1247.fpg') and it
succeeded.
Could fpga.upload_to_flash('qdr_err_check_2015_Mar_16_1247.fpg') be
exhibiting
Hi Marc. Thanks for the help.
I'm not exactly sure what I'm supposed to be looking for, but here's the
dmesg dump:
roach2: claiming matching platform
Using PowerPC 44x Platform machine description
Linux version 3.9.0-rc1+ (shanly@shanly-HP8710w) (gcc version 4.6.1
20110627 (prerelease) (GCC) )
On Tue, Mar 17, 2015 at 8:54 PM, Brad Dober do...@sas.upenn.edu wrote:
#log error 957577359468 raw
unable\_to\_map\_file\_/dev/roach/mem:\_Invalid\_argument
#log error 957577359471 raw Unable\_to\_map\_/dev/roach/mem
That looks like you have a kernel which doesn't have the roach2 mmap
Hi Casperites,
I'm trying to program an fpg file onto the Roach2, but I can't seem to get
it to program the fpga.
I keep getting this error:
?progdev qdr_err_check_2015_Mar_16_1247.fpg
#log info 957575770765 raw
attempting\_to\_program\_qdr_err_check_2015_Mar_16_1247.fpg
#log error 957575770765
12 matches
Mail list logo