Kernel panic problem when switching from MCIMX7U3DVK07SC to MCIMX7U3DVK07SD chip (Rev B1 to B2))

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

Kernel panic problem when switching from MCIMX7U3DVK07SC to MCIMX7U3DVK07SD chip (Rev B1 to B2))

3,149 Views
budulger
Contributor II

Hi all,

 

We are having kernel panic problem in our production after changing the processor revision for IMX7ULP processors from MCIMX7U3DVK07SC to MCIMX7U3DVK07SD (revision B1 to B2).

 

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007 Kernel panic - not syncing: No working init found. Try passing init= option to kernel.

We are using the same uboot and image for the production, we were not passing the init= parameter to the bootargs before, could it related to it? or there is another problem when changing from different revisions?

We are pointing to a source code of uboot dated around 20 May 2022, should we make any update for the uboot? (https://source.denx.de/u-boot/u-boot/)

I didn't encounter any change related to revision and when I examined the silicon revision document from B1 to B2, also it claims there should not be any software or hardware differences? 

https://www.nxp.com/docs/en/engineering-bulletin/EB00911.pdf

 

Could it be related to mask set errata?  https://www.nxp.com/docs/en/errata/IMX7ULPCE.pdf

https://www.nxp.com/docs/en/errata/IMX7ULP_2N54W.pdf

 

Can you help me to solve the problem? I can provide more information if needed.

 

Regards

Burak

 

Labels (3)
13 Replies

3,109 Views
budulger
Contributor II

Hi @Rita_Wang ,

 

We are using the meta-imx version of NXP pointing to this version 

https://github.com/nxp-imx/meta-imx/tree/a0303c88a5abf96cbe3e4dccd339a323aad726fa

It is made custom for the application and version 5.15.71 linux kernel is used. U-boot version is 2022.07.

I couldn't find the specific 2.2.0 , 2.2.1 or 2.2.2  version of the linux version.

 

But the chips are using exactly the same uboot and image . only difference is silicon revision B1 and B2.

I have limited log from production, I attach both logs here. They will ship the device into me within the day, I will have more information.

I was not part of the team, when this version is released, and nobody is working for the company in these days that worked for the project. If I give insufficient info, ask for more. I will do my best

Thanks for your help.

 

0 Kudos
Reply

3,067 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

I see that the two log are the download log, not for the boot up.

They can all finishing download images to board well.

0 Kudos
Reply

3,063 Views
budulger
Contributor II

As the devices didn't boot up, this is all we get from UART. Normally we make ssh to check the kernel messages. @Rita_Wang 

0 Kudos
Reply

2,302 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Hi @budulger ,

How about the status in your side? Can  MCIMX7U3DVK07SD work with new version BSP?

If still not work tell us.

Wish you have a nice day

Best Regards

Rita

0 Kudos
Reply

2,550 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Hi @budulger ,

The version BSP you are using is the LF5.15.52_2.1.0, it is too old for the MCIMX7U3DVK07SD. 

So here recommend you to choose newest or newer BSP version Embedded Linux for i.MX Applications Processors | NXP Semiconductors.

If stll not work tell us.

Wish you have a nice day

Best Regards

Rita

0 Kudos
Reply

3,057 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Can board boot up well with the MCIMX7U3DVK07SC?

0 Kudos
Reply

3,053 Views
budulger
Contributor II
yes, it can boot up without problem,

The chips in question were sealed on 06-Dec-2024, possibly affected by the NXP mask
0 Kudos
Reply

3,085 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Both 2.2.0 , 2.2.1 or 2.2.2 are our GA version:

Rita_Wang_0-1745902680744.png

GitHub - nxp-imx/meta-imx at kirkstone-5.15.71-2.2.0

Which one are you using?

0 Kudos
Reply

3,070 Views
budulger
Contributor II

Hi @Rita_Wang ,

Right now I figured it out,

meta-imx layer is 5.15.52-2.1.0,  with srcrev = 36363d8623ba60858e2632b7d2b70dae932c9a8b

But they made a custom layer on top of it, and customized the 5.15.52-2.1.0 version.

Sorry for confusion.

Regards

Burak

 

0 Kudos
Reply

3,064 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Hi @budulger ,

For this two version chip, are you using the same code?

You can share it to us, and due to the labor holiday in our china, I will leave work now and back to work on the 7th May, I will help check it then.

If your questions is urgent you can try to creat new cases in our website, Support | NXP Semiconductors

If not urgent, you can wait for me back. Thanks.

Wish you have a nice day

Best Regards

Rita

0 Kudos
Reply

3,062 Views
budulger
Contributor II
we are using exactly the same code for these chips, it is kinda urgent issue. I will post it into support also
0 Kudos
Reply

3,006 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

OK, i will help check when I back from holiday.

0 Kudos
Reply

3,122 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Dear @budulger ,

You mean here:"We are having kernel panic problem in our production after changing the processor revision for IMX7ULP processors from MCIMX7U3DVK07SC to MCIMX7U3DVK07SD (revision B1 to B2)."

Q: Which version BSP we supply are you using? Embedded Linux for i.MX Applications Processors | NXP Semiconductors

For this two version chip, are you using the same code, do not changing anything?

Could you share the full log for both board with these two chips running?

We need the details to find the root cause as soon as possible. Thanks

Wish you have a nice day

Best Regards

Rita

0 Kudos
Reply