tinyusb.git/src/portable/microchip, branch 0.15.0Unnamed repository; edit this file 'description' to name the repository.http://cgit.235523.xyz/tinyusb.git/atom/src/portable/microchip?h=0.15.02022-12-04T12:43:23ZFix typos2022-12-04T12:43:23ZBastien Nocerahadess@hadess.net2022-12-04T06:58:47Zurn:sha1:6a2cf6728906aa61b44ecfe43b4ceef287b29bf8Merge pull request #1523 from maddyaby/dcd_edpt_open2022-10-19T15:56:36ZHa Thachthach@tinyusb.org2022-10-19T15:56:36Zurn:sha1:2cd4e27e98aff18076863964062c6fd2f59c89f6
Allow more endpoint packet sizes for SAMDMicrochip PIC24/dsPIC33 device mode support2022-10-05T19:45:51ZReimuNotMoe34613827+ReimuNotMoe@users.noreply.github.com2022-10-05T19:45:51Zurn:sha1:8096afc6dea975e95e0b50dc4b55926236b90b62Initial PIC32MM/MX & PIC24 support2022-09-02T21:19:50ZReimuNotMoe34613827+ReimuNotMoe@users.noreply.github.com2022-09-02T21:18:29Zurn:sha1:c5992edc7de6f54d5fdab801c46e964bc0f18542samd: Fix a lock-up situation at high traffic.2022-06-27T18:31:44Zrobert-hhrobert@hammelrath.com2022-06-27T18:31:44Zurn:sha1:bc4da2047bf73f81cfcd6daa9bd07901dcdff3c9
This PR fixes a transmit lock-up, which happens, when data is received
and sent at the sime time at moderate to high speeds, like code
which just echoes incoming data.
In my case, an issue was reported here:
https://github.com/micropython/micropython/issues/8521
Allow more endpoint packet sizes for SAMD2022-06-17T23:07:32Zmaddyaby32046405+maddyaby@users.noreply.github.com2022-06-17T23:07:32Zurn:sha1:2cc2a90215f94692f18e0a402470c58366bfca47
Tested on SAMD51 - we can allow more packet sizes by checking that the set size value is greater than the requested packet size instead of exactly the same.
Stub out dcd_edpt_close for samd2022-06-16T23:57:20Zmaddyaby32046405+maddyaby@users.noreply.github.com2022-06-16T23:57:20Zurn:sha1:05fc2fa7a64c32aa748c8c0f1fe119f417fed074
Not having this prevents the device from finishing the mounting process.
Tested on a SAMD51 and didn't seem to need to actually do anything in the close function.
Merge pull request #1381 from hathach/add-sof-isr2022-05-31T15:25:14ZHa Thachthach@tinyusb.org2022-05-31T15:25:14Zurn:sha1:fdeac8508be5cdd95966422d1e776604efbc9b3f
Add SOF IRQ Handler dcd_pic32: Fix memory overwrite in incoming data2022-05-01T12:26:24ZJerzy Kasenbergjerzy.kasenberg@gmail.com2022-05-01T12:18:53Zurn:sha1:e49cad84e2798ddd4ee49d3684ce7b414d30ccb2
When transfer was finished rx_fifo_read() read all that
was to read RXPKTRDY was cleared allowing next packet to
be received.
Then xfer_complete was called.
Interrupt for OUT endpoint was left enable, that would not
be a problem if data was handled fast and new transfer was
scheduled.
For MSC when host sends a lot of data this interrupt that was
enabled could cause epn_handle_rx_int() to be called after
transfer was completed and next was not scheduled yet.
Without TU_ASSERT that was added to detect this, incoming
data was written past buffer provided by user code resulting
in random memory corruption.
This just blocks RX interrupt when transfer is finished,
and also only unmasked rx interrupts are handled.
dcd_pic32: Add asserts transfer sanity check2022-05-01T12:14:42ZJerzy Kasenbergjerzy.kasenberg@gmail.com2022-05-01T12:14:42Zurn:sha1:c145777e0eb6b9add414504dd8cf4ec7da6cc61a
TU_ASSERTS added to detect transfer inconsistency.