Home
last modified time | relevance | path

Searched refs:dump (Results 1 – 25 of 67) sorted by relevance

123

/Zephyr-Core-3.6.0/subsys/debug/coredump/
DKconfig8 Enable core dump so it can be used for offline debugging.
20 Core dump is done via logging subsystem.
28 Core dump is saved to a flash partition with DTS alias
35 Core dump is done via memory window slot[1].
42 Core dump is done via custom mechanism defined out of tree
47 prompt "Memory dump"
59 minimum core dump.
Dcoredump_core.c91 api->dump(dev); in process_coredump_dev_memory()
/Zephyr-Core-3.6.0/drivers/gnss/
DKconfig18 bool "GNSS dump support"
21 Enable GNSS dump library
27 Enable GNSS dump to log.
32 int "GNSS log dump buffer size"
35 Size of GNSS log dump buffer
/Zephyr-Core-3.6.0/doc/hardware/peripherals/
Dcoredump.rst11 any dump. And the driver exposes an API to add/remove dump memory regions at runtime.
15 memory when a dump occurs.
/Zephyr-Core-3.6.0/samples/subsys/bindesc/hello_bindesc/
DREADME.rst23 To dump all binary descriptors in the image, run:
27 west bindesc dump build/zephyr/zephyr.bin
29 (Note: you can also dump the contents of ``zephyr.elf``, if your build system
/Zephyr-Core-3.6.0/boards/arm/arty/
DCMakeLists.txt7 # Generate zephyr.mem verilog memory hex dump file for initialising ITCM in
25 …message(STATUS "Verilog memory hex dump will be written to: ${PROJECT_BINARY_DIR}/${CONFIG_KERNEL_…
27 …{CROSS_COMPILE_TARGET}-bin2hex) utility was not found, verilog memory hex dump file cannot be gene…
/Zephyr-Core-3.6.0/doc/services/debugging/
Dcoredump.rst6 The core dump module enables dumping the CPU registers and memory content
18 Here are the options to enable output backends for core dump:
20 * ``DEBUG_COREDUMP_BACKEND_LOGGING``: use log module for core dump output.
22 dump output.
23 * ``DEBUG_COREDUMP_BACKEND_NULL``: fallback core dump backend if other
26 Here are the choices regarding memory dump:
31 dump is desired.
33 Additional memory can be included in a dump (even with the "DEBUG_COREDUMP_MEMORY_DUMP_MIN"
39 When the core dump module is enabled, during a fatal error, CPU registers
41 are enabled. This core dump data can fed into a custom-made GDB server as
[all …]
/Zephyr-Core-3.6.0/samples/subsys/input/input_dump/
DREADME.rst1 .. zephyr:code-sample:: input-dump
2 :name: Input dump
/Zephyr-Core-3.6.0/drivers/pcie/host/
Dshell.c288 static void show(const struct shell *sh, pcie_bdf_t bdf, bool details, bool dump) in show() argument
334 if (dump) { in show()
341 bool dump; member
348 show(data->sh, bdf, false, data->dump); in scan_cb()
358 .dump = false, in cmd_pcie_ls()
369 data.dump = true; in cmd_pcie_ls()
386 show(sh, bdf, true, data.dump); in cmd_pcie_ls()
/Zephyr-Core-3.6.0/scripts/pylib/twister/twisterlib/
Dhardwaremap.py161 self.dump(connected_only=True)
361 yaml.dump(hwm, yaml_file, Dumper=Dumper, default_flow_style=False)
365 self.dump()
386 yaml.dump(dl, yaml_file, Dumper=Dumper, default_flow_style=False)
388 self.dump(detected=True)
390 def dump(self, filtered=[], header=[], connected_only=False, detected=False): member in HardwareMap
/Zephyr-Core-3.6.0/tests/subsys/debug/gdbstub/
Dtest_breakpoints.gdbinit16 # exit main() and continue with code coverage dump, if configured
/Zephyr-Core-3.6.0/samples/subsys/usb/hid/
DREADME.rst47 You can monitor report sending using standard Linux ``usbhid-dump`` command.
51 $ sudo usbhid-dump -d 2fe3:0006 -es
/Zephyr-Core-3.6.0/scripts/
Dmake_bugs_pickle.py59 pickle.dump(open_bugs, out_file)
/Zephyr-Core-3.6.0/include/zephyr/drivers/
Dcoredump.h94 coredump_device_dump_t dump; member
/Zephyr-Core-3.6.0/scripts/utils/
Dtwister_to_list.py71 yaml.dump(conf, f)
/Zephyr-Core-3.6.0/scripts/tests/twister/
Dtest_hardwaremap.py160 mocked_hm.dump = mock.Mock()
192 mocked_hm.dump.assert_called_once_with(
653 mocked_hm.dump = mock.Mock()
716 mocked_hm.dump(filtered, header, connected_only, detected)
/Zephyr-Core-3.6.0/drivers/dma/
DKconfig.intel_adsp_gpdma30 bool "Debug dump for IP registers"
/Zephyr-Core-3.6.0/tests/bsim/bluetooth/host/misc/conn_stress/scripts/
D_conn_stress.sh60 Execute ./bs_2G4_phy_v1 -dump -v=2 -s=${simulation_id} -D=13 -sim_length=1000e6 &
/Zephyr-Core-3.6.0/drivers/usb_c/ppc/
Dshell.c120 SHELL_CMD_ARG(dump, &list_device_names,
/Zephyr-Core-3.6.0/drivers/i2c/
DKconfig45 "zephyr,i2c-dump-allowlist" and phandles to the devices that need to be traced.
47 i2c-dump-allowlist {
48 compatible = "zephyr,i2c-dump-allowlist";
/Zephyr-Core-3.6.0/doc/develop/debug/
Dindex.rst297 The sample output of the dump looks like this::
316 called internally by ``i2c_transfer`` API function with read content dump enabled.
327 The content dump consist of both the hex and ASCII representation.
329 Filtering the I2C communication dump
350 i2c-dump-allowlist {
351 compatible = "zephyr,i2c-dump-allowlist";
356 The filters nodes are identified by the compatible string with ``zephyr,i2c-dump-allowlist`` value.
/Zephyr-Core-3.6.0/drivers/usb_c/tcpc/
Dshell.c143 SHELL_CMD_ARG(dump, &list_device_names,
/Zephyr-Core-3.6.0/subsys/net/ip/
Dtp.c67 static void dump(void *data, size_t len) in dump() function
94 dump(&mem->header, sizeof(mem->header)); in tp_mem_chk()
95 dump(mem->mem, mem->size); in tp_mem_chk()
96 dump(mem->footer, sizeof(*mem->footer)); in tp_mem_chk()
/Zephyr-Core-3.6.0/subsys/testsuite/
DKconfig10 # For tests, store thread names in binary and dump them on crash to
69 be available over serial. This serial dump can be passed to
76 int "Size of heap allocated for gcov coverage data dump"
/Zephyr-Core-3.6.0/scripts/ci/
Dversion_mgr.py135 json.dump(data, versions)

123