Was doing well in evaluating the IDE/HAL until now. Hit a brick wall going 100mph. I need some pointers on how to read characters from the UART. I tried the example in the Processor Ref handbook, but it won&#39;t link. Cant find fopen, fclose, fgetc even though stdio.h is included. Also tried the altera_alt_avalon_uart_read function, but don&#39;t understand how to init the alt_fd pointer. I am not a UNIX programmer and this layer of abstraction is confusing to me. Couldn&#39;t find any examples. Any help would be great! Rick

Hi, I have used this functions with the uart already and it works fine so far. I have included some more header files and I am not shure, but I thing the "stdlib.h" could be the right one. There are also some properties in the sytem library you can adjust (do not use reduced driver). Take a look in the HAL-driver for the uart, there is a description for a compiler switch you have to use if the uart should work with interrupt. The other way is to use the headerfiles from the sdk section with the register and bit definitions, switch the std-in/out/error device in the system library to "none" and use the IORD/IOWR functions with the base address of the "system.h" to read and write to the uart directly (w/wo an interrupt handler you supplied). This will also work fine and this is my prefered way but it is not the "new way" from altera. Best regards Siegmar

RPolicy I agree about the whole confusing part. Sigiz brought up the stuff about std-in/out/error but did you remember to turn those on? And if that still doesn&#39;t work and you just need printfs to see what&#39;s going on, try the jtag uart (it was very simple to use, just include stdio, and use printf(....) just like you would in any other C program) G-luck!

I&#39;ve submitted a documentation enhancement request for this to be explained better. Thanks for bringing it to our attention. If you are still having problems after all the suggestions, please reply to this post.

Still have not been able to get the UART input to work. Printfs work fine. Fopen, fclose, getc cannot be linked. I have enabled all drivers and have set the stdio/err to UART1. Still nothing. Would use the alt_avalon_uart_read if I understood how to init the alt_fd pointer. With the printf so simple, why is the input such a pain? Couldn&#39;t we just use scanf? Sounds like a simple answer to me.... Rick

An educated guess. If this fails at link time do you have the small C library box ticked, if so untick it. As you will see in table 4.5 of the Nios II Sofwtare Developer&#39;s Handbook some functionality is removed in order to reduce the size of the library, fopen, fclose and getc are amongst these functions. Hope that helps

UART Help | Altera Community

15 Replies

Altera_Forum
Honored Contributor
21 years ago
Including stdio, and something else (I forget) should be all that's needed.

But if printf was working then you probably have what you need. Was the link error anything useful or the normal nonsence that I usually get from visual studio? http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/smile.gif
Altera_Forum
Honored Contributor
21 years ago
I also thought that the scanf would work because the printf did. The error was the standard unresolved external type of error. In another words, it couldn't find code for the scanf. It was the same error generated when I tried the fopen/fclose/getc.

Rick
Altera_Forum
Honored Contributor
21 years ago
Sorry, I'm out of ideas

Are you trying to use scanf for debug or will there be input in the final design? Also what core and debug module (if any) has been added to the system? (drawing at straws, just like you are probably).

Good-luck and hopefully someone else can be of more help.
Altera_Forum
Honored Contributor
21 years ago
Can you post the linker error you get please.
Altera_Forum
Honored Contributor
21 years ago
In fact can you post the linker error you get with the small C Library selected, and then the error when you don't have the small library selected.

Forum Discussion

UART Help

15 Replies

Recent Discussions

NiosV µC/OS-II

Recommended Quartus Prime Standard Edition for Nios V Development on MAX 10 FPGA (10M25DAF4817G)

AshlingRISCFree IDE Build system: 'source directory does not appear to contain CMakeLists.txt"

Nios-V on Cyclone IV

Debug Know-How: Ashling* RiscFree* NIOS® V debug using Command Line