LPCXpresso IDE中的主题 Re: Fast Console Print Library

Fast Console Print Library

lpcware — Wed, 15 Jun 2016 21:51:43 GMT

Content originally posted in LPCWare by larryvc on Fri Apr 22 11:02:40 MST 2011
This is an example I put together using a library of consoleprint and cr_fast_printf combined. It might not be elegant but it works. Details of creating libraries are on the CodeRed Wiki.

Remember to have CMSISv1p30_LPC17xx in your workspace.

If anyone has any ideas on how to improve upon this please let me know. Specifically on how to add the library to my project without having the separate library project as extra baggage. Would doing this be a bad idea?

Re: Fast Console Print Library

lpcware — Wed, 15 Jun 2016 21:51:44 GMT

Content originally posted in LPCWare by larryvc on Fri Apr 22 12:52:13 MST 2011
0 views of the attachment, what's up guys?:eek::)

Re: Fast Console Print Library

lpcware — Wed, 15 Jun 2016 21:51:45 GMT

Content originally posted in LPCWare by whitecoe on Fri Apr 22 15:01:58 MST 2011
You may not have spotted that "Redlib_v2" in LPCXpresso for Linux (and hence assumedly the forthcoming LPCXpresso4) already effectively does this....

http://support.code-red-tech.com/CodeRedWiki/redlib_v2_notes

Quote:
[SIZE=2][B]printf variants[/B][/SIZE]
The printf() and puts() functions have been modified in Redlib_v2 in order to improve the speed with which strings are written to the debug console. This speed improvement is provided due to a single semihosted operation being carried out per string displayed (in a similar manner to the "consoleprint" example provided for some MCUs with earlier versions of the tools), rather than one semihosted operation per character.

Thus probably not worth putting to much development effort in here :)

Re: Fast Console Print Library

lpcware — Wed, 15 Jun 2016 21:51:46 GMT

Content originally posted in LPCWare by larryvc on Fri Apr 22 15:16:47 MST 2011

Quote: whitecoe

Thus probably not worth putting to much development effort in here :)

You're right, and I did know that.;) Thanks.

I posted this, as a separate thread, as an interim fix for another thread.

http://knowledgebase.nxp.com/showpost.php?p=7717&postcount=20

Thought it might be useful in the short term.

But my question above is still unanswered, it applies to any library we create. I know the linker just grabs the <filename>_Lib.a file for inclusion in the build. How do we just include the <filename>_Lib.a file without having to have the library project in the workspace?

Re: Fast Console Print Library

lpcware — Wed, 15 Jun 2016 21:51:46 GMT

Content originally posted in LPCWare by larryvc on Sat Apr 23 15:00:29 MST 2011
Bump. Maybe CodeRedSupport or someone else has an idea on this one?

See last paragraph in last post.

Thank You,
Larry

Re: Fast Console Print Library

lpcware — Wed, 15 Jun 2016 21:51:47 GMT

Content originally posted in LPCWare by martinho on Sat Apr 23 23:03:56 MST 2011
As I understand You have to add the library (your *.a file) like this:

http://wiki.eclipse.org/CDT/User/FAQ#Adding_C.2FC.2B.2B_External_Libraries

Martin

Re: Fast Console Print Library

lpcware — Wed, 15 Jun 2016 21:51:47 GMT

Content originally posted in LPCWare by CodeRedSupport on Sun Apr 24 01:59:04 MST 2011
In the Linker, to specify a library to be linked against, use the -lMY_LIBRARY option. The linker will look for a library called libMY_LIBRARY.a.

The linker will search in a set of default (system) directories for libMY_LIBRARY.a. To add an another to the list of directories searched, use -Lpath/to/my/directory. It can be a relative, or an absolute path.

In LPCXpresso IDE, these options are on the MCU Linker/Libraries settings in the project properties. On the Library Paths, option, buttons are provided so you can browse the file system or the workspace for the directory.

Hope that is clear.

Re: Fast Console Print Library

lpcware — Wed, 15 Jun 2016 21:51:48 GMT

Content originally posted in LPCWare by larryvc on Sun Apr 24 10:50:06 MST 2011

Quote: CodeRedSupport
...Hope that is clear.

Very. Thank you.