issue about i.MX6 Thermal

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

issue about i.MX6 Thermal

1,131 Views
宗標廖
Contributor V

Hello,Community

I did some tests as bellow.

1)TEST1:

I startup i.MX6DLSabreauto with BSP3.14.52 and  use HDMI as display.

Then I set the passive point of thermal to 65 degree(default is 85),and then I startup /opt/viv_samples/vdk/tutorial3 to make SoC in heavy loading.

When temperature of SoC reached 65 degree, kernel output logs as bellow:

System is too hot. GPU3D will work at 1/64 clock.

imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00100000

imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00800000

and the HDMI became to display nothing.

2)TEST2

Use LVDS as display,the other steps are the same as TEST1.

When temperature of SoC reached 65 degree, kernel output logs as bellow:

System is too hot. GPU3D will work at 1/64 clock.

and the LVDS still works normally.

3)TEST3

Use BSP3.0.35_4.1.0, the other steps are the same as TEST1.

When temperature of SoC reached 65 degree, GPU3D will work at 1/64 clock.

And HDMI still works normally.

So please tell me the reason of the abnormal result in TEST1.

Labels (3)
0 Kudos
3 Replies

524 Views
igorpadykov
NXP Employee
NXP Employee

Hi Zongbiao

latest releases implemented ARM845369 which may lead

to performance drop, one can check

i.MX6SX: ARM_ERRATA_845369 applied?

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 Kudos

524 Views
宗標廖
Contributor V

Hi igor

Thank you for you reply.

I commented out #define CONFIG_ARM_ERRATA_845369 in u-boot, and rebuilt the u-boot,but got the same result.

Best Regards,

ZongbiaoLiao

0 Kudos

524 Views
igorpadykov
NXP Employee
NXP Employee

Hi ZongbiaoLiao

one can debug it using memory profiling tool

included in imx-test package (mmdc folder),

www.nxp.com/lgfiles/NMG/MAD/YOCTO/imx-test-5.4.tar.gz

described in sect.44.7 MMDC Profiling i.MX6DQ RM.

~igor

0 Kudos