Datasheet

Differences

—a

short enum

type

—a

struct

containing only fields of short alignment.

If possible, you should recompile your SDT 2.50/2.51 object using ADS. If you

cannot recompile your object in ADS, you can compile your ADS code with the

-zas4

option to revert to SDT 2.50/2.51 behavior.

Note

— Code compiled with the

-zas4

option in ADS is incompatible with other

ADS objects, including the ADS C++ libraries.

—The

-zas

option is deprecated in ADS 1.2 and will not be supported in

future releases.

— You can specify the

-zas1

in SDT 2.50/2.51 as a starting point to migrate

your SDT code to ADS.

In addition, if you link with SDT 2.50/2.51 objects you cannot take advantage of some

ADS debug enhancements. In particular, you cannot unwind the stack through SDT

2.50/2.51 code.

Entry point used with debugger

When an image with an entry point is loaded:

• the CPSR register is set to the value corresponding to a warm boot

• the IRQ and FIQ flags are set (disabling all interrupts)

• mode is set to Supervisor

• Condition Code flags are unchanged

• the processor executes in ARM state.

If the image contains no entry point, no change is made to the CPSR.

Default interrupt settings for debug targets

The ADS default for interrupt settings is different to that for SDT, and more accurately

reflects the hardware power-up settings of an ARM core. The debuggers no longer

enable interrupts during start-up. Interrupts are initially disabled for all debug targets

except Angel (Angel requires interrupts to be turned on to behave correctly).

In SDT 2.50/2.51, initially

cpsr = %ift_SVC32

for all targets.

In ADS, initially

cpsr = %IFt_SVC

for all targets except Angel, which has

%ift_SVC