==== Adapting BSP for an own product ====
<grid>
<col sm="5">
<callout type="info" icon="true">
 We suggest to read the following pages before you proceed with this page\\   
  - [[@lang@:@mod_arch@:@mod_name_code@:@bsp_name@:prepare|preparing Development Host]]
  - [[@lang@:@mod_arch@:@mod_name_code@:@bsp_name@:build_bsp|Building BSP with PTXdist]]
</callout> </col> </grid>

==== Creating a new platform for your product ====

<grid>
<col sm="10">
<alert type="warning" icon="fa fa-warning">The BSP was developed for the starterkit <label starterkit_name></label>. To use it in a product with special needs or a different basebord we strongly recommend to define your own platform.</alert> </col> </grid>



First of all make a copy of the platform definition and select the new platform definition

<code bash> 
$ cd <BSPROOT>
$ cp -r <BSPROOT>/configs/platform-tq-@mb_name_code@ to <BSPROOT>/configs/<your-cool-platform>
$ ptxdist platform <BSPROOT>/configs/<your-cool-platform>/platformconfig
</code> 

To start configuring your new platform type

<code bash> 
$ ptxdist platformconfig
</code> 

The first thing to change should be the platform name. Adapt things like kernel configuration, image creation etc. to your needs.

The new system will be built under <BSPROOT>/platform-<platformname_from_platformconfig>
<grid>
<col sm="10">
<alert type="warning" icon="fa fa-warning"> Please read the [[http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf|build system documentation]] for further information. Keep in mind that custom mainboards may require changes in bootloader and device tree. \\ Give the new bootloader config and device tree a new name to cleanly distinguish them from the starterkit mainboard configuration. </alert> </col> </grid>

<grid>
<col sm="8">
<alert type="warning" icon="fa fa-warning">
When creating a new platform, make sure to create new configurations for bootloaders and device tree as well. </alert> </col> </grid>

==== Changing packages ====

PTXdist uses release tarballs for software it loads from the net. You have to work with patches, if you need to make (permanent) changes to the source code. Follow the instructions of the developers section in the [[http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf|PTXdist manual]].

<grid>
<col sm="8">
<callout type="danger" icon="true">
Changes made in the build directories will be deleted, when PTXdist needs to redo a buildstep. </callout> </col> </grid>

==== Adding own packages ====

Everything that should be part of your rootfilesystem needs to be provided as a PTXdist package, in order to guarantee reproducible builds. To add your application software, files etc. you have to provide local packages. Follow the instructions of the developers section in the [[http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf|PTXdist manual]]. PTXdist provides templates as starting point for own packages. 

Execute

<code bash>
$ ptxdist newpackage
</code>

for a list of available package templates.


==== Patching Uboot/Kernel ====