This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Why can't I debug SR3 v1.1 in MDK-ARM ?

Hi, I am porting my code from SR3 v1.0 to SR3 v1.1 now. I have a problem in debugging SR3 v1.1.

In SR3 v1.0, it's fine in MDK-ARM debug session. I can set break point or trace code's execution. But in SR3 v1.1, I can't set break point or single step trace the source code. The source code window and disassembly code window are irrelevant.

I've try the original SR3 v1.1 without my code. It's the same. I also ask someone else to debug SR3v1.1 with his MDK-ARM and it works. It seems that it's caused by something with environment setting!?

I just noted a error message when I try to enter debug session that I missed before. "error 59: invalid absolute module"

Anyone has idea about this?

Related