LX2160A-RDB with LSDK2004 Demo firmware cannot drive Ethernet normally

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

LX2160A-RDB with LSDK2004 Demo firmware cannot drive Ethernet normally

Jump to solution
1,202 Views
pengluo
Contributor III
LX2160A-RDB with LSDK2004 Demo firmware cannot drive Ethernet normally,From the log, no obvious abnormality was found during system startup。This problem exists in both LX2160A-RDB and LX2160A-RDB-B。
 
Please see the attachment for specific description。
0 Kudos
1 Solution
1,181 Views
pengluo
Contributor III

thanks! That's the problem.

But the LX2160 burn command needs to be modified,Otherwise, the firmware will not burn successfully.

 

Then deploy them on  FlexSPI 1 with the following command.

=> tftp 0xa0000000 firmware_lx2160ardb_uboot_xspiboot.img

=> sf probe 0:0

=> sf erase 0 +$filesize && sf write 0xa0000000 0 $filesize

=> reset

 

View solution in original post

0 Kudos
2 Replies
1,193 Views
yipingwang
NXP TechSupport
NXP TechSupport

It seems that MC firmware and u-boot image on your target board are too old.

Please download lx2160ardb FlexSPI firmware image as the following.

wget https://www.nxp.com/lgfiles/sdk/lsdk2004/firmware_lx2160ardb_uboot_xspiboot.img

wget https://www.nxp.com/lgfiles/sdk/lsdk2004/firmware_lx2160ardb_rev2_uboot_xspiboot.img

Then deploy them on bank1 of FlexSPI with the following command.

=> tftp 0xa0000000 firmware_lx2160ardb_uboot_xspiboot.img

=> sf probe 0:1

=> sf erase 0 +$filesize && sf write 0xa0000000 0 $filesize

=> qixis_reset altbank

In addition, please check whether the Ethernet port works under u-boot.

=> setenv ethact DPMAC17@rgmii-id

=> setenv ipaddr 172.18.107.90

=> ping 172.18.107.1



 

 

1,182 Views
pengluo
Contributor III

thanks! That's the problem.

But the LX2160 burn command needs to be modified,Otherwise, the firmware will not burn successfully.

 

Then deploy them on  FlexSPI 1 with the following command.

=> tftp 0xa0000000 firmware_lx2160ardb_uboot_xspiboot.img

=> sf probe 0:0

=> sf erase 0 +$filesize && sf write 0xa0000000 0 $filesize

=> reset

 

0 Kudos