OK, that's progress. The next thing I'd check is that you are *not*
using the JTAG configuration mode, as this disables the ICAP. You can
also try turning on the DEBUG flags in the driver itself. During open()
the driver attempts to read the IDCODE from the hwicap to get it back to
an initial state.
Steve
-----Original Message-----
From: <redacted>
[mailto:linuxppc-embedded-
bounces+stephen=3Dneuendorffer.name@ozlabs.org] On Behalf Of Will
Kritikos
Sent: Wednesday, May 14, 2008 12:20 PM
To: Stephen Neuendorffer
Cc: <redacted>
Subject: Re: xilinx_hwicap driver problems
=20
Steve,
Yes, this fixed that problem. the following is now printed when
booting the kernel.
=20
[ 5.866230] icap icap.0: Xilinx icap port driver
[ 5.866401] icap icap.0: ioremap 40200000 to c5000000 with size
10000
=20
The icap is at address 0x40200000 on my system, so that seems correct.
=20
However, when I copy partial bitstreams to the device, I get strange
results. Here is what I am seeing.
=20
# mknod /dev/icap c 259 0
# cp opb_prr_0_lin_partial.bit /dev/icap
cp: write error: Bad address
# cp opb_prr_0_lin_partial.bit /dev/icap
[ 66.566107] icap icap.0: Failed to open file#
# cp opb_prr_0_lin_partial.bit /dev/icap
#
=20
I know that this file exists in the current directory, and is a
working partial bitstream.
=20
Thanks for the help.
Will
=20
=20
On Wed, May 14, 2008 at 2:37 PM, Stephen Neuendorffer
[off-list ref] wrote:
quoted
I bet you're using ARCH ppc...
It looks like in arch/ppc/syslib/virtex_devices.c:
#define XPAR_HWICAP(num) { \
.name =3D "xilinx_icap", \
Should probably be:
#define XPAR_HWICAP(num) { \
.name =3D "icap", \
now.
Can you make this change locally and verify that it solves the
problem?
quoted
Steve
quoted
-----Original Message-----
From:
linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@ozlabs.org
quoted
[mailto:linuxppc-embedded-
quoted
bounces+stephen=3Dneuendorffer.name@ozlabs.org] On Behalf Of Will
Kritikos
quoted
Sent: Wednesday, May 14, 2008 9:03 AM
To: <redacted>
Subject: xilinx_hwicap driver problems
I am having some trouble using the xilinx_hwicap driver in Linux.
I am using version 2.6.24-rc8-xlnx of the Linux kernel from the
Xilinx
quoted
quoted
GIT repository.
The xilinx_hwicap driver is statically compiled in - not a loadable
module.
quoted
I am using the opb_hwicap device on a V4FX60 FPGA, Linux running on
the PPC405.
quoted
The driver successfully is initialized on boot - I added a printk
to
quoted
quoted
the init function to verify this. However, as far as I can tell,
the
quoted
quoted
probe function is never called. There is nothing in dmesg from the
icap driver.
After boot, the following files exist in /sys
/sys/bus/platform/xilinx_icap.0
/sys/bus/platform/drivers/icap/bind
/sys/bus/platform/drivers/icap/uevent
/sys/bus/platform/drivers/icap/unbind
/sys/devices/platform/xilinx_icap.0
I can make a device node /dev/icap, major number 259 minor number
0,
quoted
quoted
and copy partial bitstreams to it, but again nothing happens, and
no
quoted
quoted
output in dmesg.
Any help is appreciated. I am probably overlooking something
simple.
quoted
quoted
Thanks,
Will Kritikos
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
This email and any attachments are intended for the sole use of the
named recipient(s) and
contain(s) confidential information that may be proprietary,
privileged or copyrighted under
applicable law. If you are not the intended recipient, do not read,
copy, or forward this email
message or any attachments. Delete this email message and any
attachments immediately.
quoted
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
This email and any attachments are intended for the sole use of the named=
recipient(s) and contain(s) confidential information that may be=
proprietary, privileged or copyrighted under applicable law. If you are=
not the intended recipient, do not read, copy, or forward this email=
message or any attachments. Delete this email message and any attachments=
immediately.