LJMP "label" in 24 bit contiguous mode (80c400) appears to always compile neumonics for a LJMP 000000. What gives? LJMP immediate works fine. Anybody else run into this? 200012 02000000 F 282 LJMP LONG1 Also what does the F mean in the list? Thanks
The F means the target address is Fixed-Up by the linker. Jon
Right you are. I was reading the .lst file the hex is correct. Now is there a way to get a "complete" listing with forward/final values in the list?
OK, if you put in a LJMP Immediate in 24 bit contiguous mode, it still puts an F in the list. You would not think it needs help fixing this up.
There are several fancy linker directives that let you move things around in memory. So, even if you use immediate values for JMPs, the linker can still move them around if it knows about them. That's why this is a fixup. Jon
View all questions in Keil forum