| The Datasheet Archive - 100 Million Datasheets from 7500 Manufacturers. |
1.0.1 Release Notes Sept 2000 This document gives additional
Top Searches for this datasheetRelease Notes 1.0.1 Release Notes Sept 2000 This document gives additional general information Developer Suite (ADS 1.0.1). overview main differences between (Software Development Toolkit), Getting Started Guide. INSTALLATION supported hardware platforms described Installation Guides Windows Unix platforms. following Operating System Patches/Service Packs required: users should running with Service Pack above. Solaris 2.5.1 requires Patch number 103640-xx SunOS 5.5.1 kernel patch, where higher. This patch available from http://sunsolve1.sun.com 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 unable commands (either from session, CodeWarrior) registry entry Manager\Environment exists your Windows machine. installer will environment variables under this entry, will them autoexec.bat. During installation will asked want update autoexec.bat. This problem occurs Windows only, 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\ARM Developer Suite\LIB ARMINC=C:\Program Files\ARM\ARM Developer Suite\INCLUDE ARMHOME=C:\Program Files\ARM\ARM Developer Suite upgrading from 1.0.1: 1.0.1 uses same license-management 1.0. therefore your existing licence file (i.e. armlmdxx.lic file licenses directory) with 1.0.1. 1.0.1 Installer (Windows) will recognise earlier installation allow upgrade without having de-install 1.0. However, 1.0.1 Installer doesn't deduct space existing files when calculating space required installing 1.0.1. This means that 1.0.1 refuse upgrade disk space becoming low. solution uninstall 1.0, retain licence (armldxx.lic) file. Uninstaller (Windows) 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. Release Notes Page Release Notes 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 English Documentation full details DynaText. CORE TOOLS Assembler: armasm defaults -apcs /noswst (not -apcs /swstna 1.0). 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. C/C++ Compilers packed field integer-like struct union) that itself packed struct union) loses packed attribute, compiler generates wrong code result. (The compiled code accesses field were naturally aligned). 37565] integer-like struct word struct union which addressable fields have same address, word structure containing bitfields only). select setting which implies (such "-cpu ARM10200", which implies VFP), also select "soft" version FPU, your selection will (partially) ignored. example, -cpu ARM10200 -fpu softvfp -cpu ARM10200 -cpu ARM10200 -fpu softvfp Given: const a[]; only legal const int* return gives hard still gives hard VFP, silently compiles code soft produces hard build attributes Note that ARM1020T equivalent with implied setting. incorrectly placed zero-init section. This harmless (but slightly undesirable) unless compiling /ropi (run-time error) /rwpi (link error). work round problem changing code equivalent: const a[]; const int* return const Library support routines provided RogueWave libraries. These offer wider support than that with 1.10, although image sizes using will slightly larger about 25KB). asm("") syntax will work member functions defined within class. syntax instead. Release Notes Page Release Notes RogueWave libraries support 'long long' type 38333]. Opcode 'AND' inline assembler within compiler, please type upper case. 'and' alternate keyword '&&', converted '&&' front-end. Overload resolution conversion operators does consider implicit this argument. C++, static data inline function (which initialised with address file-scope variable) does work correctly. example: inline int* static int* data area return main() (&y! printf("WRONG!\n") return tries reference current data area instead workaround declare function inline. should compiler-generated section names scatter-loading descriptions. names generated different those generated particular C$$code C$$data longer supported), changed future. much safer specify areas objects' names attributes, described Linker section Tools Guide. $Sub$$ $Super$$ 37485] These defined specification ARMELFA08.pdf. 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: 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 example. Profiling: Call graph profiling cannot used program built ROPI (Read Only Position Independent) uses function pointers launched address other than preferred base address profiler will recognise Thumb <register> instructions correctly. must compile Thumb code containing variable function calls architecture wish call-graph profiling. Release Notes Page Release Notes CODEWARRIOR 1.0.1 uses CodeWarrior Pro5.1 4.0.1 build from Metrowerks. already have installation CodeWarrior before CodeWarrior Pro5 please note that format CodeWarrior projects (*.mcp files) changed over that used CodeWarrior Pro4. advised make backup copies those projects before opening them with CodeWarrior supplied with this product. Opening format project will prompt convert attempt save original project project.old.mcp. 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 Files\ARM\ARM Developer Suite\bin\401comupd.exe 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 keyboard accelerators 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 (large). Korean Windows, there known display problem with tool configuration dialogs (e.g. Compiler configuration), even when small fonts used 30583]. 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 compiler supports "-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). Both options create text file named "source.c.s" from source file "source.c". However, because file created, CodeWarrior will then invoke armasm, attempt assemble With "-S", this assemble step will succeed because output from fully assemblable source file. With -fs", assembly will fail with many errors. possible switch explicitly name output file prevent this assemble step, because equivalent command line must suitable with sources project. Release Notes Page Release Notes wish create build Target (e.g. "DebugRel_listings"), that uses same build settings your 'normal' build, with addition "-S" -fs" generate necessary output file. 39643] 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 debug agents targets within have been upgraded 1.51, version Remote Debug Interface. debuggers support debug agents (ARMulator, Remote_A) which released part ADS. They additionally support Multi-ICE 1.4. supports debug agents, Multi-ICE Multi-ICE 1.4. supports debug agents Multi-ICE (but Multi-ICE 1.3). Armsd supports debug agents, except Multi-ICE ARM966 ARMulator Unix. supports debug agents Multi-ICE 1.4. designed RDI1.51, does provide limited support Multi-ICE 1.3. limitation that stop" button does function. executing image will only stop result hitting break/watch point normal program termination. MultiICE users should upgrade Multi-ICE 1.4. EmbeddedICE still 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) Currently will allow watchpoints monitor same location. Therefore attempt create second watchpoint monitoring same location existing watchpoint results initial watchpoint being destroyed second watchpoint being instantiated. deletion initial watchpoint currently reflected GUI, which shows both watchpoints monitoring same location. (Location this context means register address) 35141] debuggers debugger will allow breakpoint statement that compiler determined never executed. allow your breakpoint could never reached. these circumstances compiler will generate code unnecessary statements, this form optimisation occurs levels optimisation. debuggers Under some circumstances, compiler' optimisations cause confusion local variables being displayed. Consider following examples: Case f(int global_var 200; return Compiler knows that later overwritten thus need Hence undefined until later assignment Release Notes Page Release Notes Looking variable between lines will show erratic value will show Only line will value displayed expected. compiler will perform this type optimisation (removal unnecessary code) optimisation levels. Case void f(int global_var 200; Compiler stores registers Compiler knows that used from this point re-uses Looking variable between lines will show correct value. After line will show erratic value. compiler performs this type optimisation higher, debuggers 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. debuggers Interleaving code containing for() loops result blocks assembler code being displayed twice. loop form "for where for(A; line body line will result assembler code being displayed lines debuggers support DWARF2 debug information. provides multi-processor enabled interface, there targets that support this feature this release. Multi-processor support Multi-ICE provided running multiple copies AXD. does support coproc command. this command describes register coprocessor specifies contents registers formatted display. will only display/edit standard coprocessor registers. 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. Release Notes Page Release Notes Some options available (listed option) unlikely needed. Note that registering component will silently remove registration earlier version. currently difficult restore input focus semihosting window focus lost while window waiting input. This give user impression that window hung. restore input user must click line which input expected, that after output text that visible current line. saves persistent data within Registry. this becomes corrupt, fail start. this occurs corrupted registry entry needs deleted. registry entry HKEY_CURRENT_USER\Software\ARM Limited\ARM Developer Suite\V1.0\AXD. Additional data held file called axd.env within directory. This should also deleted. tooltips intermittently fail appear Win98. Some data views within display intermittent redraw problems. problems occur more frequently within floating views than docked views. They occur where focus returns from other applications, Help windows dismissed while dialog boxes present. result rectangular areas view refreshed appear grey. Resizing view will refresh correctly. Minimising maximised floating views within area will cause minimised view lose system menu titlebar icons. then becomes confused state other views which behave erratically. Restoring views will correct behaviour. variable window does automatically update child objects dynamic classes when they change, message "Out Scope" displayed. However, watch window does correctly handle this problem, workaround view dynamic classes watch window. experience intermittent problems with help floating windows AXD. following specific problems known: only. This problem most likely occur when calling help from view views where Float within main window'is checked. reduce help screen less than main window position somewhere within window, then call help, subsequent calls (particularly from view) often fail repaint contents half help window. When some windows floated, example, Backtrace, pressing causes 'Help Topic does exist' displayed. same window docked call repeated, help topic displayed. 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. 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 /tmp_mnt/home/mydir/myimage.axf 37165] execute script file when launching 37859] 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 semihosting_enabled swat $top_of_memory 0x1000000 etc. also launch with script file from CodeWarrior, configuring target settings. However, this *must* done with 'Other' debugger selected. 'Command Line non-ARM debugger', enter: -script go.txt Release Notes Page Release Notes then press 'Save'. this with selected debugger, CodeWarrior (wrongly) complains: "Found '-script', expected -debug -exec". Note: currently only accepts '-param' option contrast which accepts several). Debuggers Guide, section 2.2.2, "AXD arguments" says: "Where command line includes image name options following image name will taken command line options image being loaded, AXD." Where $vector_catch $semihosting_enabled AXD? 37979] These settings commonly used when debugging embedded systems control exceptions 'caught' debugger. These Processor Properties window. access this, open System Views->Control Monitor window (Alt+C), which tabs, 'Target', 'Image', 'Files', 'Class'. Target tab, highlight processor, right-click pull menu, select 'Properties.'. These other controls available this window described 'ppvariable's section Debuggers Guide. They from AXD's using, (for example): vector_catch which equivalent armsd/ADW/ADU's: $vector_catch need update your armsd/ADW/ADU script files with AXD, like refer Command Comparison Table (between ADW) which download from page http://www.arm.com/ Some example scripts follow. Examples scripts following examples scripts which find useful: debug embedded system (code ROM/Flash) ADW/ADU/armsd: readsyms embed.axf cpsr %IFt_SVC SDT, this cpsr %IFt_SVC32) $vector_catch $semihosting_enabled $top_of_memory 0x40000 AXD: loadsymbols embed.axf setpc sreg cpsr 0xd3 vector_catch semihosting_enabled $top_of_memory 0x40000 check correct implementation memory management (e.g. Byte/short read/write access memory) ADW/ADU/armsd: examine 0x8000, *(char *)0x8000 0x99 print/h *(char *)0x8000 examine 0x8000, *(short *)0x8000 0x1234 Display Write Display Display Write word memory byte that address byte just written whole word again half-word that address Release Notes Page Release Notes print/h *(short *)0x8000 examine 0x8000, Display half-word just written Display whole word again byte read/writes, value read step does match value written step then there byte memory access problem (probably memory controller). Whether this read write problem identifiable comparing results steps Similarly half-word read/writes steps AXD: 0x8000 smem 0x8000 0x99 0x8000 0x8000 smem 0x8000 0x1234 0x8000 0x8000 prepare semihosting: ADW/ADU/armsd: load embed.axf $semihosting_dcchandler_address 0x100000 $semihosting_enabled AXD: load embed.axf semihosting_dcchandler_address 0x100000 semihosting_enabled Note: important semihosting_dcchandler_address before setting semihosting_enabled, because code downloaded when semihosting_enabled=2 command executed. program EmbeddedICE logic chain RANGEOUT ADW/ADU/armsd: $vector_catch $semihosting_enabled 0x00008098 0x00000003 0x00000000 0xffffffff 0x140 0x0bf 0x000080a8 0x00000003 0x00000006 0x00000000 0x001 0x0fe AXD: vector_catch semihosting_enabled sreg "coproc 0|c8" 0x00008098 sreg "coproc 0|c9" 0x00000003 sreg "coproc 0|c10" 0x00000000 sreg "coproc 0|c11" 0xffffffff Release Notes Page -Address value, unit (write_cycle) -Address mask, unit (ignore bottom bits) -Data value, unit -Data mask, unit (ignore data) -Control value, unit (enabled, chain SET) -Control mask, unit (chain only) -Address value, unit (flag_addr) -Address mask, unit (ignore bottom bits) -Data value, unit (value 0x6) -Data mask, unit (compare whole value) -Control value, unit (disabled, writes) -Control mask, unit (nRW only) Release Notes sreg sreg sreg sreg sreg sreg sreg sreg "coproc "coproc "coproc "coproc "coproc "coproc "coproc "coproc 0|c12" 0|c13" 0|c16" 0|c17" 0|c18" 0|c19" 0|c20" 0|c21" 0x140 0x0bf 0x000080a8 0x00000003 0x00000006 0x00000000 0x001 0x0fe ARMULATORS ARMulator booted with HighVec enabled, then neither semihosting calls will work. They will work system booted with HighVec disabled subsequently enabled. ARM9 LDRH, LDRB (unaligned) instructions, when followed instruction that uses loaded value, result interlock. Unfortunately, ARM9 ARMulator does correctly interlock loaded register (the loaded register available cycle soon). result correct cycle counts will cycle 33147]. This fixed ARM966 ARMulator. impact results when benchmarking real code will small because: code, compiler applies 'instruction scheduling' default (except with -O0). This rearranges machine instructions specifically avoid interlocks. Therefore, number interlock cases will minimised with compiled code. cycle counts will only cycle each interlocked instruction (i.e. cycle count will slightly lower than true one). This inaccuracy tiny compared total cycles consumed rest code over period time. ARMulator appear ignore changes armul.cnf configuration file Under certain conditions ARMulator read default armul.cnf configuration from "bin" directory installation. This occur finds armul.cnf file elsewhere program search path, Unix installations) your home directory. prevent this, ensure that armul.cnf file exists elsewhere your program search path Unix installations) your home directory. armul.cnf file exist elsewhere program search path previous version Software Development Toolkit been properly uninstalled. REMOTE_A connect JEENI Embedded baud rates 9600 debugger time out. will reliably baud rate 9600, should connected 19200 higher. 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. Release Notes Page Other recent searchesXC62KN - XC62KN XC62KN Datasheet VCO-305 - VCO-305 VCO-305 Datasheet PSA-30R - PSA-30R PSA-30R Datasheet NLU2G14 - NLU2G14 NLU2G14 Datasheet M39029 - M39029 M39029 Datasheet ITR20403 - ITR20403 ITR20403 Datasheet
Privacy Policy | Disclaimer |