TCF: default Quark SE's ARC core to use UART1 as console for testing
The current code redirects the ARC output to UART0. Our test setup is laid out with a single serial port (which is mostly UART1). For simplicity (as the extra cabling would be prohibitive), we will change the default test building to redirect output back to ARC1. This implies that the output from test cases will be intermixed when test cases are not prepared to share the serial port, so running of testcases combined in x86+arc will have to be disabled by default and only done in testcases which declare they need to do so. Change-Id: I5a6b79ecb48ecfb2d711be7f5fdbe08b4c3d34e9 Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
This commit is contained in:
parent
462f431791
commit
5452bbdfdb
1 changed files with 12 additions and 0 deletions
12
defaults.tc
12
defaults.tc
|
@ -116,6 +116,18 @@
|
|||
#
|
||||
# @images [ type == "ma" and quark_se_stub == 'yes' and bsp_model == 'arc'] \
|
||||
# kernel-x86:%(srcdir)s/outdir-%(tchash)s-stub-x86-quark_se_devboard/zephyr.bin
|
||||
#
|
||||
# (2.3.4) When running the ARC in Quark SE, we redirect the output to the
|
||||
# UART_1 (the same as the x86) to simplify the test setup (no
|
||||
# need to connect multiple console cables)
|
||||
#
|
||||
# However, this makes it impossible to run independent test cases
|
||||
# at the same time (BSP model x86+arc) because they'd interfere
|
||||
# with each other.
|
||||
#
|
||||
# ^build [ quark_se_stub == 'yes' and bsp == 'arc' ] \
|
||||
# echo "# Generated by Zephyr's TCF defaults.tc" > %(srcdir)s/outdir-%(tchash)s-%(board)s/tcf_2.3.4.conf; \
|
||||
# echo 'CONFIG_UART_CONSOLE_ON_DEV_NAME="UART_1"' >> %(srcdir)s/outdir-%(tchash)s-%(board)s/tcf_2.3.4.conf
|
||||
|
||||
|
||||
# (3) Generate the initial configuration
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue