PRs about real-time-cpp HOT 9 CLOSED

I am interested in working on adding a few platforms, and adding CMake build support.

Yes. Absolutely. Thank you for your interest. Looking forward to it.
Kind regards, Chris.

from real-time-cpp.

Just wondering... What builds to start with? Which compilers? Which compiler locations?
Good starting point could be the ref_app itself with any of the supported targets.
That is, if you elect to go for some of this work. Happy if you give it a try.
Kind regards. Chris

from real-time-cpp.

Hi Chris.

I just brought up the ref_app on a NXP OM13093 (LPC11C24 32k flash /8k RAM) board. Cortex M0. It's an old one, but a great one for CAN projects (J1939/NMEA 2000, UDS, UAV, etc).

One I clean this up, I will submit a PR. Next goals to include Ambiq Apollo 3 Blue (384k RAM) support, and in parallel multi-host CMake support.

Joel

from real-time-cpp.

arm-none-eabi-g++ --version
arm-none-eabi-g++ (GNU Tools for Arm Embedded Processors 8-2018-q4-major) 8.2.1 20181213 (release) [gcc-8-branch revision 267074]

VSCodium (w/ Cortex-Debug), and Segger JLink.

from real-time-cpp.

I just brought up the ref_app on a NXP OM13093 (LPC11C24 32k flash /8k RAM) board. Cortex M0.

Fantastic! It will be good to have an M0 or M0+ running. Thank you for progressing on this topic.

This reminds me of another idea I've been considering. For ARM(R) architectures, to switch the clock base (in microseconds) to the SysTick if this has sufficiently high frequency. This would free up a timer resource and improve the "generic-ness" of the ref_app. I will look into this as well.

from real-time-cpp.

I'm using the SysTick on PR 33. It's currently configured for 100 microseconds.

Also I created a new namespace for all the config values. I'm using mcal::config to hold things usually layered in "project/board" layers. If this scheme works for you, I'll use the same approach for the Apollo 3 (M4).

from real-time-cpp.

I'm using the SysTick on PR 33. It's currently configured for 100 microseconds.

Yes. Cool. I get it.

Also I created a new namespace for all the config values.
I'm using mcal::config to hold things usually layered in
"project/board" layers. If this scheme works for you,
I'll use the same approach for the Apollo 3 (M4).

Fine. Please feel free to do this. I corrected what seemed like a simple cut/paste
error in your original PR of mcal_config.h in the file header guard.

from real-time-cpp.

I have also added the new configuration "target lpc11c24" to
the VS2017 workspace.

Great job Joel. The build worked perfectly with GCC 8.2.1.

from real-time-cpp.

Next goals to include Ambiq Apollo 3 Blue (384k RAM) support,
and in parallel multi-host CMake support

Go for it. Many thanks.

Kind regards, Chris

from real-time-cpp.