Home
last modified time | relevance | path

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

12

/Zephyr-latest/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-latest/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.
59 Transmission of segments is separated by a segment transmission interval (see the
[all …]
/Zephyr-latest/soc/espressif/common/
Dloader.c117 unsigned int segments = 0; in map_rom_segments() local
122 while (segments++ < 16) { in map_rom_segments()
167 if (segments == 0 || segments == 16) { in map_rom_segments()
172 ESP_EARLY_LOGI(TAG, "Image with %d segments", segments - 1); in map_rom_segments()
/Zephyr-latest/arch/common/
Dfill_with_zeros.ld9 * counter) in executable segments with TrapInstr pattern, e.g. for ARM the
/Zephyr-latest/doc/connectivity/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
/Zephyr-latest/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-latest/subsys/bluetooth/mesh/
DKconfig538 segments from the same pool. Each segment is a 12 byte block,
541 Outgoing messages will allocate their segments at the start of the
544 segments at the start of the transaction, and won't release them until
548 int "Maximum number of segments in incoming messages"
555 Maximum number of segments supported for incoming messages.
561 specification would allow (32 segments).
565 example, 5 segments means the maximum SDU size is 60 bytes,
570 int "Maximum number of segments in outgoing messages"
577 Maximum number of segments supported for outgoing messages.
583 would allow (32 segments).
[all …]
/Zephyr-latest/subsys/bluetooth/host/
DKconfig.l2cap65 Enable API for direct receiving of L2CAP SDU segments, bypassing the
/Zephyr-latest/samples/shields/x_nucleo_53l0a1/
DREADME.rst9 This sample demonstrate the usage of the 4 digits x 7 segments display and the
/Zephyr-latest/samples/net/sockets/coap_server/src/
Dtest.c240 COAP_RESOURCE_DEFINE(segments, coap_server,
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig.mcs98 int "Maximum number of tracks segments in a track segment object"
102 Sets the maximum number of tracks segments in a track segment object.
/Zephyr-latest/soc/espressif/esp32/
Ddefault_appcpu.ld19 /* User available SRAM memory segments */
40 /* Flash segments (rodata and text) should be mapped in the virtual address spaces.
Ddefault.ld15 /* User available SRAM memory segments */
51 /* Flash segments (rodata and text) should be mapped in virtual address space by providing VMA.
/Zephyr-latest/soc/espressif/esp32s3/
Ddefault_appcpu.ld17 /* User available SRAM memory segments */
27 /* User available ROM memory segments */
48 /* Flash segments (rodata and text) should be mapped in the virtual address spaces.
Ddefault.ld13 /* User available SRAM memory segments */
23 /* User available ROM memory segments */
56 /* Flash segments (rodata and text) should be mapped in the virtual address spaces.
/Zephyr-latest/scripts/west_commands/runners/
Dnrf_common.py253 for segment_start, _ in self.hex_contents.segments():
/Zephyr-latest/boards/st/stm32l476g_disco/doc/
Dindex.rst19 - LCD 24 segments, 4 commons in DIP 28 package
/Zephyr-latest/soc/espressif/esp32c6/
Ddefault.ld23 /* User available memory segments */
39 /* Flash segments (rodata and text) should be mapped in the virtual address spaces.
92 * Thus, the following region segments are
/Zephyr-latest/boards/st/stm32u083c_dk/doc/
Dindex.rst132 - 8*48 or 4*52 segments, with step-up converter
/Zephyr-latest/subsys/net/ip/
DKconfig.tcp142 SEQs 5,4,3,6 and are waiting SEQ 2, the data in segments 3,4,5,6 is
/Zephyr-latest/soc/espressif/esp32c2/
Ddefault.ld23 /* User available SRAM memory segments */
45 /* Flash segments (rodata and text) should be mapped in the virtual address spaces.
/Zephyr-latest/soc/espressif/esp32c3/
Ddefault.ld23 /* User available SRAM memory segments */
45 /* Flash segments (rodata and text) should be mapped in the virtual address spaces.
/Zephyr-latest/doc/hardware/peripherals/can/
Dcontroller.rst33 A single bit is split into four segments.
/Zephyr-latest/soc/espressif/esp32s2/
Ddefault.ld25 /* User available SRAM memory segments */
56 /* Flash segments (rodata and text) should be mapped in virtual address space by providing VMA.
/Zephyr-latest/doc/connectivity/networking/
Dnet_config_guide.rst221 SEQs 5,4,3,6 and are waiting SEQ 2, the data in segments 3,4,5,6 is

12