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

Sponsor

Industry's highest performing at the lowest power DSPs now as low as $5.00*
Start development today!
*volume pricing for 10ku

Discussion Groups

See Also

Embedded SystemsFPGAElectronics

Discussion Groups | TMS320C6x | Re:[2] Looking for TMS320C6x EVM PCI Borad's driver for Windows XP

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

  

Post a new Thread

Re:[2] Looking for TMS320C6x EVM PCI Borad's driver for Windows XP - Craig Peacock - Apr 23 10:06:00 2002


Par,

>I have run CCS2.0 with a EVM6201 PCI board under XP. I used the same
>driver as for NT4.0/Win2K.
>
>I originally had it working under NT4.0 and installed Win2k instead.
>It did not work, tried all sorts of things and a new driver was one
>thing I thought of. However there only seems to exist a single really
>old driver for the EVM board.
>
>As a desperate measure I installed XP instead of win2k and it worked
>just like that. For other reasons I decided to throw out XP and I
>finally got it working under Win2K. The trick was to set the BIOS to
>"non plug and play OS". This is against TIs instructions and does not
>make sense but it worked.

Yes, Ti actually mention this under bug# SDSsq19226 6201/6701 EVMs via
PCI will not work on some PCs running windows 2000 (v2.00)
http://www.ti.com/sc/docs/dsps/hotline/techbits/c6bug.htm#SDSsq19226

But I think it also has a lot to do with your hardware as I have tried
endlessly to get it working on a machine at work. We have turned
plug'n'play off, and reinstalled the drivers with no luck.

>My theory is that the driver or the PCI bridge chip is sensitive about
>how it is configured. Simply, this BIOS and Win2K does the PCI
>configuration process differently. The driver was probably developed
>when configuration was done by BIOS and depends on some quirk.

Regards,

Craig Peacock


______________________________
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 )