SAME70 Simple Vendor Device Issues #1138

spembo · 2021-10-13T09:32:04Z

spembo
Oct 13, 2021

Trying to set up simple vendor device with single bulk in/out endpoint
An STM32 has been successfully communicating with a usb PC application for over 10 years, now changing to SAME70 with tinyusb.

Have got the CDC echo example working without any problems, so hardware ok.

All GET/SET descriptor and string transactions work correctly, however when I start to receive bulk in/out transactions from the PC application, the problems start.

I have included code below, application waits for a received bulk out message, then replies with bulk in.

If I set TUD_VENDOR_DESCRIPTOR() macro with endpoints in the correct order:
#define IFACE_OUT_EP 0x01
#define IFACE_IN_EP 0x81
TUD_VENDOR_DESCRIPTOR(IFACE_0, 0, IFACE_OUT_EP, IFACE_IN_EP, FS_MAX_PACKET_SIZE),
then tud_vendor_available() always returns false, and I cannot send or receive data.

If I set TUD_VENDOR_DESCRIPTOR() macro with endpoints switched (as per the previous STM32 descriptor):
TUD_VENDOR_DESCRIPTOR(IFACE_0, 0, IFACE_IN_EP, IFACE_OUT_EP, FS_MAX_PACKET_SIZE),
then I can receive the first bulk out properly and attempt to send a reply.
I can see that dcd_transmit_packet() is called and the correct data is loaded, but nothing comes out of the board when viewed with wireshark.

Any ideas as to where to start looking for the problem?
The relevant code is below:

/* usb_decriptors.c ***********************************************************/
//--------------------------------------------------------------------+
// Device Descriptors
//--------------------------------------------------------------------+
#define USB_VID   		0x0483
#define USB_PID           	0xA3A8
#define USB_BCD   	0x0200 //0x0110


tusb_desc_device_t const desc_device =
{
  .bLength            = sizeof(tusb_desc_device_t),
  .bDescriptorType    = TUSB_DESC_DEVICE,
  .bcdUSB             = USB_BCD,
  .bDeviceClass       = TUSB_CLASS_UNSPECIFIED, /* specified at interface level */
  .bDeviceSubClass    = TUSB_CLASS_UNSPECIFIED, /* specified at interface level */
  .bDeviceProtocol    = TUSB_CLASS_UNSPECIFIED, /* specified at interface level */
  .bMaxPacketSize0    = CFG_TUD_ENDPOINT0_SIZE,
  .idVendor           = USB_VID,
  .idProduct          = USB_PID,
  .bcdDevice          = 0x0300, //0x0110,
  .iManufacturer      = 0x01,
  .iProduct           = 0x02,
  .iSerialNumber      = 0x03,
  .bNumConfigurations = 0x01
};

// Invoked when received GET DEVICE DESCRIPTOR
// Application return pointer to descriptor
uint8_t const * tud_descriptor_device_cb(void)
{
  return (uint8_t const *) &desc_device;
}

//--------------------------------------------------------------------+
// Configuration Descriptor
//--------------------------------------------------------------------+
#define CONFIG_TOTAL_LEN    (TUD_CONFIG_DESC_LEN + TUD_VENDOR_DESC_LEN) // 9+9+7+7 = 32

#define NUM_IFACES          	1
#define IFACE_0             	0
#define IFACE_OUT_EP        	0x01
#define IFACE_IN_EP         	0x81

#define FS_MAX_PACKET_SIZE      64
#define HS_MAX_PACKET_SIZE      512


uint8_t const desc_fs_configuration[] =
{
    // Config number, interface count, string index, total length, attribute, power in mA
    TUD_CONFIG_DESCRIPTOR(1, NUM_IFACES, 0, CONFIG_TOTAL_LEN, 0, 0),

    // Interface number, string index, EP notification address and size, EP data address (out, in) and size.
    TUD_VENDOR_DESCRIPTOR(IFACE_0, 0, IFACE_IN_EP, IFACE_OUT_EP, FS_MAX_PACKET_SIZE),
};


#if TUD_OPT_HIGH_SPEED
uint8_t const desc_hs_configuration[] =
{
    TUD_CONFIG_DESCRIPTOR(1, NUM_IFACES, 0, CONFIG_TOTAL_LEN, 0, 0),
    TUD_VENDOR_DESCRIPTOR(IFACE_0, 0, IFACE_IN_EP, IFACE_OUT_EP, HS_MAX_PACKET_SIZE),
};




/* tusb_config.h **************************************************************/

//--------------------------------------------------------------------
// COMMON CONFIGURATION
//--------------------------------------------------------------------
#define CFG_TUSB_MCU  (OPT_MCU_SAMX7X)


// RHPort number used for device can be defined by board.mk, default to port 0
#ifndef BOARD_DEVICE_RHPORT_NUM
  #define BOARD_DEVICE_RHPORT_NUM     0
