ATNEL tech-forum 2017-12-28T00:45:29+01:00 https://forum.atnel.pl/feed.php?f=4&t=19858&mode 2017-12-28T00:45:29+01:00 2017-12-28T00:45:29+01:00 https://forum.atnel.pl/viewtopic.php?t=19858&p=201149#p201149 <![CDATA[Re: vusb linux problem z wykryciem]]> Jakiś czas temu walczyłem z dostawcą pewnego sprzętu, który to nie działał poprawnie pod linuxem, bo ten za dużo chciał od urządzenia a ono niepoprawnie reagowało i linux w końcu je "olewał". Przy okazji też wyszły problemy z podłączaniem do portów USB 3.0. Urządzenie niepoprawnie sterowało pull-upami na liniach danych i się wszystko wykładało :(. Co ciekawe te niepoprawne sterowanie nie przeszkadzało starym mostkom USB 2.0 :).

Zrób swój układ zgodnie ze schematem USBasp http://www.fischl.de/usbasp/. Wrzuć na początek kod oryginalny a potem zacznij modyfikować.

--
Pozdrawiam,
Robert

------------------------ [ Dodano po: 8 minutach ]

Zastanów się bo może warto za 10 zł zakupić na aledrogo płytkę USBasp. Może nie są one górnolotnych lotów, ale działają i do zabawy z V-USB nadają się idealnie (oczywiście nie mówię, że są to dobrze zrobione programatory ISP) :).

Statystyki: Napisane przez rskup — 28 gru 2017, o 00:45

]]> 2017-12-27T22:05:16+01:00 2017-12-27T22:05:16+01:00 https://forum.atnel.pl/viewtopic.php?t=19858&p=201143#p201143 <![CDATA[Re: vusb linux problem z wykryciem]]>

WoodPaker napisał(a):

http://forum.atnel.pl/topic6137.html?hilit=VUSB

Czytalem, bardzo fajny i przydatny poradnik, co do rezystorow 68 Ohm to rowniez manipulowalem z nimi na wszystkie mozliwe sposoby.

rskup napisał(a):

Czy na pewno masz poprawnie podefniowane descryptory?
Proponuję Ci wziąć na początek jakiś działający projekt oparty o V-USB i na nim się pobawić. Ja polecam projekt USBasp

Probowalem juz z innymi projektami i nic to nie dało, ale z USBasp jeszcze nie, a chyba warto.

roske napisał(a):

Co do rezystora na D+ wyjaśnienie jest w usbdrv.h:
"... A pull-down or pull-up of 1M SHOULD be connected from D+ to +3.5V to prevent interference when no USB master is connected. If you use Zener diodes to limit the voltage on D+ and D-, you MUST use a pull-down resistor, not a pull-up...."
I dalej:
"Operation without an USB master:
The driver behaves neutral without connection to an USB master if D- reads
as 1. To avoid spurious interrupts, we recommend a high impedance (e.g. 1M)
pull-down or pull-up resistor on D+ (interrupt). If Zener diodes are used,
use a pull-down. If D- becomes statically 0, the driver may block in the
interrupt routine."

Probowalem juz z roznych kombinacji, rezystor 1M do GND lub do VCC, badz tez kompletny jego brak.
I przepraszam najmocniej, ale nie dopisalem ze korzystam z dołączonego przeze mnie schematu + zener 3,6 V. Oczywiscie jak zasilalem uklad z 3v3 to pozbylem sie diod zenera. Mimo wszystko nic to nie zmieniło. Dziekuje za linki, skorzystałem z nich, ale niestety nic to nie pomoglo :(.

Co wiecej dzisiaj sprobowalem podlaczyc uklad do kilku jednostek i jest taka dziwna zależnosc
Jezeli komputer posiada co najmniej jeden port USB 3.0 to uklad nie dziala, nawet jezei podlacze sie do portu USB 2.0
Jezeli komputer nie posiada portu USB 3.0 wszystko dziala jak nalezy.
Nie sprawdzalem na windowsie, na linuksie taka zaleznosc wystepowala.
Smiem przez to twierdzic, ze moze miec na to wplyw kontroler USB na plycie glownej, ale nie dam sobie nawet wlosa z glowy za to wyrwac, bo to brzmi jak propagowanie herezji. Co wiecej jezeli projekt USBasp jest oparty na v-usb to rowniez ten programator nie powinien mi dzialac, a jest zupelnie inaczej…

Jezli ktos na cos wpadnie, bede bardzo wdzieczny za wszystkie odpowiedzi, bo jestem ciekaw co jest nie tak.

PS. I strasznie mocno przepraszam za RZyczenia, niech karą bedzie wstyd jakiego doznalem :)

