Where is the "printf" output routed to?

This topic has 2 replies, 2 voices, and was last updated October 23, 2017 at 11:04 PM by marqs.

Viewing 3 posts - 1 through 3 (of 3 total)

Author

Posts
October 20, 2017 at 5:05 PM #16234
krivx
Participant
I’ve seen use of printf in the C sources to output debug info – where does this information go? Is there a serial port somewhere on the board that this can be monitored?
October 21, 2017 at 2:35 PM #16250
krivx
Participant
I haven’t put together a toolchain yet but this is what I am expecting: https://www.altera.com/support/support-resources/knowledge-base/solutions/rd09142004_1190.html
October 23, 2017 at 11:04 PM #16349
marqs
Participant
Yes, you’ll need to build application in debug mode (See last section of README) to get the output via JTAG UART.
Author

Posts

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.

Necessary

Always Enabled

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Cookie	Duration	Description
_gat	1 minute	This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.

Cookie	Duration	Description
__gads	1 year 24 days	The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites.
_ga	2 years	The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gid	1 day	Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.

Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.

Cookie	Duration	Description
IDE	1 year 24 days	Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie	15 minutes	The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.

Others

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

Cookie	Duration	Description
ct_checked_emails	session	No description
ct_has_scrolled	session	No description
ct_mouse_moved	session	No description
ct_screen_info	session	No description
wordpress_apbct_antibot	session	No description
wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5	2 days	No description