t0mac0 / 16fusb Goto Github PK

I realized that some ports aren't recognizing the device in enumeration 
process. Using a oscilloscope i saw that timing between host's requests were 
much faster than other ports. However, this faster interval timing still 
correctly according to USB specification.

What steps will reproduce the problem?
1. Use standart firmware 16USB-dio-1.2.hex . "ProcessOut" procedure is empty. 
Even more, you can commented ;call VendorRequest in usb.asm;
2. On host side, create new function:
int writeByteArray(int byteToSend, char buffer[]) {
    return usb_control_msg(
                h16FUsb,
                0x40,
                0x01,
                0x0001,
                byteToSend,             
                buffer,
                8,
                1000
            );
}
3. Send random data with help writeByteArray(1,randombuffer) many times. My 
data is control messages to YM2149f chip, but its not important

What is the expected output? What do you see instead?
After several successful packages PIC halted (or looped, or stoped) and don't 
send anymore ACK to host, don't anymore accept control frames.

What version of the product are you using? On what operating system?
I am using PIC16F628A, default firmware 16USB-dio-1.2.hex without modification. 
PIC clocked from external clock generator 24 Mhz.

Please provide any additional information below.
So i am install USBPcap sniffer and create .pcap file that can be viewed using 
Wireshark. PIC is out control after 5480 frame. .pcap file in attachment

What steps will reproduce the problem?
1. gpasm -c usb.asm # -c param to produce object file
2. Compiler outputs " Segment fault (core dump)" error
3.

What is the expected output? What do you see instead?
expected corect usb.o 

What version of the product are you using? On what operating system?
16Fusb.dio.hid.1.2 under ubuntu linux 12.04 LTS

Please provide any additional information below.

Project structure must be changed to make core and functionalities code more 
decoupled.
The new structure must enable many functionalities to use the same core 
objects, in a separated folder. Each functionality should have its own MPLAB 
project and/or its own Makefile for GNU Make.