Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

Printf() size in a non debug-monitor environment

Status
Not open for further replies.
J

john2020

Full Member level 5
Joined
Nov 13, 2005
Messages
292
Helped
12
Reputation
24
Reaction score
8
Trophy points
1,298
Activity points
4,911
hi all,

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()? how much space will the function take? I've heard people say that printf() may take up to 2K of code space. Meaning
that if printf() is used in the embedded application, then 2K of code
space will be eaten up. If thats the case then I'll have to come up
with my own transmission mechanism. any suggestions?
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top