Articles with tag "ptxdist"
PTXdist comes with a tool to make license management more simple, namely the command: ptxdist make license-report. This tool generates a license report in pdf format, which filters the used BSP for all known licenses. To generate and comply with the license report should be seen as minimum standard, exceeding efforts should, if possible, be done.
Whenever it is a requirement to be able to switch off an embedded device without any previous preparation, the next question is about the consistence of the used filesystem. If this filesystem is used to be written with new content and this new/changed data hasn't done it's way to the persistent media when the power is cut, this new/changed data is lost.
A BSP (Board Support Package) in Embedded Software is the layer of software that lets you run your application on a specific hardware. For Pengutronix a BSP usually contains a bootloader, Linux Kernel and a userspace. DistroKit is our Demo-BSP that supports a variety of common evaluation boards. DistroKit gives you a head start if you want to develop an application on top of such an evaluation board with most of the hard problems already solved.
While the development on an embedded system I need to reboot it quite often. Doing so I appreciate to keep the required steps as less as possible and be sure the embedded system uses the recently changed data in a consistent manner.
Simplify and beautify your developer's life. An example.
Hildesheim, Germany - Pengutronix offers a new release of its free Board Support Package for generic and emulated platforms. It provides all required components to get everything run in a QEMU environment, and is dedicated for beginners in the embedded world. And for the experienced user it can act as a quick start for her/his own development as well.
The main new feature was the introduction and tuning of the toolchain 'wrapper': This wrapper ensures a new level of control about how a PTXdist project is build. In earlier days, the binary results relied more or less on the buildsystem each package comes with. With the new wrapper, a package's buildsystem calls the wrapper instead of gcc and other toolchain components, and all command line parameters given to it can be checked or extended. The wrapper provides enforcement of: