Make online debug optional

It could be useful for very small targets like Atmega (Arduino) and
for target bring-up there developer want to have running PLC program,
but has not implemented runtime communication yet.


TARGET_DEBUG_AND_RETAIN_DISABLE - completely disable debug and retain
functionality. Previously named TARGET_DEBUG_DISABLE.

TARGET_ONLINE_DEBUG_DISABLE - can be used to enable retain
functionality (no define TARGET_DEBUG_AND_RETAIN_DISABLE is used), but disable
online debug with corresponding RAM/FLASH overhead.

TARGET_LOGGING_DISABLE - disables logging functionality from runtime and PLC program

TARGET_EXT_SYNC_DISABLE - disables PLC program synchronization with
external events. For example, it could be used to synchronize several
PLCs that control motors for different axes.

By default all these options are off.

To test generate program for Generic target, put following files in
project files directory and run build.sh after generating PLC program.
This is very easy to integrate into makefile (Generic target).

[------------- build.sh --------------------------]
files=$(find $PWD/../build -iname '*.c' | grep -v POUS.c)
arm-none-eabi-gcc \
-DTARGET_DEBUG_AND_RETAIN_DISABLE \
-DTARGET_ONLINE_DEBUG_DISABLE \
-DTARGET_LOGGING_DISABLE \
-DTARGET_EXT_SYNC_DISABLE \
-flto -ffunction-sections -fdata-sections -I../../../../matiec/lib/C \
$files \
main.c \
-Wl,--Map=./program.map,--cref \
-nodefaultlibs --specs=nano.specs -Wl,--static -Wl,--gc-section -Wl,--start-group -lc -lm -lnosys -lgcc -Wl,--end-group
[------------------------------------------------]

[------------- main.c --------------------------]
#ifndef TARGET_DEBUG_AND_RETAIN_DISABLE
void Retain(void){}
void InValidateRetainBuffer(void){}
void ValidateRetainBuffer(void){}
#endif

extern void __run(void);
int main(void)
{
for(;;) {
__run();
// sleep common_ticktime__ ns
// add common_ticktime__ ns to __CURRENT_TIME
}
return 0;
}
[------------------------------------------------]

     1

How Do I Submit A Good Pull Request?

     2

----------------------------------

     3

     4

It's highly recommended to write nice and clean python code. Beremiz

     5

project tries to follows most of PEP-8 recommendations. They are

     6

automatically checked on every push and merge by Bitbucket pipelines.

     7

     8

To avoid pushing "unclean" code, i's recommended to add one of the following

     9

commands to pre commit Mercurial hook into .hg/hgrc configuration file.

    10

    11

Unfortunately script can't distinguish between real commit and shelve. If you

    12

are using shelve (or maybe some other affected commands), it's recommended to

    13

use pre-<command> and post-<command> hooks to create flags to skip checks on

    14

some operations.

    15

    16

    17

```

    18

[hooks]

    19

pre-shelve.linter = touch .hg/skiphook

    20

post-shelve.linter = rm .hg/skiphook

    21

pretxncommit.linter = ./tests/tools/check_source.sh --only-changes

    22

```

    23

or the same done using Docker container, so result will be the same as

    24

on Bitbucket pipeline.

    25

    26

```

    27

[hooks]

    28

pre-shelve.linter = touch .hg/skiphook

    29

post-shelve.linter = rm .hg/skiphook

    30

pretxncommit.linter = hg status -m -n -a -n -I '**.py' --change $HG_NODE > files.lst && docker run --volume=$PWD:/beremiz --workdir="/beremiz" --volume=$PWD/../CanFestival-3:/CanFestival-3 --memory=1g --entrypoint=/beremiz/tests/tools/check_source.sh skvorl/beremiz-requirements --files-to-check files.lst

    31

```