We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
All:
I've been playing around with some of the RTL (RL-ARM) code examples and running in the simulator. All works well with most examples (generic or based on ARM7 stuff). But, when I try to use the Simulator to run STR9 (ARM9) code, I get a flurry of error messages that all seem to point back to a missing DLL called DARMST9.dll. Apparently it has to do with dialog boxes required for simulation.
Anyway, I've searched the \Keil\Bin directory (and every other directory on my machine) and there is definitely not a DARMST9.dll anywhere to be found.
Interestingly enough, if I use Help|About uVision,then I get the following information:
IDE-Version: µVision3 V3.33 Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2006
License Information: Richard McCoy Oceaneering International LIC=BUUSP-M1ED3-3EQH9-MYL30-WVZY4-PV1SI
Tool Version Numbers: Toolchain Path: BIN30\ C Compiler: ARM/Thumb C/C++ Compiler, RVCT3.0 [Build 942] for uVision [Full] Assembler: ARM/Thumb Macro Assembler, RVCT3.0 [Build 942] for uVision [Full] Linker/Locator: ARM Linker, RVCT3.0 [Build 942] for uVision [Full] Librarian: ARM Archiver, RVCT3.0 [Build 942] for uVision Hex Converter: ARM FromELF, RVCT3.0 [Build 942] for uVision [Full] CPU DLL: SARM.DLL V3.02a Dialog DLL: DARMST9.DLL Target DLL: BIN\UL2ARM.DLL V1.20a Dialog DLL: TARMST9.DLL V1.00
So my Help file seems to think there is a DARMST9.dll but I'll be darned if I (or my simulator!) can find it.
Does anyone know where I can get this file?
Thanks In Advance,
-=Rich=-
error 65: access violation at 0x54000004: 'no write permission' Any ideas on what this message refers to and how to get debugging working with STR9 simulation?
Read the manual on debugger init files, and on the 'map' command that informs the simulator where you have what kind of memory.
The device simulation for the STR9 parts is still not fully complete. We work on it and expected is Nov. 2006 as release date.
The reason why we included this DLL in this release already was that it supports already a good portion of the peripherals (but not yet all of them).