-
Notifications
You must be signed in to change notification settings - Fork 3k
M263: Support custom board #12642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
M263: Support custom board #12642
Conversation
@ccli8, thank you for your changes. |
CI started |
Test run: FAILEDSummary: 3 of 4 test jobs failed Failed test jobs:
|
Looks like new MCU target is getting build (not set to private?) |
@@ -14712,13 +14712,12 @@ | |||
"5" | |||
] | |||
}, | |||
"NUMAKER_IOT_M263A": { | |||
"MCU_M261": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As noted in my comment, if this is base MCU, needs to be private
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@0xc0170 Fixed it. Thanks for your explanation.
This is to support M261 series based targets.
Don't set SERIAL_TX/SERIAL_RX to USBTX/USBRX which should be dedicated for USB VCOM and not for other uses.
This is to support custom boards based on M261 series chips.
- STDIO_UART and STDIO_UART_TX/STDIO_UART_RX - USB_UART and USBTX/USBRX
This is to support custom boards based on M261 series chips.
6901277
to
f5cb899
Compare
CI restarted |
Test run: SUCCESSSummary: 6 of 6 test jobs passed |
Summary of changes
Continuing #12576, this PR tries to support custom board based on M261 series chips by enabling capability of being configurable for the following items:
Pull request type
Test results