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?

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

Parents
  • 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

Reply
  • 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

Children
No data