Statystyki: Napisane przez mozerpol — 27 gru 2017, o 22:05

]]> 2017-12-27T16:02:44+01:00 2017-12-27T16:02:44+01:00 https://forum.atnel.pl/viewtopic.php?t=19858&p=201113#p201113 <![CDATA[Re: vusb linux problem z wykryciem]]>
Proponuję Ci wziąć na początek jakiś działający projekt oparty o V-USB i na nim się pobawić. Ja polecam projekt USBasp, on wykorzystuje V-USB i jest prosto napisany i łatwo oddzielić warstwę USB od reszty projektu (kody i schematy dostępne na stronie projektu).

--
Pozdrawiam,
Robert

Statystyki: Napisane przez rskup — 27 gru 2017, o 16:02

]]> 2017-12-26T22:25:50+01:00 2017-12-26T22:25:50+01:00 https://forum.atnel.pl/viewtopic.php?t=19858&p=201083#p201083 <![CDATA[Re: vusb linux problem z wykryciem]]>
No i oczywiście też Ci RZyczę WesołyH ŚwiONt :roll:

P.S.
topic6137.html?hilit=VUSB

Statystyki: Napisane przez WoodPaker — 26 gru 2017, o 22:25

]]> 2017-12-26T21:52:46+01:00 2017-12-26T21:52:46+01:00 https://forum.atnel.pl/viewtopic.php?t=19858&p=201082#p201082 <![CDATA[vusb linux problem z wykryciem]]> Moim celem jest użycie projektu vusb. Niestety napotykam na poważne problemy, z ktorymi nie jestem w stanie sobie sam poradzic.
zlozylem uklad wg tego schematu:
Obrazek

Uklad na plytce wyglada tak:
Obrazek

Procek to atmega16A taktowana zegarem 12 MHz, linia D+ (do INT0) to zielony przewod, natomiast D- (do INT1) to bialy przewod. Oba sa podlaczone przez rezystor 68 om + zener 3,6 V. Dodatkowo D+ jest podciagniety do VCC przez rezystor 1M om, a D- do VCC, przez reyzstor 1,5K om. Sam procek zasilany jest z 5 V (dzieki USB), w pliku usbconfig.h oczywiscie jest to uwzglednione.

Wgrywam taki program do procka:
Plik main:
[syntax=c]#include<avr/io.h>
#include<avr/interrupt.h>
#include<avr/wdt.h>
#include<util/delay.h>
#include"usbdrv.h"
#define F_CPU 12000000

#define USB_LED_OFF 0
#define USB_LED_ON 1

USB_PUBLIC uchar usbFunctionSetup(uchar data[8])//funkcja obslugujaca wywolania USB, mozna ja wykorzystac do wysylania danych satycznych. Natomiast
{//jesli chcemy przesyłać dane odczytywane "w locie" winnismy użyć funkcji usbFunctionRead.
usbRequest_t *rq = (void *)data;
switch(rq->bRequest) // custom command is in the bRequest field
{
case USB_LED_ON:
PORTB |= 1; // turn LED on
return 0;
case USB_LED_OFF:
PORTB &= ~1; // turn LED off
return 0;
}

return 0;// Narazie nic nie rób
}

