The EDL Utility is a Win32 utility for accessing the Qualcomm Emergency Download interface on Qualcomm processors.
Aprende a exportar tus trabajos, como por ejemplo, a formato PDF para presentar planos técnicos.
Descargar "El Gran Libro de Autodesk Inventor PDF Gratis": Mitos y Realidades
: Un enfoque práctico para principiantes sobre modelado digital. Academia.edu ¿Necesitas ayuda con algún comando específico de Inventor o buscas una guía para una versión particular del software? El gran libro de Autodesk Inventor®
, is a comprehensive technical guide designed for users who want to master Autodesk Inventor, a leading 3D mechanical design software. First published in Marcombo/Alfaomega el gran libro de autodesk inventor pdf gratis libro work
user wants a long article about "el gran libro de autodesk inventor pdf gratis libro work". I need to follow the search plan. The first step is to search for the book and free PDF options. I will perform the searches as outlined. search results show several potential sources for the book. I need to open them to gather more information. I'll start with the most relevant ones: result 0 from the first search, result 0 from the second search, result 1 from the fifth search, and result 3 from the third search. user's question is about "el gran libro de autodesk inventor pdf gratis libro work". My response will be a long article about this book. I will structure it as follows: an introduction, a detailed description of the book's content, information about the author, legal methods to access the book, other free resources for learning Autodesk Inventor, and a conclusion. I will cite the sources I've found. “El Gran Libro de Autodesk Inventor”: Guía Completa y Recursos Gratuitos (PDF)
Es un texto técnico que abarca la interfaz del usuario, el modelado de piezas, la creación de ensamblajes y la generación de planos normalizados. Explica el porqué de cada herramienta y las reglas del diseño paramétrico.
The following essay explores the significance of this work and the broader impact of Autodesk Inventor on modern engineering. Aprende a exportar tus trabajos, como por ejemplo,
: Existen varios sitios web y foros dedicados a compartir conocimientos y recursos para software de diseño asistido por computadora (CAD), como GrabCAD, Reddit (r/AutodeskInventor), y otros foros especializados. Aunque ten cuidado con los recursos que descargas de sitios no oficiales, ya que podrían contener malware.
En resumen, "El Gran Libro de Autodesk Inventor" es un recurso excepcional para cualquier persona interesada en aprender y mejorar sus habilidades en Autodesk Inventor. La calidad del contenido, la estructura lógica y los ejemplos prácticos hacen de este libro una herramienta indispensable para diseñadores, ingenieros y arquitectos que trabajan con esta herramienta.
El gran libro de Autodesk Inventor " by Francisco Grande is a comprehensive manual designed for users with basic knowledge who want to deepen their mastery of parametric design. While it is a commercial publication, you can find official previews and related educational resources online. Book Content & Structure El gran libro de Autodesk Inventor® , is
The following table summarizes the legitimate and safe methods to access the content:
Aunque la búsqueda de material gratuito ("gratis") es común, es importante destacar que los libros técnicos de calidad suelen tener derechos de autor. Sin embargo, existen opciones legítimas y legales para obtener este conocimiento:
La misma Autodesk ofrece tutoriales gratuitos y documentación completa en su sitio web. Alternativas de Aprendizaje Práctico (PDF)
Extrusiones, revoluciones, vaciados y operaciones 3D complejas.
: A veces, Autodesk ofrece recursos educativos y materiales de aprendizaje gratuitos para sus productos, incluido Inventor. Puedes visitar el sitio web oficial de Autodesk y buscar en su sección de soporte o educación para ver si tienen algún material disponible.
The usage has changed and /e is only for erasing NAND memories.
To zero out sections of eMMC or UFS use the new /f fill command.
/u takes a hexadecimal value.
This should make no difference on the standard LUNs (0-7) but will make things clearer on LUNs 81, b0, c4, d0.
Qualcomm processors support two different protocols, "Sahara" and "Firehose". Sahara is supported in ROM and is always present. Firehose is implemented in downloadable loaders in ELF format.
The usual procedure is to first get your device in EDL mode, i.e. where it is presenting USB VID/PID 05c6/9008. This can be achieved by:
Everything under Windows needs some kind of driver. Zadig is a simple generic driver generator. Select "WinUSB" as the type of driver to install. Do NOT use any Windows drivers from Qualcomm. They will try to present your device as a serial port. Now you can do a simple check if you like.
This shows you that the device is connected and has the right driver.
Next, you must use the Sahara protocol to load a loader for the Firehose protocol.
Loaders are specific to processor, device manufacturer, possibly flash memory type and hash.
To decide which one you need you need to collect some basic info.
There are reports that Sahara protocol version 3.0 does not support querying the HWID or Hash.
If this happens to you, use the /qbc quirk (see below).
These files often use .bin or .mbn as the extension despite it actually being a normal ELF file. The file names are based on the 16 hexit HWID and the first 16 hexits of the Hash. By one website they are listed under the last 8 hexits of the Hash. As the filenames tend to be cumbersome, you might rename them something short and mnemonic.
To look up available loaders by Hash see this table.
For Boox Onyx devices see this table.
From this point on the processor is using the Firehose protocol and you need not (can not) reload the loader unless you reboot.
A device might be using eMMC storage (older devices), NAND storage or UFS storage (newer devices).
The /u flag must be used for all operation in Firehose on devices with UFS.
The flags /d (slot), /u (LUN), /p (partition), /s (start block), /c (count of blocks) and /b (block size) are used to specify the range of operation.
If the partition is specified then the start block is relative to the start of the partition.
If partition is not specified, then the start block is absolute.
Zero is the default for both start block and count of blocks.
Partition operations often do not specify either start block or count of blocks.
Operations on raw devices (i.e. not a partition) require an explicit /s and /c to prevent accidents like edl /f.
| Start | Count | Partition | |
|---|---|---|---|
| Unspecified | Specified | ||
| 0 | 0 | Whole device | Whole partition |
| 0 | + | Start of device | Start of partition |
| + | + | Middle of device | Middle of partition |
| + | 0 | End of device | End of partition |
| − | 0 | End of device | End of partition |
| − | + | Part of end of device | Part of end of partition |
The major operations are /r (read), /e (erase), /w (write).
The erase and write operations can be combined which yields the non-optimized operations of full erase and (possibly) partial write (depending on the size of the input file).
Be very careful when you specify /e (erase), /w (write) as not specifying a partition means the whole device!
Partitions are sized for the maximum anticipated size of the contents.
Often the fraction of a partition that is actively being used is as low as 20%.
(There are often many partitons with all zeroes in them also.)
There is no particular need to transfer a whole partition when 20% will do.
Of course, if you still want to transfer another 50MB of zeroes, just don't use the /t flag.
Also note that some images have signing or other (sometimes) necessary things after the end of the normal image.
Currently the EDL utility has the capability to recognize the actual size of:
Android images are naturally aligned to pagesize (normally 4096 bytes) but ELF files can be any size. Therefore, when they are read, even when truncated, they are rounded up to the current device blocksize (normally 512 or 4096 bytes). This simplifies matters when/if they are written back to the device.
NAND memory has two peculiarities that require special handling. The first peculiarity is that they have "bad blocks" (an erase block is sometimes 64 x 4096 bytes). During a read the output file will be filled with 0xff wherever bad blocks are to maintain alignment. During a write the input file will be skipped over wherever bad blocks are to maintain alignment. The second peculiarity is that because of the hidden CRC32 and ECC on each page, a freshly erased page must never be written with all 0xff values. The EDL utility will do explicit multiple writes (in the hundreds) around the bad blocks and the empty pages. The EDL utility will do explicit multiple reads (a few) around the bad blocks. You must explicitly erase whichever region of the NAND memory before writing but this may be combined in the same command. The EDL utility now supports NAND volume tables analogously to GPT partition tables.
Quirks are idiosyncracies, anomalies or incorrect implementations of Firehose loaders.
By specifying the /q flag you can bypass problematic parts.
/qabcd, for example, will not query serial number, HWID, hash or SBL version.
There is a default of /qad so you need to /q to display serial number and SBL version.
| A | Do not query serial number |
| B | Do not query HWID |
| C | Do not query hash |
| D | Do not query SBL version |
| E | Allow CSD read to fail (Sony Vivo) |
Show usage:
Query basic info:
Load a loader (needs to be done only once after a fresh start):
List the partitions:
Download the MBR of a UFS LUN:
Download the boot partition (and truncate to its actual size):
Erase the the last 4096 bytes of /vendor (removes FEC correction):
Flash the recovery partition:
Erase and write to NAND memory blocks:
Read accessory SD card:
Try some random XML:
Reboot to normal system:
Reboot to fastboot (probably only works on Motorola):
Multiple compatible commands, reboot to recovery:
Download edl.exe, the EDL utiliy.
Download ubi.exe, a simple utility for examining full dumps of NAND/UBI.
See also: QcomView – a utility for analyzing Qualcomm xbl/abl/Firehose loaders