Coder for Life - Project. For the Tivo I was building I had to build a driver for a standard HD4. LCD screen (up to 4x. I started from the excellent work by ch. He was even kind enough to give me the source code for his microchip. Well, I had never really made a circuit before, and I had definitely never programmed a microchip before, so I wanted to have a go at re- doing his work to better suit my needs and wants. So I completely re- designed his circuit and re- coded the entire project. I definitely used his code and circuit as a starting point, but I reworked every part of it to be my own. Additionally I received help from the RPI Electronics Club.
Capabilities. Controls any HD4. KS0. 06. 6U compatible LCD screen with at most 4x. Connects and is powered with USB (+5. V, ~1. 25m. A)Emulates a serial port and can be used with the very powerful LCD Smartie software. Up to 5 digital inputs (e. LEDs and buzzers)Backlight and contrast can be changed in real- time through software. Button presses send upper- case letters and releases send lower- case letters. Reading the current state of the LCD, including: the text on the screen, the custom characters, the state of buttons, etc. Saving default for use during boot- up, including: the text, custom characters, backlight and contrast levels, output states, etc. Has an optional bootloader so firmware can be updated through standard USB (the bootloader requires a PIC programmer though)* May work with KS0. Use the links on this page to download the latest version of Microchip Custom USB Device drivers. All drivers available for download have been scanned by antivirus. Disclaimer: Both samples of the DragonFly Red and DragonFly Black were given to me free of charge for this review by AudioQuest during our meeting at High End in. VCC GND (top to bottom, these provide lower currents) The difference between the two types of OUT are that 1-3 draw current directly from the USB port (suitable for. The Bluetooth enabled. Will not work with T6. C or KS0. 06. 6FF0. Change Log. Version 1. Minor update to software only, no changes to firmware. BUG: LCD- Setter and LCD Smartie driver registry code needed some more fixing. Version 1. 2. 2: Minor update to software only, no changes to firmware. BUG: LCD- Setter and LCD Smartie driver registry code needed some fixing. Made some 'invisible' changes in preparation for v. Version 1. 2. 1: Minor update to software only, no changes to firmware. BUG: LCD- Setter and LCD Smartie driver used WMI to find the USB2. LCD+ (requires administrator privileges), now uses the registry. BUG: LCD- Setter would not report the COM port that caused errors. Version 1. 2: Note: LCD- Setter and display driver are ONLY compatible with bootloader and firmware v. Added a programmable ID to the chip so you can uniquely identify each USB2. LCD+Firmware updating is much more reliable now with more than one USB2. LCD+Display driver can use the programmable ID to select a particular USB2. LCD+BUG: The read version and module commands used the wrong values. BUG: Bootloader now reports versions similar to firmware. Version 1. 1. Added a bootloader and adjusted the main firmware to support this. BUG: Startup message was showing while the computer was off or while USB was suspended. BUG: Backlight/contrast/GPO updating was not happening until the computer had fully turned on. BUG: Interrupt timer was always on even if unnecessary. BUG: Problems with Windows driver. BUG: COM Security error for the LCD Smartie display driver. BUG: Special characters not being sent to LCD from LCD- Setter. Future Work. Add support for 4x. LCD screens. Microchip. The circuit uses a PIC1. F2. 55. 0 DIP2. 8. With little or no changes to the code PIC1. F2. 45. 5/4. 45. 5/4. The program is written in C1. It uses separate bootloader and firmware programs. The bootloader loads first and in particular situations enters . The firmware does most of the work. Bootloader: hex (5. KB, updated 2. 01. KB, updated 2. 01. Firmware: hex (3. KB, updated 2. 01. KB, updated 2. 01. Note: The bootloader is optional. The firmware can be applied directly with a PIC programmer. If you do not have the bootloader, any firmware updates will need to be applied with a PIC programmer as well. Programming the Microchip. To install the bootloader onto the PIC you will need to buy, make, or borrow a PIC programmer. A tutorial is available from Obd. Diag. net. You need to make sure to set the programmer configuration as in this image. Especially important is the USB voltage regulator setting. I may have actually compiled these into the bootloader hex file above, but I am not sure. When plugging in the USB device you will need to install the MCHPUSB driver from Microchip to recognize the device in bootloader mode. Then use the LCD- Setter program to install the firmware. To update the firmware in the future all you have to do is use the LCD- Setter program. Download MCHPUSB Bootloader Driver (6. KB, updated 2. 01. Pinout. Where MCLR is the clear pin, BL- is the backlight ground, IN# are inputs, OUT# are output pins, RB ports are the 8 pins to the LCD, OSC1/2 are the clock pins connected to a 4 MHz crystal, VDD is +5. V from USB, VSS is ground, D+/D- are USB data pins, and VUSB is the voltage regulator. The Circuit. The circuit was designed using Cadsoft Eagle Free. Here is the board I designed: View larger image (1. KB, updated 2. 01. Download Eagle schematic (3. KB, updated 2. 01. Download Eagle board (2. KB, updated 2. 01. Components. R1, R6- R1. R2- R5: 4k. 7R1. 1: 1. C1, C2: 2. 2p. F2. C3, C5: 1. 00n. FC4: 2. FC6, C7: 1. 00u. FQ1- Q4: BC1. L3. X1: 4. MHz. 2IC1: PIC1. F2. 55. 0 DIP2. 8Note 1: The contrast resistor R1. LCD. Note 2: You may replace C1, C2, and X1 (the crystal clock) with a ceramic resonator. Note 3: Any bipolar NPN transistor (BC5. B), BC5. 48(A/B), (2. S)C1. 81. 5, ..) will likely work for Q1- Q4, just make sure to adjust for the order of the pins and the base pin resistor (R2- R5). Note 4: Some LCDs require a resistor for the backlight pins. Connectors. J- LCD: BL- BL+ D7 D6 D5 D4 EN RW RS CT VDD VSS (left to right)J- USB: VCC/Red D- /White D+/Green GND/Black (top to bottom)J- IN: IN1 IN2 IN3 IN4 IN5 GND (left to right, all inputs will use the same ground)J- OUT 1- 3: GND VCC (left to right, these provide higher currents)J- OUT 4- 5: VCC GND (top to bottom, these provide lower currents)The difference between the two types of OUT are that 1- 3 draw current directly from the USB port (suitable for fans) and 4- 5 draw current through the chip (suitable for LEDs). You can make any of them how you want (high or low current draw). If you use the transistor setup it will allow more current draw. Also note that the GND and VCC are kinda backwards between the two types. Connecting to the Computer. Once the firmware is installed a different driver is needed. For Windows XP/Vista/Windows 7 (3. You will get an unsigned driver warning, but can safely ignore it. It is actually using a serial emulation driver built into Windows. You will get a new USB2. LCD+ Communications Port which you can use as a normal serial port. Note: For Vista 6. In XP / Vista 3. 2 / Windows 7 this removes all unsigned driver warnings. To install the certificate, do the following BEFORE installing the driver: Double click usb. INF file)Click . Sadly you will still need Windows to install the firmware the first time with the LCD- Setter program.* Some distributions of Linux are missing the USB cdc- acm driver module and require additional setup. Using LCD- Setter. I made a program that utilizes almost every feature of the USB2. LCD+ interface. It is required to install or update the firmware on the chip. It is very useful for testing the circuit and code. Additionally it is the easiest way to set the startup message for the chip. It also comes with a utility library that has all the code for finding devices and updating the firmware. You need at least . NET Framework 2. 0 to use the program. The program source code is written in C++/CLI and the utility DLL is in C++. It allows you to define what characters your display actually uses so that you can see what the output will look like. Download LCD Setter Application (4. KB, updated 2. 01. Download LCD Setter Source Code (1. KB, updated 2. 01. Using LCD Smartie. Use the Matrix display driver, set the COM port appropriately, and you should be all good to go! Or you can use a custom driver I made for LCD Smartie. The custom driver has slightly better performance, a little more power, and you don't need to know the COM port. It is able to find which COM port it is on it's own (which is really nice if you plug the LCD into different USB ports and the COM port changes). To install just download the DLL file and put it in the . The commands are used by sending special characters over the serial connection and can be used from a custom made program, from a terminal (cmd. Hyperterminal or Secure. CRT, or from within LCD Smartie with $Chr(). Anything that does not start with a 2. Here is the brief list: Display on: 2. As I get emails with questions, I will post the most common problems and solutions here. The most common is the following error in Windows: If this happens before you install the firmware it is most likely that the bootloader was not installed properly or part of the circuit is not setup correctly. The components that can cause this are C4, X1/C1/C2, C3/C5, C6, or R1. Other components are not required before the firmware is installed. If you get this error after installing the firmware it is most likely that the LCD is not properly connected in the circuit. The firmware freezes if it cannot communicate with the LCD. When the firmware freezes, the USB connection freezes, which causes Windows to complain. Hardware Compatibility Specification for Systems for Windows 1. This section of the documentation provides specifications for hardware compatibility for systems running Windows 1. System. Client. Bluetooth. Controller. Base. These requirements apply to systems that have generic Bluetooth controllers. System. Client. Bluetooth. Controller. Base. Le. Specification. If a system includes a Bluetooth enabled controller it must support the Bluetooth 4. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description. The Bluetooth enabled controller must comply with the Basic Rate (BR) and Low Energy (LE) Combined Core Configuration Controller Parts and Host/Controller Interface (HCI) Core Configuration requirements outlined in the Compliance Bluetooth Version 4. System. Client. Bluetooth. Controller. Base. CSSystems that support Connected Standby with Bluetooth enabled controllers must ship with Microsoft's inbox Bluetooth stack. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description. Systems that support Connected Standby that ship with Bluetooth enabled controllers must ship with Microsoft's inbox Bluetooth stack. System. Client. Bluetooth. Controller. Base. Hci. Extensions (if implemented)MSFT Defined HCI extensions support for hardware offload of advertisement and RSSI monitoring. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description Radios that support the Microsoft- OSG Defined Bluetooth HCI Extensions must comply with the specification and pass the related HLKWLK tests. The details of the specifications will be shared at a later date. Partners will be notified via Connect. System. Client. Bluetooth. Controller. Base. LEState. Combinations. Systems with Bluetooth enabled controllers must support a minimum set of LE state combinations. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description. The Bluetooth enabled controller must allow the spec LE state combinations (as allowed in section . Windows will terminate Bluetooth activity by unloading the inbox protocol drivers and their children, submitting the HCI. The radio can be completely powered off if a bus- supported method is available to turn the radio back on. No additional vendor software control components will be supported. On turning the radio back on, the Bluetooth stack for Windows shall resume the device to D0, allowing bus drivers to restart the device. The Windows Bluetooth stack shall then reinitialize the Bluetooth enabled components of the controller. Bluetooth Radio Management shall only be enabled for internal Bluetooth 4. The on/off state of Bluetooth- enabled controllers shall be controllable via software as described in Bluetooth Software Radio Switch. The Off state is defined, at a minimum, as disabling the antenna component of the Bluetooth enabled module so there can be no transmission/reception. There must not be any hardware- only switches to control power to the Bluetooth enabled radio. The radio must maintain on/off state across sleep and reboot. System. Client. Bluetooth. Controller. Base. Simultaneous. Br. Edr. And. Le. Traffic. Bluetooth enabled controllers must support simultaneous BR/EDR and LE traffic. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description. Bluetooth enabled controllers must allow the simultaneous use of both Basic Rate (BR)/Enhanced Data Rate (EDR) and Low Energy (LE) radios. System. Client. Bluetooth. Controller. Base. Wideband. Speech. Applies to. Windows 1. Mobile ARMWindows 1. Mobile x. 86. Description. Wideband speech enables high definition voice quality (audio is sampled at 1. KHz as opposed to only 8 KHz) for telephony audio on Windows devices when the user is communicating via a Bluetooth peripheral that also supports wideband speech. What this means is that Bluetooth radios must support wideband speech in the hardware as defined by the Bluetooth SIG Hands- Free Profile (HFP) 1. Core Specification Addendum (CSA) 2 which is included in the Core Version 4. Bluetooth specification. At a minimum it must use at least one Bluetooth SIG defined wideband speech codec (currently m. SBC). Business Justification: We want users to experience the best possible quality audio when using Bluetooth peripherals on Windows. Wideband speech is becoming a standard for peripherals that support the HFP profile. Our competition already supports it. System. Client. Bluetooth. Controller. Base. WLANBTCoexistence. Windows Systems that support both WLAN and Bluetooth must meet WLAN- BT Co- existence requirements. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description. Windows systems that support both WLAN and Bluetooth must meet WLAN- BT Co- existence requirements listed below. The requirement is applicable to all WLAN devices across all bus types. Must not drop the connection with WLAN AP when Bluetooth is scanning for new devices. Must be able to scan simultaneously for both WLAN and Bluetooth networks. System. Client. Bluetooth. Controller. Non. USBThese requirements apply to systems that have non- USB Bluetooth enabled controllers. System. Client. Bluetooth. Controller. Non. USB. Non. Usb. Uses. Microsofts. Stack. Any platform using a non- USB connected Bluetooth enabled controller must ship with Microsoft’s inbox Bluetooth stack. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description. Any platform using a non- USB connected Bluetooth enabled controller must ship with Microsoft’s inbox Bluetooth stack. System. Client. Bluetooth. Controller. Non. USB. Sco. Support. Any platform with a non- USB connected Bluetooth enabled controller must use a sideband channel for SCO. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description. Any platform using a Non- USB connected Bluetooth enabled controller must use sideband channel for SCO (such as SCO over an I2. S/PCM interface). System. Client. Bluetooth. Controller. USBThese requirements apply to systems that have USB Bluetooth enabled controllers. System. Client. Bluetooth. Controller. USB. Sco. Data. Transport. Layer. Bluetooth enabled host controllers support the SCO data transport layer as specified in the Bluetooth 2. EDR specifications. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Description. A System with a Bluetooth enabled controller must comply with the Synchronous Connection Oriented (SCO)- USB requirements that are outlined in the Specification of the Bluetooth System, Version 2. Enhanced Data Rate (EDR), Part A, Section 3. System. Client. Brightness. Controls. This section describes requirements systems with brightness controls. System. Client. Brightness. Controls. Backlight. Optimization. Windows Display Driver Model (WDDM) 1. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Windows Server 2. Description. If WDDM driver supports scenario based backlight power optimization, it must indicate the support by implementing the DXGK. Driver must optimize for scenarios like photo viewing, browser, and Office documents. Dxgk. Backlight. Optimization. Dynamic: Driver is required to enable backlight optimization at a higher aggressiveness level. Driver must optimize for scenarios like video playback and gaming. Dxgk. Backlight. Optimization. Dimmed: Driver is required to enable backlight optimization at a higher aggressiveness level. Driver must make sure that the content on the screen is visible but it need not be easily readable. Driver is allowed to dynamically change the aggressiveness level based on the content on the screen. Driver is required to handle Windows requests for change to brightness level (based on user input or ambient light sensor) while keeping backlight optimization enabled. Driver is required to gradually transition between aggressiveness levels: This is important in the case when user briefly invokes playback controls. At that time, Windows will reset the scenario from Dxgk. Backlight. Optimization. Dynamic to Dxgk. Backlight. Optimization. Desktop. The transition must not be a step but must be gradual. WDDM driver is required to provide accurate information when Windows queries Dxgk. Ddi. Get. Backlight. Reduction. Connecting additional display devices to the system must not impact the ability to perform backlight optimization on the integrated panel of the system. System. Client. Brightness. Controls. Brightness. Control. Buttons. Systems that have built in physical brightness control function keys use standard ACPI events and support control of LCD backlight brightness via ACPI methods in the system firmware. Applies to. Windows 1. Home, Pro, Enterprise, and Education) x. Windows 1. 0 for desktop editions (Home, Pro, Enterprise, and Education) x. Windows 1. 0 Mobile ARMWindows 1. Mobile x. 86. Windows Server 2. Description. Windows provides users with an LCD brightness control user interface.
0 Comments
Official Site for Microsoft Windows 1. Home, S & Pro OS, laptops, PCs, tablets & more. Count on the broadest range of innovative laptops, 2- in- 1’s, portable All- in- Ones, and phones that you can use like a PC. Expect long- lasting batteries, faster processors, and high- resolution displays. Windows Mail (formerly Outlook Express) is an online communication tool supplied as part of Windows Vista and later versions. Windows Mail. This category will teach you how to use E-Mail with Windows Mail. An e-mail is a data file that must contain at least one E-Mail Address (i.e. Windows Vista (codenamed Longhorn) is an operating system by Microsoft for use on personal computers, including home and business desktops, laptops, tablet PCs and. It’s true – Outlook Express was replaced by Windows Mail in Windows Vista, but with the release of Windows 7 even that has disappeared, along with Windows. Setting up an Email Account in : Microsoft Mail (Vista Only) Below are the steps required to get your email account setup in Windows Mail in Windows Vista. Set up and sync your email and calendar accounts with the Mail and Calendar apps in Windows 10. Windows Mail replaces Outlook Express on computers that are running the Windows Vista operating system. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2018
Categories |