int main()
{
uchar i;
DDRB = 1; // PB0 as output

wdt_enable(WDTO_1S);// uaktywnij jednosekundowy watchdog

usbInit();//inicjuje biblioteke VUSB

usbDeviceDisconnect();// Wymuś przenumerowanie
for(i =0; i<250; i++)
{// Odczekaj około 500 ms
wdt_reset();// Poinformuj watchdog, ze procesor działa
_delay_ms(2);
}
usbDeviceConnect();

sei();// Aktywuj przerwania po renumeracji

while(1){
wdt_reset();// wiadomo, jak wyżej
usbPoll();
}

return 0;
}[/syntax]

Plik usbconfig.h:
[syntax=c]#ifndef __usbconfig_h_included__
#define __usbconfig_h_included__

/*
General Description:
This file is an example configuration (with inline documentation) for the USB
driver. It configures V-USB for USB D+ connected to Port D bit 2 (which is
also hardware interrupt 0 on many devices) and USB D- to Port D bit 4. You may
wire the lines to any other port, as long as D+ is also wired to INT0 (or any
other hardware interrupt, as long as it is the highest level interrupt, see
section at the end of this file).
+ To create your own usbconfig.h file, copy this file to your project's
+ firmware source directory) and rename it to "usbconfig.h".
+ Then edit it accordingly.
*/

/* ---------------------------- Hardware Config ---------------------------- */

#define USB_CFG_IOPORTNAME D
/* This is the port where the USB bus is connected. When you configure it to
* "B", the registers PORTB, PINB and DDRB will be used.
*/
#define USB_CFG_DMINUS_BIT 3
/* This is the bit number in USB_CFG_IOPORT where the USB D- line is connected.
* This may be any bit in the port.
*/
#define USB_CFG_DPLUS_BIT 2
/* This is the bit number in USB_CFG_IOPORT where the USB D+ line is connected.
* This may be any bit in the port. Please note that D+ must also be connected
* to interrupt pin INT0! [You can also use other interrupts, see section
* "Optional MCU Description" below, or you can connect D- to the interrupt, as
* it is required if you use the USB_COUNT_SOF feature. If you use D- for the
* interrupt, the USB interrupt will also be triggered at Start-Of-Frame
* markers every millisecond.]
*/
#define F_CPU 12000000
#define USB_CFG_CLOCK_KHZ (F_CPU/1000)
/* Clock rate of the AVR in kHz. Legal values are 12000, 12800, 15000, 16000,
* 16500, 18000 and 20000. The 12.8 MHz and 16.5 MHz versions of the code
* require no crystal, they tolerate +/- 1% deviation from the nominal
* frequency. All other rates require a precision of 2000 ppm and thus a
* crystal!
* Since F_CPU should be defined to your actual clock rate anyway, you should
* not need to modify this setting.
*/
#define USB_CFG_CHECK_CRC 0
/* Define this to 1 if you want that the driver checks integrity of incoming
* data packets (CRC checks). CRC checks cost quite a bit of code size and are
* currently only available for 18 MHz crystal clock. You must choose
* USB_CFG_CLOCK_KHZ = 18000 if you enable this option.
*/

/* ----------------------- Optional Hardware Config ------------------------ */

/* #define USB_CFG_PULLUP_IOPORTNAME D */
/* If you connect the 1.5k pullup resistor from D- to a port pin instead of
* V+, you can connect and disconnect the device from firmware by calling
* the macros usbDeviceConnect() and usbDeviceDisconnect() (see usbdrv.h).
* This constant defines the port on which the pullup resistor is connected.
*/
/* #define USB_CFG_PULLUP_BIT 4 */
/* This constant defines the bit number in USB_CFG_PULLUP_IOPORT (defined
* above) where the 1.5k pullup resistor is connected. See description
* above for details.
*/

/* --------------------------- Functional Range ---------------------------- */