#endif

// RHPort max operational speed can defined by board.mk
// Default to Highspeed for MCU with internal HighSpeed PHY (can be port specific), otherwise FullSpeed
#ifndef BOARD_DEVICE_RHPORT_SPEED
  #if (CFG_TUSB_MCU == OPT_MCU_SAMX7X)
    #define BOARD_DEVICE_RHPORT_SPEED   OPT_MODE_HIGH_SPEED
  #else
    #define BOARD_DEVICE_RHPORT_SPEED   OPT_MODE_FULL_SPEED
  #endif
#endif

// Device mode with rhport and speed defined by board.mk
#if   BOARD_DEVICE_RHPORT_NUM == 0
  #define CFG_TUSB_RHPORT0_MODE     (OPT_MODE_DEVICE | BOARD_DEVICE_RHPORT_SPEED)
#elif BOARD_DEVICE_RHPORT_NUM == 1
  #define CFG_TUSB_RHPORT1_MODE     (OPT_MODE_DEVICE | BOARD_DEVICE_RHPORT_SPEED)
#else
  #error "Incorrect RHPort configuration"
#endif

// This example doesn't use an RTOS
#ifndef CFG_TUSB_OS
#define CFG_TUSB_OS               OPT_OS_NONE
#endif

// CFG_TUSB_DEBUG is defined by compiler in DEBUG build
// #define CFG_TUSB_DEBUG           0

/* USB DMA on some MCUs can only access a specific SRAM region with restriction on alignment.
 * Tinyusb use follows macros to declare transferring memory so that they can be put
 * into those specific section.
 * e.g
 * - CFG_TUSB_MEM SECTION : __attribute__ (( section(".usb_ram") ))
 * - CFG_TUSB_MEM_ALIGN   : __attribute__ ((aligned(4)))
 */
#ifndef CFG_TUSB_MEM_SECTION
#define CFG_TUSB_MEM_SECTION
#endif

#ifndef CFG_TUSB_MEM_ALIGN
#define CFG_TUSB_MEM_ALIGN          __attribute__ ((aligned(4)))
#endif

//--------------------------------------------------------------------
// DEVICE CONFIGURATION
//--------------------------------------------------------------------

#ifndef CFG_TUD_ENDPOINT0_SIZE
#define CFG_TUD_ENDPOINT0_SIZE    64
#endif

//------------- CLASS -------------//
#define CFG_TUD_CDC              0
#define CFG_TUD_MSC              0
#define CFG_TUD_HID              0
#define CFG_TUD_MIDI             0
#define CFG_TUD_VENDOR           1

// VENDOR FIFO size of TX and RX
#define CFG_TUD_VENDOR_RX_BUFSIZE   (TUD_OPT_HIGH_SPEED ? 512 : 64)
#define CFG_TUD_VENDOR_TX_BUFSIZE   (TUD_OPT_HIGH_SPEED ? 512 : 64)

// VENDOR Endpoint transfer buffer size, more is faster
#define CFG_TUD_VENDOR_EP_BUFSIZE   (TUD_OPT_HIGH_SPEED ? 512 : 64)


/* main.c *********************************************************************/

/* application code - will parse data and send back a reply */
void usb_rx_task(void)
{
    if( tud_vendor_available() )
    {
	nbytes = tud_vendor_read(&rx_buf, sizeof(rx_buf));
	if( nbytes )
	{
	    usb_msg_rx_handle_msg(&usbMsgMngr, buf, &nbytes);
	}
    }
}


void usb_tx_task(void)
{
    if( tx_buffer_has_data(&usbTx) )
    {
        if( tud_vendor_write_available() )
        {
            size_t size = 0;
            uint8_t * buf = tx_buffer_read(&usbTx, &size);
            if ( buf && size )
            {
                tud_vendor_write(buf, size);
            }
        }
    }
}

Answered by HiFiPhile

Oct 13, 2021

You need to use different EP for IN and OUT transfer due to SAME70 limitation, like in CDC example:

tinyusb/examples/device/cdc_dual_ports/src/usb_descriptors.c

Line 101 in 9da234c

     // SAMG & SAME70 don't support a same endpoint number with different direction IN and OUT  

 

View full answer

HiFiPhile · 2021-10-13T09:35:38Z

HiFiPhile
Oct 13, 2021
Collaborator

You need to use different EP for IN and OUT transfer due to SAME70 limitation, like in CDC example:

tinyusb/examples/device/cdc_dual_ports/src/usb_descriptors.c

Line 101 in 9da234c

    
           // SAMG & SAME70 don't support a same endpoint number with different direction IN and OUT

1 reply

spembo Oct 13, 2021
Author

Thank you so much, that has solved it!!!
Would have taken me quite a while to find that in the datasheet!

spembo · 2021-10-13T09:38:21Z

spembo
Oct 13, 2021
Author

In addition I've enabled the USB debugging feature. Messages starting with ### are ones I've added.
I've included to first 8 bytes of messages im receiving and transmitting to ensure data is getting to the various functions correctly.

I receive a bulk msg starting with 22, and reply with a message starting with 21.
### RX: 22 00 28 00 00 00 00 00
### tx: 21 00 28 00 00 00 00 80

The tx: 21 message seems to get all the way to dcd_transmit_packet() correctly, but nothing is actually transmitted according to wireshark.

After that although bulk out/in messages are seen on the bus, tinyusb does not receive anything.
Im starting to think this is a hardware issue in the dcd code, but as the cdc echo example works im not so sure.

### START ###
USBD init
VENDOR init
USBD Bus Reset : High Speed

USBD Setup Received 80 06 00 01 00 00 40 00 
  Get Descriptor Device
  Queue EP 80 with 18 bytes ...
### dcd_edpt_xfer() ep: 0, dir: 1, bytes: 180, d

USBD Setup Received 00 09 01 00 00 00 00 00 
  Set Configuration
  Open EP 81 with Size = 512
  Open EP 01 with Size = 512
  Queue EP 01 with 64 bytes ...
### dcd_edpt_xfer() ep: 1, dir: 0, bytes: 64 = 00 00 00 00 00 00 00 00
  VENDOR opened
  Bind EP 81 to driver id 0
  Bind EP 01 to driver id 0
  Queue EP 80 with 0 bytes ...
### dcd_edpt_xfer() ep: 0, dir: 1, bytes: 0 = 60 6B 40 20 95 13 40 00
### dcd_edpt_xfer() --> dcd_transmit_packet()
### dcd_transmit_packet(), bytes: 0 = 60 6B 40 20 95 13 40 00
USBD Xfer Complete on EP 80 with 0 bytes

USBD Setup Received 00 09 01 00 00 00 00 00 
  Set Configuration
  Queue EP 80 with 0 bytes ...
### dcd_edpt_xfer() ep: 0, dir: 1, bytes: 0 = 60 6B 40 20 95 13 40 00
### dcd_edpt_xfer() --> dcd_transmit_packet()
### dcd_transmit_packet(), bytes: 0 = 60 6B 40 20 95 13 40 00
USBD Xfer Complete on EP 80 with 0 bytes
USBD Xfer Complete on EP 01 with 40 bytes
  VENDOR xfer callback
  Queue EP 01 with 64 bytes ...
### dcd_edpt_xfer() ep: 1, dir: 0, bytes: 64 = 22 00 28 00 00 00 00 00
### RX: 22 00 28 00 00 00 00 00
### tx: 21 00 28 00 00 00 00 80
  Queue EP 81 with 40 bytes ...
### dcd_edpt_xfer() ep: 1, dir: 1, bytes: 40 = 21 00 28 00 00 00 00 80
### dcd_edpt_xfer() --> dcd_transmit_packet()
### dcd_transmit_packet(), bytes: 40 = 21 00 28 00 00 00 00 80
###             tx cmnd
USBD Xfer Complete on EP 81 with 40 bytes
  VENDOR xfer callback

USBD Setup Received 00 09 01 00 00 00 00 00 
  Set Configuration
  Queue EP 80 with 0 bytes ...
### dcd_edpt_xfer() ep: 0, dir: 1, bytes: 0 = 60 6B 40 20 95 13 40 00
### dcd_edpt_xfer() --> dcd_transmit_packet()
### dcd_transmit_packet(), bytes: 0 = 60 6B 40 20 95 13 40 00
USBD Xfer Complete on EP 80 with 0 bytes

USBD Setup Received 00 09 01 00 00 00 00 00 
  Set Configuration
  Queue EP 80 with 0 bytes ...
### dcd_edpt_xfer() ep: 0, dir: 1, bytes: 0 = 60 6B 40 20 95 13 40 00
### dcd_edpt_xfer() --> dcd_transmit_packet()
### dcd_transmit_packet(), bytes: 0 = 60 6B 40 20 95 13 40 00
USBD Xfer Complete on EP 80 with 0 bytes
USBD Suspend : Remote Wakeup = 0

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SAME70 Simple Vendor Device Issues #1138

{{title}}

Replies: 2 comments 1 reply

{{title}}

{{title}}

{{title}}

Select a reply

SAME70 Simple Vendor Device Issues #1138

spembo Oct 13, 2021

Replies: 2 comments · 1 reply

HiFiPhile Oct 13, 2021 Collaborator

spembo Oct 13, 2021 Author

spembo Oct 13, 2021 Author

spembo
Oct 13, 2021

Replies: 2 comments 1 reply

HiFiPhile
Oct 13, 2021
Collaborator

spembo Oct 13, 2021
Author

spembo
Oct 13, 2021
Author