0177c59f4a
* Add editorconfig and pre-commit config Editorconfig is widly used and supported file. It says basic things how files should be formatted. pre-commit is tool which can automatically check some basic checks like code formatting everytime someone makes commit. This can also be used in CI to run these things. Then it is very easy to do same things locally as in CI. This also makes easy to select clang-format version so everyone is using same one. * clang-format: Ignore folders where are external code We should not format external code. Add clang-format files to exclude those. We should move external code always to example external/ folder so we can exclude those more easily. * clang-format: Remove custom zephyr/.clang-gormat This clang-format file where introduces before our root clang-format. It does not make sense anymore as we have root clang-format. Removing this will unifie formatting in whole repo. * clang-format: Add couple new rules Add couple new formatting rules. Always align const to left side. We did have only one place where it was right side so this make sense as it is already rule for us. I choose also insertbraces becuase when I run this I notice that we have lot of multiline code without braces. So very error prone places. This will take error possibility away. Repo also always use braces even with single line statments so this does not matter much. * ci: Add pre-commit validation Validate pre-commit in CI. * format: Convert spaces to tabs in Makefiles Makefile normally use tabs. We enforce that with editorconfig. Fix couple places where spaces where still in use. --------- Co-authored-by: Kari Argillander <kari.argillander@fidelix.com>
BACnet MS/TP on Atmel XMEGA-A3BU XPLAINED evaluation board. An RS-485 add-on board (daughterboard, shield) was designed to handle the RS-485 interface and some LEDs. See rs485-shield/ folder for EAGLE CAD design files. Use the Configuration "Debug-XPLAINED" and not in "Debug" or "Release". "CONF_BOARD_ENABLE_RS485_XPLAINED" is defined and used in led.c, rs485.c, and main.c for specific board I/O. When it is not defined, the I/O is either removed (i.e. led.c, main.c) or altered (rs485.c). There are other defines in the "Debug-XPLAINED" Configuration which include other parts of the XPLAINED platform code. For your own board, you could just change rs485.c, main.c, and led.c to use the I/O that you want to use, and not worry about the "CONF_BOARD_ENABLE_RS485_XPLAINED". Or you can leave the "CONF_BOARD_ENABLE_RS485_XPLAINED" in the files so that you can always test on the XPLAINED platform with Debug-XPLAINED, and use "Debug" or "Release" for your project.