• Learning center

129. Working principle of constant current and current jump faults 2
In this video, we mainly explain the working principle of constant current and current jump.
Detail
Comments

1

00:00:00,466 --> 00:00:04,766

The maintenance of iPhone startup constant current and current jump faults

2

00:00:05,600 --> 00:00:10,833

In this video, we mainly explain the working principle of constant current and current jump

3

00:00:11,366 --> 00:00:13,733

Let's take a look at how the CPU works

4

00:00:14,566 --> 00:00:18,466

After the CPU has a power supply, clock signal and reset signal,

5

00:00:18,566 --> 00:00:21,133

its internal self-test module starts to work,

6

00:00:22,366 --> 00:00:24,766

and the current will jump slightly once

7

00:00:27,066 --> 00:00:33,300

If the self-test module fails to start, the current will be set directly after starting up,

8

00:00:33,933 --> 00:00:36,633

and the current will be around 50mA

9

00:00:37,833 --> 00:00:40,800

After the self-test module starts successfully,

10

00:00:41,200 --> 00:00:44,533

it will send clock signal and reset signal for the hard disk

11

00:00:45,733 --> 00:00:49,666

After the hard disk has power supply, clock signal and reset signal

12

00:00:50,366 --> 00:00:54,133

the CPU reads the self-test program through the SPI bus

13

00:00:56,200 --> 00:01:01,600

If the working condition of the hard disk is abnormal, or the data cable is disconnected,

14

00:01:01,900 --> 00:01:04,366

it will also cause constant current

15

00:01:05,000 --> 00:01:08,200

At this time, its current will be slightly higher,

16

00:01:08,300 --> 00:01:11,366

and the current is about 60- 70mA

17

00:01:12,866 --> 00:01:16,633

After the CPU self-test module reads the self-test program,

18

00:01:16,900 --> 00:01:21,200

it first test itself, such as the GPU and the upper cover

19

00:01:23,300 --> 00:01:29,533

If the self-test fails, it will lead to constant current or current cycle jump

20

00:01:29,966 --> 00:01:33,733

The current at this time is basically around 100mA

21

00:01:35,366 --> 00:01:38,533

After the self-test of the CPU is completed,

22

00:01:38,933 --> 00:01:42,266

it starts to self-test the devices connected to the bus

23

00:01:42,833 --> 00:01:46,400

Generally, it mainly detects the I2C bus,

24

00:01:46,933 --> 00:01:50,666

and the I2C bus will connect many external devices and chips

25

00:01:51,366 --> 00:01:56,500

If there is a damage or abnormality, there will also be a constant current jump

26

00:01:57,800 --> 00:02:04,033

At this time, the current is not 100mA, but around 100-200mA

27

00:02:04,933 --> 00:02:08,100

If there is no problem with the I2C bus self-test,

28

00:02:08,233 --> 00:02:11,766

the CPU will read the system boot file in the logic chip

29

00:02:12,266 --> 00:02:15,833

Then read the system in the hard disk through the PCIe bus

30

00:02:16,866 --> 00:02:21,033

If there is a problem with the system, or a problem with the logic chip,

31

00:02:21,233 --> 00:02:25,100

it will also cause constant current or current cycle jump

32

00:02:26,400 --> 00:02:31,533

At this time, the current is relatively high, around 300mA

33

00:02:32,866 --> 00:02:37,800

According to the principle, we found that problems with the CPU itself,

34

00:02:37,933 --> 00:02:39,533

problems with the hard disk,

35

00:02:40,233 --> 00:02:45,700

and problems with the I2C bus will also lead to constant current and current jump

36

00:02:47,100 --> 00:02:52,633

In actual maintenance, there is no way to directly judge whether the CPU is good or bad,

37

00:02:53,766 --> 00:02:57,033

and the hard disk can only be replaced to eliminate

38

00:02:58,100 --> 00:03:01,466

In actual measurement, we can only measure the bus

39

00:03:01,933 --> 00:03:06,566

Like these buses, only the I2C bus is convenient for measurement

40

00:03:07,233 --> 00:03:10,333

Like GPU, hard disk and other bus chips,

41

00:03:10,466 --> 00:03:12,100

It's not easy to judge

42

00:03:12,766 --> 00:03:17,833

At this time, we can troubleshoot by brushing the machine and reporting an error

43

00:03:18,733 --> 00:03:24,833

Because Apple's brushing will proceed from the first step to the last step according to the CPU's workflow

44

00:03:26,500 --> 00:03:29,666

If there is a problem in any step during the operation,

45

00:03:30,300 --> 00:03:35,900

it will provide an error code such as 4013, 4014

46

00:03:38,300 --> 00:03:41,500

4013 is generally a problem with the CPU,

47

00:03:41,766 --> 00:03:45,400

and 4014 is generally a problem with the upper cover

48

00:03:45,566 --> 00:03:47,466

Like the CPU and hard disk,

49

00:03:47,933 --> 00:03:52,533

we can troubleshoot their problems by brushing the machine and reporting an error

50

00:03:53,200 --> 00:03:55,200

Ok, that's all for this lesson

No comments yet
Come and write your comments
Links: