This is an old revision of the document!


Embedded module TQMLS102xA - PTXdist Linux BSP documentation


Adapting BSP for an own product

we suggest to read the following pages before you proceed with this page

  1. preparing Development Host
  2. Building BSP with PTXdist

The BSP was developed for the starterkit STKLS102xA. To use it in a product with special needs or a different basebord we suggest to define an own platform. To start with it make a copy of the platform definition and select the new platform definition 

$ cd <BSPROOT>
$ cp -r <BSPROOT>/configs/platform-tq-mbals102xa 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>

Please read the build system documentation howto go further. Keep in mind that custom mainboards may need 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.

If creating BSP for a new motherboard, make sure to create new configurations for bootloaders and device tree.

Changing packages

PTXdist uses release tar balls for software it loads from the net. You have to work with patches, if you need to make changes to the source code. Follow the instructions of the developers section in the PTXdist manual.

Changes that are made in the build directories will be deleted, when PTXdist needs to redo a buildstep.

Adding own packages

PTXdist needs a package for every bit you need in your root FS to guarantee reproducible builds. To add your 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. Type 

$ ptxdist newpackage

to see what package templates exist.

Partition scheme

Changing the partition scheme may affect the bootloader update capability and / or the kernel command line parameters!

SD / eMMC images
  • sector size 512 Byte
  • unpartitioned area: 4MiB (0x2000 sectors)
Sector Size Usage
0x00000 … 0x000000 0x0001 sector / 512 Byte MBR / Partition Table
0x00001 … 0x000001 0x0001 sector / 512 Byte free
0x00002 … 0x0007FF 0x07FE sectors / 1023 KiB u-boot
0x00800 … 0x000FFF 0x0800 sectors / 1MiB environment
0x01000 … 0x001FFF 0x1000 sectors / 2 MiB free
0x02000 … 0x00BFFF 0xA000 sectors / 20 MiB boot /firmware (Kernel,devicetrees)
0x0C000 … 0x08BFFF 0x80000 sectors / 256 MiB root
0x8C000 … 0x10BFFF 0x80000 sectors / 256 MiB spare, unformated

eMMC/SD partition layout was changed in BSP REV.0109

BSP Revision < 0109

The partition scheme is defined using the config file config/platform-tq-mbls102xa/config/images/uboot-hd.config.

To create the image the genimage host tool is used. This tool is automatically selected and built. You can find the build directory under <BSPROOT>/platform-MBLS102x/build-host/genimage. See the README file for how to use this tool.

QSPI NOR
  • sector size 64 KiB
Sector Size Usage
0x0000 … 0x0013 0x000E sectors / 896 KiB U-Boot
0x0014 … 0x0014 0x0001 sector / 64 KiB environment0
0x0015 … 0x0015 0x0005 sectors / 64 KiB devicetree
0x0016 … 0x0086 0x0070 sectors / 7 MiB Kernel
0x0087 … 0x0467 0x0380 sectors / 56 MiB RootFS

  • Last modified: 2022/08/04 15:04