Amber ARM-compatible core

I just started working with the amber project. I have installed all the tools and the repository in a VM centos 6.6(32bits) and I'm having problems in running the amber project scripts. For example, when I run the hello-world example I got:

Test hello-world, type 4 make -s -C ../mini-libc MIN_SIZE=1 arm-none-linux-gnueabi-gcc -c -Os -march=armv2a -mno-thumb-interwork -ffreestanding -I../include -c -o boot-loader-serial.o boot-loader-serial.c arm-none-linux-gnueabi-gcc -I../include -c -o start.o start.S arm-none-linux-gnueabi-gcc -c -Os -march=armv2a -mno-thumb-interwork -ffreestanding -I../include -c -o crc16.o crc16.c arm-none-linux-gnueabi-gcc -c -Os -march=armv2a -mno-thumb-interwork -ffreestanding -I../include -c -o xmodem.o xmodem.c arm-none-linux-gnueabi-gcc -c -Os -march=armv2a -mno-thumb-interwork -ffreestanding -I../include -c -o elfsplitter.o elfsplitter.c arm-none-linux-gnueabi-gcc -c -Os -march=armv2a -mno-thumb-interwork -ffreestanding -I../include -c -o ../mini-libc/printf.o ../mini-libc/printf.c arm-none-linux-gnueabi-gcc -I../include -c -o ../mini-libc/libc_asm.o ../mini-libc/libc_asm.S arm-none-linux-gnueabi-gcc -c -Os -march=armv2a -mno-thumb-interwork -ffreestanding -I../include -c -o ../mini-libc/memcpy.o ../mini-libc/memcpy.c arm-none-linux-gnueabi-ld -Bstatic -Map boot-loader-serial.map --strip-debug --fix-v4bx -o boot-loader-serial.elf -T sections.lds boot-loader-serial.o start.o crc16.o xmodem.o elfsplitter.o ../mini-libc/printf.o ../mini-libc/libc_asm.o ../mini-libc/memcpy.o arm-none-linux-gnueabi-objcopy -R .comment -R .note boot-loader-serial.elf ../tools/amber-elfsplitter boot-loader-serial.elf > boot-loader-serial.mem ../tools/amber-memparams32.sh boot-loader-serial.mem boot-loader-serial_memparams32.v make: execvp: ../tools/amber-memparams32.sh: Permission denied make: *** boot-loader-serial_memparams32.v Error 127 Error compiling boot-loader-serial

**I tried rolling back to some old versions of the project and got the same error. I think it mut be something in my configuration. Do you have any idea on what is going on here ?

thanks for your help,

Rodrigo Fonseca

Fixed this specif issue changing the permissions of all file in: trunk/sw/tools