Home
last modified time | relevance | path

Searched refs:segments (Results 1 – 24 of 24) sorted by relevance

/Zephyr-Core-3.5.0/scripts/build/
Dgen_image_info.py28 def write_header(filename, segments, adjusted_lma): argument
38 for idx, segment in enumerate(segments):
58 segments = list()
60 segments.insert(segment_idx, dict())
61 segments[segment_idx]['segment'] = elffile.get_segment(segment_idx)
62 return segments
79 segments = read_segments(args.elf_file)
80 write_header(args.header_file, segments, args.adjusted_lma)
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/
Dsar_cfg.rst15 PDU into multiple segments.
17 The lower transport layer on the receiving device reassembles the segments into a single Upper
25 The transport layer is able to transport up to 32 segments with its SAR mechanism, with a maximum
29 * :kconfig:option:`CONFIG_BT_MESH_RX_SEG_MAX` to set the maximum number of segments in an incoming …
30 * :kconfig:option:`CONFIG_BT_MESH_TX_SEG_MAX` to set the maximum number of segments in an outgoing …
37 Incoming and outgoing segmented messages share the same pool for allocation of their segments. This
39 Both incoming and outgoing messages allocate segments at the start of the transaction. The outgoing
40 segmented message releases its segments one by one as soon as they are acknowledged by the receiver,
41 while the incoming message releases the segments first after the message is fully received.
51 When sending a segmented message to a unicast address, the unacknowledged segments are repeated
[all …]
/Zephyr-Core-3.5.0/arch/common/
Dfill_with_zeros.ld9 * counter) in executable segments with TrapInstr pattern, e.g. for ARM the
/Zephyr-Core-3.5.0/doc/hardware/peripherals/canbus/
Disotp.rst23 behavior. ISO-TP segments packets into small fragments depending on the payload
24 size of the CAN frame. The header of those segments is called Protocol Control
Dcontroller.rst55 A single bit is split into four segments.
/Zephyr-Core-3.5.0/boards/shields/x_nucleo_53l0a1/doc/
Dindex.rst46 2 digits x 7 segments = 14 pins:
65 sensors (soldered + 2 satellites) and the 7 segments display.
/Zephyr-Core-3.5.0/subsys/bluetooth/audio/
DKconfig.mcs99 int "Maximum number of tracks segments in a track segment object"
103 Sets the maximum number of tracks segments in a track segment object.
/Zephyr-Core-3.5.0/subsys/bluetooth/mesh/
DKconfig421 segments from the same pool. Each segment is a 12 byte block,
424 Outgoing messages will allocate their segments at the start of the
427 segments at the start of the transaction, and won't release them until
431 int "Maximum number of segments in incoming messages"
438 Maximum number of segments supported for incoming messages.
444 specification would allow (32 segments).
448 example, 5 segments means the maximum SDU size is 60 bytes,
453 int "Maximum number of segments in outgoing messages"
460 Maximum number of segments supported for outgoing messages.
466 would allow (32 segments).
[all …]
/Zephyr-Core-3.5.0/scripts/west_commands/runners/
Dnrf_common.py170 for segment_start, _ in self.hex_contents.segments():
311 for start, end in self.hex_contents.segments():
/Zephyr-Core-3.5.0/samples/shields/x_nucleo_53l0a1/
DREADME.rst9 This sample demonstrate the usage of the 4 digits x 7 segments display and the
/Zephyr-Core-3.5.0/subsys/bluetooth/host/
DKconfig.l2cap80 Enable API for direct receiving of L2CAP SDU segments, bypassing the
/Zephyr-Core-3.5.0/soc/riscv/espressif_esp32/esp32c3/
Ddefault.ld52 /* Flash segments (rodata and text) should be mapped in virtual address space by providing VMA.
456 * data segments reflect the same address space on different buses.
/Zephyr-Core-3.5.0/boards/arm/stm32l476g_disco/doc/
Dindex.rst22 - LCD 24 segments, 4 commons in DIP 28 package
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32s3/
Ddefault_appcpu.ld179 /* Flash segments (rodata and text) should be mapped in virtual address space by providing VMA.
Ddefault.ld70 /* Flash segments (rodata and text) should be mapped in virtual address space by providing VMA.
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32_net/
Dlinker.ld29 /* Flash segments (rodata and text) should be mapped in virtual address space by providing VMA.
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32s2/
Ddefault.ld56 /* Flash segments (rodata and text) should be mapped in virtual address space by providing VMA.
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32/
Ddefault.ld49 /* Flash segments (rodata and text) should be mapped in virtual address space by providing VMA.
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/shell/
Dmcp.rst42 not other groups.) Tracks can be divided into segments.
/Zephyr-Core-3.5.0/
DKconfig.zephyr672 - Number of segments in the image
/Zephyr-Core-3.5.0/subsys/net/ip/
DKconfig515 SEQs 5,4,3,6 and are waiting SEQ 2, the data in segments 3,4,5,6 is
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-3.4.rst430 segments directly and manage credits explicitly.
Drelease-notes-2.2.rst743 * :github:`23121` - Bluetooth: Mesh: Proxy servers only resends segments to proxy
Drelease-notes-3.3.rst2802 - :github:`54577` - IPv6 defragmenting fails when segments do not overlap