Aeneas

Members
  • Content Count

    10
  • Joined

  • Last visited

Everything posted by Aeneas

  1. Diligent should pay you those 2 cents -- that clarified their vague instructions in Getting Started. Pressing the buttons, not the aforementioned switches, does indeed generate the text messages through COM16 into TeraTerm. Onto another one of their introductory scenarios. Hopefully no more minefields.
  2. 1) I already stated that the LEDx toggles relative to the movement of switch SWx. 2) I connect to the terminal program TeraTerm after having sent the SDK program into the device with Run History/System Debugger on Local app.elf I see no LED activity on LD8 (RX) or LD9 (TX) on Program FPGA or on the System Debugger on Local . When Program FPGA completes LD10 (Done) is lit. After these programmings I open TeraTerm and pull down Setup/Serial Port... , and then select COM16 and change 9600 to 115200 and then OK. The title line changes to COM16 - Tera Term VT . I then toggle the SWx and the LDx lights go on/off. No text comes out of TeraTerm. So far I have not heard you state that you have done this yourself today and seen messages from TeraTerm, so I assume there are some Bugs in Vivado or in the Zybo.
  3. Yes I am seeing the LEDs light when turned on and off when the switch is turned off. In what window/tab (the exact window/tab name) are you seeing the messages displayed ? Do you have access to a Zybo and Vivado right now or are you responding based on memory or training materials ?
  4. I have established that of the 3 com ports on this laptop, com16 is the one which pops up in //Device Manager//Ports// when the Zybo is plugged in. From there, I have seen No messages while toggling the Zybo switches, either in the SDK Terminal window (or Console window) after receiving the "Connected COM16 at 115200" from SDK Terminal, or through TeraTerm after disconnecting SDK Terminal connection and connecting at 115200 8/1 through the Serial Port command.
  5. I tried all available 3 Com Ports but do not see the canned messages displayed in the SDK Terminal window when manipulating the switches. Which com port does xil_printf use ?
  6. The Getting Started demo is now working and LEDs are now lighting when switches are adjusted on/off. Where does the FTDI Serial Port data from the micro-USB appear within the SDK context ? Also, how does the writer on this forum avoid the double-space default in typing messages (IE11) ?
  7. I tried that configuration as one iteration but found that PGOOD would flash but would not be solid. The J10 standard USB connector also must be connected to the 2 Amp USB Hub for the PGOOD to be solid. -------------------------------------------------------- However, I just tried the micro-USB cable that comes from Digilent (which had to be bought separately and just arrived) and now the PGOOD Is now solid without the J10 USB connected. (I was using a cell phone micro-USB cable). I will try the SDK again.
  8. There are 2 USB cables connected from the laptop to the Zybo pcb, at J10 and J11. This is a vague sentence: " You should have a single USB cable connected to your computer and to the micro-USB connector on the ZYBO (J11)." -- do clarify. What should be the USB configuration, when Zybo JP7 is jumpered for USB power and JP5 is jumpered for JTAG ? All of what I am doing now is through the USB Hub, with the 5V/2.0A power supply plugged into the USB Hub.
  9. //Windows 7 64//i7-2620M//Vivado v2016.2 (64-bit)//SW Build 1577090--June 2//IP Build 1577682--June 3// In Device Manager the board appears as: USB Composite Device USB Serial Converter A USB Serial Converter B To which drivers do you refer ? Where is the installer ? I have configured with USBs directly connected to the laptop, and alternately with a USB Hub, with a 5V/2.0A power supply plugged into the USB Hub, the power supply being required to obtain the PGOOD light on.
  10. Followed the Zybo Getting Started scenario with Vivado and then SDK, Program FPGA results in "Done" light going on. However,the Run As→Launch on Hardware(GDB) results in error message " Unexpected error while launching program: Error while running ps7_init method. Cannot write to target Cannot access JTAG-DP: invalid ACK value (0x00, expected=0x02) Error Address = 0xf800074c " Jumpered for USB power, with both the USB and the micro-USB plugs connected to laptop, which together cause PGOOD to be lit on. JP5 jumpered for JTAG. What is causing this .elf "Cannot write" error, when the prior Program FPGA does result in Done success ? More experiences: ============================================================================= XSDB ----------------------------------------- Program FPGA (success, with Done light on) ----------------------------------------- 100% 1MB 1.9MB/s 00:01 ----------------------------------------- mrd 0xF800025C xsdb% Context does not support memory read. Unsupported command ----------------------------------------- System Debugger on Local app.elf ----------------------------------------- Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0xffffff28 (Suspended) Info: ARM Cortex-A9 MPCore #1 (target 3) Stopped at 0xffffff34 (Suspended) ----------------------------------------- Error while launching program: Invalid DAP ACK value: 0 ----------------------------------------- mrd 0xF800025C F800025C: 00000000 ----------------------------------------- ================================================================================ Is this normal for this PCB or do I have a bad board ?