Hello,
I'm trying to customize the startup process for flashing an application with bootloader. However I want some manual actions (like resetting or connecting without download) still work relatively "normal", so my idea was to check the state of some variables within the customized callbacks in the Ozone project file to do different things.
Now to the problem: I've found out that there is a system variable VAR_CONNECT_MODE to define the type of connection/download (although this variable name is nowhere listed in the Ozone documentation!). But reading this variable always returns 0xC, no matter which of the modes CM_DOWNLOAD_RESET/CM_ATTACH/CM_ATTACH_HALT has been set before. This seems like a bug. Can you confirm?
The possible values CM_DOWNLOAD_RESET/CM_ATTACH/CM_ATTACH_HALT evaluate to 0/1/2 respectively, so where does that 0xC come from?
I tried:
Util.LogHex("VAR_CONNECT_MODE=", VAR_CONNECT_MODE); -> always prints "VAR_CONNECT_MODE=0xC"
if (VAR_CONNECT_MODE == 0xC) {Util.Log("true");} -> always prints "true"
A similar phenomenon happens with reading VAR_RESET_MODE which returns 0x10 although the possible values RM_RESET_AND_RUN/RM_RESET_HALT/RM_BREAK_AT_SYMBOL are 0/1/2.
I'm using Ozone V3.26e.
I'm trying to customize the startup process for flashing an application with bootloader. However I want some manual actions (like resetting or connecting without download) still work relatively "normal", so my idea was to check the state of some variables within the customized callbacks in the Ozone project file to do different things.
Now to the problem: I've found out that there is a system variable VAR_CONNECT_MODE to define the type of connection/download (although this variable name is nowhere listed in the Ozone documentation!). But reading this variable always returns 0xC, no matter which of the modes CM_DOWNLOAD_RESET/CM_ATTACH/CM_ATTACH_HALT has been set before. This seems like a bug. Can you confirm?
The possible values CM_DOWNLOAD_RESET/CM_ATTACH/CM_ATTACH_HALT evaluate to 0/1/2 respectively, so where does that 0xC come from?
I tried:
Util.LogHex("VAR_CONNECT_MODE=", VAR_CONNECT_MODE); -> always prints "VAR_CONNECT_MODE=0xC"
if (VAR_CONNECT_MODE == 0xC) {Util.Log("true");} -> always prints "true"
A similar phenomenon happens with reading VAR_RESET_MODE which returns 0x10 although the possible values RM_RESET_AND_RUN/RM_RESET_HALT/RM_BREAK_AT_SYMBOL are 0/1/2.
I'm using Ozone V3.26e.