Target STM USBHOST support #3432
Conversation
|
Is something blocking the review? By the way why usb is on a directory named "unsupported". What does "unsupported" mean precisely? |
|
Add one more commit , for the support of NUCLEO_F411RE, NUCLEO_L476VG, NUCLEO_F746ZG, DISCO_L476VG |
|
Seems ok. It should be noted there is no automated testing or statement of quality about the USB code. We'd like to refactor and integrate with mbed OS 5 with testing to support the functionality and make it easier to accept contributions. Anyone interested in helping out please reach out. @jamike please resolve the conflict. |
jamike
force-pushed
the
TARGET_STM_USBHOST_FS
branch
from
11b7ca7 to
0e91688
Compare
|
rebased and conflict solved |
|
Just realized this is modifying some common target code too, so I'll kick off the bots. /morph test |
|
@mbed-bot: TEST HOST_OSES=ALL |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
[Build 1178] |
|
@jamike Can you please rebase to resolve the conflict? |
jamike
force-pushed
the
TARGET_STM_USBHOST_FS
branch
from
0e91688 to
572ae35
Compare
|
/morph test |
|
@mbed-bot: TEST HOST_OSES=ALL |
|
[Build ${MBED_BUILD_ID}] |
|
There's another conflict, earlier PR made this again. @jamike please let me know if you can rebase again or I'll do it and send a new PR |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
modify add transfer to support return value.
- reset toggle_out , toggle_in at init - in/out toggle in on ctrl endpoint - remove call back when transmission restarted
NUCLEO : F429ZI, F446ZE, F207ZG, F767ZI, F401RE, DISCO : F429ZI
NUCLEO : F411RE, L476VG, F746ZG DISCO : L476VG
jamike
force-pushed
the
TARGET_STM_USBHOST_FS
branch
from
572ae35 to
25c0d90
Compare
|
Rebased done, and CI passed... |
|
/morph test |
|
@mbed-bot: TEST HOST_OSES=ALL |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
[Build 1205] |
Ports for Upcoming Targets Fixes and Changes 3432: Target STM USBHOST support ARMmbed/mbed-os#3432 3181: NUCLEO_F207ZG extending PeripheralPins.c: all available alternate functions can be used now ARMmbed/mbed-os#3181 3626: NUCLEO_F412ZG : Add USB Device +Host ARMmbed/mbed-os#3626 3628: Fix warnings ARMmbed/mbed-os#3628 3629: STM32: L0 LL layer ARMmbed/mbed-os#3629 3632: IDE Export support for platform VK_RZ_A1H ARMmbed/mbed-os#3632 3642: Missing IRQ pin fix for platform VK_RZ_A1H ARMmbed/mbed-os#3642 3664: Fix ncs36510 sleep definitions ARMmbed/mbed-os#3664 3655: [STM32F4] Modify folder structure ARMmbed/mbed-os#3655 3657: [STM32L4] Modify folder structure ARMmbed/mbed-os#3657 3658: [STM32F3] Modify folder structure ARMmbed/mbed-os#3658 3685: STM32: I2C: reset state machine ARMmbed/mbed-os#3685 3692: uVisor: Standardize available legacy heap and stack ARMmbed/mbed-os#3692 3621: Fix for #2884, LPC824: export to LPCXpresso, target running with wron ARMmbed/mbed-os#3621 3649: [STM32F7] Modify folder structure ARMmbed/mbed-os#3649 3695: Enforce device_name is valid in targets.json ARMmbed/mbed-os#3695 3723: NCS36510: spi_format function bug fix ARMmbed/mbed-os#3723
Description
Add the USBHOST support on STM target
(NUCLEO_F401RE, NUCLEO_F446ZE, NUCLEO_F207ZG, NUCLEO_F429ZI, DISCO_F429ZI, NUCLEO_F767ZI)
As STM USBHOST IP is not OHCI compliant and current USBHOST class relies on OHCI register structure, modification under flag USBHOST_OTHER have been done for NON OHCI device on USBHOST USBENDPOINT class.
Status
ready