Adapting BSP for an own product
Creating a new platform for your product
First of all make a copy of the platform definition and select the new platform definition
$ 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
To start configuring your new platform type
$ ptxdist platformconfig
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>
Give the new bootloader config and device tree a new name to cleanly distinguish them from the starterkit mainboard configuration.
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 PTXdist manual.
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 PTXdist manual. PTXdist provides templates as starting point for own packages.
Execute
$ ptxdist newpackage
for a list of available package templates.
Patching Uboot/Kernel
TQ-Systems GmbH provides the Board Support Packages (BSP) free of charge. The software included in the shipment has been configured individually for the starter kits. The software is only intended to evaluate the module. The use of the Board Support Packages (BSP) is only allowed within the scope of functionality described by TQ-Systems GmbH. TQ-Systems GmbH does not accept any liability for all further changes of the Board Support Package and for any damage resulting from its use.