Jump to content

JColvin

Administrators
  • Posts

    6,702
  • Joined

  • Last visited

Posts posted by JColvin

  1. Hi @kraiskil,

    You can take out the screws and remove the frame without voiding the warranty (though I guess if you physically break the case that'll be a different story :) ).

    What are you experiencing specifically with the AD2? Is it detected by the WaveForms software? What do you see in the device manager (if you are using a Windows based device) when you connect/disconnect the AD2 from your computer?

    Thank you,
    JColvin

  2. Hi @RedskullDC,

    Unfortunately, we have not yet developed such a product at this point in time. We do have a have a product manager specifically for Pmods now (which was not the case when this thread was created), so I will get this request to them. I'll give an update later if I can, but it may be some time (i.e. months) before I am aware of any development status for such a product.

    Thanks,
    JColvin

  3. Hello!

    Welcome to the Digilent Forums! All of us here, both Digilent Staff and our incredible community members, are excited to be able to help you out with your project. 

    That being said, we are not the ultimate experts on Embedded Linux. A couple of us have a decent amount of experience, but unfortunately we cannot guarantee that we can identify the issue and have the solution to your problem for your exact distro, drivers, board, and application. We will try to help out the best that we can, but it may take some additional time to provide feedback on any questions that you may have.

    Thanks,

    The Digilent Team

  4. Hello,

    From my understanding at this point in time, none of the Digilent FPGA boards are compatible with LabVIEW. LabVIEW is able to interact with our microcontroller boards and our instrumentation line and we have VIs to go with them, but not for our FPGAs at this point in time.

    Let us know if you have any more questions.

    Thanks,
    JColvin

  5. Hello,

    I just wanted to let people know that we (Digilent) have not yet been able to get WaveForms 2015/Analog Discovery 2 working on a Raspberry Pi 3 either; we're still running into the issue mentioned and linked to by attila up towards the top of this thread. I guess I know that we've been able to get WaveForms to work briefly on the Pi 3, only to then receive a message about a lack of adequate power for the AD2 as mentioned on the linked thread. So, no resolution as of yet.

    Thanks,
    JColvin

  6. Hi @robertdigital and @ChristopherN,

    Letting you know that @attila and I see your responses/questions (although I don't have the knowledge to help debug the problems), but we're still waiting for the engineer to get back to Digilent from vacation. I'm hoping they'll be back sometime early January to collaborate with attlia on debugging the issues you are experiencing. 

    I guess as a side note, D@n is correct in his guess about the small team you're working with (~2 people who can address this particular situation), so we're not able to get this resolved in an expedited fashion (so-to-speak).

    Thanks,
    JColvin

  7. Very cool! I don't personally have a Cmod A7-35T to try it out for myself, but definitely looks very useful to try a number of features out without having to worry about any IP getting updated on you. The readme is also very detailed, which is nice.

    Do you mind if I post this on the Cmod A7 Resource Center page as a community project (with a link back to this thread)?

    Thanks,
    JColvin

  8. A customer on our website asked the following question:

    Hello Digilent! Since i could not send my feedback through your feedback option in Waveforms, i will attach the entire message here:

    Version: 2.7.5 32bit (2014-02-05)
    Device: Analog Discovery rev: C configuration: 1
    Open Forms: 4; Handle Count: 917; GDI Objects: 155; User Objects: 107; Threads: 32; Memory Working Set: 114,42 MB; Processor Time: 00:00:05.6316361
    -------------------------------------------------------------------------------------------
    OS : Microsoft Windows 7 Ultimate Service Pack 1
    version: 6.1.7601 language: 1033
    architecture: 64-bit Operating System
    .NET : v2.0.50727.5485 v3.0.30729.5420 v3.5.30729.5420
    CPU 1: Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz L2: 256 kB L3: 6 MB
    RAM : 8 GB @ 1,6 GHz in 2 banks
    GPU 1: NVIDIA GeForce GT 540M 2 GB
    USB 1: Standard Enhanced PCI to USB Host Controller
    USB 2: NEC Electronics USB 3.0 Host Controller
    Screen1: Generic PnP Monitor (1920x1080 dpi: 96)
    -------------------------------------------------------------------------------------------
    Please describe your issue here:


    Hello Digilent!

    I have been adviced to make contact to you about my problem with analog discovery by one of my teachers. 

    When i was working with my Analog Discovery yesterday, it suddenly stopped working. The problems are as follows;

    1. I cannot connect my analog to waveforms - it tells me that "Device configuration failed" and gives me the error message:

    DptilO failed ERC:7
    Device configuration failed (PLL 3).

    2. When i somehow sometimes manage to get through the configuration phase, Waveforms simply tells me that "The Analog Discovery has stopped working due to an overcurrent condition" - even though i haven't connected it to anything at all. 

    3. All the time i am let through to the Digilent Waveforms menu, there is a flashing message in the bottom right corner saying "Discovery OFF".

    I do of course have screenshots of all three issues, but it seems like i cannot attach them here. 

    For troubleshooting i have tried using different USB ports on my PC - and even tried connecting the Analog Discovery to different Computers, where other Analog Discoveries were working, but nothing seemed to be able to solve the problem - my Analog Discovery gave the same error messages everywhere. 

    I also tried the provided troubleshooting steps and restart the analog etc. 


    I hope that you can help me!
     

    I'm not familiar with this error, so I don't personally have any recommendations, but I'll make sure the appropriate engineer see's your question. You can post any screenshots that you have though on our Forum Gallery (you'll need to create an album).

    Thanks,
    JColvin

  9. A customer on our website asked the following question:

    Hi,
    I did all the troubleshooting techniques  in the thread and I am still getting the error "Device configuration failed". I am attaching the error message with this email.

    Is there anything further the customer could try? The error message they refer to is available on our Gallery here.

    Thanks,
    JColvin

  10. Hi SteveD,

    I sincerely apologize that this thread has gotten dropped by our team, I'll make sure that Tommy gets back to you on this. 

    As for the PmodOLEDrgb, I found the datasheet for the SSD1331 available from Adafruit here. However, like the PmodOLED this datasheet is rather difficult to decipher, so I would personally look at the Cpp and header file for the PmodOLEDrgb (available to download from it's Resource Center here in the MPIDE zip file). I agree that this is not the most helpful in terms of developing a MicroBlaze project, but at the very least will give you some insight into the initialization procedure and the needed SPI commands to send the display controller.

    Thank you for your patience,
    JColvin

  11. Hi Steve,

    I know I would certainly like some cool FPGA projects for various Pmods; I know there are plans to do this in the near future. In the meantime, I'll ask some of our applications engineers to see if they have helpful resources that they know of.

    Thanks,
    JColvin

  12. Hi Dan,

    I looked into this since I also recall having issues with the backslash character, and found that (bizzare as it seems) the backslash does not have a predefined character for it. The reason for this is because the PmodCLS uses the set of characters that is directly inside the memory of the KS0066 LCD controller that the host board (in your case a Basys 3) communicates with. The set of characters that it directly supports are here. (I'll update the PmodCLS reference manual to include this diagram as well) Why Samsung didn't include support in their LCD controller for a backslash is beyond me.

    I am not aware of a way to directly reconfigure the pre-defined library, so what would be done in this case tell the controller to define a custom character within it's own memory. I can try to explain it if you want since the functionality is provided in the C++ library for MPIDE within the last three functions or so, but I'm not too familiar with FPGA's and their hardware language, so I won't be able to personally help as much there.

    Let me know if you have any more questions.

    Thanks,
    JColvin

×
×
  • Create New...