Improve Validation of Config

[HTRamsey]

Improve Validation of Config

Description

Verifies FreeRTOSConfig.h values that are required
Uses static asserts on a few ipconfig values that can't be compile time checked normally

Test Steps

Checklist:

• I have tested my changes. No regression in existing tests.
• I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[paulbartell]

@HTRamsey Thanks for the PR. Would you mind running uncrustify on your changes?

[HTRamsey]

/bot run formatting

[AniruddhaKanhere]

Yes, this is good. We can remove this once #449 has been resolved.

[HTRamsey]

@tony-josi-aws we can change the static assert definition, that semi colon is just to allow multiple asserts on the same line.

Have to change unsigned comparisons against 0 too

[tony-josi-aws]

@HTRamsey, makes sense to remove the semicolon if we are not using multiple asserts on the same line.

And MISRA doesn't like literals without a sign (U) explicitly specified.

[HTRamsey]

@tony-josi-aws Should I add literal signs to all of the default configs?

[tony-josi-aws]

@HTRamsey, not all, but those that are compared/used/assigned to unsigned variables. The latest main branch is validated with coverity for MISRA 2012, so unless new macros are being added, the existing default macro definitions should be good.

[HTRamsey]

Is there an actual minimum kernel version that is supported?

[tony-josi-aws]

@HTRamsey

FreeRTOS+TCP requires kernel version that supports event groups, which is added with kernel version v8.1.