lowRISC / lowrisc-chip

The root repo for lowRISC project and FPGA demos.
http://www.lowrisc.org/
Other
596 stars 148 forks source link

Segmentation Error #91

Closed clare7 closed 6 years ago

clare7 commented 6 years ago

Hi, I keep facing the error when I run the

<> it has no problem with <> so the problems only came at make target. Any advice?

INFO: [Common 17-83] Releasing license: Implementation write_bitstream: Time (s): cpu = 00:01:05 ; elapsed = 00:01:13 . Memory (MB): peak = 3507.039 ; gain = 0.000 ; free physical = 8960 ; free virtual = 117162 INFO: [Vivado_Tcl 4-395] Unable to parse hwdef file chip_top.hwdef INFO: [Common 17-206] Exiting Vivado at Mon May 21 10:06:51 2018... [Mon May 21 10:06:55 2018] impl_1 finished wait_on_run: Time (s): cpu = 00:00:00.26 ; elapsed = 00:10:15 . Memory (MB): peak = 1052.715 ; gain = 0.000 ; free physical = 11447 ; free virtual = 119649 INFO: [Common 17-206] Exiting Vivado at Mon May 21 10:06:55 2018... vivado -mode batch -source ../../common/script/search_ramb.tcl -tclargs lowrisc-chip-imp > search-ramb.log python ../../common/script/bmm_gen.py search-ramb.log src/boot.bmm 128 65536 data2mem -bm src/boot.mem -bd src/boot.mem -bt lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.bit -o b lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit /opt/Xilinx/SDK/2015.4/bin/loader: line 164: 16352 Segmentation fault (core dumped) "$RDI_PROG" "$@" Makefile:200: recipe for target 'lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit' failed make[1]: [lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit] Error 139 make[1]: Leaving directory '/home/mmwong/Documents/lowrisc-chip/fpga/board/nexys4_ddr' Makefile:230: recipe for target 'selftest' failed make: [selftest] Error 2

wsong83 commented 6 years ago

The error is related to the data2mem command provided by Xilinx SDK

data2mem -bm src/boot.mem -bd src/boot.mem -bt lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.bit -o b lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit /opt/Xilinx/SDK/2015.4/bin/loader: line 164: 16352 Segmentation fault (core dumped) "$RDI_PROG" "$@"

I suggest you to check the grammar for this command and whether all files needed are accessible and valid (not corrupted somehow). Regenerate each file if necessary. Run the command alone in shell (without the Make/Python) can be helpful as well. If all those failed, try another version of Xilinx, (downgrade is more promising than upgrade)

jrrk commented 6 years ago

As Wei says, this error is usually due to an incorrect (usually empty) input file due to a failed previous stage. Try make vivado and check for errors and/or make cleanall then try again.

Sent from my iPhone

On 21 May 2018, at 04:05, Wei Song (宋威) notifications@github.com wrote:

The error is related to the data2mem command provided by Xilinx SDK

data2mem -bm src/boot.mem -bd src/boot.mem -bt lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.bit -o b lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit /opt/Xilinx/SDK/2015.4/bin/loader: line 164: 16352 Segmentation fault (core dumped) "$RDI_PROG" "$@"

I suggest you to check the grammar for this command and whether all files needed are accessible and valid (not corrupted somehow). Regenerate each file if necessary. Run the command alone in shell (without the Make/Python) can be helpful as well. If all those failed, try another version of Xilinx, (downgrade is more promising than upgrade)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

clare7 commented 6 years ago

all the files are valid and available and running the command alone is successful

data2mem -bm src/boot.mem -bd src/boot.mem -bt lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.bit -o b lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit

i have check the make bit-update command and the syntax/grammar of the command is correct

jrrk commented 6 years ago

In that case perhaps the LD_LIBRARY_PATH variable is incorrect or some other environment difference between the Makefile

and the command line. This particular variable determines which version of system libraries will be picked up,

a common problem when a fixed binary is compiled to run on many different versions of Linux. However since you have managed

to work around the problem manually, you should be able to proceed with 'make program-updated' or whatever finishing step you had in mind.

On 21/05/18 07:26, clare7 wrote:

all the files are valid and available and running the command alone is successful

|data2mem -bm src/boot.mem -bd src/boot.mem -bt lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.bit -o b lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit|

i have check the |make bit-update| command and the syntax/grammar of the command is correct

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/lowRISC/lowrisc-chip/issues/91#issuecomment-390564738, or mute the thread https://github.com/notifications/unsubscribe-auth/AAgF13EBjFxddn8OormJWFBK_kzOcgZZks5t0l4NgaJpZM4UGV2g.

jrrk commented 6 years ago

Or alternatively your workstation may have insufficient memory to allow all the steps to complete automatically. We tend to use workstations

with about 16GBytes of RAM, and the same amount of swap space.

On 21/05/18 07:26, clare7 wrote:

all the files are valid and available and running the command alone is successful

|data2mem -bm src/boot.mem -bd src/boot.mem -bt lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.bit -o b lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit|

i have check the |make bit-update| command and the syntax/grammar of the command is correct

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/lowRISC/lowrisc-chip/issues/91#issuecomment-390564738, or mute the thread https://github.com/notifications/unsubscribe-auth/AAgF13EBjFxddn8OormJWFBK_kzOcgZZks5t0l4NgaJpZM4UGV2g.

clare7 commented 6 years ago

Ok thanks. It works after fixing the LD_LIBRARY_PATH issue.