#define USB_CFG_HAVE_INTRIN_ENDPOINT 0
/* Define this to 1 if you want to compile a version with two endpoints: The
* default control endpoint 0 and an interrupt-in endpoint (any other endpoint
* number).
*/
#define USB_CFG_HAVE_INTRIN_ENDPOINT3 0
/* Define this to 1 if you want to compile a version with three endpoints: The
* default control endpoint 0, an interrupt-in endpoint 3 (or the number
* configured below) and a catch-all default interrupt-in endpoint as above.
* You must also define USB_CFG_HAVE_INTRIN_ENDPOINT to 1 for this feature.
*/
#define USB_CFG_EP3_NUMBER 3
/* If the so-called endpoint 3 is used, it can now be configured to any other
* endpoint number (except 0) with this macro. Default if undefined is 3.
*/
/* #define USB_INITIAL_DATATOKEN USBPID_DATA1 */
/* The above macro defines the startup condition for data toggling on the
* interrupt/bulk endpoints 1 and 3. Defaults to USBPID_DATA1.
* Since the token is toggled BEFORE sending any data, the first packet is
* sent with the oposite value of this configuration!
*/
#define USB_CFG_IMPLEMENT_HALT 0
/* Define this to 1 if you also want to implement the ENDPOINT_HALT feature
* for endpoint 1 (interrupt endpoint). Although you may not need this feature,
* it is required by the standard. We have made it a config option because it
* bloats the code considerably.
*/
#define USB_CFG_SUPPRESS_INTR_CODE 0
/* Define this to 1 if you want to declare interrupt-in endpoints, but don't
* want to send any data over them. If this macro is defined to 1, functions
* usbSetInterrupt() and usbSetInterrupt3() are omitted. This is useful if
* you need the interrupt-in endpoints in order to comply to an interface
* (e.g. HID), but never want to send any data. This option saves a couple
* of bytes in flash memory and the transmit buffers in RAM.
*/
#define USB_CFG_INTR_POLL_INTERVAL 10
/* If you compile a version with endpoint 1 (interrupt-in), this is the poll
* interval. The value is in milliseconds and must not be less than 10 ms for
* low speed devices.
*/
#define USB_CFG_IS_SELF_POWERED 0
/* Define this to 1 if the device has its own power supply. Set it to 0 if the
* device is powered from the USB bus.
*/
#define USB_CFG_MAX_BUS_POWER 100
/* Set this variable to the maximum USB bus power consumption of your device.
* The value is in milliamperes. [It will be divided by two since USB
* communicates power requirements in units of 2 mA.]
*/
#define USB_CFG_IMPLEMENT_FN_WRITE 0
/* Set this to 1 if you want usbFunctionWrite() to be called for control-out
* transfers. Set it to 0 if you don't need it and want to save a couple of
* bytes.
*/
#define USB_CFG_IMPLEMENT_FN_READ 0
/* Set this to 1 if you need to send control replies which are generated
* "on the fly" when usbFunctionRead() is called. If you only want to send
* data from a static buffer, set it to 0 and return the data from
* usbFunctionSetup(). This saves a couple of bytes.
*/
#define USB_CFG_IMPLEMENT_FN_WRITEOUT 0
/* Define this to 1 if you want to use interrupt-out (or bulk out) endpoints.
* You must implement the function usbFunctionWriteOut() which receives all
* interrupt/bulk data sent to any endpoint other than 0. The endpoint number
* can be found in 'usbRxToken'.
*/
#define USB_CFG_HAVE_FLOWCONTROL 0
/* Define this to 1 if you want flowcontrol over USB data. See the definition
* of the macros usbDisableAllRequests() and usbEnableAllRequests() in
* usbdrv.h.
*/
#define USB_CFG_DRIVER_FLASH_PAGE 0
/* If the device has more than 64 kBytes of flash, define this to the 64 k page
* where the driver's constants (descriptors) are located. Or in other words:
* Define this to 1 for boot loaders on the ATMega128.
*/
#define USB_CFG_LONG_TRANSFERS 0
/* Define this to 1 if you want to send/receive blocks of more than 254 bytes
* in a single control-in or control-out transfer. Note that the capability
* for long transfers increases the driver size.
*/
/* #define USB_RX_USER_HOOK(data, len) if(usbRxToken == (uchar)USBPID_SETUP) blinkLED(); */
/* This macro is a hook if you want to do unconventional things. If it is
* defined, it's inserted at the beginning of received message processing.
* If you eat the received message and don't want default processing to
* proceed, do a return after doing your things. One possible application
* (besides debugging) is to flash a status LED on each packet.
*/
/* #define USB_RESET_HOOK(resetStarts) if(!resetStarts){hadUsbReset();} */
/* This macro is a hook if you need to know when an USB RESET occurs. It has
* one parameter which distinguishes between the start of RESET state and its
* end.
*/
/* #define USB_SET_ADDRESS_HOOK() hadAddressAssigned(); */
/* This macro (if defined) is executed when a USB SET_ADDRESS request was
* received.
*/
#define USB_COUNT_SOF 0
/* define this macro to 1 if you need the global variable "usbSofCount" which
* counts SOF packets. This feature requires that the hardware interrupt is
* connected to D- instead of D+.
*/
/* #ifdef __ASSEMBLER__
* macro myAssemblerMacro
* in YL, TCNT0
* sts timer0Snapshot, YL
* endm
* #endif
* #define USB_SOF_HOOK myAssemblerMacro
* This macro (if defined) is executed in the assembler module when a
* Start Of Frame condition is detected. It is recommended to define it to
* the name of an assembler macro which is defined here as well so that more
* than one assembler instruction can be used. The macro may use the register
* YL and modify SREG. If it lasts longer than a couple of cycles, USB messages
* immediately after an SOF pulse may be lost and must be retried by the host.
* What can you do with this hook? Since the SOF signal occurs exactly every
* 1 ms (unless the host is in sleep mode), you can use it to tune OSCCAL in
* designs running on the internal RC oscillator.
* Please note that Start Of Frame detection works only if D- is wired to the
* interrupt, not D+. THIS IS DIFFERENT THAN MOST EXAMPLES!
*/
#define USB_CFG_CHECK_DATA_TOGGLING 0
/* define this macro to 1 if you want to filter out duplicate data packets
* sent by the host. Duplicates occur only as a consequence of communication
* errors, when the host does not receive an ACK. Please note that you need to
* implement the filtering yourself in usbFunctionWriteOut() and
* usbFunctionWrite(). Use the global usbCurrentDataToken and a static variable
* for each control- and out-endpoint to check for duplicate packets.
*/
#define USB_CFG_HAVE_MEASURE_FRAME_LENGTH 0
/* define this macro to 1 if you want the function usbMeasureFrameLength()
* compiled in. This function can be used to calibrate the AVR's RC oscillator.
*/
#define USB_USE_FAST_CRC 0
/* The assembler module has two implementations for the CRC algorithm. One is
* faster, the other is smaller. This CRC routine is only used for transmitted
* messages where timing is not critical. The faster routine needs 31 cycles
* per byte while the smaller one needs 61 to 69 cycles. The faster routine
* may be worth the 32 bytes bigger code size if you transmit lots of data and
* run the AVR close to its limit.
*/

