• State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 21 subscribers
  • Views 3374 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

Printf() size, questions?

Ted Dubroff

How many bytes will printf() take up in a non debug-monitor
environment?

Also, is it easy to set up printf() to map to a second UART?
I will need control of the UART ISR so that I can handle receives
appropriately. How will this confict with printf()?

Parents
  • 0 in reply to Ted Dubroff

    Again, I'm using the uVision2 eval simulator. When I try to see code size
    it doesn't appear to include the size of printf(). In fact it just tells
    me the starting location of my functions but not the sizes. Is there
    a way to list the code and data sizes of objects? Also, even at the
    end of the .m51 file, the total code size does not seem to include the
    size of the printf() function. Is this because of the simulator?

    Just look in the .m51 file for a simple foo.c file compiled and linked, don't use your big project for this. Build the file without using printf, check the total size. Then add one call to printf, check the size again. The simulator has nothing to do with the linker output file (.m51).

    - Mark

Reply
  • 0 in reply to Ted Dubroff

    Again, I'm using the uVision2 eval simulator. When I try to see code size
    it doesn't appear to include the size of printf(). In fact it just tells
    me the starting location of my functions but not the sizes. Is there
    a way to list the code and data sizes of objects? Also, even at the
    end of the .m51 file, the total code size does not seem to include the
    size of the printf() function. Is this because of the simulator?

    Just look in the .m51 file for a simple foo.c file compiled and linked, don't use your big project for this. Build the file without using printf, check the total size. Then add one call to printf, check the size again. The simulator has nothing to do with the linker output file (.m51).

    - Mark

Children
No data