FRWY-LS1012A qspi access and ethernet problem

cancel
Showing results for 
Search instead for 
Did you mean: 

FRWY-LS1012A qspi access and ethernet problem

Jump to solution
45 Views
Contributor III

Hello,

I am using a FRWY-LS1012A custom board.

QSPI is  mx25u25645g and eth phy is the same AR8033.

I ported LSDK18.12, but there is a problem with qspi control and Ethernet operation.

After building, the firmware_ls1012afrwy_uboot_qspiboot.img file was written to QSPI using an external MCU.

 

1. QSPI access problem on u-boot

If I do saveenv, I get a fail.

I tried adding the ID to vi drivers/mtd/spi/spi_flash_ids.c, but it doesn't seem to be recognized.

/*{"mx25u25635f", INFO(0xc22539, 0x0, 64 * 1024, 512, RD_FULL | WR_QPP) },*/
{"mx25u25645g", INFO(0xc22539, 0x0, 64 * 1024, 512, RD_FULL | WR_QPP) }, /* new */

=> saveenv
Saving Environment to SPI Flash... SF: unrecognized JEDEC id bytes: c2, 25, 39
*** Warning - spi_flash_probe() failed, using default environment

Failed (-5)
=>

 

2. Cannot create ethernet interface after booting

The default ubuntu rootfs is heavy, so I tested two rootfs as shown below.

 

2.1 flex-builder -i mkrfs -r ubuntu:tiny -a arm64

When ubuntu:tiny rootfs is booted, it will no longer proceed as shown below.

...

[ OK ] Started Getty on tty1.
[ OK ] Reached target Host and Network Name Lookups.
[ OK ] Started Dispatcher daemon for systemd-networkd.
[*** ] A start job is running for dev-ttyS0.device (21s / 1min 30s)

 

2.2 flex-builder -i mkrfs -r debian:tiny:stretch -a arm64

debian:tiny:stretch rootfs is logged on but the ethernet interface is not created.

[ 7.738337] pfe_hw_init
[ 7.740792] CLASS version: 20
[ 7.787386] TMU version: 1011231
[ 7.807831] BMU1 version: 21
[ 7.822016] BMU2 version: 21
[ 7.840523] EGPI1 version: 50
[ 7.860781] EGPI2 version: 50
[ 7.881513] HGPI version: 50
[ 7.900867] HIF version: 10
[ 7.921592] HIF NOPCY version: 10
[ 7.938690] bmu_init(1) done
[ 7.941581] bmu_init(2) done
[ 7.977471] class_init() done
[ 8.071784] tmu_init() done
[ 8.083860] gpi_init(1) done
[ 8.095656] gpi_init(2) done
[ 8.109681] gpi_init(hif) done
[ 8.117983] bmu_enable(1) done
[ 8.121734] bmu_enable(2) done
[ 8.125423] pfe_hif_lib_init
[ 8.128987] pfe_hif_init
[ 8.132032] pfe_hif_alloc_descr
[ 8.135962] pfe_hif_init_buffers
[ 8.140606] pfe_firmware_init
[ 8.144191] pfe 4000000.pfe: Direct firmware load for ppfe_class_ls1012a.elf failed with error -2
[ 8.154196] pfe_firmware_init: request firmware ppfe_class_ls1012a.elf failed
[ 8.161920] pfe_hif_exit
[ 8.174153] pfe_hif_release_buffers
[ 8.177924] pfe_hif_free_descr
[ 8.181672] pfe_hif_lib_exit
[ 8.185178] pfe_hw_exit
[ 8.188151] pfe: probe of 4000000.pfe failed with error -110

Debian GNU/Linux 9 localhost ttyS0

localhost login: root
Password:
Linux localhost 4.9.140 #1 SMP PREEMPT Wed Sep 16 00:28:39 UTC 2020 aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@localhost:~# ifconfig eth0 up
eth0: ERROR while getting interface flags: No such device
root@localhost:~#

 

We would appreciate it if you can tell us what the problem is and how to fix it.

 

Thank you,

Best Regards,

Gyosun.

0 Kudos
1 Solution
28 Views
NXP TechSupport
NXP TechSupport

1. Please define CONFIG_SPI_FLASH_MACRONIX in include/configs/ls1012afrwy.h in u-boot source code.

2. I uploaded tiny image built from LSDK 18.12 release in the following link.

https://drive.google.com/file/d/1P-tuGgYeBZmscex2PRm5WdAzSBokAvaP/view?usp=sharing

Please run the following command to check whether pfe driver sets up successfully.

=> tftp 0xa0000000 nxa22585/ls1012afrwy/lsdk_linux_arm64_LS_tiny.itb

=> bootm 0xa0000000#ls1012afrwy

View solution in original post

0 Kudos
2 Replies
18 Views
Contributor III

Hi yipingwang,

 

After adding CONFIG_SPI_FLASH_MACRONIX to ls1012afrwy.h, it was confirmed that it is recognized normally.

And the second pfe driver problem was solved by unpacking the  linux_lib_firmware_LS_arm64.tgz to the /lib/firmware folder.

Thanks for the help.

 

Best Regards,

Gyosun.

0 Kudos
29 Views
NXP TechSupport
NXP TechSupport

1. Please define CONFIG_SPI_FLASH_MACRONIX in include/configs/ls1012afrwy.h in u-boot source code.

2. I uploaded tiny image built from LSDK 18.12 release in the following link.

https://drive.google.com/file/d/1P-tuGgYeBZmscex2PRm5WdAzSBokAvaP/view?usp=sharing

Please run the following command to check whether pfe driver sets up successfully.

=> tftp 0xa0000000 nxa22585/ls1012afrwy/lsdk_linux_arm64_LS_tiny.itb

=> bootm 0xa0000000#ls1012afrwy

View solution in original post

0 Kudos