Lines Matching full:nsim
1 .. zephyr:board:: nsim
7 simulation with `Designware ARC nSIM`_ or run same images on FPGA prototyping platform `HAPS`_. The
22 * ``nsim/nsim_em`` - ARC EM core v4.0 with two register banks, FastIRQ's, MPUv2, DSP options and
24 * ``nsim/nsim_em7d_v22`` - ARC EM core v3.0 with one register bank and FastIRQ's
25 * ``nsim/nsim_em11d`` - ARC EM core v4.0 with one register bank, no FastIRQ's, MPUv2, DSP options a…
27 * ``nsim/nsim_sem`` - ARC EM core v4.0 with secure features (thus "SEM", i.e. Secure EM) and MPUv4
28 * ``nsim/nsim_hs`` - ARCv2 HS core v2.1 with two register banks, FastIRQ's and MPUv3
29 * ``nsim/nsim_hs/smp`` - Dual-core ARCv2 HS core v2.1 with two register banks, FastIRQ's and MPUv3
30 * ``nsim/nsim_vpx5`` - ARCv2 VPX5 core, close to vpx5_integer_full template
31 * ``nsim/nsim_hs5x`` - 32-bit ARCv3 HS core with rich set of options
32 * ``nsim/nsim_hs6x`` - 64-bit ARCv3 HS core with rich set of options
33 * ``nsim/nsim_hs5x/smp/12cores`` - SMP 12 cores 32-bit ARCv3 HS platform
34 * ``nsim/nsim_hs6x/smp/12cores`` - SMP 12 cores 64-bit ARCv3 HS platform
39 ``.props`` or ``.args`` files in :zephyr_file:`boards/snps/nsim/arc_classic/support/` directory to …
43 for nSIM simulator and ``.args`` file which contains configuration for MetaWare debugger (MDB).
45 tool: ``.props`` file for nSIM simulator and ``.args`` file for MDB (which internally uses nSIM for
52 nSIM & MDB don't exactly match, so care should be taken).
54 I.e. for the single-core ``nsim/nsim_hs5x`` platform there are
55 :zephyr_file:`boards/snps/nsim/arc_classic/support/nsim_hs5x.props` and
56 :zephyr_file:`boards/snps/nsim/arc_classic/support/mdb_hs5x.args`.
61 I.e. for the multi-core ``nsim/nsim_hs5x/smp`` platform there is only
62 :zephyr_file:`boards/snps/nsim/arc_classic/support/mdb_hs5x_smp.args`.
65 All nSIM/MDB configurations are used for demo and testing purposes. They are not meant to
75 either `DesignWare ARC nSIM`_ or `DesignWare ARC Free nSIM`_ is required.
78 `DesignWare ARC nSIM`_ and MetaWare Debugger from `ARC MWDT`_ are required.
90 I.e. for the ``nsim/nsim_hs5x`` board we can check :zephyr_file:`boards/snps/nsim/arc_classic/nsim_…
109 nSIM, for example, with the :zephyr:code-sample:`synchronization` sample:
118 nSIM, and display the following console output:
123 thread_a: Hello World from cpu 0 on nsim!
124 thread_b: Hello World from cpu 0 on nsim!
125 thread_a: Hello World from cpu 0 on nsim!
126 thread_b: Hello World from cpu 0 on nsim!
127 thread_a: Hello World from cpu 0 on nsim!
139 You can run applications built for ``nsim`` board not only on nSIM simulation itself, but also on
163 * Allows to debug both single-core and multi-core ``nsim`` targets.
166 You can use the following command to start GUI debugging when running application on nSIM simulator
171 west debug --runner mdb-nsim
187 west -v debug --runner mdb-nsim
189 it will produce the following output (the ``nsim/nsim_hs5x/smp`` configuration was used for that
195 -- west debug: using runner mdb-nsim
196 …runners.mdb-nsim: mdb -pset=1 -psetname=core0 -nooptions -nogoifmain -toggle=include_local_symbols…
197 ….mdb-nsim: mdb -pset=2 -psetname=core1 -prop=download=2 -nooptions -nogoifmain -toggle=include_loc…
198 runners.mdb-nsim: mdb -multifiles=core1,core0 -OKN
205 …e0 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/snps/nsim/sup…
206 …=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -nsim @/path/zephyr/boards/snps/nsim/sup…
216 In case of execution or debugging with MDB on multi-core configuration on nSIM
229 Debugging on nSIM via GDB is only supported on single-core configurations (which use standalone
230 nSIM). However if it's possible to launch application on multi-core nsim target that means you
232 It's the nSIM with ARC GDB restriction, real HW multi-core ARC targets can be debugged with ARC
239 The normal ``west debug`` command won't work for debugging applications using nsim boards
240 because both the nSIM simulator and the debugger (either GDB or MDB) use the same console for
242 In case of GDB debugger it's possible to use a separate terminal windows for GDB and nSIM to
245 After building your application, open two terminal windows. In terminal one, use nSIM to start a GDB
250 west debugserver --runner arc-nsim
270 If modification of existing nsim configuration is required or even there's a need in creation of a
274 * nSIM & MDB configuration
301 nSIM configuration
304 nSIM configuration is defined in :ref:`props and args files <board_arc_nsim_prop_args_files>`.
315 The hardware-specific compiler options are set in corresponding SoC cmake file. For ``nsim`` board
316 it is :zephyr_file:`soc/snps/nsim/arc_classic/CMakeLists.txt`.
335 .. _Designware ARC nSIM: https://www.synopsys.com/dw/ipdir.php?ds=sim_nsim
336 .. _DesignWare ARC Free nSIM: https://www.synopsys.com/cgi-bin/dwarcnsim/req1.cgi