search for: cypress_m8

Hello, i try to setup NUT service to read/control my UPS but without success. Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u root start" i got: /Network UPS Tools - UPS driver controller 2.6.2/ / 0.000000/ /If you're not a NUT core developer, chances are that you're told to enable debugging/ /to see why a driver

...nder Windoze, again through the USB port. The error I get is: drivers/usb/input/hid-core.c: couldn't find an input interrupt endpoint usbhid: probe of 3-2:1.0 failed with error -5 I opened the UPS and found a Cypress CY7C63723-PC chip. So I wrote to Lonnie Mendez, the maintainer of the cypress_m8 driver; this is what he replied (quoting with permission): > Yes, the CY7C63723 is in the family. However in this instance, the device seems > to go by the standards defined in the HID documentation at usb.org (notice the several > usage definitions given by the hid report descrip...

...nder Windoze, again through the USB port. The error I get is: drivers/usb/input/hid-core.c: couldn't find an input interrupt endpoint usbhid: probe of 3-2:1.0 failed with error -5 I opened the UPS and found a Cypress CY7C63723-PC chip. So I wrote to Lonnie Mendez, the maintainer of the cypress_m8 driver; this is what he replied (quoting with permission): > Yes, the CY7C63723 is in the family. However in this instance, the device seems > to go by the standards defined in the HID documentation at usb.org (notice the several > usage definitions given by the hid report descrip...

...al_generic usbserial: USB Serial Driver core usbserial: USB Serial support registered for DeLorme Earthmate USB usbserial: USB Serial support registered for HID->COM RS232 Adapter usbserial: USB Serial support registered for Nokia CA-42 V2 Adapter usbcore: registered new interface driver cypress cypress_m8: Cypress USB to Serial Driver v1.09 udevmonitor: UEVENT[1229960645.326958] add /devices/pci0000:00/0000:00:0b.0/usb2/2-3 (usb) UEVENT[1229960645.332895] add /devices/pci0000:00/0000:00:0b.0/usb2/2-3/2-3:1.0 (usb) UDEV [1229960645.341691] add /devices/pci0000:00/0000:00:0b.0/usb2/2-3 (usb) UEVENT[...

...g with minicom to the UPS, and got a status from Q1\r and heard it click on T and TL. So far, so good. I'd like to use the USB interface, but I can't get it to work. It appears in dmesg as hiddev96: USB HID v1.00 Device [Cypress Semiconductor USB to Serial] on usb-0000:00:1d.0-1 howevery cypress_m8 doesn't bind to it and create /dev/ttyUSB0. newhidups doesn't recognise it, but I don't think it should because it's a serial interface, not a proper USB HID Power device. What's my next step towards getting this device running with nut? [1] http://www.shopbot.com.au/p-34502...

...els had USB-to-serial drivers for that chip.) > -- > Charles Lepple > clepple at gmail I don't know whether someone needs help with this or not anymore, however I had a similar problem with a Mustek 848 LCD UPS and the solution was easier than I thought: there was no need to load the cypress_m8 module, because, at least on the systems that I've tried (Ubuntu 12.04 and an Openwrt i386 build), using the blazer_usb module, the first serial console was being used to communicate with the UPS and there was no /dev/ttyUSB* present. My lsusb: Bus 001 Device 038: ID 0665:5161 Cypress Semicon...

...that this driver uses the same protocol) * usbhid-ups - no information about the battery, only basic information about the UPS (it's communicated, so it's a start) (this could be the general usb driver?) * powercom - here is the output of the driver (supposed to be able to communicate if cypress_m8 is present) # ./powercom -DDDDD -a my -u root -x type=BNT Network UPS Tools - PowerCom protocol UPS driver 0.12 (2.4.1-1993) 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS0" 0.000159 send_to_all: SETINFO driver.parameter.type "BNT" 0.000265 debug level is ...