/* -------------------------- Device Description --------------------------- */

#define USB_CFG_VENDOR_ID 0xc0, 0x16 /* = 0x16c0 = 5824 = voti.nl */
/* USB vendor ID for the device, low byte first. If you have registered your
* own Vendor ID, define it here. Otherwise you may use one of obdev's free
* shared VID/PID pairs. Be sure to read USB-IDs-for-free.txt for rules!
* *** IMPORTANT NOTE ***
* This template uses obdev's shared VID/PID pair for Vendor Class devices
* with libusb: 0x16c0/0x5dc. Use this VID/PID pair ONLY if you understand
* the implications!
*/
#define USB_CFG_DEVICE_ID 0xdc, 0x05 /* = 0x05dc = 1500 */
/* This is the ID of the product, low byte first. It is interpreted in the
* scope of the vendor ID. If you have registered your own VID with usb.org
* or if you have licensed a PID from somebody else, define it here. Otherwise
* you may use one of obdev's free shared VID/PID pairs. See the file
* USB-IDs-for-free.txt for details!
* *** IMPORTANT NOTE ***
* This template uses obdev's shared VID/PID pair for Vendor Class devices
* with libusb: 0x16c0/0x5dc. Use this VID/PID pair ONLY if you understand
* the implications!
*/
#define USB_CFG_DEVICE_VERSION 0x00, 0x01
/* Version number of the device: Minor number first, then major number.
*/
#define USB_CFG_VENDOR_NAME 'm', 'o', 'z', 'e', 'r', 'p', 'o', 'l'
#define USB_CFG_VENDOR_NAME_LEN 8
/* These two values define the vendor name returned by the USB device. The name
* must be given as a list of characters under single quotes. The characters
* are interpreted as Unicode (UTF-16) entities.
* If you don't want a vendor name string, undefine these macros.
* ALWAYS define a vendor name containing your Internet domain name if you use
* obdev's free shared VID/PID pair. See the file USB-IDs-for-free.txt for
* details.
*/
#define USB_CFG_DEVICE_NAME 'm', 'o', 'z', 'z', 'z', 'z', 'e', 'r'
#define USB_CFG_DEVICE_NAME_LEN 8
/* Same as above for the device name. If you don't want a device name, undefine
* the macros. See the file USB-IDs-for-free.txt before you assign a name if
* you use a shared VID/PID.
*/
/*#define USB_CFG_SERIAL_NUMBER 'N', 'o', 'n', 'e' */
/*#define USB_CFG_SERIAL_NUMBER_LEN 0 */
/* Same as above for the serial number. If you don't want a serial number,
* undefine the macros.
* It may be useful to provide the serial number through other means than at
* compile time. See the section about descriptor properties below for how
* to fine tune control over USB descriptors such as the string descriptor
* for the serial number.
*/
#define USB_CFG_DEVICE_CLASS 0xff /* set to 0 if deferred to interface */
#define USB_CFG_DEVICE_SUBCLASS 0
/* See USB specification if you want to conform to an existing device class.
* Class 0xff is "vendor specific".
*/
#define USB_CFG_INTERFACE_CLASS 0 /* define class here if not at device level */
#define USB_CFG_INTERFACE_SUBCLASS 0
#define USB_CFG_INTERFACE_PROTOCOL 0
/* See USB specification if you want to conform to an existing device class or
* protocol. The following classes must be set at interface level:
* HID class is 3, no subclass and protocol required (but may be useful!)
* CDC class is 2, use subclass 2 and protocol 1 for ACM
*/
/* #define USB_CFG_HID_REPORT_DESCRIPTOR_LENGTH 42 */
/* Define this to the length of the HID report descriptor, if you implement
* an HID device. Otherwise don't define it or define it to 0.
* If you use this define, you must add a PROGMEM character array named
* "usbHidReportDescriptor" to your code which contains the report descriptor.
* Don't forget to keep the array and this define in sync!
*/

