• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 21 subscribers
  • Views 2272 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

generate full listing file?

Paul Fox

i can't seem to figure out how to generate a full (not per-module) listing file, showing me fully relocated assembly for the entire absolute binary. either something generated by the linker (BL51, in my case), or as a disassembly step. i can use the free "d52" program to disassemble, but i'm going to have to do a _lot_ of work to generate its control file from the keil .m51 and individual .lst files.

any tips welcomed...

paul

  • 0

    Any particular reason why you want to do this?

  • 0 in reply to Andy Neil

    habit, i guess. i find debugging easier when i have a full symbolic listing available.

  • 0 in reply to Paul Fox

    Did you figure out how to do this? I am getting a 'Error L125: Interrupt number not found' in my code and the Keil website asks me to generate the listing file to check.

  • 0 in reply to AJ Boston

    i suspect they're pointing you at the .LST file, no?

    (but to answer your question, no, i didn't figure out how to get a full symbolic listing. i did create some scripts to create the .ctl file that makes d52 useful -- it wasn't as hard as i thought it would be.)

  • 0 in reply to Paul Fox

    Does the listing options under the LISTING tab not create the list files and map files that you need?
    Bradford

  • 0 in reply to doubt that my ISP Al Bradford

    no, those options aren't really what i want. i want a full-length disassembly of the entire program space (let's face it -- it's an 8051, how big can it be?) with full absolute symbolic dereferencing.

    i find that kind of listing invaluable for making sure memory is laid out the way i think it should be, that the vector table contains what i think it should, etc. you learn things about your code that you wouldn't know otherwise. ("My, those floating point libraries are big!", or, "Whoa, look what that case statement turned into!" :-)

    i know all that information is available in piece parts in the .m51 file, plus the .lst files, but it's not all in one place, and the .lst files don't have final addressing.

    it's just a personal preference -- i'm just surprised the tool suite doesn't offer it. (i should add i'm not using the "professional" (i.e., 'x') version of the tools -- perhaps there are more options in that package.)

    in any case, i think i have most of what i need, based on some home-brew scripts that rummage through the .m51 and .lst files and feed that information to d52's control file.

    many thanks,
    paul