Sign in

username:

password:



Not a member?

Search c6x



Search tips

Subscribe to c6x



c6x by Keywords

AD535 | BIOS | Booting | Bootloader | C621 | C6211 | C6415 | C671 | C6711 | C6711DSK | C6713 | CCS | Chassaing | COFF | DAT | DM64 | DM642 | DMA | DSK671 | DSK6711 | EDM | EDMA | EMIF | Emulator | EVM | EVM620 | FFT | FIR | GPIO | Halting | HPI | HWI | IDK | JTAG | LDB | LDH | LDW | Linker | LMS | LOG_printf | Matlab | McBSP | MEM_alloc | MIPS | PCI | PCM3003 | Pipeline | Profiling | QDM | Reset | ROM | RTDX | Sampling | SDRAM | Stack | TEB | THS1206 | TMS320C621 | TMS320C6416 | TMS320C6711 | TMS320C6713 | UART | Vector Table | XBUS | XDS560


Discussion Groups

See Also

Embedded SystemsFPGAElectronics

Discussion Groups | TMS320C6x | I/O conflict between EVM6201 and Framegraber

Technical discussions about the TI C6000 DSPs (including the c62x, c64x and c67x DSPs).

  

Post a new Thread

I/O conflict between EVM6201 and Framegraber - Author Unknown - Nov 7 17:55:00 2000

Hi friends,
I am working on a MS project which requires image processing
at EVM6201. I am getting the images with a Tekram framegraber
board and camera. Both EVM6201 and framegraber are on PCI bu of my
host PC. The CCS accesses to EVM6201 with no problem
when the framegraber is not installed. But when both of them are
installed, CCS cannot access to EVM6201. I think there may be an I/O
conflict. But I have no idea about the solution. As I know, the
manuals of neither EVM nor framegraber includes information about
setting another I/O address.
I will be waiting for your experiences and solution suggestios....

Best Regards....
Ozgur




______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

Re: I/O conflict between EVM6201 and Framegraber - Brian Carlson - Nov 9 3:29:00 2000

Ozgur,

There wouldn't be an I/O address conflict, as the EVM does not use
I/O ports. The problem is that there must be IRQ (interrupt) sharing), where
your PC BIOS or Windows is assigning both boards to the same interrupt.
This is not a problem in most cases since that is the way PCI is designed
to work with level-sensitive, shareable interrupts.

However, there is a software issue involved where the drivers of devices
on the same IRQ must support sharing. If the condition that causes an interrupt

is not on its board, the driver should indicate so to the OS so the next device
driver
on the IRQ can look at its interrupt status register and act appropriately.

I am aware of several NIC and video cards that have a problem with IRQ sharing.
My recommendation is to try moving the boards to different slots to see if the
IRQs get assigned differently. You can also play games sometimes with your
BIOS settings for IRQs, as well as using the Device Manager to reserve the IRQ
and let it assign it to another one. There really isn't one answer for
everyone.

PCI is intended to make things easier, but many times it becomes "plug and
pray".

Good luck,
Brian

wrote:

> Hi friends,
> I am working on a MS project which requires image processing
> at EVM6201. I am getting the images with a Tekram framegraber
> board and camera. Both EVM6201 and framegraber are on PCI bu of my
> host PC. The CCS accesses to EVM6201 with no problem
> when the framegraber is not installed. But when both of them are
> installed, CCS cannot access to EVM6201. I think there may be an I/O
> conflict. But I have no idea about the solution. As I know, the
> manuals of neither EVM nor framegraber includes information about
> setting another I/O address.
> I will be waiting for your experiences and solution suggestios....
>
> Best Regards....
> Ozgur
>
> To Join: Send an email to
>
> To Post: Send an email to
>
> To Leave: Send an email to
>
> Archives: http://www.egroups.com/group/c6x
>
> Other Groups: http://www.dsprelated.com



______________________________
Start your Android Ice Cream Sandwich development on TI's AM35x Sitara ARM Cortex-A8 processor today.



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

RE: I/O conflict between EVM6201 and Framegraber - Jeff Bateman - Nov 9 16:16:00 2000

Brian,

I'm sure many of us have experienced all sorts of issues with drivers that
don't share interrupts properly. You mentioned that you are aware of several
NIC and video card drivers that mis-behave; would you happen to know of any
public resources where such offenders are listed? I'm not sure that such a
'Hall of Shame' could exist without attracting lawyers, but it would most
certainly be useful, would it not?

Jeff

Jeff Bateman, Senior Systems Engineer
Transtech DSP Corp.
20 Thornwood Drive, Ithaca, NY 14850-1263, USA
Voice (607)257-8678 ext. 22 Fax (607)257-8679
http://www.transtech-dsp.com

> -----Original Message-----
> From: Brian Carlson [mailto:]
> Sent: Wednesday, 08 November, 2000 22:29
> To:
> Subject: Re: [c6x] I/O conflict between EVM6201 and Framegraber > Ozgur,
>
> There wouldn't be an I/O address conflict, as the EVM does not use
> I/O ports. The problem is that there must be IRQ (interrupt)
> sharing), where
> your PC BIOS or Windows is assigning both boards to the same interrupt.
> This is not a problem in most cases since that is the way PCI is designed
> to work with level-sensitive, shareable interrupts.
>
> However, there is a software issue involved where the drivers of devices
> on the same IRQ must support sharing. If the condition that
> causes an interrupt
>
> is not on its board, the driver should indicate so to the OS so
> the next device
> driver
> on the IRQ can look at its interrupt status register and act
> appropriately.
>
> I am aware of several NIC and video cards that have a problem
> with IRQ sharing.
> My recommendation is to try moving the boards to different slots
> to see if the
> IRQs get assigned differently. You can also play games sometimes
> with your
> BIOS settings for IRQs, as well as using the Device Manager to
> reserve the IRQ
> and let it assign it to another one. There really isn't one answer for
> everyone.
>
> PCI is intended to make things easier, but many times it becomes "plug and
> pray".
>
> Good luck,
> Brian
>
> wrote:
>
> > Hi friends,
> > I am working on a MS project which requires image processing
> > at EVM6201. I am getting the images with a Tekram framegraber
> > board and camera. Both EVM6201 and framegraber are on PCI bu of my
> > host PC. The CCS accesses to EVM6201 with no problem
> > when the framegraber is not installed. But when both of them are
> > installed, CCS cannot access to EVM6201. I think there may be an I/O
> > conflict. But I have no idea about the solution. As I know, the
> > manuals of neither EVM nor framegraber includes information about
> > setting another I/O address.
> > I will be waiting for your experiences and solution suggestios....
> >
> > Best Regards....
> > Ozgur
> >
> > To Join: Send an email to
> >
> > To Post: Send an email to
> >
> > To Leave: Send an email to
> >
> > Archives: http://www.egroups.com/group/c6x
> >
> > Other Groups: http://www.dsprelated.com >
> To Join: Send an email to
>
> To Post: Send an email to
>
> To Leave: Send an email to
>
> Archives: http://www.egroups.com/group/c6x
>
> Other Groups: http://www.dsprelated.com


______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )