MediaCore’s modular and scalable design enables Tier-1 infotainment manufacturers to leverage their investments over multiple OEM projects, on low/mid/high end IVI systems, with different operating systems and CPUs.
The WinDriver™ device driver development tool supports any device, regardless of its silicon vendor, and enables you to focus on your driver’s added-value functionality, instead of on the operating system internals.
DriverCore, Jungo’s assorted collection of USB PC connectivity drivers, is built on Jungo’s extensive experience and technology leadership in the embedded connectivity arena, and has been chosen by the world’s top chipset vendors and consumer electronics device makers.
I highly recommend the WinDriver USB/PCI Driver Development Toolkit. Instead of driver development time taking months, the toolkit allowed us to complete our USB driver in weeks. Another plus was WinDriver doing all the “under the hood” Kernel Mode driver implementation and us implementing a User Mode interface to WinDriver.
When I found the Jungo Tools I initially looked at the online video showing how to drive the kit. When I tried out the real software I was amazed that within ten minutes I had my first driver working and could interact with my custom FPGA-based board.
Usually, if a problem occurs during the development process, you don’t know whether it’s in the firmware – or even in the hardware – or in the software on the PC, WinDriver helped enormously to avoid such problems.
Our alternative to using WinDriver was to build a traditional OS specific driver for each storage interface HBA we wanted to support. This created a “m x n” problem of the number of unique drivers we would have to create and support. As a cost savings move, BSI used WinDriver to reduce the “m x n” to “n”.
When we tried Jungo’s WinDriver, we were immediately pleased with what they had to offer. Using only the evaluation version, we found that none of the limitations of the competing tool that we were faced with, applied to Jungo’s WinDriver. After only three days of development, we had a working driver and a kernel plug in for interrupts.
This is not the first time we are using Jungo’s tools to develop drivers for our innovative products. We already had excellent experiences with WinDriver for other Operating Systems before using WinDriver for Windows CE. We did try developing a driver ourselves but after finding Jungo’s solution on the web, it was only natural for us to choose this easy-to-use toolkit.
I have been impressed with the relative ease with which one can develop a high performance driver for a PCI card without much detailed knowledge of the computer’s hardware or even the system software. We used the wizard to create the driver. Although we generally try to avoid licensed software, the licensing is not too onerous, and we can distribute the resulting code to all our machines.
We selected WinDriver after testing it and finding that it worked well for many of our needs. The WinDriver’s ease of implementation and generic capabilities allowed us to quickly gain access to our USB devices and insure that we will be able to add additional testing logic as requirements evolve in the future
We chose to develop with WinDriver because of its extensive functionality, broad operating system support, and customer support. We were able to communicate with the device within a few days. The ready-made samples and the extensive technical documentation that came with WinDriver proved to be very helpful.
I was already using Jungo’s WinDriver USB for XP/Vista 32/64 bit support so it was natural to try the Windows CE support, also. This saved us enormous effort as we didn’t have to do very much development to get the low-level functionality of our application working. Furthermore, the Jungo support team provided excellent support. Having converted to the Jungo driver, I can support 32/64 bit Vista as well as Windows CE devices with a single codebase.