/* #define USB_PUBLIC static */
/* Use the define above if you #include usbdrv.c instead of linking against it.
* This technique saves a couple of bytes in flash memory.
*/

/* ------------------- Fine Control over USB Descriptors ------------------- */
/* If you don't want to use the driver's default USB descriptors, you can
* provide our own. These can be provided as (1) fixed length static data in
* flash memory, (2) fixed length static data in RAM or (3) dynamically at
* runtime in the function usbFunctionDescriptor(). See usbdrv.h for more
* information about this function.
* Descriptor handling is configured through the descriptor's properties. If
* no properties are defined or if they are 0, the default descriptor is used.
* Possible properties are:
* + USB_PROP_IS_DYNAMIC: The data for the descriptor should be fetched
* at runtime via usbFunctionDescriptor(). If the usbMsgPtr mechanism is
* used, the data is in FLASH by default. Add property USB_PROP_IS_RAM if
* you want RAM pointers.
* + USB_PROP_IS_RAM: The data returned by usbFunctionDescriptor() or found
* in static memory is in RAM, not in flash memory.
* + USB_PROP_LENGTH(len): If the data is in static memory (RAM or flash),
* the driver must know the descriptor's length. The descriptor itself is
* found at the address of a well known identifier (see below).
* List of static descriptor names (must be declared PROGMEM if in flash):
* char usbDescriptorDevice[];
* char usbDescriptorConfiguration[];
* char usbDescriptorHidReport[];
* char usbDescriptorString0[];
* int usbDescriptorStringVendor[];
* int usbDescriptorStringDevice[];
* int usbDescriptorStringSerialNumber[];
* Other descriptors can't be provided statically, they must be provided
* dynamically at runtime.
*
* Descriptor properties are or-ed or added together, e.g.:
* #define USB_CFG_DESCR_PROPS_DEVICE (USB_PROP_IS_RAM | USB_PROP_LENGTH(18))
*
* The following descriptors are defined:
* USB_CFG_DESCR_PROPS_DEVICE
* USB_CFG_DESCR_PROPS_CONFIGURATION
* USB_CFG_DESCR_PROPS_STRINGS
* USB_CFG_DESCR_PROPS_STRING_0
* USB_CFG_DESCR_PROPS_STRING_VENDOR
* USB_CFG_DESCR_PROPS_STRING_PRODUCT
* USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER
* USB_CFG_DESCR_PROPS_HID
* USB_CFG_DESCR_PROPS_HID_REPORT
* USB_CFG_DESCR_PROPS_UNKNOWN (for all descriptors not handled by the driver)
*
* Note about string descriptors: String descriptors are not just strings, they
* are Unicode strings prefixed with a 2 byte header. Example:
* int serialNumberDescriptor[] = {
* USB_STRING_DESCRIPTOR_HEADER(6),
* 'S', 'e', 'r', 'i', 'a', 'l'
* };
*/

