Difference between revisions of "HANcoder/STM32/Blocks/Build Settings"
Line 3: | Line 3: | ||
info= | info= | ||
With this block you can set two options: | With this block you can set two options: | ||
− | |||
Option to automatically add parameters and signals | Option to automatically add parameters and signals | ||
− | |||
Option to automatically flash after the build procedure is completed. | Option to automatically flash after the build procedure is completed. | ||
− | ==Auto add== | + | ===Auto add=== |
The option to automatically add parameters and signals runs a script which searches for constants | The option to automatically add parameters and signals runs a script which searches for constants | ||
Line 19: | Line 17: | ||
Simulink.Signal with its storage class set to 'ExportedGlobal'. These signals will become visible in HANtune. | Simulink.Signal with its storage class set to 'ExportedGlobal'. These signals will become visible in HANtune. | ||
− | ==Auto flash== | + | ===Auto flash=== |
The option to automatically start flashing after the build procedure calls MicroBoot with the interface | The option to automatically start flashing after the build procedure calls MicroBoot with the interface | ||
Line 29: | Line 27: | ||
BuildSettings.png | BuildSettings.png | ||
− | |maskImage=BuildSettingsMask1.png | + | |maskImage= |
+ | BuildSettingsMask1.png | ||
+ | |||
+ | |||
− | + | |AutoAdd= Default | |
+ | |AutoFlash= Default | ||
}} | }} |
Revision as of 10:15, 22 March 2017
Supported Targets: Olimexino, E407, P405
General information about Build Settings
With this block you can set two options: Option to automatically add parameters and signals Option to automatically flash after the build procedure is completed.
Auto add
The option to automatically add parameters and signals runs a script which searches for constants and signals with names which have not been defined in the workspace. When it finds a constantblock it will check if the value is defined in the workspace and if not it will add this value as a Simulink.Parameter. It will also set its storage class to 'ExportedGlobal', this will ensure it will end up in the ASAP2(.A2L) file. All parameters in the ASAP2 file will be editable in HANtune. Because each constant will need a value before the model can be build, you will be prompted for a value. (press cancel to abort the build) All signals in the model that have a valid Matlab name will automatically be added to the workspace as Simulink.Signal with its storage class set to 'ExportedGlobal'. These signals will become visible in HANtune.
Auto flash
The option to automatically start flashing after the build procedure calls MicroBoot with the interface that was selected in the block. It will flash the .srec that was just built from the model. Note: MicroBoot.exe must be located in ..\Host\MicroBoot\ relative to the blockset path (the path where the model is located)