281e8cd9ec
rename OPT_MCU_RT10XX to OPT_MCU_IMXRT10XX
2019-11-22 15:42:46 +07:00
ca741dfc2a
Merge pull request #220 from hathach/develop
...
Port NXP iMX RT10XX
2019-11-22 15:16:41 +07:00
6123b600fc
rename dcd_lpc18_43 to dcd_transdimension
2019-11-22 14:47:07 +07:00
a0b2561a2d
move nxp dcd ehci controller reset and modde into dcd
...
rt1064 work with cdc msc example
2019-11-22 14:20:10 +07:00
fca4653b95
able to compile dcd 18/43 with rt1064
2019-11-22 12:34:41 +07:00
2ead26a12d
more clean up
2019-11-22 12:26:40 +07:00
ccb09db3b7
more clean up
2019-11-22 12:16:47 +07:00
7e16a9a1db
more constant rename clean up
2019-11-22 12:14:55 +07:00
8aacd1eacd
refactor dcd_lpc18_43, making it capatible with rt10xx
2019-11-22 12:11:13 +07:00
623b16af2e
clean up dcd lpc18_43
...
drop supporting both device mode on both ports.
2019-11-22 00:58:18 +07:00
1f52273d99
move dcd_lpc18_43.h into .c file
2019-11-22 00:38:22 +07:00
03deeea465
fix segger host example
2019-11-22 00:33:10 +07:00
f5d737aa7e
moving irq to bsp for lpc17/40
2019-11-21 23:19:38 +07:00
bbec47b647
adding tud_isr/tuh_isr with lpc18/43
2019-11-21 22:20:30 +07:00
043697ab95
rename lpc 17/18 irq to dcd_isr/hcd_isr
2019-11-21 16:08:08 +07:00
a9282eab51
eptri: clear proper endpoint when opening IN port
...
When opening a USB port, we ensure the buffer is NULL and has
a length of 0.
Due to a mistake in specifying the endpoint type, we never actually
cleared the value when opening an IN endpoint. This patch fixes
the comparison when opening an IN endpoint.
This fixes issue #218 .
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-20 17:45:21 +08:00
1aa3f085cb
adding support for NXP rt1064 evk board, boad test led + sw8 work.
...
LTO is temporary disabled
2019-11-20 15:30:39 +07:00
c2fb813658
Merge pull request #217 from xobs/valentyusb-eptri
...
WIP: Add Valentyusb eptri
2019-11-18 12:37:34 +07:00
56abce44f3
Merge pull request #208 from hathach/fix-issue-207
...
Fix issue 207
2019-11-14 10:10:42 +07:00
cc73990530
tusb: rename `foosn` to `valentyusb`
...
Use the name `valentyusb` as the vendor for the `valentyusb`
project, rather than the manufacturer name of the Fomu device.
This is because the `valentyusb` core can be used across multiple
vendors, much like how other cores can be used across chip vendors.
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:47 -08:00
8c5f02960b
valentyusb: rename from `foosn`
...
While Fomu is produced by Foosn, the actual name of the hardware
block is `valentyusb`. Rename the module to match that.
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:47 -08:00
e05e9801e4
fomu: gate debug/logging features
...
This gates the majority of the debug and logging features behind
testable macros.
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:47 -08:00
3292920933
fomu: first stable working commit
...
This appears to be stable, and works well.
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:47 -08:00
1882a87212
fomu: remove reference to SETUP_CTRL.ACK
...
THis bit isn't used anymore, so remove it.
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:47 -08:00
729c8d073c
fomu: dcd_fomu: add next_ev support
...
Now that we have the `USB_NEXT_EV` register, take advantage of
it to work around issue #207 .
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:09:38 -08:00
913032ae1d
dcd_fomu: nearly there
...
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:01 -08:00
835a72c595
fomu: semi-working dcd file
...
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:01 -08:00
843136d0e4
fomu: commit latest version
...
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:01 -08:00
22fd7bf85e
fomu: first fully-working release
...
This is able to transfer lots of data back and forth across MSC.
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:01 -08:00
4a8475b8a7
src: add eptri to tusb
...
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:01 -08:00
0559fd13fb
fomu: fix some issues with dcd_fomu
...
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:01 -08:00
359189ea2d
tusb_verify: add riscv assert support
...
This simply executes an "ebreak" instruction.
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:08:01 -08:00
32bb68409e
portable: fomu: get msc to enumerate
...
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:03:12 -08:00
36ede44885
fomu: wip support
...
Signed-off-by: Sean Cross <sean@xobs.io>
2019-11-13 09:03:12 -08:00
4008f0d1e6
update dcd nrf5x to be indepent from nrf_usbd.h
...
fix build error with nrfx 2.0
2019-11-11 00:01:12 +07:00
fc86a308f6
clean up
2019-11-05 11:45:02 +07:00
5209091c28
Merge branch 'master' into fix-issue-207
2019-11-05 10:20:30 +07:00
3c49ff153e
Merge pull request #149 from pigrew/ZLP_Request2
...
Zlp request2
2019-11-05 00:05:21 +07:00
8d0fa158d7
Change one more TU_ASSERT to TU_VERIFY in usbd.
2019-11-04 11:33:14 -05:00
2727983a2d
fix #211
2019-11-04 22:52:29 +07:00
a94fe05ecb
usbd: Change TU_ASSERT to TU_VERIFY as the assertion can be hit when bad data is sent from host.
2019-11-04 08:59:29 -05:00
c98acd3873
Use control transfer function to send control data (in usbtmc)
2019-11-04 08:54:18 -05:00
44ad683bd6
fix tud_control_status() didn't update request
2019-11-04 11:21:57 +07:00
62f8c14fae
add a bit of log1 for debugging
2019-11-03 14:08:38 +07:00
7bf01e218d
make control buf static
2019-11-03 11:43:07 +07:00
79fbc0b23c
wait for scsi status complete before queueing for next scsi command
...
fix #207
2019-11-01 18:43:18 +07:00
838173efc3
remove TEST_FAIL() from TU_ASSERT, since it prevents we testing how stack response with failed assert
2019-11-01 18:27:15 +07:00
d0d87d98f6
add assert to prevent div by zero
2019-11-01 18:03:43 +07:00
5b68cc91ad
adding TEST_FAIL() for TU_ASSERT()
2019-11-01 17:50:40 +07:00
164d0db825
Merge branch 'ZLP_Request2' into pigrew-ZLP_Request2
2019-11-01 10:16:59 +07:00
hathach