cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
baharlab
Contributor
Contributor
2,676 Views
Registered: ‎03-06-2019

Zcu102 Execution context is running

Hey everyone,

I am trying to run the "Hello World" example project on the ZCU102. The board is sucessfully booting from an SD card without the INIT and PSU_ERROR indicators turning Red.  However, SDK gives "execution context is running" error. What are potential causes for this error?

(Programming the PL with a design that only includes the ZYNQ without FPD or HPD ports. UART0 is enabled.)

0 Kudos
10 Replies
andresb
Xilinx Employee
Xilinx Employee
2,622 Views
Registered: ‎06-21-2018

Hi baharlab,

What version of SDK are you using?

Can you check the SN of your board? It should be 0432055-0x. If x = 5, please take a look at this:

https://www.xilinx.com/support/answers/71961.html

Thanks,
Andres

 

0 Kudos
kranthi018
Observer
Observer
2,476 Views
Registered: ‎07-02-2019

Hi andresb,
Even Im trying this same program hello world as per the steps mentioned in UG1209, using Xilinx SDK 2018.2 version on ZCU102 board,
when iam loading init_tcl, and elf files SDK throws error: Execution context running, please help us
0 Kudos
andresb
Xilinx Employee
Xilinx Employee
2,436 Views
Registered: ‎06-21-2018

Hi kranthi018,

Is your board SN 0432055-05 onward as explained here?:
https://www.xilinx.com/support/answers/71961.html

If so, please take a look at this Answer Record as well:
https://www.xilinx.com/support/answers/72210.html

Thanks,
Andres

 

0 Kudos
tsessions
Visitor
Visitor
1,958 Views
Registered: ‎12-03-2018

It looks like an answer never came for this issue. I ran through the process laid out in AR #72210 and had the same Execution context error when trying to run fsbl with Run psu_init disabled. Have you figured out what is causing this Execution context error?

0 Kudos
andresb
Xilinx Employee
Xilinx Employee
1,939 Views
Registered: ‎06-21-2018

Hi tsessions,

Unfortunately, the users are sometimes able to work through their problems and don't come back to share the results.

What version of SDK are you using?

Can you check the SN of your board? It should be 0432055-0x.

Thanks,
Andres

0 Kudos
ronnywebers
Advisor
Advisor
1,623 Views
Registered: ‎10-10-2014

@andresb 

