Host Ack on Bulk IN not sent

[bflorac]

I'm writing a custom host bulk transfer support for a device using usbh_app_driver_get_cb() on a Pico as the host. Get it to connect but when an IN is sent and the device sends data, I get no callback to my app nor is an ACK is sent to the device. I can see this using a USB analyzer. Is this a endpoint config issue? I know the control endpoints work as I can query the device, getting its PID/VID and endpoints (which I used to set up my bulk endpoints).

FYI - I borrowed a lot of my of my code from the cdc_host example, including the setup and use of streams.

All the control endpoint messages work fine. I'm only having issues with creating a BULK endpoint pair.

I have a class_driver (usbh_class_driver_t) set up with the name and the 6 functions filled in
I set up my app to have a usbh_app_driver_get_cb() function.
This gets called and I return a pointer to my class driver.
.init gets called and I create a stream for each direction:

  tu_edpt_stream_init(&sek_inf.stream.tx, true, true, false,
                      sek_inf.stream.tx_ff_buf, CFG_TUH_SEK_TX_BUFSIZE,
                      sek_epbuf.tx, CFG_TUH_SEK_TX_EPSIZE);

  tu_edpt_stream_init(&sek_inf.stream.rx, true, false, false,
                      sek_inf.stream.rx_ff_buf, CFG_TUH_SEK_RX_BUFSIZE,
                      sek_epbuf.rx, CFG_TUH_SEK_RX_EPSIZE);

.open gets called and I open the end point and connect the streams:

   tusb_desc_endpoint_t const * desc_ep = (tusb_desc_endpoint_t const *) tu_desc_next(itf_desc);
   for (size_t i = 0; i < 2; i++) {
        tuh_edpt_open(daddr, desc_ep);
        if (tu_edpt_dir(desc_ep->bEndpointAddress) == TUSB_DIR_IN) {
          tu_edpt_stream_open(&sek_inf.stream.rx, desc_ep);
        } else {
          tu_edpt_stream_open(&sek_inf.stream.tx, desc_ep);
        }
        desc_ep = (tusb_desc_endpoint_t const*) tu_desc_next(desc_ep);
      }

.set_config gets called and I set the stream to read:
tu_edpt_stream_read_xfer(daddr, &sek_inf.stream.rx);

I send data to the device to request some info:
tu_edpt_stream_write(sek_inf.daddr, &sek_inf.stream.tx, buffer, bufsize);

then flush the stream:
return tu_edpt_stream_write_xfer(sek_inf.daddr, &sek_inf.stream.tx);

I then can see the data on a USB analyzer begin sent. This seems to always be followed up by a SOF in which the devices replays IN-NAK because it has not process the request for data. From that point on, the host send IN which the device send the requested data but the host does not ACK so the device sends again and this repeats over and over.

[bflorac]

More data: The Pico seems to think it has a PID error (expected Data0 but got Data1 or visa versa). By design, it is supposed to ignore these. But, then it gets in a loop where it retries on every USB time slice. Each time the device sends the same data, which is again ignored by the Pico and this continues on forever.

1. Looking at the packets with an analyzer, the first packet on that pipe from the device is DATA1 which seems to be correct.
2. There is an IRQ set up to trap these but it does not seem to be triggered. Perhaps this is some problem with USB controller?
3. I can kind of fake things to get this to work by forcing the "next_pid" in the controller so I thought I could try to disconnect and reconnect but it seems they code to do that has not been implemented yet.