Home
last modified time | relevance | path

Searched refs:ve (Results 1 – 25 of 32) sorted by relevance

12

/Zephyr-latest/.github/ISSUE_TEMPLATE/
D002_enhancement.md20 **Describe alternatives you've considered**
22 A clear and concise description of any alternative solutions or features you've considered.
D004_feature_request.md20 **Describe alternatives you've considered**
22 A clear and concise description of any alternative solutions or features you've considered.
/Zephyr-latest/doc/
D404.rst31 It's also possible we've removed or renamed the page you're looking for.
/Zephyr-latest/boards/96boards/carbon/doc/
Dnrf51822.rst122 After you've flashed the chip, you can keep debugging using the same
125 "run" at the GDB prompt to restart the program you've flashed.
/Zephyr-latest/doc/_extensions/zephyr/doxytooltip/static/tippy/
Dpopper.min.js7ve="y"===M?"height":"width",ye=me+b[le],ge=me-b[he],be=-1!==[D,P].indexOf(x),xe=null!=(ue=null==S?… function
/Zephyr-latest/boards/openisa/rv32m1_vega/doc/
Dindex.rst548 These instructions assume you've set up a development system,
613 Make sure you've done the :ref:`JTAG setup <rv32m1-vega-jtag>`, and
624 Make sure you've followed the above instructions to set up your board
658 Make sure you've done the :ref:`JTAG setup <rv32m1-vega-jtag>`, and
669 Make sure you've followed the above instructions to set up your board
/Zephyr-latest/scripts/west_commands/
Drun_common.py490 except ValueError as ve:
491 log.err(str(ve), fatal=True)
/Zephyr-latest/boards/96boards/wistrio/doc/
D96b_wistrio.rst187 "run" at the GDB prompt to restart the program you've flashed.
/Zephyr-latest/arch/x86/zefi/
DREADME.txt82 systems I've tried, EFI uses memory near the top of 32-bit-accessible
/Zephyr-latest/boards/96boards/neonkey/doc/
Dindex.rst214 "run" at the GDB prompt to restart the program you've flashed.
/Zephyr-latest/samples/net/sockets/http_server/
DREADME.rst154 sending requests to our server. Once we've collected enough data, we can
/Zephyr-latest/doc/develop/west/
Dtroubleshooting.rst51 First, make sure you've installed west; see :ref:`west-install`. Then try
Dbasics.rst20 If you've followed the :ref:`getting_started`, your local
Dbuilt-in.rst142 ``HEAD`` checked out by west, then git will warn you that you've left
/Zephyr-latest/boards/telink/tlsr9518adk80d/doc/
Dindex.rst146 These instructions assume you've set up a development environment as
/Zephyr-latest/samples/subsys/mgmt/hawkbit/
DREADME.rst147 updates, and then download the update you've just created. If everything goes
/Zephyr-latest/boards/nordic/nrf52840dongle/doc/
Dindex.rst183 Next, do the **one-time setup** to flash MCUboot. We'll assume you've cloned
/Zephyr-latest/doc/develop/
Dbeyond-GSG.rst251 file by downloading it from their sourceforge repo, or if you've
/Zephyr-latest/samples/subsys/mgmt/updatehub/
DREADME.rst404 updates, and then download the update package you've just created. If
/Zephyr-latest/doc/project/
Ddev_env_and_tools.rst11 uploaded to GitHub but don't actually become a part of the project until they've
/Zephyr-latest/doc/contribute/documentation/
Dguidelines.rst180 (phone) screens if necessary. We've deprecated use of the ``hlist``
431 We've kept the substitutions list small but others can be added as
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst227 Once you've found an existing board that uses your SoC, you can usually start
911 #. Make sure you've followed all the :ref:`porting-general-recommendations`.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Ddfu.rst313 #. The Distributor's Firmware Update Client model queries all Target nodes to ensure that they've
/Zephyr-latest/doc/contribute/
Dguidelines.rst162 - If you've pushed your changes to GitHub already you'll need to force push
440 what you've done. Here are some examples:
/Zephyr-latest/doc/build/dts/
Dhowtos.rst431 Examples for how to do this follow. They assume you've already implemented the

12