Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maaxboard make error #2

Open
iamblue opened this issue Dec 18, 2022 · 1 comment
Open

maaxboard make error #2

iamblue opened this issue Dec 18, 2022 · 1 comment

Comments

@iamblue
Copy link

iamblue commented Dec 18, 2022

I tried this command:

make maaxboard_defconfig
make

it shows:

  LD      arch/arm/cpu/armv8/built-in.o
ld.bfd: arch/arm/cpu/armv8/cpu.o:移位於通用 ELF (EM: 183)
ld.bfd: arch/arm/cpu/armv8/cpu.o:移位於通用 ELF (EM: 183)
ld.bfd: arch/arm/cpu/armv8/cpu.o:移位於通用 ELF (EM: 183)
ld.bfd: arch/arm/cpu/armv8/cpu.o:移位於通用 ELF (EM: 183)
ld.bfd: arch/arm/cpu/armv8/cpu.o:移位於通用 ELF (EM: 183)
ld.bfd: arch/arm/cpu/armv8/cpu.o:移位於通用 ELF (EM: 183)
ld.bfd: arch/arm/cpu/armv8/cpu.o:移位於通用 ELF (EM: 183)
arch/arm/cpu/armv8/cpu.o: 無法加入符號: 檔案格式錯誤
scripts/Makefile.build:355: recipe for target 'arch/arm/cpu/armv8/built-in.o' failed
make[1]: *** [arch/arm/cpu/armv8/built-in.o] Error 1
Makefile:1728: recipe for target 'arch/arm/cpu/armv8' failed
make: *** [arch/arm/cpu/armv8] Error 2

But I ARCH in enviroment is correct is arm64. how to solve this problem ?

@zafersn
Copy link

zafersn commented Jun 12, 2023

Hi @iamblue . When I try with this commands I am not getting any error:

export AARCH64_GCC_CROSS_COMPILE=/opt/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-


to build only bootloader first set board config
	make maaxboard_defconfig
then
	make CROSS_COMPILE=${AARCH64_GCC_CROSS_COMPILE} -j8

david-fuu pushed a commit that referenced this issue Jun 28, 2024
The driver exists two issues:
1. For RX buffer, current driver release the buffer too early, should
   wait until free_pkt callback is called. Otherwise, the released
   buffer will put into rx bd ring again and may be used by enetc when
   uboot is processing the packet.

2. The RX BD size is only 16 bytes, but cache line is 64 bytes on iMX95,
   so when flush a free RX BD to submit it ring, the flush may write
   adjacent BDs which locate in same cache line into memory. It has the
   possibility that netc has used (filled) this adjacent BD before uboot
   processes it. So the BD content is overwritten. It will cause polling
   Ready bit of this BD always failed. We already observed such issue
   in 1000Mbps network.

The patch added the free_pkt call back implementation for issue #1. And
for issue #2, it adjusts to submit BDs in cache line size to ring.
For example, on iMX95, we submit 4 RX BDs which are in one cache line.
The cache operations are also re-fined in the patch with clean codes.

Signed-off-by: Ye Li <[email protected]>
Reviewed-by: Peng Fan <[email protected]>
Acked-by: Wei Fang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants