WARP Project Forums - Wireless Open-Access Research Platform

You are not logged in.

#1 2019-Dec-11 02:13:14

Ayan_Chatterjee
Member
Registered: 2019-Oct-31
Posts: 15

Regarding Generation of Linker Script in SDK Workspace

In SDK Workspace of "Mango_802.11_RefDes_v1.7.7" you have given 5 C-projects.

When I want to generate linker Script for each one of the projects, it is asking for "Place Code Sections", "Place Data Sections" and "Place Heap and Stack Memory".

In that it is given with Multiple Options including

1) mb_high_ilmb_bram_cntlr_0_mb_high_dlmb_bram_cntlr_0
2) mb_high_ilmb_bram_cntlr_1_mb_high_dlmb_bram_cntlr_1
3) pkt_buff_tx_bram_ctrl_S_AXI_BASEADDR
4) pkt_buff_rx_bram_ctrl_S_AXI_BASEADDR
5) mb_high_aux_bram_ctrl_S_AXI_BASEADDR
6) ddr3_sodimm_S_AXI_BASEADDR

It is showing below Error.

-------------------------------------------------------------------------------------------------------------

c:/xilinx/14.7/ise_ds/edk/gnu/microblaze/nt/bin/../lib/gcc/microblaze-xilinx-elf/4.6.4/../../../../microblaze-xilinx-elf/bin/ld.exe: wlan_mac_high_ap.elf section `.text' will not fit in region `mb_high_ilmb_bram_cntlr_0_mb_high_dlmb_bram_cntlr_0'
c:/xilinx/14.7/ise_ds/edk/gnu/microblaze/nt/bin/../lib/gcc/microblaze-xilinx-elf/4.6.4/../../../../microblaze-xilinx-elf/bin/ld.exe: section .ctors loaded at [00020000,00020007] overlaps section .text loaded at [00000050,0002e33b]
c:/xilinx/14.7/ise_ds/edk/gnu/microblaze/nt/bin/../lib/gcc/microblaze-xilinx-elf/4.6.4/../../../../microblaze-xilinx-elf/bin/ld.exe: section .init loaded at [0002e33c,0002e377] overlaps section .ip_udp_eth_buffers loaded at [000257c0,00030c7f]
c:/xilinx/14.7/ise_ds/edk/gnu/microblaze/nt/bin/../lib/gcc/microblaze-xilinx-elf/4.6.4/../../../../microblaze-xilinx-elf/bin/ld.exe: region `mb_high_ilmb_bram_cntlr_0_mb_high_dlmb_bram_cntlr_0' overflowed by 58264 bytes
./wlan_mac_high_framework/wlan_mac_high.o: In function `wlan_mac_high_init':
C:/Users/NIT/Desktop/Mango_802.11_RefDes_v1.7.7/EDK_Projects/Mango_802.11_RefDes_v1.7.7/SDK_Workspace/wlan-mac-sw/wlan_mac_high_framework/wlan_mac_high.c:1916: undefined reference to `__wlan_exp_eth_buffers_section_start'
C:/Users/NIT/Desktop/Mango_802.11_RefDes_v1.7.7/EDK_Projects/Mango_802.11_RefDes_v1.7.7/SDK_Workspace/wlan-mac-sw/wlan_mac_high_framework/wlan_mac_high.c:1916: undefined reference to `__wlan_exp_eth_buffers_section_end'
collect2: ld returned 1 exit status
make: *** [wlan_mac_high_ap.elf] Error 1

-------------------------------------------------------------------------------------------------------------

I have followed all the procedure given in the link as follows "https://warpproject.org/trac/wiki/Exercises/13_4/IntroToSDK"

Then,what should I choose there?

Offline

 

#2 2019-Dec-11 09:21:53

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: Regarding Generation of Linker Script in SDK Workspace

The five application projects in the 802.11 Ref Design include pre-made linker scripts. The 802.11 apps require linker configuration which is not supported by the "Generate Linker Script" tool. You should use the linker scripts included in the 802.11 SDK projects without modification.

Offline

 

#3 2019-Dec-12 00:50:31

Ayan_Chatterjee
Member
Registered: 2019-Oct-31
Posts: 15

Re: Regarding Generation of Linker Script in SDK Workspace

As you have said without modification the Linker File is to be used.

But we want to add one Custom made "Full Duplex Pre-coder IP" in System.xmp so that it work in Hardware level.

In this regards, I have three doubts:

1) Linker file will allocate the memory space for Data and Program, is there any free space available to add that IP?
2) If free space is there, what will be the starting address where we have to add our IP?
3) So, is it required to change the Linker File if we add our Full Duplex IP in System.xmp?

Please give answer for those three questions individually.

Thanks in advance.

Offline

 

#4 2019-Dec-12 10:12:39

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: Regarding Generation of Linker Script in SDK Workspace

The hardware design (including which IP cores are used, their connections, and each core's memory address allocation) is defined in system.mhs. You should not modify system.xmp. The linker script is only used by the software compilation tools and does not change when new IP cores are added to the hardware design.

Offline

 

#5 2019-Dec-12 11:12:21

Ayan_Chatterjee
Member
Registered: 2019-Oct-31
Posts: 15

Re: Regarding Generation of Linker Script in SDK Workspace

So, how to attach an IP to AXI Bus without changing the connection in System.xmp?

Offline

 

#6 2019-Dec-12 12:22:50

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: Regarding Generation of Linker Script in SDK Workspace

The hardware design is specified in system.mhs (also in the XPS GUI, which modifies system.mhs). system.xmp only sets various project settings for the XPS tool.

Offline

 

Board footer