How to add New BSP in RTEMS 5.0

Sebastian Huber sebastian.huber at embedded-brains.de
Tue Dec 11 06:48:44 UTC 2018



On 11/12/2018 07:38, Amarnath MB wrote:
> Hi,
>
> Currently working on developing an RTEMS 5.0 BSP for a new SOC based 
> on ARM926EJS.
> I have taken lpc32xx_mzx as the reference BSP and have made following 
> changes in the RTEMS master,
>
>  1. Created a new folder <target> for my target inside /bsps/arm/
>  2. Added .inc and .cfg files for the target inside
>     /bsps/arm/<target>/config (Modified copy of lpc32xx)
>  3. Added linkcmds.<target> file inside  /bsps/arm/<target>/start
>     (Modified copy of lpc32xx)
>  4. Created a new folder <target> inside /c/src/lib/libbsp/arm/
>  5. Added configure.ac <http://configure.ac> and Makefile.am inside
>     /c/src/lib/libbsp/arm/<target>/ (Modified copy of lpc32xx)
>
> Issuing make command after bootstrapping and configuring gave me the 
> following error,
>
> checking for RTEMS_BSP... mytarget
> checking for perl... /usr/bin/perl
> configure: error: Invalid BSP
> configure: error: 
> ../../../../../.././../../rtems-git/c/src/lib/libbsp/arm/configure 
> failed for lib/libbsp/arm
> Makefile:731: recipe for target 'mytarget' failed
> gmake[2]: *** [mytarget] Error 1
> gmake[2]: Leaving directory 
> '/mnt/OS/LAP000426/RTEMS_BUILD/development/rtems/mytarget/rtems/5.00/build/LPC/arm-rtems5/c'
> Makefile:289: recipe for target 'all-recursive' failed
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory 
> '/mnt/OS/LAP000426/RTEMS_BUILD/development/rtems/mytarget/rtems/5.00/build/LPC/arm-rtems5/c'
> Makefile:410: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
>
> Am I doing something wrong here or am I missing some steps?

Please try to add it it to:

c/src/lib/libbsp/arm/acinclude.m4

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.




More information about the users mailing list