...type=IMP automatically re-detects the UPS as "KIN" and then interprets raw data incorrectly. The same problem was reported by other Powercom users on the official support forum ( http://forum.pcm.ru ). I suppose the problem concerns models with serial-over-usb connection implemented via cypress_m8 chip (ID 0d9f:0002), e.g. IMD-865AP USB, BNT-1000AP USB, etc. (these are on sale everywhere in Russia). The thing is that such UPS sends raw_data[UPSVERSION]==0xFF like "Imperial" series and simultaneously raw_data[MODELNAME]==0x4B like "KING" series (the explanation is proposed...

Howdy, I've been trying for a while now to get this running. Can anybody please tell me what the proper configuration is for this unit ??? This is what I've got/tried so far: # cat ups.conf # Start with # # # upsdrvctl -u nut -D start MEGATEC MODE=netserver user=nut # Ultra ULT33046 2000 VA 1200 W

On 8/15/2017 6:13 AM, Charles Lepple wrote: > On Aug 10, 2017, at 12:19 AM, Harlan Stenn wrote: >> >> 0.447497 HID descriptor length 37 >> 0.450449 Report Descriptor size = 37 >> 0.451062 Using subdriver: PowerCOM HID 0.5 >> 0.451996 3 HID objects found >> 0.453502 Path: ffa00001.ffa00001, Type: Input, ReportID: 0x00, >> Offset: 0, Size: 8,

I just bought an Ultra UPS system for my linux server, and I need help getting it set up. It's an Ultra 700VA UPS. NUT INFORMATION: Package (apt-get install nut) NUT VERSION: Latest Driver: I don't have one? Here's the device information from my syslog: Code: Jul 7 23:25:27 eric-desktop kernel: [ 3045.609066] usb 2-1: USB disconnect, address 3 Jul 7 23:25:30 eric-desktop

cmd test.battery.start.deep was not tested yet. cmd test.battery.start.quick works as expected. cmd test.battery.start 120 works as expected. cmd test.battery.stop works as expected. cmd beeper.toggle works as expected. cmd shutdown.return works as expected. cmd shutdown.reboot does not work entirely. After a minute, UPS is shut down but didn't come back. (Issuing shutdown.stop power up it

Hello again! Sorry for not being able to test this before. Ulisses, please apply the patch to fix typo in my e-mail address. I've compiled it against nut-2.6.5 about 10 hours ago. It was everything fine until now. I'm seeing CHRG but the ups led wasn't blinking at all. Vendor software was strangely showing charging also. I am assuming this is expected behavior. I've set the

...drivers/usb/phy/phy-fsl-usb.c | 4 +- drivers/usb/phy/phy-isp1301-omap.c | 15 ++- drivers/usb/phy/phy-mv-usb.c | 2 +- drivers/usb/renesas_usbhs/mod_gadget.c | 2 +- drivers/usb/renesas_usbhs/pipe.c | 2 +- drivers/usb/serial/cypress_m8.c | 4 +- drivers/usb/serial/io_edgeport.c | 4 +- drivers/usb/serial/kobil_sct.c | 2 +- drivers/usb/serial/upd78f0730.c | 2 +- drivers/usb/storage/sddr55.c | 2 +- drivers/usb/storage/uas.c |...

...drivers/usb/phy/phy-fsl-usb.c | 4 +- drivers/usb/phy/phy-isp1301-omap.c | 15 ++- drivers/usb/phy/phy-mv-usb.c | 2 +- drivers/usb/renesas_usbhs/mod_gadget.c | 2 +- drivers/usb/renesas_usbhs/pipe.c | 2 +- drivers/usb/serial/cypress_m8.c | 4 +- drivers/usb/serial/io_edgeport.c | 4 +- drivers/usb/serial/kobil_sct.c | 2 +- drivers/usb/serial/upd78f0730.c | 2 +- drivers/usb/storage/sddr55.c | 2 +- drivers/usb/storage/uas.c |...

...drivers/usb/phy/phy-fsl-usb.c | 4 +- drivers/usb/phy/phy-isp1301-omap.c | 15 ++- drivers/usb/phy/phy-mv-usb.c | 2 +- drivers/usb/renesas_usbhs/mod_gadget.c | 2 +- drivers/usb/renesas_usbhs/pipe.c | 2 +- drivers/usb/serial/cypress_m8.c | 4 +- drivers/usb/serial/io_edgeport.c | 4 +- drivers/usb/serial/kobil_sct.c | 2 +- drivers/usb/serial/upd78f0730.c | 2 +- drivers/usb/storage/sddr55.c | 2 +- drivers/usb/storage/uas.c |...

...drivers/usb/phy/phy-fsl-usb.c | 4 +- drivers/usb/phy/phy-isp1301-omap.c | 15 ++- drivers/usb/phy/phy-mv-usb.c | 2 +- drivers/usb/renesas_usbhs/mod_gadget.c | 2 +- drivers/usb/renesas_usbhs/pipe.c | 2 +- drivers/usb/serial/cypress_m8.c | 4 +- drivers/usb/serial/io_edgeport.c | 4 +- drivers/usb/serial/kobil_sct.c | 2 +- drivers/usb/serial/upd78f0730.c | 2 +- drivers/usb/storage/sddr55.c | 2 +- drivers/usb/storage/uas.c |...

...drivers/usb/phy/phy-fsl-usb.c | 4 +- drivers/usb/phy/phy-isp1301-omap.c | 15 ++- drivers/usb/phy/phy-mv-usb.c | 2 +- drivers/usb/renesas_usbhs/mod_gadget.c | 2 +- drivers/usb/renesas_usbhs/pipe.c | 2 +- drivers/usb/serial/cypress_m8.c | 4 +- drivers/usb/serial/io_edgeport.c | 4 +- drivers/usb/serial/kobil_sct.c | 2 +- drivers/usb/serial/upd78f0730.c | 2 +- drivers/usb/storage/sddr55.c | 2 +- drivers/usb/storage/uas.c |...

Hi Konrad, Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361). It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0." With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between. dmesg and xm dmesg attached -- Sander Dom0 shows: total

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the