I get the below error message when I start the ULINK debugger with my KEIL MCBSTM32 eval board:
Cannot access Memory *** error 57: illegal address (0x8000000)
I've searched KEIL's website for error 57, but couldn't find anything. I've searched uVsion help, but couldn't find anything. Can someone point me to where these types of errors are documented?
The debugger is actually stopped at address 0x80001A4, and these are the instructions before and at that line:
0x080001A0 F002BBF6 B.W 0x080002990 0x080001A4 4804 LDR r0,[PC,#32] ; @0x080001C8
and this is what's at 0x080001C8: 0x080001C8 00ED LSLS r5,r5,#3
and this is what's at 0x08002990: 0x08002990 4770 BX lr
Address 0x8000000 is the start of flash ROM for the uC on this eval board (an STM32F103RBT6). I'm using the default KEIL assembly startup code (STM32F103x.s) and the default project options for where ROM and RAM is (IROM1 at 0x8000000 with size = 0x20000, and IRAM1 at 0x20000000 with size = 0x5000).
If I start the debugger then stop it, I get this error message:
ULINK - Cortex-M Error Could not stop Cortex-M device! Please check the JTAG cable
I found some knowledgebase articles that suggested slowing down the JTAG clock, using internal or external 3.3V inside the ULINK, and/or making sure that a hardware reset was used with the ULINK; so I tried those suggestions. Unfortunately, they didn't change my symptoms.
I've been trying to find somwhere where I could insert a breakpoint to try to step through the startup code, but uVision won't let me put a breakpoint anywhere in the startup assembly code (and yes, I do have the "Debug Information" checkbox checked in the project options). I've unchecked the debugger "Reset and Run" and "Run to main()" options, but when I start the debugger and try to single step, I can only step a few times and then the code appears to start and never stop. If I hit the "halt" button, I get the same error message about not being able to stop the uC.
The debugger always starts at address 0x080001A4 with the error message about not being able to access memory.
Can anyone suggest something else to do that might fix these problems?
Thanks, Dave.
Well... I had tried a new way to organize source code for this project, and on a whim I decided to go back to my old way of organizing it (all source code for the project in one directory). That made the error 57 error go away. No idea why that is!
Also, now I get the assembly source code in the disassembly window (which I didn't get before), and I can see that the line of code where the debugger stops (0x080001A4) is where the assembly code is trying to jump to the library startup code (I think):
117: LDR R0, =__main 0x080001A4 LDR r0,[PC#32] ; @0x080001C8
If I "step into" at that point, the debugger stops at:
__main: 0x080000EC BL.W __scatterload_rt2_thumb_only (0x080000F4)
I started single-stepping through this code, and it seems to run okay (the debugger doesn't crash); but if I try to run to [my] main, the debugger never makes it there. If I then try to halt the debugger, I get that same error message about not being able to stop the debugger.
Should I expect the KEIL IDE to work right with projects where the source code is not in a single directory?
Also, other than including the cortexm3_macros.s and cortexm3.h files in my project, do I need to do anything else in order to be able to use the macros in these files?
Does anyone know if there's a problem with the default startup code for the STM32F10x parts?
Well... reorganizing the project code helped (when I first did it), but error 57 comes back somewhat randomly whenever I build new code.
I'm stumped... sometimes I can use the hardware debugger, but usually I can't (because of error 57, which won't let me set breakpoints when it's active).
Anyone have any suggestions...?
Sigh... Dave.
Hi,
can you try Blinky example provided with MDK for that board and then build on it?
btw...
did you try a new project using cmsis? There are less files included/used than in the ST Lib projects - perhaps easier.
Just a startup (s) and a init (c), a SystemInit() in main() does the nessessary work.
BR, /th.
Not sure if it's the problem with your project, but I did face this message in a near past. Here's what I did:
Under Options for Target->Debug->Ulink Cortex Debugger->Settings->Debug you may try disabling Download to Flash under Download Options ( far right end ).
You may download to flash manually before entering debugging. (if firmware has changed).
BR,
Thanks for all the suggestions.
I did try the Blinky project, and it worked.
I un-checked "Download to Flash", downloaded the code manually, and now the debugger seems to be working again. I'll keep my fingers crossed and hope that the debugger keeps working if I do things this way.
It still bothers me though that I can't find a list on KEIL's website that describes this error (or any others).
I so miss the old hard copy manuals you used to get with the tools. I hate these online ones where if you don't know the right keyword, it can be virtually impossible to find what you're looking for! Surely a search term like "error list" (or at least one of several variations of that) should produce a link to a list of errors (including error 57).
I don't miss hardcopy - but I do miss the PDFs.
"I hate these online ones where if you don't know the right keyword, it can be virtually impossible to find what you're looking for!"
Absolutely
See: http://www.keil.com/forum/docs/thread15201.asp
And: http://www.keil.com/forum/docs/thread15011.asp
BTW the *** error 57: is probably a Debugger error - not a compiler error...
Since my project compiles and links with zero errors or warnings, I wouldn't think that the error I've been talking about would be a compiler error.
I've looked in the ULINK, uVision, and the RealView utilities online manuals, and can't find error 57 in any of them. I haven't been able to find a manual for the debugger.
Can you tell me where I can find the list of errors that includes this error 57?
The debugger is an integral part of uVision - so it'd be in the uVision manual if it's anywhere.
But, AFAIR, there has never been such a thing.
:-(
Thanks Andy.
Since my support agreement ended some time ago, I guess I have no valid/official method to complain, or to request support about this.
My guess is that errors like these are documented somewhere in the public domain. I sure wish I knew where!
:-<
ARM: MEMORY MISMATCH ERRORS DURING LOAD
http://www.keil.com/support/docs/2925.htm
ANSWER
This can be caused by the microcontroller hardware not being reset properly. Check the Use Reset at Startup check box in the ARM Target Driver Setup Dialog (Options for Target -> Debug -> Settings). Checking this tells the debugger to send a hardware reset over the JTAG link before loading.
Thanks John.
Unfortunately, I've tried this several different ways (I think every possible via the different dialog boxes), but it hasn't solved the problem.
In case you haven't seen the earlier threads, I'm having this problem on both a KEIL MCBSTM32 eval board and an ST STM3210E eval board. I'm assuming that both of these eval board vendors know how to design reset circuits for them that are compatible with the KEIL debugger.
Hi David,
You are right. I thought that I had read this thread before, so I didn't scroll up, and then lost a lot of information in the earlier posts.
I have a question, who creates/builds the problematic project? Is that some example you downloaded from Internet?
If it is a project not created/built by yourself, then I will suggest that: 1.Extract all the source code out. 2.Create a totally new project, include all the source code in. 3.Configure the new project as your need.