You are not logged in.
Pages: 1
Since in our project we adjust the logic of PHY, we have to rebuild the XPS project to get the .bit and .bmm files. But when I try to program the project of SDK to FPGA it gives out a error about the overlapping between code segment and high_ctrl address. I compare the lscript files of v1.7.1 and v1.6.2, and find the problem is cause by the mismatching between the .bmm and lscript. The XPS project of v1.7.1 is the old version project which use two
bram controller for each CPU.Therefore the address matching are not fit for the new structure(high-common-low and has combined bram controller) in SDK project in v1.7.1. Maybe this is the reason for the problem I encountered.
Therefore, the EDK folder should be updated or there are other reasons for the problem.
Offline
See Updating SDK Hardware BMM File in the 802.11 ref design user guide. This process is required when modifying the hardware design starting with design v1.7.0.
Starting in v1.7 we needed to merge the two CPU High LMB areas into a single logical area so the linker could fill the entire space. Ideally we could use a single LMB for this, but we consistently get timing failures when building that design. Hand-editing the .bmm file is the best solution we've found.
Offline
Thanks a lot for the answer.
In fact, the original problem is that after I finished building the bitstream, I copied the .bit and .bmm to SDK_Workspace/Mango_802.11_RefDes_v1.7.0_hw_platform and when I program FPGA the consoler gives the error
ERROR:Data2MEM:31 - Out of bounds code segment for ram space in 'D:\MAP_FI\Mango_802.11_RefDes_v1.7.1-changed\EDK_Projects\Mango_802.11_RefDes_v1.7.1\SDK_Workspace\Mango_802.11_RefDes_v1.7.1_hw_platform\system_bd.bmm'.
Memory space 'mb_high.mb_high_lmb_bram_0_combined' occupies [0x00000000:0x0001FFFF]
Code segment #1 occupies [0x00000050:0x00036FE3]
I repeat the procedure with a replacement of the .bmm and it works!
Maybe I should reread the user guides more carefully.
Offline
I repeat the procedure with a replacement of the .bmm and it works!
Just to clarify - you must modify the system.bmm file generated by XPS, *not* copy the old system.bmm file from our .zip archive. The hardware implementation flow usually assigns new BRAM locations for the LMB blocks on every build (at least every build where anything changed in the design). You must use the .bmm file corresponding to your .bit file, then modify it to merge the ADDRESS_SPACE blocks.
Offline
Also, you should always use the "Export to SDK" process from XPS. This copies the .bit and .bmm files, along with the very important xml file that describes the peripheral list and memory map, required for BSP generation. The .bmm, .bit and .xml files in the SDK hardware project must match.
Offline
Got it. Thanks!
Offline
Pages: 1