cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
560 Views
Registered: ‎10-04-2018

Zynq not detecting ARM system with SDK

Jump to solution

I realize that this problem has been addressed before on this forum. I have examined the previous posts and have not found a solution.

The board in question is the zcu104 develpment board.

I have been able to communicate with the board when the board is booted up from the SD card. No problem using putty. Also no problem using the SDK to connect via the SDK terminal. Therefore, I expect that the problem is not in the cable.

Problem occurs when I attempt to run the Hello_World demo and "run as-> Launch on hardware".

I have the SW connected for JTAG as ON, ON, ON, ON. Although I have tried in other configurations with no luck.

Some of the other responses to posts have suggested to use the iMPACT application but it is not included in the Xilinx lab Tools installation (which I have done) and through the reading I have found that it is not available for those using Ubuntu or, I think, Linux.

Are there other suggestions?

Thank You

Tom

Error.png

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Adventurer
Adventurer
416 Views
Registered: ‎10-04-2018

Watari,

Thank you again for your support. This turned out to be a cable driver issue.

I found a good description for how to install the cable driver at https://www.xilinx.com/support/answers/59128.html 

 

Tom

 

View solution in original post

0 Kudos
4 Replies
Highlighted
Teacher
Teacher
550 Views
Registered: ‎06-16-2013

Hi @miner_tom 

 

I guess it seems CPU idle issue.

Would you refer AR #69143 ?

 

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

 

Best regards,

Highlighted
Adventurer
Adventurer
503 Views
Registered: ‎10-04-2018

watari,

Thank you for the reply.

I have read the link that you shared, https://www.xilinx.com/support/answers/69143.html , as well as others in that vein, https://forums.xilinx.com/t5/Embedded-Linux/About-Linux-CPU-idle-disable-AR-69143/td-p/1037783 , and they appear to be referring to events occuring when the linux kernel boots.

 I expect that the implication is that when attempting to run, for example, the "Hello_World" program via the SDK, a linux kernel must already be running, having been booted from the SD Card. Is that correct? Therefore, SW6, as shown below must be OFF, OFF, OFF, ON, as opposed to the JTAG configuration of ON, ON, ON, ON. 

If that is correct then I expect  that I can perform the configuration and build of a new BOOT.BIN with the BSP for the zcu104, having already done a build as a test to see if I could do it.

What about when booting via jtag (or do I misunderstand)? Are there ways to send a kernel directly to the DDR? I have seen posts where iMPACT is used but as I mentioned in the previous post, I don't have access to that. 

Oh, one more thing if I might: In the link that you shared, there was reference to a prompt at "zynqMP". I am not sure that I know what that means.

Thank You

Tom

Jtag.png

Tags (3)
0 Kudos
Highlighted
Adventurer
Adventurer
450 Views
Registered: ‎10-04-2018
watari,
Thank you for your help so far.
I did refer to AR #69143.
There were a couple of ways suggested to disable the CPU Idle in Linux kernel bootargs. I tried two of them. The builds were successful but they did not fix the problem.

I disabled CONFIG_CPU_IDLE in the kernel using "petalinux-config -c kernel" and then did a "petalinux-build". I packaged up the zynqmp_fsbl.elf and system.bit into a new BOOT.BIN and loaded it as well as image.ub into a SD card and booted. I checked the time stamps on the files to make sure that I was loading the correct ones.
The result was the same error when attempting to run the Hello_World program "run as".

I also tried the method of editing the "system-user.dtsi" file and including
/ {
chosen {
bootargs = "cpuidle.off=1";
};
};

Same result.

What would be your recommendation at this point.

Thank You again.
Tom
0 Kudos
Highlighted
Adventurer
Adventurer
417 Views
Registered: ‎10-04-2018

Watari,

Thank you again for your support. This turned out to be a cable driver issue.

I found a good description for how to install the cable driver at https://www.xilinx.com/support/answers/59128.html 

 

Tom

 

View solution in original post

0 Kudos