• Content Count

  • Joined

  • Last visited

About dand400

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Switched from Pmod JE to Pmod JB for the TX & RX of UartLite and everything worked. Does UartLite not work on JE (Std) on Zybo?
  2. To further explain: When I enable PS UART1 and add fabric IP UartLite but do not physically connect anything to the PMOD pins (JE-9 and JE-10) where the UartLIte is routed, the stdin/stdout (UART1) functions correctly. But when I physically connect the Digilent "Pmod RS232: Serial Converter and Interface Standard" to Pmod JE, the stdin/stdout stops working to the point that some combination of power cycle to the Zybo and restarting the serial communication application must be done to restore stdin/stdout functionality. Dan
  3. Jon, I might have narrowed the problem down (or maybe muddled it up). It now appears that one or more of the MIO/PS pushbuttons, LEDs, and/or UART1 (stdin/stdout) stop working when a second serial port is attached via the Zybo PMOD connectors. At first I had attempted to use MIO/PS UART0 routed via some PMOD pins. Next I have attempted to use the fabric IP UartLite routed via PMOD pins. I have tried two different logic to RS232 converters and both cause the same problem. Currently neither serial port works when the second serial port, UartLite, is physically connected to the logic to RS23
  4. Jon, I always launch SDK from Vivado (to ensure proper files are loaded). Thanks, Dan
  5. jpeyron, Problem is not with SDK code, but in export of hardware to SDK from Vivado (see above post) and/or possible attempt to use UART0 on JF9 and JF10 (MIO14 and MIO15). Also, cannot get files from system where performing this work, quite impossible. Thanks, dand400
  6. Renamed the .sdk folder, regenerated the bitstream, exported hardware to SDK, launched SDK, created new SDK project, imported previous SDK source files into new SDK project, and everything worked! Evidently when changing the PS configuration in Vivado (then creating HDL wrapper, generating bitstream, and exporting hardware to SDK) something is not making it to the hardware or BSP in SDK and then things no longer work corretly. Is there a step I am omitting (when making changes to PS and/or fabric in Vivado) that corrupts or prohibits all changes being exported to SDK correctly? Than
  7. I spoke too soon, and made a mistake above (swapped names). Above should have said "... variables as XGpio instead of XGpioPs". But after doing new fabric/bitsream project and new SDK project (but with same code from the examples) with the PS MIO for the two pushbuttons (BTN4 and BTN5, MIO50 and MIO51) and the LED (LD4 MIO7), the LED works but the two pushbuttons always return 1. The pushbuttons and LED are enabled in the PS in the block design in Vivado. Any thoughts on why the two pushbuttons always return 1 (buttons pressed)? PS: I cannot attach anything from the de
  8. Problem solved (coding error)! Had erroneously declared the gpio variables as XGpioPs instead of XGpio.
  9. Using a Zybo board, PB200-279 Rev. B, with Vivado and Xilinx SDK 2015.2 (64-bit). When running the PS software in SDK and a call is made to access the PS MIO LED or pushbuttons via the XGpioPS_... (CfgInitialize, SetDirection, ReadPin, WritePin, etc.) functions, the software hangs at that call and never returns. Has anyone seen this problem or know what the cause of the problem is and what the solution would be? Thanks!
  10. In the first ("Linux on Zybo") tutorial, in Step 9: Obtaining the Linaro file system, the link to the Linaro file system page is no longer valid! How do you currently obtain the Linaro file system? Thanks, DanD
  11. Hello sbobrowicz, Question: The github link for petalinux you gave above, does that require Linux host to be any particular platform/vendor/release? Thanks! DanD