imx8qxp Q10.0.0_2.2.0_AUTO_SOURCE select mek_8q_car-userdebug product problem

cancel
Showing results for 
Search instead for 
Did you mean: 

imx8qxp Q10.0.0_2.2.0_AUTO_SOURCE select mek_8q_car-userdebug product problem

Jump to solution
469 Views
relax-wu
Contributor IV

I am a little worried. The SDK I use is Q10.0.0_2.2.0_AUTO_SOURCE. The product I chose at the beginning is mek_8q-userdebug. I have implemented display, touch screen, wifi/Bluetooth.
I am now changing the product to mek_8q_car-userdebug. I reconfigured the device tree, but it cannot be displayed normally, and the i2c bus registration is not successful.

0 Kudos
1 Solution
352 Views
relax-wu
Contributor IV

I have solved this problem
We did not use extended I2C and extended IO chips. When M4 starts, it will perform LVDS display by default and use I2C to control extended IO. M4 will execute the LPI2C_MasterStop function.
Can't pick it out in the while.
The solution is to delete the code used to operate PCA9646PW and PCA9557PW.

 

if ((status & kLPI2C_MasterStopDetectFlag) && (status & kLPI2C_MasterTxReadyFlag))
{
    LPI2C_MasterClearStatusFlags(base, kLPI2C_MasterStopDetectFlag);
    break;
}

View solution in original post

0 Kudos
8 Replies
454 Views
relax-wu
Contributor IV

The print information of flash automotive-10.0.0_2.2.0_image_8qmek.tar.gz in the attachment. kernel.log is our product board, board-kernel.log is the development board

0 Kudos
447 Views
joanxie
NXP TechSupport
NXP TechSupport

do you mean when build Q10.0.0_2.2.0_AUTO by command "lunch mek_8q-userdebug", everything is ok, but when you choose "lunch mek_8q_car-userdebug" to build the source code, the images you flash to the board, you couldn't display normally? 

if yes, but according to the user guide, this bsp version only supports mek_8q_car-userdebug and mek_8q_car2-userdebug, how about use the demo images from nxp official website?

https://www.nxp.com/design/software/embedded-software/i-mx-software/android-os-for-i-mx-applications...

 

0 Kudos
407 Views
relax-wu
Contributor IV

I use automotive-10.0.0_2.2.0_image_8qmek2.tar.gz. It is normal and the I2C bus will be created. But using automotive-10.0.0_2.2.0_image_8qmek.tar.gz, there is no i2c bus created.

0 Kudos
435 Views
relax-wu
Contributor IV

Yes, I have used the official images (automotive-10.0.0_2.2.0_image_8qmek.tar.gz), which is normal on the development board (B0), and its log is board-kernel.log, in our product board ( C0) is abnormal, its log is kernel.log

0 Kudos
396 Views
joanxie
NXP TechSupport
NXP TechSupport

you C0 board is nxp board or customized board? I have downloaded the automotive-10.0.0_2.2.0_image_8qmek.tar.gz to my C0 board successfully, I don't find any issue about this, I attach my log file for reference

0 Kudos
353 Views
relax-wu
Contributor IV

I have solved this problem
We did not use extended I2C and extended IO chips. When M4 starts, it will perform LVDS display by default and use I2C to control extended IO. M4 will execute the LPI2C_MasterStop function.
Can't pick it out in the while.
The solution is to delete the code used to operate PCA9646PW and PCA9557PW.

 

if ((status & kLPI2C_MasterStopDetectFlag) && (status & kLPI2C_MasterTxReadyFlag))
{
    LPI2C_MasterClearStatusFlags(base, kLPI2C_MasterStopDetectFlag);
    break;
}

0 Kudos
370 Views
relax-wu
Contributor IV

The PMIC I currently use is MC33PF8100A0ES.
The official website requires MC33PF8100CCES
I don't know if this has any effect?

pmic.bmp

0 Kudos
382 Views
relax-wu
Contributor IV

thank you for your reply
Yes, I use a custom board, and the important parts are as consistent as possible, such as MIPI-DSI (DS90UB941/8), MIPI-CSI (NVP6324). There are some differences. M4_I2C0 is not used, and the debug ports of A core and M4 are separate.

During the startup of the board, there is no output from the debug port of M4.

Compare your [Com COM49] (2021-01-28_111250).log and confirm again that the i2c bus of the machine is not registered.

[115.922025] read descriptors
[115.924942] read strings
mek_8q:/ # i2cdetect -l
[116.961940] read descriptors
[116.964863] read strings
mek_8q:/ #
[118.005965] read descriptors
[118.008882] read strings

i2c-error.png

0 Kudos