Mediate Fuse and É-fuse, all you need to know

🔰(FUSE & e-Fuses)

MediaTek, which disrupts the situation of the potroom that was accessible via:

- Voulme buttons.

- Force preloader to BRom by Da crash.

- Force preloader to BRom with Emergency SoC Reset.

- - Force preloader to BRom by read from address 0 using 32bit/16bit registers read CMD.

- Also by working Downgrade to lower version or creating formats for the basic and secondary bot sector.

- And how come all these things were repaired without the devices breaking apart, or changing the processor settings in the post-production stage.

- How can the setup of the processor itself be changed with a simple OTA, its size does not exceed 300MB.

- And how do companies make an account that it is possible to be hacked at any moment while they make the fuses and use it blow via Hot-patch.

- Theoretically, the subject is complicated, and no one can fully understand it except the person who wrote the code itself, we have tools that analyze the code, and we see what happens superficially, but we can not change the basic code, because it is protected most often and in the process, check like checksum, so instead T letter One in the code, you would have completely frozen the section containing the code.

- All settings are mostly linked to Registers and have many types like (8-bit & 16-bit & 32-bit)

- The preloader code itself contains the efuses and is ready to be applied on the board at any time, and this is a basic method, in all companies secure themselves against any hacking, but the activation stage is a little difficult because it affects the software settings itself, because the company that manufactures the software Treat, cod available One dedicated to the service centers, to operate the devices and the application of fuses affects this code, here they have to write a new code and build a new DA loader, to deal with the fact that the devices are already in the market.

- In short, your media could have locked the gap on the same day it was published, but this would have caused problems for sellers and service centers, and they will not be able to install software for the devices through the tools they have provided by the company that manufactures the processor.

- To explain the matter first, we need to know what is important

Rum and healer and memory

And any one of them is responsible for what, and its impact on the take-off and control code.

This is an abbreviation of important terms to know:

RAM = (Random Access Memory)

CPU = (Central Processing Unit)

GPIO = (General Purpose Input/Output)

- Ram's main task is to transfer data, store data in a form, temporarily, for example, in his book software on memory, the speed of writing and reading here depends on the RAM, not the memory itself, because memory writes and reads data from it, and can not be used at the same time for transfer and writing, Rum means mini memory can be considered.

Memory, its main task is to store, transfer data and retain software.

- The processor is the basis and is responsible for the formation of the device fully, and it is the one who is recognized on the software starting from the off code and verification.

- The term storage may refer to data used in general, and more specifically, an electronic memory device used to store digital data. Think of storage as a book memory, information or data that takes longer to access but is stored and accessible even after computer/mobile is turned off. Storage devices use magnetic or visual media to store information or data.

- CPU needs two types of memory to handle data or instructions: RAM and storage memory. RMS are flying memory chips containing data and the CPU needs to handle instructions. Before the CPU starts processing the data, the AMM loads data quickly and can be erased quickly. People often exchange memory with storage, but there are big differences between the two.

- The most important point, is that the first time you hear the word fuse, you forget that you are playing with the memory or the contact lines that connect you to the processor - I mean, if you separate the memory completely from the device or make shorts, their lines, whether communication or communication lines, will not affect or change anything, because eFuses are in EEPROM On the inside to I2C for the processor, and the device recognizes it before the take-off stage before even USB-INIT, once it is installed here, you will not be able to cancel it except by the same code that you installed or erased RPMB in some cases, which in turn does a reset to the processor code itself but by memory of course, and Count it out the settings The novelty after installing software or modifying it until the processor recognizes the new settings and the responsible value is changed, this is in case the Efuses was installed through AP.

- Surviving the term eFuses itself

(Simplified, it is a technology that allows vendors to control take-off settings and adjust them stage by stage of production),

- This is a simplified explanation for it in general from

according to PSOC programming :

* Electronic Fuses (eFuses) - non-volatile memory whose

* each bit is one-time programmable (OTP). One eFuse macro consists of

* 256 bits (32 * 8 ). The PSoC devices have up to 16 eFuse macros.

* - eFuses are used to control the device protection settings.

* - eFuse memory can be programmed (eFuse bit value changed from '0' to '1')

* only once; if an eFuse bit is blown, it cannot be cleared again;

* - programming fuses requires the associated I/O supply to be at a specific level.

* The e-Fuses structure container main flag value could look or be defined this way :

* - 0x00 - Not blown;

* - 0x01 - Blown;

* - 0xFF - Ignore.

Credit : Mofadal El-Tayeb

Related Posts

Share this post

Subscribe Our Newsletter