Release Notes February 2001 This document gives additional g
|
|
|
Top Searches for this datasheet
Release Notes
Release Notes
February 2001
This document gives additional general information Developer Suite (ADS 1.1). overview main differences between 1.1, 1.0.1 earlier (Software Development Toolkit), Getting Started Guide.
INSTALLATION
readme describes these issues: supported hardware platforms described Installation Guides Windows Unix platforms. following Operating System Patches/Service Packs required/recommended: Windows Service Pack above. Windows 2000 ServicePack Windows Second Edition Windows version HP-UX 10.20 requires Patch Number PHSS_16585 s700_800 10.X aC++ runtime library components (A.01.18), higher. This patch available from Electronic Support System
uses different license from that used with 1.0.1 1.0. upgrading from 1.0.1 1.0, contact your supplier license key. installing Windows error message
IDE.EXE, linked missing export OLE32.DLL
then need update DLLs. ole32.dll version less than 4.71.2900.0 then please download Microsoft' Dcom95.exe from Alternatively, could install Internet Explorer 38375]. During Installation, message
procedure entry point _lc_collate_cp could located dynamic link library MSVCRT.dll
please reboot install again. This occur with e.g. where older version msvcrt.dll still (loaded RAM), despite installing updated version onto disk. 41695] installed, deinstalled, then installed again different, directory, running from Start menu will report:
Warning 00066: Could change directory 'C:\Program Files\ARM\ADSv1_1\Bin'.
where directory where _previously_ installed. this, should either configure target (with Options->Configure Target), locate AXD' default session file (named default-1-1-0-0.ses) delete 41937] upgrading from 1.1: CodeWarrior uses folder named Metrowerks'in Windows directory store e.g. preference settings projects. running another version CodeWarrior that version will same folder files (and hence same preference information). When uninstall 1.0, uninstaller will delete Metrowerks folder. This usually correct thing running second version CodeWarrior using another CodeWarrior different target, will have lost preference settings. want retain preference settings non-ADS CodeWarrior, should save preferences file, 'CodeWarrior Prefs' before start uninstaller. This only applies Uninstaller, 1.0.1 Uninstaller Uninstaller. Windows unable commands (either from session, CodeWarrior) registry entry Release Notes Page
Release Notes
Manager\Environment exists. installer will environment variables under this entry, will them autoexec.bat. During installation will asked want update autoexec.bat. This problem rare, suspected happen only dual boot machine W98/NT machine. avoid problem ensuring that your autoexec file exists contains following information equivalent your installed path different default):
ARMLIB=C:\Program Files\ARM\ADSv1_1\LIB ARMINC=C:\Program Files\ARM\ADSv1_1\INCLUDE Path=C:\Program Files\ARM\ADSv1_1\BIN;%PATH% ARMHOME=C:\Program Files\ARM\ADSv1_1
DOCUMENTATION
cannot search following characters DynaText searches. first described within DynaText documentation, second described. (i.e. underscore, dollar, minus, period) (i.e. colon, semicolon, question mark, asterisk, open round bracket, close round bracket, equal, less than, greater than, double quote, open square bracket, close square bracket). workaround documents. install documents part your original installation, install them invoking installation again, choosing PDFs. DynaText allows search occurrences words, phrases, patterns. This means that must wildcard characters want search pattern which complete word. example should specify option*'if want find references both option'and options'(and optional' specify option' will find references options'(or optional' Read DynaText Documentation full details DynaText.
CORE TOOLS
Assembler: Very large assembler files under Windows Under Windows, assembler source files must CR-LF terminated total source size exceeds assembler's cache size (default 8MB). most likely visible effect that assembler appears looping. syntax ADRL directive given Assembler Guide, section 4.9.2, ADRL pseudoinstruction"
ADRL<cond> register,expr register,expr
should read:
ADR<cond>L
C/C++ Compilers When compiling stack checking, dropped below sl-256 amount exceeding size register save area. solution allow more than bytes slop below 256+56 bytes your program makes floating-point hardware (all integer registers saved). 256+56+96 bytes your program uses (all registers saved). 256+56+132 bytes your program uses (all registers saved "map" word from FSTMX). memory models supported library stack stacking, must claim extra stack slop implementing function _user_stack_slop (see Compiler, Linker, Utilities Guide, section 4.9.7). suitable implementation assembly language (build using armasm -apcs /swst) AREA ||.text||, CODE, READONLY EXPORT _user_stack_slop Release Notes Page
Release Notes
user_stack_slop PROC r0,#56 r1#0 pc,lr ENDP
#56+96 #56+132 your value.
(build using armcc -apcs /swst), use: struct _stack_slop {int always, cleanup;}; _value_in_regs struct _stack_slop _user_stack_slop(void) struct _stack_slop slop; slop.always 56+96 56+132 slop.cleanup your value return slop; aware that _user_stack_slop only exists weak reference, _user_stack_slop only function section, linker will remove prevent this, -keep _user_stack_slop option when linking. 41901] select which implies (such "-cpu ARM10200", which implies VFP), also select different (e.g. softvfp), compiler will compile code whatever specified last. example, -cpu ARM10200 -fpu softvfp -cpu ARM10200 -cpu ARM10200 -fpu softvfp correctly gives hard gives hard VFP, silently compiles code soft with (correctly) hard build attributes
command line then your choice must come after your choice. Similarly, CodeWarrior should after CPU. Note that ARM1020T equivalent with implied setting), want compile ARM10 require hardware then '-cpu ARM1020T -fpu softvfp' instead '-cpu ARM10200 -fpu softvfp'. 37665] Overload resolution conversion operators does consider implicit this" argument. 32449] should compiler-generated section names scatter-loading descriptions. names generated different those generated standard section names used:. "C$$code" ".text" "C$$data" ".data" "C$zidata" ".bss" "C$$constdata" ".constdata". normally safer specify code/data sections scatter files using objects' names attributes (unless using -zo) $Sub$$ $Super$$ 37485] These defined specification ARMELF.pdf (SWS ESPC 0003 B-01) which supplied with pdf\specs directory. Section 5.4.4, Sub-class super-class symbols" says: symbol $Sub$$name sub-class version name. symbol $Super$$name super-class version name. presence definition both name $Sub$$name: reference name resolves definition $Sub$$name. reference $Super$$name resolves definition name. error refer $Sub$$name, define $Super$$name, $Sub$$. $Super$$. recursively." These symbols used example, 'patch' existing functions. Suppose have some legacy code/objects which cannot change. Suppose function foo() called from fred(), want perform some additional processing front foo. simply define function called $Sub$$foo, which does extra work, then jumps $Super$$foo, e.g:
Release Notes
Page
Release Notes
extern void ExtraFunc(void); extern void $Super$$foo(void); void $Sub$$foo(void) ExtraFunc(); does some extra work $Super$$foo();
example their given ADS\Examples\picpid. Profiling: Callgraph profiling cannot used program built ROPI (Read Only Position Independent) uses function pointers launched address other than preferred base address profiler does understand virtual function calls. Profiling assumes (r12) unused over function calls, take care when using assembler. profiler will recognise Thumb <register> instructions correctly. must compile Thumb code containing variable function calls architecture wish callgraph profiling.
CODEWARRIOR
uses CodeWarrior Pro5.1 4.0.4 build from Metrowerks. ADS1.0.1 used 4.0.1 build Metrowerks changed format Debugger Settings target preference data. This means that opening existing project files (*.mcp files) will cause CodeWarrior prompt whether convert Debugger Settings format, then attempt save original project project.old.mcp, before converting original file. projects make Debugger Settings panel, this change should benign projects will convert back opened with ADS1.0.1 again. CodeWarrior appears briefly then vanishes, crashes before managing show toolbar buttons, there likely problem with servers being registered properly. resolve this running regservers.bat from bin" directory. This should display
Registering core DLLs DllRegisterServer succeeded. DllRegisterServer succeeded. DllRegisterServer .\plugins\Support\Catalog.dll succeeded. DllRegisterServer succeeded. DllRegisterServer .\plugins\com\LayoutEditor.dll succeeded. DllRegisterServer succeeded. DllRegisterServer .\plugins\com\MenuEditor.dll succeeded. DllRegisterServer .\plugins\com\CatalogWin32.dll succeeded. IDE.exe Done.
Buttons project view text window work, Text window gets Unhandled Exceptions when closing CodeWarrior, very likely that have version comctl32 which insufficiently mature because Installer failed install have rebooted after install. CodeWarrior requires version 4.71 later. check version upgrade please
C:\Program
must upgrade Administrator also check version selecting comctl32.dll your Windows System (winnt\system32) directory looking properties version page (alt+Enter, context menu, right mouse Properties). version that known work shows 4.72.3609.2200. Revert Panel button settings panels enabled tools. must Save button store your changes project, close settings panel window discard unwanted changes. Tooltips work target settings panels. preferable small fonts. Small fonts allow some target settings panels used more easily. Start->Settings->Control panel->Display->Settings->Font Size switch small fonts. After that, improve legibility Start->Settings->Control Standard
Release Notes
Page
Release Notes
(large). Large fonts will cause tools displayed scrolling window, buttons field labels CodeWarrior panels have their text compressed off. Implicit template instantiations generate definition compilation unit. This might result multiple definitions template item browser. should include files CodeWarrior using option 'Equivalent Command Line' dialogue compilers'Language Settings. this, CodeWarrior knowledge included files will lose Browse information Error processing associated with included files. Instead, should Target->Access Paths. Interleaved C/assembler output (armcc -fs) from CodeWarrior compilers support "-S" -fs" options. generates assembly source file (.s) from source. generates text file source code interleaved with assembly code generated. either these switches "Equivalent Command line" target setting window (Alt+F7). will create text file named "source.c.s" from source file "source.c". However, because file created, CodeWarrior adds project, will then invoke armasm, attempt assemble This assemble step will succeed because output from fully assemblable source file. -fs" will create text file named "source.c.txt" from source file "source.c", link step will fail expected. possible switch explicitly name output file prevent this behaviour, because equivalent command line must suitable with sources project. wish create build Target (e.g. "DebugRel_listings"), that uses same build settings your 'normal' build, with addition "-S" -fs" generate necessary output file. 43159] Synchronization problem with files remote server CodeWarrior sometimes lose synchronisation between files your working directory files remote server (which CodeWarrior caches). this, change Target settings, Build extras' modification date caching'to (for targets). When CodeWarrior always able determine source file been modified outside immediate CodeWarrior environment. This applies using third-party editor, multi-user development environments where source files modified checked through version control systems. more detail, refer CodeWarrior Guide, section 9.3.3. 38713]
DEBUGGERS
Debugger-to-target support debuggers (AXD, ADW, ADU, armsd), ARMulator Remote_A within support 1.5.1, latest version Remote Debug Interface. AXD, support ARMulator, Remote_A, Multi-ICE Multi-ICE 2.0. additionally supports RealMonitor, RMHost (RealMonitor.dll) through RMTarget. Armsd supports ARMulator Remote_A, Multi-ICE. EmbeddedICE supported (via Remote_A) debuggers, must have ICEAgent version 2.07 EPROM fitted.
default interrupt settings different that SDT, more accurately reflects hardware power-up settings core. debuggers longer enable interrupts during start-up. Interrupts therefore initially disabled debug targets except Angel (which requires interrupts turned order behave correctly). 2.50/2.51, initially cpsr %ift_SVC32 (for targets) ADS, initially cpsr %IFt_SVC (for targets except Angel, which %ift_SVC, because requires interrupts enabled) accidentally download Multi-ICE' Semihosting handler target board invalid address (above $top_of_memory), will report:
"DBE Warning 00023: Internal/Usage error DBE_ERROR_INTERFACE_USAGE: Debug Engine called with wrong parameters with missing/inconsistent data filled into objects passed
Release Notes
Page
Release Notes
instead more friendly:
"Unable install Semihosting Handler".
This happen, example, when Semihosting handler downloaded default address (0x70000) onto Integrator board which memory 0x40000. 44413] AXD' report 'Error occured' some commands (e.g. stop'when image loaded). This message means that command cannot executed with target current state (busy, stopped, etc). Solaris appear hang'when focus changed during in-place editing. example, double-click register Registers window edit then double-click different register. this, should modify X-Windows configuration file. users $HOME there should file called .Xdefaults, needs created. file needs contain line
Dtwm*secondariesOnTop: True
Take care enter this exactly given case important! 41213] hardware watchpoint e.g. global variable, code execution will stop whenever that address written even value written same. will message:
Warning 00085: target stopped because hardware breakpoint watchpoint
when same value written (i.e. contents have changed). Conditional hardware watchpoints also broken, because code execution will always stop when watchpoint hit, even condition been met. Software watchpoints behave correctly, stopping only content actually changes. 44055] Can't hardware watchpoints global/static objects above Stack Pointer 42061] possible hardware watchpoint e.g. global variable which resides address above stack pointer (SP). This applies debuggers (armsd, AXD, ADU). debuggers wrongly assume that global stack because resides address above stack pointer (SP). Watchpoints stack variables always software watchpoints, hardware watchpoint will used. workaround specify address global variable, instead name, when setting watchpoint. address variable found using e.g.: 'print &variable'. Suppose this returns address 0xA00000, hardware watchpoint then placed variable (assuming target supports this) with: 0xA00000 (AXD) watch 0xA00000 (armsd, ADW, ADU) When connecting non-stop targets (e.g. RealMonitor) which already running, unable ascertain current execution context. this case current visual indicators will positioned according this address. 39119] When using Multi-ICE with AXD, watchpoints individual bytes within word. However, change watched byte only detected byte itself addressed value changed. change location detected occurs instruction changing word half-word that contains byte, unless address word half-word also that byte. This happens because Multi-ICE programs registers watchpoint unit EmbeddedICE logic core stop execution when data write specified address occurs. Only exact address matches stop program execution. Suppose want watch byte address 0x3. This could changed write size) address 0x3, halfword write address 0x2, word write address 0x0. There program EmbeddedICE logic trap conditions, Multi-ICE uses only 42613] Interleaving source which several instances code exist disabled i.e. such source interleaved. example would template that instantiated with different parameters. This results least copies code source lines. provides multi-processor enabled interface, there targets that support this feature this release. Multi-processor support Multi-ICE provided running multiple copies AXD. ADW/ADU/armsd commands coproc'and cregdef'describe register coprocessor specifies contents registers formatted display. direct equivalent these commands will only display/edit standard coprocessor registers, except when ARMulating ARM10
Release Notes
Page
Release Notes
XScale processors, where equivalent functionality provided self-describing module armperip.xml 31341]. requires components registered before start message:
initialization failed. Ensure relevant OCX's registered Router Init Failed" this because OCXs have been registered, registration
failed. 39311] version, rectify this running register.bat" from \bin" directory. Unix version, solution 'register.sh' \bin" directory. Note Desktop must before doing this. part Unix installer, usrsetup.sh offers user option register OCX's debugger. might answer 'no' e.g. debugger will different machine than being installed this case, will need manually register OCXs above) machine debugger. uses scripting support Command Line Interface, (CLI). This implemented using VBScript.DLL which component. components need registered" before they utilized other applications. version VBScript shipped with 3.1. There other versions your machine. installer will copy version into directory, will overwrite existing versions your system directories elsewhere. will function correctly with versions VBScript earlier than 3.1. Specifically command line interface will available. This means version VBScript registered must least 3.1. However applications which rely versions earlier than function with later versions. possible have only version registered time. your system currently relying pre-3.1 version being registered, wish command line interface, suggested that temporarily register version directory. When using should re-register your existing version return normal system usage. directory contains tool regcomif.exe which will register supplied OCX. This program used register either supplied re-register earlier version this necessary. simply invoked with name parameter:
regcomif <file>
Note that program uses Win32 LoadLibrary call which attempt load file from directory containing program itself. therefore safer specify full pathname there uncertainty which might found. Some options available (listed option) unlikely needed. Note that registering component will silently remove registration earlier version. tooltips intermittently fail appear Win98. 28581] variable window does automatically update child objects dynamic classes when they change, message "Out Scope" displayed. workaround view dynamic classes watch window. 32629] When running HP/UX connecting Multi-ICE 1.4, message "Wind/U Error (240): Function SetCursor, API's must only called from primary thread this platform" appear console window. This harmless ignored. This will fixed next release Multi-ICE 37903] Loading images into from command-line (with -debug -exec) fail HP/UX systems which have auto-mount when image loaded auto-mount point. avoid this, specify full path name, e.g. -debug This problem caused HP/UX system bug, which fixed applying these patches: ACE5 (Dec These Additional Core Enhancements QualityPack (Dec Quality Pack pack cumulative patches that releases every months. 37165] execute script file when launching possible execute script file when launching AXD, some debug target properties, e.g. launch from with:
-script go.txt
where go.txt contains:
load image.axf vector_catch
Release Notes
Page
Release Notes
semihosting_enabled swat $top_of_memory 0x400000 etc.
also launch with script file from CodeWarrior, configuring target settings. 'Equivalent Command Line', enter:
-script go.txt
then press 'Save'.
ARMULATORS
ARMulator booted with HighVec enabled, then neither semihosting calls will work. They will work system booted with HighVec disabled subsequently enabled.
REMOTE_A
Users EPI' JEENI with debugger remote_a should ensure they have latest version JEENI firmware fitted, currently version 2.0. Contact more details.
ANGEL
These releases Angel supported ADS: Angel 1.31, released with 1.0.1 Angel 1.20, released with 2.50 2.51 Angel 1.04, released with 2.11a
does support Angel 1.02, released with 2.11, earlier releases Angel. Angel supplied part Firmware Suite (AFS),
GATEWAY
Users Agilent Probe with debugger gateway.dll should ensure they have latest version Probe firmware fitted. HPE3499B Series Emulation System, please ensure that generics version A.07.65 higher JTAG Emulation version B.02.07 higher. using HPE8130A Series Emulation System, please ensure that generics version A.01.06 higher emulator version A.05.05 higher. Refer your Agilent documentation details display update firmware versions. Breakpoints watchpoints fail cleared correctly when semihosting vector_catch been cleared semihosting been switched single vector_catch breakpoint been set. Under these circumstances, debugger will typically report error setting clearing breakpoint when reloading current image. 43905] This release Gateway does support RealMonitor. Contact latest details availability.
TRACE
Trace Debug Tools work with 1.0/1.0.1, 1.1. Please upgrade 1.1.
Release Notes
Page
Other recent searches
XC4000E-1 - XC4000E-1 XC4000E-1 Datasheet
XC4000E-2 - XC4000E-2 XC4000E-2 Datasheet
TPS51217 - TPS51217 TPS51217 Datasheet
TDA9209 - TDA9209 TDA9209 Datasheet
SK1929 - SK1929 SK1929 Datasheet
KPDA02-103 - KPDA02-103 KPDA02-103 Datasheet
EM484M3244VBA - EM484M3244VBA EM484M3244VBA Datasheet
CR2300SA - CR2300SA CR2300SA Datasheet
Privacy Policy | Disclaimer
© 2012 Datasheet Archive
