Sorry, you need to enable JavaScript to visit this website.

Zynq Concepts, Tools, and Techniques on ZedBoard - Issues

Unsolved
13 posts / 0 new
lavigne@unb.ca's picture
lavigne@unb.ca
Junior(0)
Zynq Concepts, Tools, and Techniques on ZedBoard - Issues

Hi all,

I'm new to the Zedboard, running through the 14.3 CTT tutorial, and I've encountered two problems:

1) Section 3.1.2 - The application code does not compile without error:

../src/helloworld.c:39:6: error: conflicting types for 'print'
../../Hello_world_bsp/ps7_cortexa9_0/include/xil_printf.h:39:6: note: previous declaration of 'print' was here
make: *** [src/helloworld.o] Error 1

To compile, the following line must be removed/commented:
void print(char *str);

2) The expanded Helloworld.c example contained in Appendix A crashes when run on hardware (within the SDK). After an open is selected (pressing '1' for example), a popup Terminal Error message appears :"IO Error! Bad file descriptor in nativeDrain"

##### Application Starts #####

SELECT the Operation from the Below Menu
###################### Menu Starts ########################
Press '1' to use NORMAL GPIO as an input (BTNU switch)
Press '2' to use EMIO as an input (BTNR switch)
Press any other key to Exit
##################### Menu Ends #########################
Selection : 1
Press Switch 'BTNU' push button on
Bad file descriptor in nativeDrain
board

I haven't found a resolution yet to the nativeDrain error. Has anyone encountered similar issues? I've tried this on two PC's (Win7), same result.

Same problem

I'm having the same problem. Any solutions? Thanks.

ikarus23's picture
ikarus23
Junior(0)
Bad file Descriptor

I had the same problem. I solved it by using Putty istead the SDK Terminal.

thiesbdd's picture
thiesbdd
Junior(0)
problem with input

I had the same problem, now with putty or tera term there is no response to any keyboard input.
Any suggestions? Thanks.

TroutChaser's picture
TroutChaser
Moderator(18)
USB Terminal Issues

It may be the Cypress UART-USB driver that is causing the problem. Originally the Cypress driver had a 'persistent mode' such that even though you powered down the ZedBoard it kept the connection to TerraTerm or Putty active and it would reconnect when you powered the board up again. This also helped for those applications that booted quickly and output to the terminal before you could set up TerraTerm or Putty. Then, at some point Cypress changed the driver to remove the persistent mode so that if you downloaded the driver later or if it was updated the persistent mode was lost.
 
We have worked with Cypress and they have posted a new version of the driver that includes persistent mode again. We will be updating the ZedBoard documentation but I will outline the steps to get the new driver here for now:
 
1. Connect the evaluation board’s Cypress UART-USB interface to the PC.
2. Browse to the website: https://secure.cypress.com/?mpn=CY7C64225-28PVXC
3. Scroll down to Technical Documents and download the "Microsoft Certified USB UART Driver" for your PC’s operating system. You should see a driver that was updated 25/11/2013.
4. Download the driver and unzip the file.
5. Unplug your USB UART device and then run "Setup.exe".
6. Once the installation is done connect the USB UART back.
To configure the persistent mode:
7. Open up Windows Device Manager and make sure the device manger view is in "Device by Type" (Device Manager: View > "Device by type:)
8. Locate the device type node called "Ports (COM & LPT)". Under this node locate "USB Serial Port (COM xx)". Double click on this device node. Under the "port settings" tab click the "Advanced" button.
9. In the new pop up window check the "Enable Port Persist" box. Click OK and close property windows.
10. Next serial port open operation should have the port persistence property enabled.
 
-Gary
 

thiesbdd's picture
thiesbdd
Junior(0)
Many thanks to TroutChaser :)

Many thanks to TroutChaser :)

GMA's picture
GMA
Junior(0)
hello,

hello,

i tried all your recommendation, but still the same error

jmassol's picture
jmassol
Junior(0)
Same problem

Hello everyone,

I did all the steps that you told us but there's nothing to do I always have this error in SDK terminal...

Could you help me ?

Thanks,
Jerome.

TroutChaser's picture
TroutChaser
Moderator(18)
Could you be specifc about your error

Could you be specific about the problem you are encountering? And please detail the tutorial and version you are using as well and the version of the Xilinx tools. Is this wth ZedBoard or a MicroZed board?
 
-Gary

KaiW's picture
KaiW
Junior(0)
Use Putty instead of SDK can

Use Putty instead of SDK can fix the issue

Arpit Sodani's picture
Arpit Sodani
Junior(0)
Terminal Issue- no response on pressing '1' or '2'

I have the same issue,
When running the program, the output from zedboard is displayed on putty terminal properly(i.e. all the print commands works fine) but on pressing '1' or '2' from keyboard I do not see any action on the terminal. To troubleshoot, I hard-coded the value '1' and the program worked fine then. Hence, there is some issue with the "inbyte()" command and program is stuck there. Can anybody please provide any help regarding that.
I am using vivado 2013.3 and following the 2013.4 version of the document bcs i could not find any for 2013.3
P.S. - already completed all the steps necessary related to cypress driver.

TroutChaser's picture
TroutChaser
Moderator(18)
Is the 'Putty' terminal

Is the 'Putty' terminal window selected when you are pressing the keys?
 
If so you might want to try the Out of the Box Linux provided with the ZedBoard to verify that you are able to input in the Putty terminal with a known good application.
 
-Gary

rohini's picture
rohini
Junior(0)
I/O bad file descriptor error

After following the above steps also i am getting the same error.any other solutions?