Re: RTEMS on TMS570

Hello Martin, On Tuesday 03 of February 2015 16:49:44 Martin Galvan wrote: > Hello Pavel! I'm writing you about the RTEMS support on the TMS570. Last > time we spoke I mentioned a bug on printf which caused the system to hang > when trying to print a two-digit decimal numer (e.g. 42). We've been t

dl01 failure on all blackfin BSPs

Hi All bfin BSPs fail with this: rtems-syms -e -c "-O2 -g -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs" -o dl-sym.o dl02.pre bfin-rtems4.11-gcc -B../../../../../bf537Stamp/lib/ -specs bsp_specs -qrtems -O2 -g -Wall -Wmissing-prototypes -Wimplicit

dl01 - 17 PowerPC BSP have relocation truncated

Hi The following 17 PowerPC BSPs fail in a similar manner. gwlcfm mpc5566evb mpc5566evb_spe mpc5643l_dpu mpc5643l_evb mpc5668g mpc5674f_ecu508_app mpc5674f_ecu508_boot mpc5674fevb mpc5674fevb_spe mpc5674f_rsm6 phycore_mpc5554 qoriq_core_0 qoriq_core_1 qoriq_p1020rdb qoriq_t2080rdb qoriq_t4240rdb

dl01/libdl - All MIPS BSPs fail

Hi Another build failure when linking dl01: mips-rtems4.11-gcc -B../../../../../csb350/lib/ -specs bsp_specs -qrtems -mips32 -G0 -msoft-float -O2 -g -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -mips32 -G0 -msoft-float \ -o dl01.

dl01/libdl - All v850 BSPs fail with unknown machine type

Hi Another from the build sweep. All v850 BSPs fail with this: rtems-syms -e -c "-mv850e1 -O2 -g -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs" -o dl-sym.o dl01.pre error: machine-type: unknown machine type: 36 -- Joel Sherrill, Ph.D.

Multiple SPARC BSP Build Failures

Hi Looking over the build logs, I saw this failure which needs to be fixed. sparc-rtems4.11-gcc --pipe -B../../../../../.././lib/ -B../../../../../.././leon3/lib/ -specs bsp_specs -qrtems -DHAVE_CONFIG_H -I../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/include -mcpu=cypress -msoft

Re: Xilinx Microblaze copyrights question

On Mon, Feb 2, 2015 at 9:18 PM, Chris Johns wrote: > On 3/02/2015 1:36 am, Joel Sherrill wrote: >>> >>> Should I (or anyone of you) create a thread on Xilinx >>> forums to discuss about that issue? >> >> Chris should answer this since he is leading the discussions with Xilinx >> we have been havin