#define USB_CFG_DESCR_PROPS_DEVICE 0
#define USB_CFG_DESCR_PROPS_CONFIGURATION 0
#define USB_CFG_DESCR_PROPS_STRINGS 0
#define USB_CFG_DESCR_PROPS_STRING_0 0
#define USB_CFG_DESCR_PROPS_STRING_VENDOR 0
#define USB_CFG_DESCR_PROPS_STRING_PRODUCT 0
#define USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER 0
#define USB_CFG_DESCR_PROPS_HID 0
#define USB_CFG_DESCR_PROPS_HID_REPORT 0
#define USB_CFG_DESCR_PROPS_UNKNOWN 0


#define usbMsgPtr_t unsigned short
/* If usbMsgPtr_t is not defined, it defaults to 'uchar *'. We define it to
* a scalar type here because gcc generates slightly shorter code for scalar
* arithmetics than for pointer arithmetics. Remove this define for backward
* type compatibility or define it to an 8 bit type if you use data in RAM only
* and all RAM is below 256 bytes (tiny memory model in IAR CC).
*/

/* ----------------------- Optional MCU Description ------------------------ */

/* The following configurations have working defaults in usbdrv.h. You
* usually don't need to set them explicitly. Only if you want to run
* the driver on a device which is not yet supported or with a compiler
* which is not fully supported (such as IAR C) or if you use a differnt
* interrupt than INT0, you may have to define some of these.
*/
/* #define USB_INTR_CFG MCUCR */
/* #define USB_INTR_CFG_SET ((1 << ISC00) | (1 << ISC01)) */
/* #define USB_INTR_CFG_CLR 0 */
/* #define USB_INTR_ENABLE GIMSK */
/* #define USB_INTR_ENABLE_BIT INT0 */
/* #define USB_INTR_PENDING GIFR */
/* #define USB_INTR_PENDING_BIT INTF0 */
/* #define USB_INTR_VECTOR INT0_vect */

#endif /* __usbconfig_h_included__ */[/syntax]

