Dear All, I have a problem where in my firmware is working in
debug mode but it does not work in release mode. I am using LM3S3748
microcontroller target motherboard with Wavecomm GSM modem interfaced
to it. The application is to receive SMS from the server and display
it on LED Matrix board. I have used KEIL Compiler to develop the
firmware. The program runs fine when it is running in debug mode of
ULINK debugger i.e the GSM modem receive the SMS from the server and
can be displayed on the LED board . But when I run target board is in
release mode the GSM modem receives the SMS from the server but the
microcontroller cannot receive the display data from the GSM modem.
Raghu Nandan Ravi
Rather than simply re-post exactly the same text verbatim,
you could at least have included the clarifications already added in
your original post on the TI forum:
Have you done any further investigations since then?
Have they yielded any information that might be helpful?
Strange. You did get a lot of help on the other forum. So why do
you waste peoples time by starting a new thread on this forum? And
how many other forums have you posted to?
As Andy notes, you really are using strange terminology when
writing ""when the system is out of debug mode " means when the
target micro controller is out of debug mode i.e. target micro
controller board is in release mode"
Hardware is very seldom designed to have one debug mode and one
release mode. What would it imply? Running at different clock speeds?
Different supply voltages?
So, the first question for you to ask is what is different in a
system in "debug mode" and in a system in "release mode"?
A common change is in compiler optimizations. Bad code does not
survive optimization well because of aliasing and other problems.
What steps have you taken to subdivide your problem and find out
exactly what module/action that fails? We can't do that for you,
since we have neither the hardware nor the software - and maybe not
the build tools either.
And the whole point of having on-chip debug (as accessed by the
uLink) is to ensure that you don't need a different hardware
configuration for debugging - other than attaching the debug "probe"
(uLink, in this case).
I faced a similar issue today.
I just wanted to share this here :
If we want Debug information, keep this box ticked else untick it and then create an Executable.
I hope this helps.
PS: I use Keil.
The presence or absence of Debug Information would not make any difference to whether the code runs or not - because the debug information is not loaded into the chip.
So I don't see how this related to the original, 9-year-old issue?
View all questions in Keil forum