Fix the issue where the default configuration parameters for the log …

[yangbryant]

…do not take effect

[github-actions]

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

• maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

• maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change, no action is needed.

---

This is an automated suggestion to help route contributions to the appropriate branch.

[github-actions]

Test firmware build ready — commit cd464f0

Download firmware for PR #11453

228 targets built. Find your board's .hex file by name on that page (e.g. MATEKF405SE.hex). Files are individually downloadable — no GitHub login required.

Development build for testing only. Use Full Chip Erase when flashing.

[sensei-hacker]

Thanks for the PR!
The log.c change looks good and fixes a real bug — PG_REGISTER was silently discarding the non-zero defaults in the reset template.

The serial.c change adds a TERMINALLOG_UART block but TERMINALLOG_UART isn't defined in any target .h file, so that code is currently unreachable, as far as I can see. Could you either add the definition or docuemtnation for how it should be used, or else split this into two PRs so the log.c fix can be merged now?"

[yangbryant]

Thanks for the PR! The log.c change looks good and fixes a real bug — PG_REGISTER was silently discarding the non-zero defaults in the reset template.

The serial.c change adds a TERMINALLOG_UART block but TERMINALLOG_UART isn't defined in any target .h file, so that code is currently unreachable, as far as I can see. Could you either add the definition or docuemtnation for how it should be used, or else split this into two PRs so the log.c fix can be merged now?"

OK，i will split this into two PRs, i will submit one PR of the log.c fix first, and refine it with another PR later.

[yangbryant]

the log.c fix is here #11493