Po poprawnym wgraniu podaczam sie do portu USB w swoim laptopie. Otrzymuje niestety taki wynik w dmesg:
[ 4137.610467] usb 3-1: new low-speed USB device number 3 using xhci_hcd
[ 4137.730530] usb 3-1: device descriptor read/64, error -71
[ 4137.958523] usb 3-1: device descriptor read/64, error -71
[ 4138.186535] usb 3-1: new low-speed USB device number 4 using xhci_hcd
[ 4138.306564] usb 3-1: device descriptor read/64, error -71
[ 4138.534613] usb 3-1: device descriptor read/64, error -71
[ 4138.762559] usb 3-1: new low-speed USB device number 5 using xhci_hcd
[ 4138.763103] usb 3-1: Device not responding to setup address.
[ 4138.971147] usb 3-1: Device not responding to setup address.
[ 4139.178661] usb 3-1: device not accepting address 5, error -71
[ 4139.298650] usb 3-1: new low-speed USB device number 6 using xhci_hcd
[ 4139.299190] usb 3-1: Device not responding to setup address.
[ 4139.507196] usb 3-1: Device not responding to setup address.
[ 4139.714658] usb 3-1: device not accepting address 6, error -71
[ 4139.714707] usb usb3-port1: unable to enumerate USB device
[ 4140.430730] usb 3-1: new low-speed USB device number 7 using xhci_hcd
[ 4140.550777] usb 3-1: device descriptor read/64, error -71
[ 4140.778791] usb 3-1: device descriptor read/64, error -71
[ 4141.006811] usb 3-1: new low-speed USB device number 8 using xhci_hcd
[ 4141.126845] usb 3-1: device descriptor read/64, error -71
[ 4141.354859] usb 3-1: device descriptor read/64, error -71

Komenda lsusb nie pokazuje, aby podlaczono nowe urzadzenie.

Nie mam najmniejszego pojecia co zrobic, aby wszystko dzialalo jak nalezy.
Co zrobilem do tej pory:
- wgranie programu do swiecenia dioda, aby sprawdzic, czy fusy sa ok oraz same podlaczenie, to dziala
- wymiana kwarcu na 16 Mhz
- zmiana rezystora 1,5K om na mniejsze inne wartosci
- dołożenie kondensatorow 100 nF, 10 nF, 10 uF przy linii zasilajacej, tzn przy "+" oraz "-" z USB
- zasilanie ukladu z programatora i uwzglednienie tego w usbconfig.h
- zasilenie 3v3 i wyrzucenie zenera
- wgrywanie gotowych projektow z vusb, zeby wykluczyc moje bledy
- kombinacje z wszystkim powyzszym

Odpalilem rowniez inny system z live cd, ten sam efekt, czyli dmesg wywala blad, a lsusb nic nie pokazuje. Kolejna proba bylo podlaczenie urzadzenia do kompa, ktory jest sprzed dobrych dziesieciu lat, na ktorym smiga debian net install (czyli absolutne minimum, ktore je 8 MB ramu) i oto co uzyskalem:
Obrazek

I to jest najlepsze, ze po wielu dniach walki z vusb, okazalo sie ze wszystko dziala :D
Laptop, na ktorym vusb nie dziala posiada dwa porty USB 3.0 i jeden USB 2.0, na kazdym ten sam efekt,
Komputer na ktorym dzialalo ma wylacznie porty USB 2.0
Dystrybucje obu jednostek roznia sie wylacznie tym, ze laptop ma pelna wersje debiana, a komputer net install.
Teraz mam dwa pytania.
Jak zyc, zeby wszystko dzialalo na moim laptopie?
Czy ktos uzywal vusb z portem USB 3.0 (ale osobiscie uzywal, a nie kolega kolegi lub pan na forum kupil u chinczyka...)
I chce uniknac sprzetowego usb, poki co...

Dziekuje za udzielona mi pomoc :)
I wszystkim rzycze wesołych świat :)

Statystyki: Napisane przez mozerpol — 26 gru 2017, o 21:52

]]>