#apertus IRC Channel Logs

umm...trying to find settings64.sh

but it shouldn't be hard to find

erm ISE installer

Well, I know it installed to /opt

good, source it

(or lin instead of lin64 if you are 32bit)

nah, been all 64 bit for me since 2010

actually that's false

hehe

what's interesting is that many companies still produce 32bit only versions of their software

I guess it is related to having locked down toolchains and a very crude programming style :)

exactly

seems that open source cares a lot more about avoiding such issues in the first place

now, there's plenty of crap/unstable open source software and a fair amount of horrible architecture

(and a lot of open source as well, but hey, you just avoid that :)

it can take forever to install and get working properly

In the open source world, well I booted Ubuntu from a liveusb and installed Novacut in the middle of a demoing a class project

yay, I found something positive to say :P

when programs require ancient libraries and such

for example, try to get the fpga_editor working which comes with the xilinx ISE

we would either have had to support old (and missing useful functionality) versions of key libraries and have trouble going to new libraries later or maintain backports (which would replace important system libraries),

where there is windoof 8 without a start button :)

can somebody say "security vulnerability"

so your tools/jtag working now as expected?

run 'strace -fF -o xmd.trace xmd'

then check the xmd.trace for pathes

[pid 20514] open("/opt/XILINX/14.5/ISE_DS/ISE/lib/lin64/plugins/Digilent/libCseDigilent/libCseDigilent.xml", O_RDONLY) = 5

and if you get an error from xmd, please paste it ...

so it does see the Cortex-A9 and XC7Z020

(you won't be able to see that without a working jtag)

btw, IMHO, I wouldn't waste any time on the GUI tools, I've played around with them trying this and that but with little success ... till I switched to xflow

it's basically the batch processor

I see

have you ever used Mentor Graphics?

nope, not yet

hehe, well, happens if folks without any GUI design knowledge start randomly putting building blocks together ...

like scroll wheel doing something but not scrolling the diagram

define real components

is that on your site?

ah, okay

(and the compiled .dtb as well)

I'll probably add some more aliases for the different kernels but it should do the job for most PS devices and configurations

I'll take a look tomorrow

hello Bertl

Bertl: would you mind walking me through the device tree stuff?

the device tree thing is basically teaching the linux kernel on the arm side about the board, right?

at least that's what I think I remember from Linaro conference in Hong Kong

so I'm just trying to get going with working on things

sounds good!

I've booted a recent kernel with my custom PL code and tested all available drivers

yep, that is how I call it

(which is also the term coined by xilinx)

the PS7 is actually a lot more than just the arm cores

so basically the CPU + chipset

what's the bandwidth on the interconnect?

that I haven't tested so far, but it should allow up to GB/s tranfer speeds

sure, note that I use TFTP booting for convenience, but you can also do the much slower JTAG boot

no I haven't gotten to that yet

shouldn't be too hard, if you like I can walk you through that right now

but that should be pretty easy

anyway, all you need installed is TFTP and DHCPD (packages for your distro should be available)

then simply start a normal SD boot, and watch the logs on your DHCPD network, the boot should show up with an IP request

pick your preferred IP address for the board and assign it via dhcpd

hardware ethernet 00:0A:35:00:01:22;

filename "/ZED/u-boot.scr";

this is how the entry looks here

at that point, you should already see failing TFTP requests

after that, you simply put the boot script into your tftp directory http://vserver.13thfloor.at/Stuff/AXIOM/TFTP/ZED/u-boot.scr

why would the board be asking my computer for an ip address

whoever answers the dhcp/bootp request

if you connect the zedboard directly to your dev system, e.g. via some spare gbit interface, then it will be your dev system dhcpd

so I kinda have to connect the zedboard to the switch with my desktops that feeds into the router

next-server 192.168.2.1;

this way the router will instruct the zedboard to fetch the file from there

he's out doing research atm though

you can easily hardcode the bootp part to a fixed IP and request the file from your specific dev machine

yeah, it autoassigns IPs

192.168.1.142

/24 ?

yeah /24

or an IP you would like the zedboard to use

not seeing it appear in the DHCP list

if not, just interrupt the bootload (via serial console)

and enter 'bootp'

no, the UART

http://vserver.13thfloor.at/Stuff/AXIOM/minirc.ACM0

and start minicom like this:

(in a terminal which has access to /dev/ttyACM0)