I ran into the same error today, using SDK 2018.3, a ZCU102 board with serial : 0432055-04 (so the 'old' memory which doesn't need the FSBL patch)

for me it occurs when I try to run a simple hello world on the R5 processor in debug configuration. I tried quitting SDK, turning of my board, turngin off SmartLynq, ... keeps popping up :

what does the message actually mean? 'execution context running'?

here's the SDK log :

18:24:05 INFO	: Connected through redirection to target on host '10.0.1.26' and port '3121'.
18:24:06 INFO	: Jtag cable 'JTAG Cable 2018.3 AAo1BK6O0' is selected.
18:24:06 INFO	: 'jtag frequency' command is executed.
18:24:06 INFO	: Sourcing of '/opt/Xilinx/SDK/2018.3/scripts/sdk/util/zynqmp_utils.tcl' is done.
18:24:06 INFO	: Context for 'RPU' is selected.
18:24:06 INFO	: Cleared RPU and R5 resets
18:24:06 INFO	: Split mode is enabled for R5#1
18:24:06 INFO	: Context for 'APU' is selected.
18:24:07 INFO	: Hardware design information is loaded from '/home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/system.hdf'.
18:24:07 INFO	: 'configparams force-mem-access 1' command is executed.
18:24:07 INFO	: Context for 'APU' is selected.
18:24:07 INFO	: Sourcing of '/home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/psu_init.tcl' is done.
18:24:11 INFO	: 'psu_init' command is executed.
18:24:11 INFO	: Sourcing of '/opt/Xilinx/SDK/2018.3/scripts/sdk/util/fsbl.tcl' is done.
18:24:11 INFO	: 'catch {psu_protection}' command is executed.
18:24:11 INFO	: Context for processor 'psu_cortexr5_0' is selected.
18:24:11 ERROR	: Execution context is running
18:24:11 INFO	: ----------------XSDB Script----------------
connect -path [list tcp::1534 tcp:10.0.1.26:3121]
source /opt/Xilinx/SDK/2018.3/scripts/sdk/util/zynqmp_utils.tcl
targets -set -nocase -filter {name =~"RPU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
clear_rpu_reset
enable_split_mode
targets -set -nocase -filter {name =~"APU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
loadhw -hw /home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/system.hdf -mem-ranges [list {0x80000000 0xbfffffff} {0x400000000 0x5ffffffff} {0x1000000000 0x7fffffffff}]
configparams force-mem-access 1
targets -set -nocase -filter {name =~"APU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
source /home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/psu_init.tcl
psu_init
source /opt/Xilinx/SDK/2018.3/scripts/sdk/util/fsbl.tcl
catch {psu_protection}
targets -set -nocase -filter {name =~"*R5*0" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
rst -processor
----------------End of Script----------------

Here's my debug config :

Screenshot 2020-08-07 at 18.26.56.pngScreenshot 2020-08-07 at 18.27.02.png

 

 

** kudo if the answer was helpful. Accept as solution if your question is answered **
0 Kudos
ronnywebers
Advisor
Advisor
1,635 Views
Registered: ‎10-10-2014

@andresb I ran into the same issue in a kind of random fashion, when trying to run a simple hello world app (using system debugger) on the R5#0 processor multiple times. Sometimes this works fine, sometimes I get the error 'execution context is running'

Vivado version : 2018.3

ZUC102 board, serial 0432055-04, so it's with the 'old' memory and does not need the FSBL patch. The application is just the default hello world, but it's with any application on the R5.

My preliminary conclusion is that this is some (non consistent) reset / init issue, you can see that at the end of this post in the sdk session logs :

I created a system debug config with the following settings:

Screenshot 2020-08-07 at 18.26.56.png

Screenshot 2020-08-07 at 20.38.19.png

Then I launch a debug session. So sometimes that works, sometimes I get the error (execution context is running). Most of the time, just launching again after I get an error works. But sometimes this needs a try or 2, 3, or even more. Then I end up turning my board on and off, and I'm still not sure if that always fixes the issue, it's that random.

At first I was thinking the flag 'reset RPU' had something to do with the issue, but it doesn't seem to make much difference.

I also captured the SDK log, one for a 'correct session', one for a session with the error

1) correct debug session log

19:43:40 INFO	: Launching XSCT server: xsct -n -interactive /home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/temp_xsdb_launch_script.tcl
19:43:40 INFO	: Registering command handlers for SDK TCF services
19:43:40 INFO	: XSCT server has started successfully.
19:43:40 INFO	: Successfully done setting XSCT server connection channel  
19:43:40 INFO	: Successfully done setting SDK workspace  
19:44:31 INFO	: Connected through redirection to target on host '10.0.1.26' and port '3121'.
19:44:33 INFO	: Jtag cable 'JTAG Cable 2018.3 AAo1BK6O0' is selected.
19:44:33 INFO	: 'jtag frequency' command is executed.
19:44:33 INFO	: Sourcing of '/opt/Xilinx/SDK/2018.3/scripts/sdk/util/zynqmp_utils.tcl' is done.
19:44:33 INFO	: Context for 'RPU' is selected.
19:44:33 INFO	: Split mode is enabled for R5#1
19:44:33 INFO	: Context for 'APU' is selected.
19:44:33 INFO	: Hardware design information is loaded from '/home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/system.hdf'.
19:44:33 INFO	: 'configparams force-mem-access 1' command is executed.
19:44:33 INFO	: Context for 'APU' is selected.
19:44:33 INFO	: Sourcing of '/home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/psu_init.tcl' is done.
19:44:37 INFO	: 'psu_init' command is executed.
19:44:37 INFO	: Sourcing of '/opt/Xilinx/SDK/2018.3/scripts/sdk/util/fsbl.tcl' is done.
19:44:37 INFO	: 'catch {psu_protection}' command is executed.
19:44:37 INFO	: Context for processor 'psu_cortexr5_0' is selected.
19:44:37 INFO	: Processor reset is completed for 'psu_cortexr5_0'.
19:44:37 INFO	: 'catch {XFsbl_TcmEccInit R5_0}' command is executed.
19:44:38 INFO	: The application '/home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/hello_world_r5/Debug/hello_world_r5.elf' is downloaded to processor 'psu_cortexr5_0'.
19:44:38 INFO	: 'configparams force-mem-access 0' command is executed.
19:44:38 INFO	: ----------------XSDB Script----------------
connect -path [list tcp::1534 tcp:10.0.1.26:3121]
source /opt/Xilinx/SDK/2018.3/scripts/sdk/util/zynqmp_utils.tcl
targets -set -nocase -filter {name =~"RPU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
enable_split_mode
targets -set -nocase -filter {name =~"APU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
loadhw -hw /home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/system.hdf -mem-ranges [list {0x80000000 0xbfffffff} {0x400000000 0x5ffffffff} {0x1000000000 0x7fffffffff}]
configparams force-mem-access 1
targets -set -nocase -filter {name =~"APU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
source /home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/psu_init.tcl
psu_init
source /opt/Xilinx/SDK/2018.3/scripts/sdk/util/fsbl.tcl
catch {psu_protection}
targets -set -nocase -filter {name =~"*R5*0" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
rst -processor
catch {XFsbl_TcmEccInit R5_0}
dow /home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/hello_world_r5/Debug/hello_world_r5.elf
configparams force-mem-access 0
----------------End of Script----------------

19:44:38 INFO	: Context for processor 'psu_cortexr5_0' is selected.
19:44:38 INFO	: 'con' command is executed.
19:44:38 INFO	: ----------------XSDB Script (After Launch)----------------
targets -set -nocase -filter {name =~"*R5*0" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
con
----------------End of Script----------------

19:44:38 INFO	: Launch script is exported to file '/home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/.sdk/launch_scripts/xilinx_c-c++_application_(system_debugger)/system_debugger_using_debug_hello_world_r5.elf_on_smartlynq.tcl'

2) debug session log when the error occurs

20:09:18 INFO	: Connected through redirection to target on host '10.0.1.26' and port '3121'.
20:09:18 INFO	: Jtag cable 'JTAG Cable 2018.3 AAo1BK6O0' is selected.
20:09:18 INFO	: 'jtag frequency' command is executed.
20:09:18 INFO	: Sourcing of '/opt/Xilinx/SDK/2018.3/scripts/sdk/util/zynqmp_utils.tcl' is done.
20:09:18 INFO	: Context for 'RPU' is selected.
20:09:18 INFO	: Split mode is enabled for R5#1
20:09:18 INFO	: Context for 'APU' is selected.
20:09:18 INFO	: Hardware design information is loaded from '/home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/system.hdf'.
20:09:18 INFO	: 'configparams force-mem-access 1' command is executed.
20:09:18 INFO	: Context for 'APU' is selected.
20:09:18 INFO	: Sourcing of '/home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/psu_init.tcl' is done.
20:09:22 INFO	: 'psu_init' command is executed.
20:09:22 INFO	: Sourcing of '/opt/Xilinx/SDK/2018.3/scripts/sdk/util/fsbl.tcl' is done.
20:09:22 INFO	: 'catch {psu_protection}' command is executed.
20:09:22 INFO	: Context for processor 'psu_cortexr5_0' is selected.
20:09:23 ERROR	: Execution context is running
20:09:23 INFO	: ----------------XSDB Script----------------
connect -path [list tcp::1534 tcp:10.0.1.26:3121]
source /opt/Xilinx/SDK/2018.3/scripts/sdk/util/zynqmp_utils.tcl
targets -set -nocase -filter {name =~"RPU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
enable_split_mode
targets -set -nocase -filter {name =~"APU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
loadhw -hw /home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/system.hdf -mem-ranges [list {0x80000000 0xbfffffff} {0x400000000 0x5ffffffff} {0x1000000000 0x7fffffffff}]
configparams force-mem-access 1
targets -set -nocase -filter {name =~"APU*" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
source /home/zynqdev/zynq/2018_3/zcu102/ug1209/edt_zcu102/edt_zcu102.sdk/edt_zcu102_wrapper_hw_platform_0/psu_init.tcl
psu_init
source /opt/Xilinx/SDK/2018.3/scripts/sdk/util/fsbl.tcl
catch {psu_protection}
targets -set -nocase -filter {name =~"*R5*0" && jtag_cable_name =~ "JTAG Cable 2018.3 AAo1BK6O0"} -index 1
rst -processor
----------------End of Script----------------

So to me that looks like the R5 reset does not always complete 

 

** kudo if the answer was helpful. Accept as solution if your question is answered **
andresb
Xilinx Employee
Xilinx Employee
1,481 Views
Registered: ‎06-21-2018

Hi Ronny,

The fact that it doesn't happy every single time makes me wonder if it's a problem related to this AR:

https://www.xilinx.com/support/answers/71968.html

Can you take a look at the SN that starts with 88143572 and see if it matches?

ZCU102 board:

To identify the affected date code, look for a board serial number with a date code earlier than 1847-YYWW.

For example: Board Serial Number: 881435721847-94842

Thanks,
Andres

 

ronnywebers
Advisor
Advisor
1,402 Views
Registered: ‎10-10-2014

@andresb thanks for the tip, I checked my S/N, it's 881435911901-98638, so my board is newer than the ones affected by AR# 71968

If I discover something more I'll post it here, or if you have any further suggestions to try, let me know please

** kudo if the answer was helpful. Accept as solution if your question is answered **
0 Kudos
andresb
Xilinx Employee
Xilinx Employee
1,384 Views
Registered: ‎06-21-2018

Hi ronny,

Do you think it might have something to do with how long it takes to run?

I see that's what it's done here with the 5 second wait: https://www.xilinx.com/support/answers/72210.html

Cheers,
Andres

 

0 Kudos