------------------------------------------------------------------------- For the potential PYTHON detection issue, create a proper and clear description of this phenomenon and send to: support@axivion.com RESOLUTION: Cached Python is OK. Be sure to use a 64-bit python. ------------------------------------------------------------------------- VS Plugin Download the VSIX from the dashboard (or store it locally. Install normal way the VSIX. Then add the local host in the AXIVION properties (Tools Options) Now we add the AXIVION plugin window with view->Other Windows-> ------------------------------------------------------------------------- GCC ARM path W:\ALGitRepo\ToolsGeneric\Compilation\ArmGeneric\GCC\arm-none-eabi\9.2.1\bin;%PATH% CAFE CC Path set PATH=C:\Program Files (x86)\Bauhaus\bin;%PATH% ------------------------------------------------------------------------- This section handles changes in Make.bat for running the bare-metal build. We will make a separete instance of a so-called "compiler" for AXIVION. This is separated as an independent solution configuration where needed. It is easy to batch for the nightly and also run locally so this could or should be expected to be a good solution method. ------------------------------------------------------------------------- ------------------------------------------------------------------------- This section handles setting the environment variables to run "start_analysis.bat". We need PYTHON ENV variable for this and also the Bauhaus path. Option for AL standalone: (Use relative path) set PATH=%CD%\..\..\..\..\..\..\..\ToolsGeneric\StaticCodeAnalysis\AXIVION\bauhaus-suite-7_4_3-x86_64-windows\bauhaus-suite\bin;%PATH% set BAUHAUS_PYTHON=%CD%\..\..\..\..\..\..\..\ToolsGeneric\Utilities\CommonDomain\python\Python310_64bit\python.exe ------------------------------------------------------------------- This section briefly handles how to run an analysis from a project that is already setup using start_analysis.bat. * Change the project name in "start_analysis.bat" (around line 15). * Method 1: Execute the full REBUILD just with AXIVION. This gives us the *.ir file. * Ensure that you have configured the compiler, as shown in the brief sub-section below. * Method 2: - Navigate to the "AXIVION" folder in the standard "ToolsSpecific" area of your project. - Add Bauhaus and JAVA to your path (see above). - Now execute: "start_analysis.bat --skip_build" * Now we should have the *.ir file and we can observe the messages and statistics in the TBD. ------------------------------------------------------------------- This section briefly handles how to view the analysis results with the dashboard. * Some of these tricks are related to our (local, specialized) use of IBM rational JAVA that comes onto a lot of client machines through the ifrastructure of DOORS. * In other words, if you have an environment variable JDK_HOME or JRE_HOME, then please "un-set" both of these in your command shell with the "set" command. Example: set JDK_HOME * Navigate to "C:\Axivion\dashboard\config" * Add Bauhaus and java to the path. Example (Use Bauhaus from ToolsGeneric): (TBD: Introduce our own AL-specific JAVA location, environment, etc.) (TBD: Maybe consider to establish Dashboard-Location to be either directly in or relative to "ToolsGeneric"). set PATH=W:\ALGitRepo\ToolsGeneric\StaticCodeAnalysis\AXIVION\bauhaus-suite-7_4_3-x86_64-windows\bauhaus-suite\bin;W:\ALGitRepo\ToolsGeneric\Utilities\CommonDomain\java\jdk-11.0.16.8-hotspot\bin;%PATH% * set JAVA_HOME (use the Java in ToolsGeneric). Example: (TBD: Introduce our own AL-specific JAVA location, environment, etc.) (Please note when setting JAVA_HOME, do *not* include the "bin" folder!!!!) set JAVA_HOME=W:\ALGitRepo\ToolsGeneric\Utilities\CommonDomain\java\jdk-11.0.16.8-hotspot * Run the dashboard with "dashserver start". * Look for the message "dashboard started successfully" in the command shell results. * Then open the browser and navigate to "localhost:9090". ------------------------------------------------------------------- ------------------------------------------------------------------- This section briefly handles how to set up BAUHAUS for a new project such as Cln1 or HDRTWO. * Install AXIVION. * Put the license file into the config directory. Let's remember how to configure a compiler. * Get the stuff from the project-specific AXIVION folder. * Delete the compiler-config JSON. * Identify the bin path and important core flags of the compiler: Example HDWTRO Tricore HiTech: PATH is: W:\ALGitRepo\ToolsGeneric\Compilation\TriCore\GCC_HighTec\tricore\v4.9.2.0\bin AND add Bauhaus to the path: set PATH="C:\Program Files (x86)\Bauhaus\bin";W:\ALGitRepo\ToolsGeneric\Compilation\TriCore\GCC_HighTec\tricore\v4.9.2.0\bin;%PATH% TOOL is: tricore-g++ KEY FLAGS is/are: -mtc162 Now configure the compiler with the program "gccsetup" (remember any licensing stuff for the compiler if needed, since AXIVION obviously calls the compiler). This should create "compiler_config.json". * Go to the location of the specialized JSON files and add BAUHAUS path. Then run "axivion_config .". * Go to the project-specific AXIVION foler in "ToolsSpecific". Open a command shell. Add "Bauhaus-bin" to the path. Add path of python to ENV-variable such as: set BAUHAUS_PYTHON=W:\ALGitRepo\ToolsGeneric\Utilities\CommonDomain\python\Python310_64bit\python.exe AND also set JAVA_HOME set JAVA_HOME=W:\ALGitRepo\ToolsGeneric\Utilities\CommonDomain\java\jdk-11.0.16.8-hotspot (But *do not* use the \bin part of the java path.) Then run: "dashserver init SERVER_HTTP" "dashserver start" Note the password for the browser. * Now go to chrome and navigate to "localhost:9090". * The server instance is: http://139.128.32.47:9090 * Now we configure your specialized JSON files. * Go to the location of the specialized JSON files and add BAUHAUS path. Then run "axivion_config ." ------------------------------------------------------------------- LOCATION of IR file W:\ALGitRepo\Cln1\Build\Bin\Z03In005_App_AXIVION\Z03In005_App_AXIVION.ir (Or something similar for Al073 in HDRTWO) How do I start the dashserver? dashserver init SERVER_HTTP dashserver start Open a browser such as chrome. Go to local host as shown here: localhost:9090 Use these credentials user: admin password: HvsJUyAIfY1botK5_ozAh2IJBdw g++ -x c -std=c99 -gdwarf-2 -fno-exceptions -ffunction-sections -fdata-sections -mcpu=cortex-m4 -mtune=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -ffast-math -mno-unaligned-access -mno-long-calls -O2 -finline-functions -finline-limit=16 -Wall -Wextra -pedantic -Wmain -Wundef -Wsign-conversion -Wunused-parameter -Wuninitialized -Wunreachable-code -Wswitch-default -Wcast-align -Wmissing-include-dirs -Winit-self -Wdouble-promotion -Wunsuffixed-float-constants g++ -x c++ -std=c++11 -fno-rtti -fno-weak -fno-nonansi-builtins -fno-use-cxa-atexit -fno-enforce-eh-specs -fno-nonansi-builtins -fno-threadsafe-statics -fconstexpr-depth=16 -fno-enforce-eh-specs -fno-use-cxa-atexit -gdwarf-2 -fno-exceptions -ffunction-sections -fdata-sections -mcpu=cortex-m4 -mtune=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -ffast-math -mno-unaligned-access -mno-long-calls -O2 -finline-functions -finline-limit=16 -Wall -Wextra -pedantic -Wmain -Wundef -Wsign-conversion -Wunused-parameter -Wuninitialized -Wunreachable-code -Wswitch-default -Wcast-align -Wmissing-include-dirs -Winit-self -Wdouble-promotion GCC C/C++ flags: -mcpu=cortex-m4 -mtune=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -ffast-math -mno-unaligned-access -mno-long-calls