• Content Count

  • Joined

  • Last visited

About GogMagog

  • Rank

Recent Profile Visitors

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

  1. I'm "resolving" this since it all works now. I noticed while running the project from Jon that the log files contained paths to other projects. I did have 6 other projects attempted. I took a guess at purging. Today I "rm -rf'd" all projects but two, and started anew. Now it works. Clearly the error was my own and unknown. Thanks again for your help. Just for fun I've added the "hello.c" program I modified. I needed to make sure I could make simple changes and that it truly was my code running: helloworld.c
  2. I said "Altera" and pushed a button and it worked. No seriously, I got it working and I will put here what I did at the end in case it helps others. The problem is that I tried to follow a procedure to manually install Digilent Programming Cable drivers and the Digilent Adept run-time SW, this one: https://www.xilinx.com/support/answers/54382.html but the procedure is not correct for my system (Vivado 2016.4 on a 64-bit Ubuntu 16.04), so I had to abandon it. Nonetheless, that seems to have made the difference. 1) I downloaded the tarball digilent.adept.runtime_2.16.6-x86_64.tar.gz and for lack of direction I dropped it in my home dir. Unzip and untar. 2) Create a /tmp/digilent_install directory. 664 mkdir /tmp/digilent/SDK 665 mkdir /tmp/digilent/Vivado 3) Copy the /<Xilinx install>/bin/lin(64)/digilent directory to the newly created /tmp/digilent_install. Nope. No such directory. I took this guess: 667 cp -rf /opt/Xilinx/SDK/2016.4/data/xicom/cable_data/digilent /tmp/digilent/SDK/ 669 cp -rf /opt/Xilinx/Vivado/2016.4/data/xicom/cable_data/digilent /tmp/digilent/Vivado/ 4) cd digilent.adept.runtime_2.16.6-x86_64 ./install.sh silent=1 cd .. cd ftdi.drivers_1.0.4-x86_64 ./install.sh silent=1 cd .. - cd libCseDigilent* - ./install.sh silent=1 OK no. There is no libCseDiglient. Not even here: find / -name \*libCseDiglient\*. There is a digilent.adept.runtime_2.16.6-x86_64/lib64. But, I did not continue with the process. Again, that's half of an install procedure that seems to have made a difference. You tell me. GogMagog
  3. I started this post and got a good response. I was able to use jpeyron's project (Hi Jon) to get the Zybo Getting Started to turn on LEDs with the switches. However, I still cannot get any output on any console. I am sticking with his project until I get this console business sorted out. Here's what I have: Vivado 2016.4 on a 64-bit Ubuntu 16.04. I'm trying this: https://reference.digilentinc.com/learn/programmable-logic/tutorials/zybo-getting-started-with-zynq/start and I do indeed have the correct board activity (LEDs and switches). On power on, I see this: [email protected]:~$ lr /dev/ttyU* ls: cannot access '/dev/ttyU*': No such file or directory turn on the Zybo and: [email protected]:~$ lr /dev/ttyU* crw-rw---- 1 root dialout 188, 1 Sep 14 18:08 /dev/ttyUSB1 So it looks like it's ttyUSB1. I am in the dialout group. I have tried, minicom, screen, putty, and cutecom, all with /dev/ttyUSB1, 115200, 8, none, 1, and I've played around with the flow control. If I type anything in the console I see the Zybo board's TX led flash. So it's the right port and I can program the board, and the SW is running on the Zynq. But I never get anything out on the console. The "getting started" is meant to tell me via the console which button I pushed (and that's something I so want to know). I have read and tried about 20 different "solutions". Any help appreciated as I have had zero success. Specific question: For anyone else with Vivado 2016.4 on a 64-bit Ubuntu 16.04, have you had to install the Digilent Adept SW to get this working? Any help appreciated as I have had zero success and for the first time in my many years I'm thinking about Altera. GogMagog
  4. Hi Jon, I used your project and the LEDs respond to the switches. There is clearly something I'm not doing according to the Getting Started, or something you just know to add. I'll be doing a side-by-side compare to see what I've left out. I didn't even export hardware. Just loaded it, programmed the device, started SDK, run->launch on hardware. The serial port still does not work, but that's a different issue now (different because before, without the LEDs changing, I shouldn't be expecting the program to be running). Thank you for your help on this. I'll post a solution when I uncover my error. GogMagog
  5. Too many diffs. I'll be trying your project soon. Thanks again.
  6. Hi Jon, I'm not sure what you mean by "Are you changing anything in the Zynq processor?" I really tried to follow to the letter the tutorial. If that means changing anything in the Zynq, then I am. I don't know what you mean by "using the board files" since in order to create the HW wrapper and export HW to SDK, then that's required, yes? On this: > Have you tried using my project that I posted above? not yet .... I'm running an intelligent recursive diff of it first. Here's the block design:
  7. Thanks. I should have mentioned that I did all that. I can program the PL with my own Verilog code and that works. It's the PS that doesn't work. Independent of the console, if that demo is meant to change the LEDs, it's not doing it for me. Here are some screenshots. I'm in the dialout group. It shows the selected board. I start with the vcse_server, then I launch Vivado. There is a screenshot of the only thing I can get minicom to do ... respond to Ctrl-A Z. Not sure what to try next.
  8. I am fighting to get any one of 5 different simple ZYBO demos to work. At all. I can download bitfiles with my own Verilog code and blink, or scan, or pulsate the LEDs, and get behaviour changes based on buttons and switches ... so I know the board works, but nothing I do with the with the processor core (PS block) works. I am here looking for information on how to get some kind of information out of the board so I can figure out what's going on. The demo I am working on now is this one: https://reference.digilentinc.com/learn/programmable-logic/tutorials/zybo-getting-started-with-zynq/start It does not ask for a Debug Configuration, or a Run Configuration, ... just the Run as -> Launch on hardware. There is a terminal setup at the end of that tutorial. Frankly I don't know why a separate console is needed since SDK has a "Console" and an "SDK Terminal". Nonetheless, I tried 'screen' and putty as others recommended, then minicom as well ... all I ever see is a blank screen. I don't know what I should expect to see really. I followed the tutorial to the letter. The only indication I get that things are connected at all is that with screen and putty, when I hit any key, I see ZYBO's TX LED flash once. I am running Ubuntu 16.04 and Vivado 2016.4. I have lots of Xilinx experience, but all command line and not with SDK (so telling me "It's just like ISE but ..." will make me cry. I just want something out of the console. Smoke would be nice. If it helps, I do see this in XSCT Console: Downloading Program -- /-----/projects/zybo/ZYBO_getting_started/ZYBO_getting_started.sdk/getting_started_with_ZYBO2/Debug/getting_started_with_ZYBO2.elf section, .text: 0x00100000 - 0x00102467 section, .init: 0x00102468 - 0x0010247f section, .fini: 0x00102480 - 0x00102497 section, .rodata: 0x00102498 - 0x0010263b section, .data: 0x00102640 - 0x00102adb section, .eh_frame: 0x00102adc - 0x00102adf section, .mmu_tbl: 0x00104000 - 0x00107fff section, .init_array: 0x00108000 - 0x00108003 section, .fini_array: 0x00108004 - 0x00108007 section, .bss: 0x00108008 - 0x00108037 section, .heap: 0x00108038 - 0x0010a03f section, .stack: 0x0010a040 - 0x0010d83f 100% 0MB 0.5MB/s 00:00 Setting PC to Program Start Address 0x00100000 Successfully downloaded /-----/projects/zybo/ZYBO_getting_started/ZYBO_getting_started.sdk/getting_started_with_ZYBO2/Debug/getting_started_with_ZYBO2.elf Info: ARM Cortex-A9 MPCore #0 (target 2) Running So it's "running", there is no debug config, and the Hello World demo says I should see: > The demo will be running on the ZYBO. Try playing around with the 4 switches (labeled SW0-SW3). Doing so should light its respective LED. Also over the serial port, pressing each button (labeled BTN0-BTN3) will produce the message “button x pressed”. Any suggestions appreciated. What do I do? Create a debug config for this and try again? GogMagog