Code: Select all
struct _qtd_head * head = _create_qtd_head(-1 , device , 0);
head->qtd.next_qtd = setup_qtd;
Code: Select all
*_USBCMD |= ASYNC_ENABLE | ASYNC_ADV_DOORBELL_ENABLEThe _next pointer of the incoming qtd is a valid qtd pointer. The page buffer pointer is also appears to be a valid adress, so the worst that will be in there is zero's. The incoming qtd is not the last one, it's next is also set.Jonatan44 wrote:Hi,
it seems that the async's set the reclamation bit in USBSTS, but if you still get an timeout check the following:
1)is the "_next" pointer to the incoming qtd valid? is the qtd pointer to the page buffer valid?
2)is the incoming qtd is the last one? if so, doest it's "_next" points to "0x01"?
if non of the above I would like you to print the memory footprints (hex will do the job) of the qtd tokens (io/setup and handshakes) and there pages before and after interrupt handling, also the queue head.
First I should note that I am not actually receiving a parity error, that was a mistake on my part. The PCI status register shows nothing out of the ordinary.Jonatan44 wrote:if you have a usb bus tracer it would be really helpful in this situation.
Can you tell more about you hardware configuration? what is your device speed? what is the setup request you wish to perform (SET_ADDR,GET_CONF,..) and if there is a hub in the middle?
Code: Select all
OUT QTD: CD7FFC40
Next QTD: 1
Alternate QTD: 1
QTD Token 8880
You are right about the toggle bit, and that is now set. This hasn't changed my current situation.Jonatan44 wrote:is an handshak token - 1000100010000000 means:Code: Select all
OUT QTD: CD7FFC40 Next QTD: 1 Alternate QTD: 1 QTD Token 8880
status 0x80 (token not handled yet), out packet, cerr = 3, length = 4, toggle bit off
as i recall the toggle bit should be set, and the legnth in a handshak packet should be zero.
your right,my mistake.But if I understand the specification correctly, length is set in the 16th -> 30th bit, and the 15th bit being set indicates that I want an interrupt on completion. I could be reading it wrong or have an incorrect version.
Here's my current QTD Head Struct:Jonatan44 wrote:Hi.your right,my mistake.But if I understand the specification correctly, length is set in the 16th -> 30th bit, and the 15th bit being set indicates that I want an interrupt on completion. I could be reading it wrong or have an incorrect version.
except the toggle bit issue, you QTDs looks fine, could you post here you queue head memory structure?
Code: Select all
struct _qtd_head
{
uint32_t qhlp;
uint32_t device_address: 7;
uint32_t inactive: 1;
uint32_t endpoint: 4;
uint32_t endpoint_speed: 2;
#define EPS_HIGH_SPEED 0x02
uint32_t data_toggle: 1;
uint32_t H: 1;
uint32_t max_packet_length: 11;
uint32_t control_edndpoint_flag: 1;
uint32_t nak_count_reload: 4;
uint8_t interrupt_schedule_mask;
uint8_t split_completion_mask;
uint16_t hub_address: 7;
uint16_t port_number: 7;
uint16_t mult: 2;
uint32_t curr_qtd;
struct _qtd qtd;
} __attribute__((packed));