Run on HW, Ctrl-C to terminate a long test, then "can not attach action"
Closed this issue · 0 comments
When I was writing test scripts, some tests were quite long. I didn't want to wait, so I Ctrl-C to terminate it. Then I found next time when I want to execute the testscript again, it would timeout.
I found this problem in NSA121B first, but then I found it also happened on KU3.
My steps:
-
Flash the card with a proper bistream (bin file)
-
Call software/tools/snap_maint -vvv (Will recoganize the correct action_type)
-
Call (for example), ./actions/hdl_example/tests/10140000_test.sh
Everything goes well, If I do nothing, it will go to end with a SUCCESS.
But I Ctrl-C in the middle -
Call
./actions/hdl_example/tests/10140000_test.sh
again
Testing Action 1 from 200 msec to 1 sec in 200 msec steps
Testing Action 1 from 200 msec to 1 sec in 200 msec steps with Interrupts
Error: Can not attach Action: 10140000
Try to run snap_main tool
cmd: ./actions/hdl_example/sw/snap_example -a 1 -C0 -e 1000 -t 2 -I
failed
- I run snap_maint again, everything seems ok
SNAP FPGA Release: v1.1.0 Distance: 82 GIT: 0xf97d45a6
SNAP FPGA Build (Y/M/D): 2017/08/09 Time (H:M): 06:12
SNAP FPGA CIR Master: 1 My ID: 0
SNAP FPGA Up Time: 758 sec
SNAP FPGA Exploration already done (MSAT: 1 MAID: 1)
Short | Action Type | Level |
------+--------------+-----------+-----------
0 0x10140000 0x00000000 IBM Sample Code
- But
./actions/hdl_example/tests/10140000_test.sh
still timeout.
The only way is to re-program the FPGA flash again.
It seems when a middle termination happened, hardware didn't return to a reset state?