• Content Count

  • Joined

  • Last visited

  1. Thanks for the information Dan. I will look into that. I am trying to figure out how to make a system that can be programmed in C using the SDK so I can do the hardware design and let someone else program the microblaze based on existing RTOS code. I will look at OpenArty and see how it looks.
  2. Hi, Is there any example code anywhere of how to initialize and use additional pins on the arty board for things like Uarts or I2C? Obviously some of this stuff would need to be supported to use the arduino headers but I can't figure out how to do it in the SDK. Any help is appreciated. Scott
  3. Looks like that did it, Thanks Jon!
  4. The block design screenshot is attached
  5. Hi Jon, That is the tutorial and board I am using. I have tried stopping the sdk and relaunching. I have also regenerated the bitstream and rexported it. No luck. After I run as: hardware as shown in the tutorial I get an error that says: Error while launching program: Cannot stop MicroBlaze. Stalled on instruction fetch. The xilinx site says the MMI flow is recommended but I am new to this so I have not spent the time to figure out what that means.
  6. Unfortunately, I don't "quite" have it going yet. I am using 2015.4 as mentioned but when I try to run the hello world project I get an error that says it can't halt the microblaze which I guess is a known issue with 2015.4. As a result, this program fails to load into the microblaze. Is this solved by the git repo by chance?
  7. I solved this by downloading separate VCP drivers from the FTDI site.
  8. Hi, I am using vivado 2015.4 v2 and I can't get the Arty to show up as a COM port. In Windows 7, I see the digilent device under USB Controllers but I do not see it connect as a COM port. I am also showing 2 devices with driver issues with non-useful names like usb controller and unknown device. I can load the bitstream through the USB cable with no errors. I am running the hello world program and I can't connect to the board through teraterm etc as suggested in the tutorial. Does this sound like a driver issue or does it sound like an issue with my block design or sdk setup? I have tried uninstalling and reinstalling the drivers as shown here: https://www.xilinx.com/support/answers/54381.html Thanks, Scott