Bare Metal QBS GCC Arm
Bare Metal multi vendor Blinky ARM SDK in QBS for GCC compilers.
This is a project utilising Qt build system (QBS) to manage the cross-compilation of an application targeted for Arm MCUs. The structure enables fast porting between different MCUs and also facilitates compilation for desktop targets.
It is comprised of:
- Latest Arm CMSIS driver libraries
- Vendor specific driver libraries
- Managed linker generation
- Blinky example (using systick) that compiles for every board
- Mini vendor specific GPIO library to facilitate the blinky.
Currently there are examples for TI, NXP/LPC, NXP/Freescale/Kinetis and Cypress/Spansion (STM examples to follow)
MCU definitions are located in modules/ and formatted like: chip_*
A select few boards are implemented.
Board definitions are located in modules/ and formatted like: board_*
The intent of this library is to provide a ready to go environment for development, testing and verification of production firmware for commercial use. Secondarily, it enables porting between MCU's and Desktop targets to be trivial. This is especially handy as it allows offline development of your application on desktop targets, which with a little thought and pre-planning, can make debugging a sizeable project a pleasure and a breeze.
Why QBS?
QBS accomplishes the same task as make and cmake, but is far more flexible and readable.
It allows conditional forward and backwards dependency attributes to be applied to the build. For this project QBS is essential to organising build variant's compilation source and build environment per vendor MCU.
Make and cmake just cant deliver this amount of flexibility, whilst retaining readability.
No, QBS is a cli tool akin to make & cmake.
Qt Creator does compliment QBS in order to display only the current compilation source in the tree.
Firstly, I urge you to file a bug report if you are struggling to 'get started' as the intention of this project is to expedite the 'getting started' process, if you run into problems, then that is a bug.