| /hal_espressif-latest/tools/esptool_py/flasher_stub/ |
| D | stub_flasher.c | 36 esp_command_req_t *command; /* Pointer to buf_a or buf_b as latest command received */ member
160 ub.command = (esp_command_req_t *)ub.buf_a; in stub_handle_rx_byte()
163 ub.command = (esp_command_req_t *)ub.buf_b; in stub_handle_rx_byte()
170 static esp_command_error verify_data_len(esp_command_req_t *command, uint8_t len) in verify_data_len() argument
172 return (command->data_len == len) ? ESP_OK : ESP_BAD_DATA_LEN; in verify_data_len()
178 while(ub.command == NULL) { in cmd_loop()
181 esp_command_req_t *command = ub.command; in cmd_loop() local
182 ub.command = NULL; in cmd_loop()
184 uint32_t *data_words = (uint32_t *)command->data_buf; in cmd_loop()
189 .op_ret = command->op, in cmd_loop()
[all …]
|
| /hal_espressif-latest/tools/esptool_py/docs/en/esptool/ |
| D | scripting.rst | 12 command = ['--baud', '460800', 'read_flash', '0', '0x200000', 'flash_contents.bin']
13 print('Using command %s' % ' '.join(command))
14 esptool.main(command)
|
| D | advanced-commands.rst | 17 The ``verify_flash`` command allows you to verify that data in flash matches a local file.
19 …command always verifies the MD5 hash of data which is written to flash, so additional verification…
33 …* Another way to compare flash contents is to use the ``read_flash`` command, and then use binary …
40 The ``dump_mem`` command will dump a region from the chip's memory space to a file. For example, to…
51 …command allows the loading of an executable binary image (created with the ``elf2image`` or ``make…
59 …not load correctly and the image will probably crash. The ``image_info`` command can be used to ch…
83 This command is intended for use when debugging hardware flash chip-related problems. It allows sen…
91 * ``--bytes 1`` sends the most common ``RDSR`` command (05h) and returns a single byte of status.
104 This command is intended for use when debugging hardware flash chip-related problems. It allows sen…
110 …it argument and then with an 8-bit argument, as different flash chips use this command differently.
[all …]
|
| D | flashing-firmware.rst | 35 …work. If you are unsure of the location, see the generated esptool `command <#command>`__ containi…
40 Compile and upload your firmware once with your preferred framework. The detailed esptool command w…
42 It is also possible to assemble the command manually, please see the :ref:`esptool usage documentat…
47 ESP-IDF outputs the full esptool command used for flashing after the build is finished, for example…
49 Project build complete. To flash, run this command:
56 …command is hidden from the user by default. To expose it, open the preferences window and check th…
61 …ad`` in the terminal. In the generated output, there is the full esptool command, you will see som…
71 If you split the output, you’ll find the ``write_flash`` command with a list of paths to binary fil…
73 Change ``PORT`` to the name of :ref:`actually used serial port <serial-port>` and run the command. …
107 … the flashed device and repeat the process by connecting another one and running the command again.
|
| D | index.rst | 6 Use ``esptool.py -h`` to see a summary of all available commands and command line options.
8 To see all options for a particular command, append ``-h`` to the command name. ie ``esptool.py wri…
|
| D | basic-commands.rst | 9 Binary data can be written to the ESP's flash chip via the serial ``write_flash`` command:
15 Multiple flash addresses and file names can be given on the same command line:
36 See the :ref:`troubleshooting` section if the ``write_flash`` command is failing, or the flashed mo…
102 The read_flash command allows reading back the contents of flash. The arguments to the command are …
118 …When using the ``read_flash`` command in combination with the ``--no-stub`` argument, it may be ne…
186 The ``elf2image`` command converts an ELF file (from compiler/linker output) into the binary execut…
192 This command does not require a serial connection.
195 …command, see the `write_flash command <#write-binary-data-to-flash-write-flash>`__ for details. Ov…
201 …The default command output for {IDF_TARGET_NAME} is two binary files: ``my_app.elf-0x00000.bin`` a…
228 …command outputs some information (load addresses, sizes, etc) about a ``.bin`` file created by ``e…
[all …]
|
| /hal_espressif-latest/components/spi_flash/ |
| D | memspi_host_driver.c | 27 uint32_t command,
91 .command = CMD_RDID, in memspi_host_read_id_hs()
116 .command = CMD_RDSR, in memspi_host_read_status_hs()
139 t.command = CMD_CHIP_ERASE; in memspi_host_erase_chip()
148 .command = CMD_SECTOR_ERASE, in memspi_host_erase_sector()
160 .command = CMD_LARGE_BLOCK_ERASE, in memspi_host_erase_block()
172 .command = CMD_PROGRAM_PAGE, in memspi_host_program_page()
184 .command = CMD_READ, in memspi_host_read()
197 .command = wp ? CMD_WRDI : CMD_WREN in memspi_host_set_write_protect()
|
| D | spi_flash_chip_mxic_opi.c | 73 t.command = CMD_OPI_FLASH_MXIC(CMD_WRDI); in spi_flash_chip_mxic_opi_set_write_protect()
75 t.command = CMD_OPI_FLASH_MXIC(CMD_WREN); in spi_flash_chip_mxic_opi_set_write_protect()
103 .command = CMD_OPI_FLASH_MXIC(CMD_RDID), in spi_flash_chip_mxic_opi_read_id()
138 .command = CMD_OPI_FLASH_MXIC(CMD_RDSR), in spi_flash_chip_mxic_opi_read_reg()
180 .command = CMD_OPI_FLASH_MXIC_CHIP_ERASE, in spi_flash_chip_mxic_opi_erase_chip()
208 .command = CMD_OPI_FLASH_MXIC(CMD_SECTOR_ERASE_4B), in spi_flash_chip_mxic_opi_erase_sector()
237 .command = CMD_OPI_FLASH_MXIC(CMD_LARGE_BLOCK_ERASE_4B), in spi_flash_chip_mxic_opi_erase_block()
266 .command = CMD_OPI_FLASH_MXIC(CMD_PROGRAM_PAGE_4B), in spi_flash_chip_mxic_opi_page_program()
319 .command = CMD_OPI_FLASH_MXIC_RDCR2, in spi_flash_chip_mxic_opi_get_io_mode()
|
| /hal_espressif-latest/components/bt/host/bluedroid/hci/ |
| D | hci_layer.c | 251 BT_HDR *command, in transmit_command() argument
256 hci_cmd_metadata_t *metadata = HCI_GET_CMD_METAMSG(command); in transmit_command()
259 assert(command->layer_specific == HCI_CMD_BUF_TYPE_METADATA); in transmit_command()
264 command->event = MSG_STACK_TO_HC_HCI_CMD; in transmit_command()
267 BTTRC_DUMP_BUFFER(NULL, command->data + command->offset, command->len); in transmit_command()
274 static future_t *transmit_command_futured(BT_HDR *command) in transmit_command_futured() argument
276 hci_cmd_metadata_t *metadata = HCI_GET_CMD_METAMSG(command); in transmit_command_futured()
279 assert(command->layer_specific == HCI_CMD_BUF_TYPE_METADATA); in transmit_command_futured()
288 command->event = MSG_STACK_TO_HC_HCI_CMD; in transmit_command_futured()
320 packet_fragmenter->fragment_and_dispatch(&metadata->command); in event_command_ready()
[all …]
|
| /hal_espressif-latest/tools/esptool_py/docs/en/espefuse/ |
| D | burn-bit-cmd.rst | 6 The ``espefuse.py burn_bit`` command burns bits in efuse blocks by bit number. This is useful when …
26 === Run "burn_bit" command ===
50 === Run "burn_bit" command ===
55 Batch mode is enabled, the burn will be done at the end of the command.
57 === Run "burn_bit" command ===
62 Batch mode is enabled, the burn will be done at the end of the command.
|
| D | adc-info-cmd.rst | 6 The ``espefuse.py adc_info`` command displays information about ADC calibration data stored in eFus…
14 === Run "adc_info" command ===
23 === Run "adc_info" command ===
52 === Run "adc_info" command ===
|
| D | burn-custom-mac-cmd.rst | 6 The ``espefuse.py burn_custom_mac`` command burns a 48-bit Custom MAC Address.
20 This command burns a few eFuse fields:
30 === Run "burn_custom_mac" command ===
59 This command burns a few eFuse fields:
68 === Run "burn_custom_mac" command ===
96 This command burns a given MAC to ``CUSTOM_MAC`` field.
102 === Run "burn_custom_mac" command ===
|
| D | get-custom-mac-cmd.rst | 6 The ``espefuse.py burn_custom_mac`` command prints the Custom MAC Address (``CUSTOM_MAC``).
16 === Run "get_custom_mac" command ===
27 === Run "get_custom_mac" command ===
|
| D | execute-scripts-cmd.rst | 6 The ``espefuse.py execute_scripts`` command executes scripts to burn at one time.
21 …command allows burning all needed efuses at one time based on your own python script and control i…
30 …-help``. To run a efuse command you need to call ``espefuse(esp, efuses, args, 'burn_efuse DISABLE…
31 … go without confirmation just add the ``--do-not-confirm`` flag to the ``execute_scripts`` command.
33 This command supports nesting. This means that one script can be called from another script (see th…
39 …rt from a value to a human-readable as it looks in the table is printed by the ``summary`` command.
78 …command from your production script, you may need to pass ``index`` to get the unique data for eac…
|
| D | dump-cmd.rst | 6 The ``espefuse.py dump`` command allows:
92 …command saves dump for each block into a separate file. You need to provide the common path name `…
98 === Run "dump" command ===
119 To save all eFuse blocks in one file, use the following command:
125 === Run "dump" command ===
|
| D | set-flash-voltage-cmd.rst | 12 The ``espefuse.py set_flash_voltage`` command permanently sets the internal flash voltage regulator…
22 … This command is not supported. The tool prints the error ``set_flash_voltage not supported!``.
47 …ned with individual ``burn_efuse`` commands, but the ``set_flash_voltage`` command makes it easier:
106 === Run "set_flash_voltage" command ===
127 === Run "set_flash_voltage" command ===
148 === Run "set_flash_voltage" command ===
|
| D | burn-block-data-cmd.rst | 6 The ``espefuse.py burn_block_data`` command allows writing arbitrary data (non-key data) from a fil…
8 This command is available in ``espefuse.py`` v2.6 and newer.
28 === Run "burn_block_data" command ===
59 3. This command is not suitable for writing key data which will be used by flash encryption or secu…
|
| D | summary-cmd.rst | 6 …summary`` command reads the eFuses from the chip and outputs them in text or json format. It is al…
117 === Run "summary" command ===
125 The ``espefuse.py summary`` command supports filtering eFuses by name. The eFuses to filter needs t…
131 === Run "summary" command ===
145 === Run "summary" command ===
|
| D | burn-efuse-cmd.rst | 6 The ``espefuse.py burn_efuse`` command burns eFuses. The arguments to ``burn_efuse`` are eFuse name…
19 … eFuses (MAC addresses, keys) can be set with this command, but it's better to use a specific comm…
21 This command supports simultaneous burning of multiple eFuses, it doesn't matter if they are from d…
27 === Run "burn_efuse" command ===
105 If using the ``burn_efuse`` command to configure these pins, always specify the actual GPIO number …
|
| D | check-error-cmd.rst | 6 …or`` command checks eFuse errors. It triggers several reads to force the eFuse controller to reloa…
44 === Run "check_error" command ===
69 === Run "check_error" command ===
|
| /hal_espressif-latest/components/bt/host/bluedroid/hci/include/hci/ |
| D | hci_layer.h | 77 typedef void (*command_status_cb)(uint8_t status, BT_HDR *command, void *context);
88 BT_HDR *command,
94 future_t *(*transmit_command_futured)(BT_HDR *command);
|
| /hal_espressif-latest/tools/esptool_py/docs/en/advanced-topics/ |
| D | serial-protocol.rst | 23 The host computer sends a SLIP encoded command request to the ESP chip. The ESP chip responds to th…
37 Each command is a SLIP packet initiated by the host and results in a response packet. Inside the pa…
55 …ata payload (0-65535 bytes, as indicated by Size parameter). Usage depends on specific command. |
61 Each received command will result in a response SLIP packet sent from the ESP chip to the host. Con…
76 | 4-7 | Value | Response value used by READ_REG command (see below). Zero otherwise. …
84 The final bytes of the Data payload indicate command status:
149 …r codes. They all take the form ``0xC*``, or ``0xFF`` for "unimplemented command". (`Full list her…
151 After sending a command, the host should continue to read response packets until one is received wh…
168 …ord: ``0`` to reboot, ``1`` to run user code. Not necessary to send this command if you wish to st…
192 …ord: ``0`` to reboot, ``1`` to run user code. Not necessary to send this command if you wish to st…
[all …]
|
| D | spi-flash-modes.rst | 55 …`` mode, the host uses the "Dual Output Fast Read" (3BH) command to read data. Each read command a…
58 …dio`` mode, the host uses the "Dual I/O Fast Read" (BBH) command to read data. Each read command i…
61 For ESP chips, 32 bytes is read per command and ``dio`` mode is approximately 5% faster than ``dout…
72 …ut`` mode, the host uses the "Quad Output Fast Read" (6BH) command to read data. This command is t…
74 In ``qio`` mode, the host uses the "Quad I/O Fast Read" (EBH) command to read data. This command is…
86 …fy the flash chip visually, or by using the :ref:`esptool.py flash_id <read-spi-flash-id>` command.
|
| /hal_espressif-latest/components/hal/ |
| D | spi_flash_hal_common.inc | 81 uint32_t command,
95 * will go into a "continuous (XIP)" mode, where the command field will be skipped in the next
133 if (command >= 0x100) {
134 spi_flash_ll_set_command(dev, command, 16);
136 spi_flash_ll_set_command(dev, command, 8);
152 uint16_t command;
155 command = trans->command;
161 … host->driver->configure_host_io_mode(host, command, trans->address_bitlen, dummy_bitlen, io_mode);
|
| /hal_espressif-latest/components/wpa_supplicant/esp_supplicant/src/ |
| D | esp_dpp.c | 415 char *command = (char *)evt->data; in esp_dpp_task() local
418 s_dpp_ctx.id = dpp_bootstrap_gen(s_dpp_ctx.dpp_global, command); in esp_dpp_task()
422 os_free(command); in esp_dpp_task()
604 char *command = os_zalloc(1200); in esp_supp_dpp_bootstrap_gen() local
607 if (!uri_chan_list || !command || params->num_chan >= 14 || params->num_chan == 0) { in esp_supp_dpp_bootstrap_gen()
609 if (command) { in esp_supp_dpp_bootstrap_gen()
610 os_free(command); in esp_supp_dpp_bootstrap_gen()
618 os_free(command); in esp_supp_dpp_bootstrap_gen()
630 os_free(command); in esp_supp_dpp_bootstrap_gen()
638 os_snprintf(command, 1200, "type=qrcode mac=" MACSTR "%s%s%s%s%s", in esp_supp_dpp_bootstrap_gen()
[all …]
|
