Cannot boot LX2160A-RDB

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

Cannot boot LX2160A-RDB

7,793 Views
diljithka
Contributor I

I am currently using LX2160A-RDB board . The board is failing in the U-boot sequence immediately after detecting the DDR.("Waiting for D_INIT timeout. Memory may not work."). I tried with different DDR with the same clock frequency,but still the error is showing .Is there any suggestion in why this is happening?? How can this issue be  resolved?image.png

0 Kudos
Reply
16 Replies

6,113 Views
Madhan
Contributor I

Do you guys find any Solution i am also getting same error? 
i used to work fine but now it is not working. 

 

 

 

0 Kudos
Reply

7,781 Views
ufedor
NXP Employee
NXP Employee

Is the board brand new?

I'm asking because Rev.1 silicon is obsolete and is not supported anymore.

0 Kudos
Reply

7,773 Views
diljithka
Contributor I

The board is not Rev.1 silicon.

0 Kudos
Reply

7,768 Views
ufedor
NXP Employee
NXP Employee

Rev.jpg

0 Kudos
Reply

7,765 Views
diljithka
Contributor I

Really sorry for the mistake.

Actually this board was working fine few days back. I am not really understanding what has happened to the board.we are really stuck with this issue. Is there any way that you can bring me out of this. we really cannot move forward without solving this DDR issue.

0 Kudos
Reply

7,757 Views
ufedor
NXP Employee
NXP Employee

Please try to re-seat the DDR SDRAM modules.

0 Kudos
Reply

7,746 Views
diljithka
Contributor I

We have tried changing the DDR modules multiple times but still the board is showing the same issue

0 Kudos
Reply

7,741 Views
ufedor
NXP Employee
NXP Employee

Please use CodeWarrior and re-program composite firmware binary image available at:

https://lsdk.github.io/components.html

section LSDK IMAGES (for silicon Rev1.0 use LSDK 20.04 or earlier).

0 Kudos
Reply

7,727 Views
diljithka
Contributor I

In the link provided https://lsdk.github.io/components.html there is no image for REV 1.

Screenshot from 2021-02-18 16-40-18.png

So i tried using the composite image provided in the lsdk 20.04 document.Screenshot from 2021-02-18 16-36-43.pngI had followed the steps to recover the board using the
CodeWarrior tool, see section " 8.6 Board Recovery " in ARM V8 ISA, Targeting Manual.

But still i am not able to boot the board. This is the error which i am getting.

Screenshot from 2021-02-18 16-35-17.png

 

0 Kudos
Reply

7,708 Views
ufedor
NXP Employee
NXP Employee

> In the link provided https://lsdk.github.io/components.html there is no image for REV 1.

Use drop-down selector at the top of the page:

drop.jpg

0 Kudos
Reply

7,698 Views
diljithka
Contributor I

Hi

Thanks for the support. I had downloaded the 19.09 image.and tried flashing using code warrior studio.Still i am getting the error.

  • The image which i used is :  firmware_lx2160ardb_uboot_xspiboot.img.
  • And have flashed this image using code warrior studio.
  • codewarrior.png
  • Then power-cycled the board
  • On power-On the board get stuck here
  • Screenshot from 2021-02-19 15-30-08.png
  • Please correct if the steps which i followed is wrong or if i had missed any steps .
  • How can these issues be solved?
  •  

 

 

 

 

 

0 Kudos
Reply

7,694 Views
ufedor
NXP Employee
NXP Employee

Check all on-board configuration switches and set them into default positions.

0 Kudos
Reply

7,690 Views
diljithka
Contributor I

On board switches are already set to default as per the document.

Screenshot from 2021-02-19 15-59-32.png

0 Kudos
Reply

7,686 Views
ufedor
NXP Employee
NXP Employee

Firmware which you programmed has RCW setting 2900 MT/s data rate, but installed modules support only 2600.

Please try attached firmware.

0 Kudos
Reply

7,682 Views
diljithka
Contributor I

I used the attached  firmware , but still board didn't came up.

Screenshot from 2021-02-19 17-22-36.png

Tags (1)
0 Kudos
Reply

7,670 Views
ufedor
NXP Employee
NXP Employee

According to the log the last firmware image is the same as it was originally.

It seems that the processor was damaged (may be by a ESD).

0 Kudos
Reply