• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 22 subscribers
  • Views 1349 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

C_START Problem

Filgis Simon

Hello,

please have a look:

http://www.keil.com/forum/18146/

I have sometimes the same problem.

C:0x0B57 020B96 LJMP 0x0B96

But at 0x0B96 disassembly shows no valid opcode:

C:0x0B94 8090 SJUMP C:0B26
C:0x0B96 10BEE4 JBC 0xB8.6,C:0B7D

Jumping to 0x0B96 leads to crashes.

What can I do to get rid of this permanently?

Best regards,

Simon

Parents
  • 0 in reply to Filgis Simon

    jump to 0x0B95 is not jumping to a valid opcode...

    The snippet you show does not allow that conclusion. The fact that a disassembly begun for whatever reason at C:0x0B94 shows a somewhat strange result tells you nothing about what the CPU (and the disassembler) would see if you pointed it at the correct point that really is being jumped to: C:0x0B95 What you're actually looking at is

    C:0x0B95 9010BE   MOV DPTR #0x10BE

    There's absolutely nothing wrong with that line. You're looking at the wrong part of your source code, in the wrong way.

Reply
  • 0 in reply to Filgis Simon

    jump to 0x0B95 is not jumping to a valid opcode...

    The snippet you show does not allow that conclusion. The fact that a disassembly begun for whatever reason at C:0x0B94 shows a somewhat strange result tells you nothing about what the CPU (and the disassembler) would see if you pointed it at the correct point that really is being jumped to: C:0x0B95 What you're actually looking at is

    C:0x0B95 9010BE   MOV DPTR #0x10BE

    There's absolutely nothing wrong with that line. You're looking at the wrong part of your source code, in the wrong way.

Children
No data