summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-11-23doc updatehathach
2019-11-23added rt1015 evk boardhathach
2019-11-23doc updatehathach
2019-11-23fix rt1010 rt1020 only has 1 usb controller, rt1050 rt1060 has 2hathach
2019-11-23added MIMX RT1052 Evaluation Kithathach
2019-11-22update doc for RT1060 evkhathach
2019-11-22rename OPT_MCU_IMXRT10XX to OPT_MCU_MIMXRT10XXhathach
2019-11-22added iMX RT1060 EVK board supporthathach
board_text, cdc_msc, hid_composite all work
2019-11-22rename OPT_MCU_RT10XX to OPT_MCU_IMXRT10XXhathach
2019-11-22doc updatehathach
2019-11-22Merge pull request #220 from hathach/developHa Thach
Port NXP iMX RT10XX
2019-11-22rename dcd lpc18_43 to transdimensionhathach
2019-11-22rename dcd_lpc18_43 to dcd_transdimensionhathach
2019-11-22move nxp dcd ehci controller reset and modde into dcdhathach
rt1064 work with cdc msc example
2019-11-22config clean uphathach
2019-11-22clean uphathach
2019-11-22able to compile dcd 18/43 with rt1064hathach
2019-11-22more clean uphathach
2019-11-22more clean uphathach
2019-11-22more constant rename clean uphathach
2019-11-22refactor dcd_lpc18_43, making it capatible with rt10xxhathach
2019-11-22clean up dcd lpc18_43hathach
drop supporting both device mode on both ports.
2019-11-22move dcd_lpc18_43.h into .c filehathach
2019-11-22adding irq to rt1064evkhathach
2019-11-22fix segger host examplehathach
2019-11-21moving irq to bsp for lpc17/40hathach
2019-11-21adding tud_isr/tuh_isr with lpc18/43hathach
2019-11-21update build all script to build a specifichathach
2019-11-21rename lpc 17/18 irq to dcd_isr/hcd_isrhathach
2019-11-20Merge pull request #219 from xobs/fix-eptri-ep-clearhathach
eptri: clear proper endpoint when opening IN port
2019-11-20rt1064evk led, button, uart all workhathach
2019-11-20eptri: clear proper endpoint when opening IN portSean Cross
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 <[email protected]>
2019-11-20move -flto to board.mkhathach
current board that doesn work with flto is spresense and mimxrt10xx (due to xip image_vector_table is optimized out).
2019-11-20adding support for NXP rt1064 evk board, boad test led + sw8 work.hathach
LTO is temporary disabled
2019-11-18Merge pull request #217 from xobs/valentyusb-eptrihathach
WIP: Add Valentyusb eptri
2019-11-14Merge pull request #208 from hathach/fix-issue-207hathach
Fix issue 207
2019-11-13fomu: bsp: don't call usb isr when usb is disabledSean Cross
When compiled without usb support, we don't want to call the USB ISR. Signed-off-by: Sean Cross <[email protected]>
2019-11-13fomu: bsp: remove unused messible functionsSean Cross
These functions are unused in the current implementation. Signed-off-by: Sean Cross <[email protected]>
2019-11-13examples: make: specify CROSS_COMPILE for fomuSean Cross
When BOARD=fomu, use the riscv cross-compiler. Otherwise, use the default arm compiler. This can be overridden by passing CROSS_COMIPLE on the command line. Note that there are now three common risc-v prefixes: - riscv32-unknown-elf- : Common for users who compile their own - riscv64-unknown-elf- : Upstream multiarch toolchain from SiFive - riscv-none-embed- : xPack embedded version of SiFive toolchain Here we assume users are using the `riscv-none-embed-` toolchain from xPack, because it appears to be growing more common. Additionally, there is much confusion surrounding `riscv64-unknown-elf-`, which actually includes both 32- and 64-bit runtimes and can generate software for both. Signed-off-by: Sean Cross <[email protected]>
2019-11-13travis: fetch xPack risc-v toolchainSean Cross
This toolchain seems popular in the embedded space, and is generally preferred over the upstream SiFive toolchain. It can produce both 32- and 64-bit binaries, so its prefix is riscv-none-embed-. Signed-off-by: Sean Cross <[email protected]>
2019-11-13tusb: rename `foosn` to `valentyusb`Sean Cross
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 <[email protected]>
2019-11-13valentyusb: rename from `foosn`Sean Cross
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 <[email protected]>
2019-11-13fomu: gate debug/logging featuresSean Cross
This gates the majority of the debug and logging features behind testable macros. Signed-off-by: Sean Cross <[email protected]>
2019-11-13fomu: first stable working commitSean Cross
This appears to be stable, and works well. Signed-off-by: Sean Cross <[email protected]>
2019-11-13fomu: csr: sync csrSean Cross
Signed-off-by: Sean Cross <[email protected]>
2019-11-13fomu: crt0: minor text refactorSean Cross
Signed-off-by: Sean Cross <[email protected]>
2019-11-13fomu: remove reference to SETUP_CTRL.ACKSean Cross
THis bit isn't used anymore, so remove it. Signed-off-by: Sean Cross <[email protected]>
2019-11-13fomu: dcd_fomu: add next_ev supportSean Cross
Now that we have the `USB_NEXT_EV` register, take advantage of it to work around issue #207. Signed-off-by: Sean Cross <[email protected]>
2019-11-13fomu: csr: add version with next_ev registerSean Cross
The Fomu bitstream now includes a `USB_NEXT_EV` register to indicate which is the next logical event to process. Add this register to the CSR definition. Signed-off-by: Sean Cross <[email protected]>
2019-11-13dcd_fomu: nearly thereSean Cross
Signed-off-by: Sean Cross <[email protected]>