[meta-xilinx] Xilinx SDK toolchain

I've been using a jethro build on a Zynq-7000 system. When I create/build a Linux Application hello world project on Xilinx SDK 2016.3 and try executing it, I get "-sh: ./test.elf: No such file or directory". I think this is because of a toolchain or rootfs library mismatch between the Xilinx

Re: [meta-xilinx] Zynq TTC usage by Linux

On Tue, Oct 25, 2016 at 12:01 AM, Mike Looijmans wrote: > Usually the term "real time" is applied to too many things. For example, > your desktop PC experiences latencies of over 1 ms for typical interrupts, > but it still functions fine when running various audio and

Re: [meta-xilinx] Zynq TTC usage by Linux

On Fri, Oct 21, 2016 at 12:26 AM, Nathan Rossi wrote: > This is informing that the ttc device is probed and setup as a > clocksource device. Althought it is probably not used. > You can also check to see what is currently in use: cat >

Re: [meta-xilinx] Zynq TTC usage by Linux

phys=f8001000 ioremap I can disable it in my device tree with: ps7_ttc_0: ps7-ttc@f8001000 { compatible = "invalid"; } Does anyone know what TTC0 would be used for? Doesn't seem to be critical as Linux stills boots and runs OK. Thanks for your help. On Thu, Oct 20, 2016 at 5:31

Re: [meta-xilinx] cross-compiling

Thanks Nathan and Mike, I just installed the SDK from Yocto and the Linux executables it generates are working fine. On Tue, Oct 11, 2016 at 12:31 AM, Nathan Rossi wrote: > On Tue, Oct 11, 2016 at 5:17 PM, Mike Looijmans > wrote: >> I suspect

[meta-xilinx] cross-compiling

I cross-compiled an application to run on Linux on the Zynq-7020. Trying to execute it gives "No such file or directory" error. # file app_hello.elf app_hello.elf: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux

[meta-xilinx] Xilinx SDK projects in Yocto

Is it possible to use Yocto to compile a Xilinx SDK project? Would I use the Linux version of Xilinx SDK, or could/would I use some other toolchain that's more command-line oriented? Could I furthermore build a BOOT.BIN from, say, a Xilinx SDK-based FSBL and a Yocto generated u-boot.elf? Can

Re: [meta-xilinx] Help with ethernet0 device tree node

On Mon, Aug 29, 2016 at 3:52 PM, Edward Wingate <edwinga...@gmail.com> wrote: > So it turns out the application I'm running on CPU1 was interfering > with Linux on CPU0. And apologies for not mentioning my running in an AMP configuration, but it did not seem related

Re: [meta-xilinx] Help with ethernet0 device tree node

the SLCR_LOCKSTA register for the lock status and unlock if necessary. I tried to find in the kernel where this would occur, but got lost in the kernel driver code. On Thu, Aug 11, 2016 at 4:41 AM, Nathan Rossi <nat...@nathanrossi.com> wrote: > On Wed, Aug 10, 2016 at 7:29 AM, Edward Wingate

Re: [meta-xilinx] Help with ethernet0 device tree node

this in it: clock-names = "ref_clk", "aper_clk"; clocks = < 13>, < 30>; The "30" in clocks is referring to gem0_aper, which looks out of place in the clock tree (being under armpll instead of iopll). On Mon, Aug 8, 2016 at 12:08 PM, Edward Wingate <edwing

Re: [meta-xilinx] Help with ethernet0 device tree node

On Sun, Jul 31, 2016 at 6:26 AM, Nathan Rossi wrote: > > I tested this with both the emacps and the macb driver (linux-xlnx > kernel v2016.2, on a ZYBO). Both advertise and link correctly with a > 100M switch and forced advert 100M with a 1G switch, and packets are >

[meta-xilinx] Help with ethernet0 device tree node

My eth0 interface can only run at 1Gbps. If I plug into a 100 Mbps switch or use ethtool to set the link speed, it looks like it succeeded: xemacps e000b000.ps7-ethernet: link down xemacps e000b000.ps7-ethernet: Set clk to 2500 Hz xemacps e000b000.ps7-ethernet: link up (100/FULL)

[meta-xilinx] PS I2C access by CPU1

I'm using Zynq 7020 AMP config with Linux on CPU0 and FreeRTOS on CPU1. ps7_i2c_0 is to be used by CPU1. What is the proper device tree setting to use for ps7_i2c_0 in this case? 1) ps7_i2c_0: ps7-i2c@e0004000 { compatible = "invalid"; }; or 2) ps7_i2c_0: ps7-i2c@e0004000 { bus-id =

[meta-xilinx] linux-xlnx-dev.bb recipe

I've been using linux-xlnx-dev.bb recipe to compile a kernel with the following: PREFERRED_PROVIDER_virtual/kernel = "linux-xlnx-dev" SRCREV_pn-linux-xlnx-dev = "3be00480727bf360d912223026b789011b1e5251" This was pointing to a 4.0 kernel. Now, on a fresh build, I get "unable to find revision"