#apertus IRC Channel Logs

good morning

Bertl: hi, are you currently around?

lets say I need help with the SDK

I have managed to setup the SDK et al, also compiled my "own" gcc version which works on my platform and isn't 32bit

with a few minor alterations (because of the changed *-gcc) to the Makefile I am manage to compile all libraries

the Xilinx libraries that is

But, from the Xilinx SDK GUI the number of errors flooding my screen makes me cry, from undefined __ctype_ptr__ (which was relatively easily solved)

I read that it might be related to a not specified Uart

2) did you modify anything related to the standard build that might account for these curious errors?

well, first, I built for the ZedBoard, and it was back then with rather old tools

I did figure out how to get the errors on the console, so that already makes me happy

http://pastebin.com/czjAwRmi

okay, I just tried what I did back then and this seems to work with 2014.2 as well

yup that is what i did

i don't mind to try it again

what do you choose as target software?

I'll repeat the steps now and tell you what choices I made

then file/new/application project

target software is 'C', OS standalone, BSP Create new

then 'next' and Zynq FSBL

finish and project 'build all'

hmm, okay, what's the problem with that?

and you system doesn't execute 32bit binaries?

exactly

anyway, the command executed is:

arm-xilinx-eabi-gcc -Wall -O0 -g3 -I"/var/opt/AXIOM/PROJ/MicroZed/workspace/MicroZed_hw_platform" -c -fmessage-length=0 -I../../microzed_fsbl_bsp/ps7_cortexa9_0/include -MMD -MP -MF"src/ps7_init.d" -MT"src/ps7_init.d" -o "src/ps7_init.o" "/opt/Xilinx/SDK/2014.2/data/embeddedsw/lib/hwplatform_templates/MicroZed_hw_platform/ps7_init.c"

Finished building: /opt/Xilinx/SDK/2014.2/data/embeddedsw/lib/hwplatform_templates/MicroZed_hw_platform/ps7_init.c

anyway I am able to build my 'bertl_bsp'

arm-xilinx-eabi-gcc -L"/var/opt/AXIOM/PROJ/MicroZed/workspace/microzed_fsbl/src" -Wl,-T -Wl,../src/lscript.ld -L../../microzed_fsbl_bsp/ps7_cortexa9_0/lib -o "microzed_fsbl.elf" ./src/ddr_init.o ./src/fsbl_handoff.o ./src/fsbl_hooks.o ./src/image_mover.o ./src/main.o ./src/md5.o ./src/nand.o ./src/nor.o ./src/pcap.o ./src/ps7_init.o ./src/qspi.o ./src/rsa.o ./src/sd.o -lrsa -Wl,--start-group,-lxil,-lgcc,-lc,--end-group -Wl,--start-group,-lxilffs,-lxil,-

make -C ps7_cortexa9_0/libsrc/uartps_v2_1/src -s libs "SHELL=/bin/sh" "COMPILER=arm-xilinx-linux-gnueabi-gcc" "ARCHIVER=arm-xilinx-linux-gnueabi-ar" "COMPILER_FLAGS= -O2 -c" "EXTRA_COMPILER_FLAGS=-g"

Finished building libraries

thats in "bertl_bsp"

Finished building: /home/skinkie/Sources/MicroZed_hw_platform/ps7_init.c

or in your case, bertl_bsp.elf I guess

thats the first problem i am able to fix by the correct mcpu

-lgcc ?

i.e. some gcc versions tend to drop libraries if they are not used right away

/opt/Xilinx/SDK/2014.2/gnu/arm/lin/arm-xilinx-linux-gnueabi/libc/lib/libm.so.6 for example

hence you need to have that

but anyway i am also able to resolve the ctype error

at least i was...

did you try LD_LIBRARY_PATH=/opt/Xilinx/SDK/2014.2/gnu/arm/lin/arm-xilinx-linux-gnueabi/libc/lib/ /opt/Xilinx/SDK/2014.2/gnu/arm/lin/bin/arm-xilinx-eabi-gcc

just tried it, that doesn't work

anyway if this all doesn't work out i'll copy this to another box with multilib support

agreed, and I'm all for it if you can resolve it

(if legal) or by providing a kvm environment to build in

sure

that can be compiled with any crosscompiled arm gcc

you'll get there :)

have you got a clue about that one?

if you help me fix this one i have a working workaround for all the problems, and i know how to reproduce it ;)

it is used for dynamic linking and libraries

-Wl,-T -Wl,../src/lscript.ld

check if the linker (ld) is actually using that script

it certainly does open it

ah, okay, maybe a syntax problem

i.e. look at maybe weird characters or strange newlines before that point

i get that

linkage for cortex-m

it might be that problem

but given that we are running a cortex-a9

so, yes, wrong cpu type

you probably need to add it to previous steps as well

If ld cannot find a matching library, it falls back to the default one. There is no error message.

arm-none-eabi-gcc -print-multi-directory -mcpu=cortex-a9

if i tell you i have an elf file now

of course :)

I added a section .rel.plt

ah, is there a .got.plt too?

hmm, interesting

what can i do with this elf file to verify it does something?

simplest test would be to combine it with a bitstream which blinks the (only available) led

or you can take a leap of faith and combine it with uboot

yes, sec, I'm sure I have a blink example

i removed that, skipped the errno with return NULL

http://vserver.13thfloor.at/Stuff/AXIOM/BETA/blink_done/

try to upload it via jtag first to see if it works as expected

promgen -w -b -p bin -u 0 blink.bit -data_width 32

it isn't between the SDK tools so to speak

they are 'working' on a version for Vivado, but I'm not too optimistic they will finish soon

i am just waiting for the moment you will tell me how "Program FPGA works" ;)

that seems to be required as well?

I have a very nifty dialog

ah, no the promgen tool is actually a 64bit binary

no idea where you got it from :)

can it make omlette?

i guess you have to blink at a resonant frequency

hmm, no, you need a jtag cable (like the one you asked me if it would work)

the microzed has no jtag via usb by default

so uboot

I'm pretty sure it worked last time I tested it

micro SD?

I mean seriously... nothing works as promised here

yeah, it took me a week to get the first code working on the ZedBoard

granted, I wanted to use the commandline which is not tested at all :)

thats very convient if it does not compile

https://dev.openwrt.org/ticket/11876

I can upload the config I created for the zedboard, might save you a few days :)

http://vserver.13thfloor.at/Stuff/AXIOM/ALPHA/u-boot-digilent.diff

great so i have xilinx uboot as well now

(it might make u-boot unuseable)

okay, have to get some stuff done before EHSM, if you have further questions, just post them here or via email, I'll read up and answer periodically

so i'll probe how far i can push this in the next 30min :)

FATAL: Exception: Multiple executable program sections in fsbl.elf

i give up for today more luck in the weekend i hope

thanks