michaelh/zephyr
1
0
Fork 0
Code Releases Activity

boards: Fix invalid paths

Browse source 
Fixes paths that are not valid

Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
This commit is contained in:
Jamie McCrae 2024-03-12 11:04:15 +00:00 • committed by Carles Cufí
commit df50197499
20 changed files with 42 additions and 50 deletions
Download patch file Download diff file Expand all files Collapse all files

8
boards/snps/em_starterkit/doc/index.rst
View file

@ -26,18 +26,18 @@ See also this URL for details about the board:
The latest version of EM Starter Kit is 2.3, developer can upgrade from
2.0/2.1/2.2 to 2.3 using latest firmware.
The default configuration for EM Starter Kit boards can be found in
:zephyr_file:`boards/synopsys/em_starterkit/em_starterkit_defconfig`.
:zephyr_file:`boards/snps/em_starterkit/em_starterkit_defconfig`.
The default SoC for this board supported in Zephyr is the EM9D.
This configuration is a Harvard Architecture, with a separate
instruction bus and data bus. Instruction memory is called ICCM
and data memory is called DCCM. The configuration file for EM9D
is found in :zephyr_file:`soc/synopsys/emsk/Kconfig.defconfig.em9d`.
is found in :zephyr_file:`soc/snps/emsk/Kconfig.defconfig.em9d`.
If you have a larger program, you can select the EM7D or EM11D, which gives
access to 128KB DRAM with i-cache and d-cache. The configuration file for EM7D
is found in :zephyr_file:`soc/synopsys/emsk/Kconfig.defconfig.em7d` and EM11D is
found in :zephyr_file:`soc/synopsys/emsk/Kconfig.defconfig.em11d`.
is found in :zephyr_file:`soc/snps/emsk/Kconfig.defconfig.em7d` and EM11D is
found in :zephyr_file:`soc/snps/emsk/Kconfig.defconfig.em11d`.
Hardware

20
boards/snps/nsim/doc/index.rst
View file

@ -39,7 +39,7 @@ available configurations are listed below:
.. _board_arc_nsim_prop_args_files:
It is recommended to look at precise description of a particular sub-configuration in either
``.props`` or ``.args`` files in :zephyr_file:`boards/synopsys/nsim/support/` directory to understand
``.props`` or ``.args`` files in :zephyr_file:`boards/snps/nsim/support/` directory to understand
which options are configured and so will be used on invocation of the simulator.
In case of single-core configurations it would be ``.props`` file which contains configuration
@ -55,14 +55,14 @@ simulation anyway).
nSIM & MDB don't exactly match, so care should be taken).
I.e. for the single-core ``nsim/nsim_hs5x`` platform there are
:zephyr_file:`boards/synopsys/nsim/support/nsim_hs5x.props` and
:zephyr_file:`boards/synopsys/nsim/support/mdb_hs5x.args`.
:zephyr_file:`boards/snps/nsim/support/nsim_hs5x.props` and
:zephyr_file:`boards/snps/nsim/support/mdb_hs5x.args`.
For the multi-core configurations there is only ``.args`` file as the multi-core configuration
can only be instantiated with help of MDB.
I.e. for the multi-core ``nsim/nsim_hs5x/smp`` platform there is only
:zephyr_file:`boards/synopsys/nsim/support/mdb_hs5x_smp.args`.
:zephyr_file:`boards/snps/nsim/support/mdb_hs5x_smp.args`.
.. warning::
All nSIM/MDB configurations are used for demo and testing purposes. They are not meant to
@ -90,7 +90,7 @@ Most board sub-configurations support building with both GNU and ARC MWDT toolch
there might be exceptions from that, especially for newly added targets. You can check supported
toolchains for the sub-configurations in the corresponding ``.yaml`` file.
I.e. for the ``nsim/nsim_hs5x`` board we can check :zephyr_file:`boards/synopsys/nsim/nsim_nsim_hs5x.yaml`
I.e. for the ``nsim/nsim_hs5x`` board we can check :zephyr_file:`boards/snps/nsim/nsim_nsim_hs5x.yaml`
The supported toolchains are listed in ``toolchain:`` array in ``.yaml`` file, where we can find:
@ -196,8 +196,8 @@ platform:
< *snip* >
-- west debug: using runner mdb-nsim
runners.mdb-nsim: mdb -pset=1 -psetname=core0 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/synopsys/nsim/support/mdb_hs5x_smp.args /path/zephyr/build/zephyr/zephyr.elf
runners.mdb-nsim: mdb -pset=2 -psetname=core1 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/synopsys/nsim/support/mdb_hs5x_smp.args /path/zephyr/build/zephyr/zephyr.elf
runners.mdb-nsim: mdb -pset=1 -psetname=core0 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/snps/nsim/support/mdb_hs5x_smp.args /path/zephyr/build/zephyr/zephyr.elf
runners.mdb-nsim: mdb -pset=2 -psetname=core1 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/snps/nsim/support/mdb_hs5x_smp.args /path/zephyr/build/zephyr/zephyr.elf
runners.mdb-nsim: mdb -multifiles=core1,core0 -OKN
From that output it's possible to extract MDB commands used for setting-up the GUI debugging
@ -205,8 +205,8 @@ platform:
.. code-block:: console
mdb -pset=1 -psetname=core0 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/synopsys/nsim/support/mdb_hs5x_smp.args /path/zephyr/build/zephyr/zephyr.elf
mdb -pset=2 -psetname=core1 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/synopsys/nsim/support/mdb_hs5x_smp.args /path/zephyr/build/zephyr/zephyr.elf
mdb -pset=1 -psetname=core0 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/snps/nsim/support/mdb_hs5x_smp.args /path/zephyr/build/zephyr/zephyr.elf
mdb -pset=2 -psetname=core1 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/snps/nsim/support/mdb_hs5x_smp.args /path/zephyr/build/zephyr/zephyr.elf
mdb -multifiles=core1,core0 -OKN
Then it's possible to use them directly or in some machinery if required.
@ -316,7 +316,7 @@ GNU & MWDT toolchain compiler options
=====================================
The hardware-specific compiler options are set in corresponding SoC cmake file. For ``nsim`` board
it is :zephyr_file:`soc/synopsys/nsim/CMakeLists.txt`.
it is :zephyr_file:`soc/snps/nsim/CMakeLists.txt`.
For the GNU toolchain the basic configuration is set via ``-mcpu`` which is defined in generic code
and based on the selected CPU model via Kconfig. It still can be forcefully set to required value