Search results

  1. R

    HardwareSerial read() suggestion for large reads

    I was experimenting with the Teensy4 implementation of the HardwareSerial read ring buffer. So I noticed that there was a primary buffer that is always used, and an additional buffer, which size is set using addMemoryForRead. As for the rest of the implementation, it does no seems to change...
  2. R

    extending the framework available USB interfaces with a vendor (bulk endpoints) interface

    yes. This is a simple sketch that fetches 8 samples from precomputed sin tables (ADC 16 bit emulation), with arbitrary sample offset between channels, wrap ups 7 consecutive chunks of these 8 samples in a buffer and appends a 64 bit timestamp representing teensy 4.1 CPU cycles, with room for two...
  3. R

    extending the framework available USB interfaces with a vendor (bulk endpoints) interface

    It works now, basically my original post had some errors. The interface is now as follows, I had swapped VENDOR_TX_ENDPOINT and VENDOR_RX_ENDPOINT #ifdef VENDOR_INTERFACE // configuration for 480 Mbit/sec speed // interface descriptor, USB spec 9.6.5, page 267-269, Table 9-12...
  4. R

    extending the framework available USB interfaces with a vendor (bulk endpoints) interface

    Thanks Paul, Please disregard my latest post, i figured why the need for txdata and tx_head buffering, as the transfers are scheduled, and not guaranteed to happen synchronously. I am now testing with 512 byte max packet size and a TX_SIZE of the same size or less. I figured out that ZLP packets...
  5. R

    extending the framework available USB interfaces with a vendor (bulk endpoints) interface

    Indeed, Paul. I successfully used 512 bytes RX maxPacketSize on the Arduino Due, although my transfers are fixed size 96 bytes, and i would prefer 96 bytes packets only on the bus. That seems to be a "short packet" in USB parlance. Looking at the usb_vendor_send transfer mechanism, it seems that...
  6. R

    extending the framework available USB interfaces with a vendor (bulk endpoints) interface

    Hi, I started recently to port an Arduino Due based bulk USB interface to TeensyDuino for Teensy 4.1 The main difference seems that Arduino supported the PluggableUSB class that allows to extend the USB device with interfaces and endpoints and its associated required functions for enumerations...
  7. R

    ENET timer and PIT timer relationship

    Hello, I am currently learning about the Teensy 4.1 ptp IEEE1588 features. Specifically, the timer correction feature that allows to discipline a timer to PTP by using timer correction For instance, there is this library based on Paul Stoffregen's work : https://github.com/HedgeHawk/QNEthernet...
Back
Top