malexander

@Kevin.C Can you try this one and let me know if it works: https://digilent.s3.us-west-2.amazonaws.com/Software/Waveforms3Beta/3.22.19/digilent.waveforms_beta_3.22.19.x86_64.rpm Thanks, Michael

@Kevin.C Will SHA512 work? I downloaded the rpm packages from our website and ran rpm -qip and looked at the signature field. All of them, with the exception of Waveforms, appears to be signed with RSA/SHA512. Please let me know if this works and I will work with Attila to get Waveforms signed with SHA512. malexander@vm-u22-lts:~/Downloads$ ls digilent.adept.runtime-2.27.9.aarch64.rpm digilent.adept.runtime-2.27.9.x86_64.rpm digilent.adept.utilities-2.7.1.i686.rpm digilent.adept.runtime-2.27.9.armhf.rpm digilent.adept.utilities-2.7.1.aarch64.rpm digilent.adept.utilities-2.7.1.x86_64.rpm digilent.adept.runtime-2.27.9.i686.rpm digilent.adept.utilities-2.7.1.armhf.rpm digilent.waveforms_beta_3.22.18.x86_64.rpm malexander@vm-u22-lts:~/Downloads$ rpm -qip *.rpm Name : digilent.adept.runtime Version : 2.27.9 Release : 1 Architecture: aarch64 Install Date: (not installed) Group : System Environment/Libraries Size : 25044427 License : see /usr/share/doc/digilent.adept.runtime-2.27.9/EULA and /usr/share/doc/digilent.adept.runtime-2.27.9/license-openssl-ssleay.txt Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:39 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.runtime-2.27.9-1.src.rpm Build Date : Mon 30 Jan 2023 02:03:57 PM PST Build Host : rpi4-ubuntu64 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Runtime Description : The Adept Runtime consists of the shared libraries, firmware images, drivers, and configuration files necessary to communicate with Digilent's devices. Name : digilent.adept.runtime Version : 2.27.9 Release : 1 Architecture: armhf Install Date: (not installed) Group : System Environment/Libraries Size : 21202338 License : see /usr/share/doc/digilent.adept.runtime-2.27.9/EULA and /usr/share/doc/digilent.adept.runtime-2.27.9/license-openssl-ssleay.txt Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:54 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.runtime-2.27.9-1.src.rpm Build Date : Mon 30 Jan 2023 01:27:45 PM PST Build Host : rpi4-ubuntu32 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Runtime Description : The Adept Runtime consists of the shared libraries, firmware images, drivers, and configuration files necessary to communicate with Digilent's devices. Name : digilent.adept.runtime Version : 2.27.9 Release : 1 Architecture: i686 Install Date: (not installed) Group : System Environment/Libraries Size : 23160188 License : see /usr/share/doc/digilent.adept.runtime-2.27.9/EULA and /usr/share/doc/digilent.adept.runtime-2.27.9/license-openssl-ssleay.txt Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:54 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.runtime-2.27.9-1.src.rpm Build Date : Mon 30 Jan 2023 11:31:24 AM PST Build Host : michael-u16-32 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Runtime Description : The Adept Runtime consists of the shared libraries, firmware images, drivers, and configuration files necessary to communicate with Digilent's devices. Name : digilent.adept.runtime Version : 2.27.9 Release : 1 Architecture: x86_64 Install Date: (not installed) Group : System Environment/Libraries Size : 25120940 License : see /usr/share/doc/digilent.adept.runtime-2.27.9/EULA and /usr/share/doc/digilent.adept.runtime-2.27.9/license-openssl-ssleay.txt Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:55 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.runtime-2.27.9-1.src.rpm Build Date : Mon 30 Jan 2023 11:47:30 AM PST Build Host : michael-u16-64 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Runtime Description : The Adept Runtime consists of the shared libraries, firmware images, drivers, and configuration files necessary to communicate with Digilent's devices. Name : digilent.adept.utilities Version : 2.7.1 Release : 1 Architecture: aarch64 Install Date: (not installed) Group : Applications/Communications Size : 6042364 License : see /usr/share/doc/adeptruntime/copyright Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:55 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.utilities-2.7.1-1.src.rpm Build Date : Tue 13 Jul 2021 05:14:31 PM PDT Build Host : rpi4-ubuntu64 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Utilities Description : Adept Utilities is a set of command line applications that can be used in conjunction with the Adept Runtime to manage and communicate with Digilent's devices. Currently Adept Utilities consists of three applications: Digilent Adept Utility (dadutil), Digilent JTAG Config Utility (djtgcfg), and Digilent NetFPGA-SUME Flash Configuration Utility (dsumecfg). The Adept Utility provides a command line interface for discovering Digilent devices, querying device information, manipulating the device table, and setting device information. The JTAG Config Utility allows users to initialize, program, and erase FPGAs and CPLDs on Digilent boards using a command line interface. The NetFPGA-SUME Flash Configuration Utility allows users to write bit or bin files to a specific section of the flash memory on Digilent's NetFPGA-SUME. For more information please consult the associated man documentation. Name : digilent.adept.utilities Version : 2.7.1 Release : 1 Architecture: armhf Install Date: (not installed) Group : Applications/Communications Size : 6013249 License : see /usr/share/doc/adeptruntime/copyright Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:56 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.utilities-2.7.1-1.src.rpm Build Date : Tue 13 Jul 2021 05:43:01 PM PDT Build Host : rpi4-ubuntu32 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Utilities Description : Adept Utilities is a set of command line applications that can be used in conjunction with the Adept Runtime to manage and communicate with Digilent's devices. Currently Adept Utilities consists of three applications: Digilent Adept Utility (dadutil), Digilent JTAG Config Utility (djtgcfg), and Digilent NetFPGA-SUME Flash Configuration Utility (dsumecfg). The Adept Utility provides a command line interface for discovering Digilent devices, querying device information, manipulating the device table, and setting device information. The JTAG Config Utility allows users to initialize, program, and erase FPGAs and CPLDs on Digilent boards using a command line interface. The NetFPGA-SUME Flash Configuration Utility allows users to write bit or bin files to a specific section of the flash memory on Digilent's NetFPGA-SUME. For more information please consult the associated man documentation. Name : digilent.adept.utilities Version : 2.7.1 Release : 1 Architecture: i686 Install Date: (not installed) Group : Applications/Communications Size : 6013794 License : see /usr/share/doc/adeptruntime/copyright Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:56 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.utilities-2.7.1-1.src.rpm Build Date : Tue 13 Jul 2021 04:15:52 PM PDT Build Host : michael-u16-32 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Utilities Description : Adept Utilities is a set of command line applications that can be used in conjunction with the Adept Runtime to manage and communicate with Digilent's devices. Currently Adept Utilities consists of three applications: Digilent Adept Utility (dadutil), Digilent JTAG Config Utility (djtgcfg), and Digilent NetFPGA-SUME Flash Configuration Utility (dsumecfg). The Adept Utility provides a command line interface for discovering Digilent devices, querying device information, manipulating the device table, and setting device information. The JTAG Config Utility allows users to initialize, program, and erase FPGAs and CPLDs on Digilent boards using a command line interface. The NetFPGA-SUME Flash Configuration Utility allows users to write bit or bin files to a specific section of the flash memory on Digilent's NetFPGA-SUME. For more information please consult the associated man documentation. Name : digilent.adept.utilities Version : 2.7.1 Release : 1 Architecture: x86_64 Install Date: (not installed) Group : Applications/Communications Size : 6039466 License : see /usr/share/doc/adeptruntime/copyright Signature : RSA/SHA512, Tue 19 Mar 2024 10:37:56 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.adept.utilities-2.7.1-1.src.rpm Build Date : Tue 13 Jul 2021 04:45:04 PM PDT Build Host : michael-u16-64 Packager : Digilent, Inc. <support@digilentinc.com> Vendor : Digilent, Inc. Summary : Digilent Adept Utilities Description : Adept Utilities is a set of command line applications that can be used in conjunction with the Adept Runtime to manage and communicate with Digilent's devices. Currently Adept Utilities consists of three applications: Digilent Adept Utility (dadutil), Digilent JTAG Config Utility (djtgcfg), and Digilent NetFPGA-SUME Flash Configuration Utility (dsumecfg). The Adept Utility provides a command line interface for discovering Digilent devices, querying device information, manipulating the device table, and setting device information. The JTAG Config Utility allows users to initialize, program, and erase FPGAs and CPLDs on Digilent boards using a command line interface. The NetFPGA-SUME Flash Configuration Utility allows users to write bit or bin files to a specific section of the flash memory on Digilent's NetFPGA-SUME. For more information please consult the associated man documentation. Name : digilent.waveforms Version : 3.22.18 Release : 1 Architecture: x86_64 Install Date: (not installed) Group : Engineering/misc Size : 68189182 License : see /usr/share/doc/digilent-waveforms/copyright Signature : RSA/SHA1, Fri 12 Apr 2024 01:23:28 AM PDT, Key ID 134da9ebeb58bc22 Source RPM : digilent.waveforms-3.22.18-1.src.rpm Build Date : Fri 12 Apr 2024 01:23:10 AM PDT Build Host : attila-u16-64 Summary : Digilent WaveForms Description : Digilent WaveForms Application, Runtime and SDK. Support for Digilent Scopes & Instruments products.

@scorbetta This makes a lot more sense now because support for network devices was added in 2020. To the best of my knowledge Vivado includes the libraries in a subdirectory underneath the Vivado directory and loads them from there. This is something I can confirm with Xilinx - can you tell me which version(s) you have installed? I think at one point we were installing files in /usr/local/lib64 but moved to /usr/lib64, so it's possible that those files may be left over from an older installation that was performed using the install script from the tar.gz instead of the debian package manager. I believe that warning message you are seeing can safely be ignored. Thanks, Michael

@scorbetta I don't see DmgrSetNetworkConnTimeout listed in the output which doesn't make sense, as that symbol is present in the latest version of the runtime which I freshly installed using the debian package from our website. Can you please provide the output of "ls -al /usr/local/lib64/digilent/adept/libdmgr.so"? Thanks, Michael

@scorbetta What Digilent hardware, if any, do you have attached to your system when attempting to launch Waveforms? Does this error show up immediately when you launch the application or are additional steps required to reproduce it? Can you try executing "nm -D --defined-only /usr/local/lib64/digilent/adept/libdmgr.so | grep DmgrSetNetworkConnTimeout" and providing the output? It should be something similar to "000000000000237d T DmgrSetNetworkConnTimeout". When I install the debian package in Ubuntu 22.04 LTS using "sudo apt install ./digilent.adept.runtime_2.27.9-amd64.deb" the library files always end up in "/usr/lib64/digilent/adept" on my system. It's possible that "/usr/lib64" is a symbolic link to "/usr/local/lib64" on your system. Can you execute "ls -al /usr/lib64" and see if that's the case? @attila I can't replicate this behavior in Ubuntu 22.04 but the package always installs the files in /usr/lib64/digilent for me. If "ldconfig -p | grep libdmgr" is able to find libdmgr.so the location of the library should only matters if the application (Waveforms in this case) loads the library (instead of links to it) and specifies a relative or absolute path that doesn't match up with "/usr/local/lib64/digilent/adept/ibdmgr.so". Do you expect to see the reported error if the library can't be loaded or is this error more in line with a missing symbol? Thanks, Michael

@Kevin.C I don't see it for WaveForms 3.22.2 but the public key should be the same as the one used for Adept so please try that one. @attila did you go back and sign and re-upload the existing stable release of WaveForms for Linux or are you only signing new releases?

@Kevin.C The GPG keys are on the download page next to the software they are applicable to:

@perdue This is not a known issue - we have linked our own libraries and applications against 2.27.9 and they run without issue. I'm curious to here if you also experience this problem with 2.22.1, as that is the earliest release that includes SSL/TLS support for the ADP3xxx series. Below are links for the desktop installers: https://digilent.s3.us-west-2.amazonaws.com/Software/Adept2+Runtime/2.22.1/digilent.adept.runtime_2.22.1-amd64.deb https://digilent.s3.us-west-2.amazonaws.com/Software/Adept2+Runtime/2.22.1/digilent.adept.runtime_2.22.1-i386.deb https://digilent.s3.us-west-2.amazonaws.com/Software/Adept2+Runtime/2.22.1/digilent.adept.runtime-2.22.1.x86_64.rpm https://digilent.s3.us-west-2.amazonaws.com/Software/Adept2+Runtime/2.22.1/digilent.adept.runtime-2.22.1.i686.rpm https://digilent.s3.us-west-2.amazonaws.com/Software/Adept2+System+Installer/2.22.1/digilent.adept.system_v2.22.1.exe The Adept SDK (includes lib files for linking in Windows) hasn't been published since 2016 since the public API hasn't changed. Can you please tell me which distribution of Linux you are using? Thanks, Michael

@aminoh I was having trouble getting OpenSUSE to work in VMWare so I was unable to verify that the error goes away. However, I have signed and re-uploaded all of the RPM and DEB packages for the Adept Runtime and Adept Utilities to our website. You will need to import our public GPG key, which I've attached here. Hopefully, that key will be published on our website soon. Thanks, Michael digilent_public_key.asc

@aminoh I briefly looked into this and resolving this issue seems fairly straight forward. I believe we just need to generate a GPG key, sign the package, and publish our public key on our website so that users can import it. Which version of OpenSUSE are you running? I'd like to spin it up in a VM verify the process. Thanks, Michael

@GLC The Cora Z7 has a dual channel USB controller attached to the USB MicroB connector next to power jack. Channel A is used for JTAG and Channel B is UART. You should see multiple devices in the device manager similar to the image I've attached. There should be two entries for the device shown under the "Universal Serial Bus controllers" section and a single entry under "Ports (COM& LPT)". Can you please check to see if you have similar entries in the device manager on your system? Are there any unknown devices? Thanks, Michael

Hi Kishore, This is outside my field of expertise, as I wrote decutil and gave the source code to a colleague back in 2019 to integrate into our Petalinux image. I sent an email to someone who has more expertise in this and asked him to help answer your questions. It's already after-hours where he is located so it may be a day or two before he responds. Thanks, Michael

Hi Kishore, I'm sorry but the PMCU firmware on the Eclypse Z7 is Digilent IP that I'm unable to share. One of our former employees took my decutil code and added a hardware abstraction layer to allow most of the code to function in both baremetal and Linux. It was then renamed to dpmutil and published on our github and you can find the code here. Can you try cloning that repository and building the application in whichever version of Petalinux you are using and see if it works? If it builds and runs but has an error finding or opening the I2C device then you might try one of the following: 1. Run it with sudo or switch to root with su and then run it. 2. Look at function I2CHALOpenI2cController in I2CHAL.c. It searches sysfs for an I2C device with name "pmcu-i2c" and if it finds one then it will open that device. Otherwise, it will attempt to open "/dev/i2c-0". It's possible that something changed with the sysfs directory struct since decutil was published and that might cause the I2C device not to be found. You can change variables szI2cDeviceName and szI2cDeviceNameDefault which are defined at lines 38 and 39 of I2CHAL or modify I2CHALOpenI2cController to skip the search entirely and just open the device using the path defined by szI2cDeviceNameDefault and then recompile the application. As far as I can remember we didn't do anything special in the device tree, other than associate "pmcu-i2c" with I2C0 of the Zynq PS. To answer your question, yes I'm convinced that this is some sort of software issue and integrating dpmutil (previously decutil) will allow you to communicate with the platform MCU from Linux to turn on the power supplies. That being said, none of this should even be necessary, as the SYZYGY specification expects anything you plug into a SYZYGY port to contain an MCU with the DNA for the module and contain the voltage ranges the module supports. If you program a valid DNA into the module then the power will turn on automatically and you shouldn't need to interact with the platform MCU at all. Thanks, Michael

Hi Kishore, I) Register 0x804C is read only and should only contain the target voltage so if it's non-zero then that suggests that the value came from reading the SYZYGY DNA (if it exists) or from writing to the override register. The value (0xC0B4) you specify for register 0x804E seems correct to me for overriding and enabling VADJA at 1.8V. I'm not sure why you read it back as 0 but one possibility is that there's a timing issue. I'm not familiar with the i2ctransfer application. One thing you might try is writing a custom application. I've attached the source code for the functions that are used by decutil to read and write the Platform MCU registers. Please note that there does appear to be a delay between reads. It would be really helpful to know if decutil from our linux image works with our Linux image running when nothing is plugged in. That might tell us if this is a software or a hardware problem. If decutil is able to override and turn on the supplies then we know this is a software issue. 2^10 is 1024 so the maximum override voltage could be 10.23V. A value of 0xB4 corresponds to 180 and since it's in 10mV increments that gives you 1.8V so I don't see an issue there. No changes are required to the platform configuration or reset registers. II) What do you mean by "get complete firmware on PMCU"? III) Yes, there is a difference between no DNA being present and nothing being connected to the ZMOD. Consider the following scenarios: 1. There is no board plugged into the ZMOD A port. This means that there isn't an MCU to ACK SLA+W from the PMCU so the PMCU will not think a module is present. In such case, you can use VADJ_n_OVERRIDE to set the voltage to anything within the valid range (I think its 1.2V to 3.6V on this board). 2. There is a board plugged into the ZMOD A port. The following scenarios are possible: a. There is no MCU on the board and no other device on the board to respond to SLA+W. Therefore the PMCU thinks that no module is present and will allow override. b. There is an MCU on the board but it doesn't respond to SLA+W. This is the same as scenario 2a and override will be allowed. c. There is an MCU on the board and it responds to SLA+W but the DNA is empty or invalid due to CRC mismatch. The PMCU will think there is a module present and consider it unsafe to allow the VADJ supply to turn on because it can't determine if the requested voltage will damage the hardware. This is a safety mechanism and override will not be allowed. We did not build in any mechanism for disabling this safety feature. If you want to get around it while doing hardware development you could consider cutting the I2C traces on your board until you are ready to include proper DNA and then reconnect them. d. There is an MCU on the board and it responds to SLA+W and the DNA is valid. Override will be allowed but the voltage will be limited to the range(s) specified in the DNA. In such case make sure your DNA contains one or more range with the voltage that you want to set or just set it to 1800mV min and max and the supply will just turn on automatically at 1.8V as desired (SmartVIO). Please try decutil with our Linux image and no boards plugged in to help us determine if this is a hardware or software issue. Thanks, Michael PlatformMCU.c

Hi Kishore, My colleague @artvvb loaded image 0.3 onto an SD card, booted the Eclypse Z7 without anything plugged into Zmod A or B, and confirmed that he was able to set the voltage to 1.8V and then 3.3V using the decutil setviocfg command. He measured voltages of 1.821V and 3.327V. Please download the v0.3 image here and then follow Step 2 of the "Setting up the Linux Projects" section described here to get our petalinux image up and running. Once you've booted please execute "sudo decutil setviocfg -chanid a -override y -enable y -voltage 1800" to set enable VADJA and set the voltage to 1.8V. If you want to do the same for VAJDB then you can execute "sudo decutil setviocfg -chanid b -override y -enable y -voltage 1800". Please let me know if this works, and again, make sure you have no boards or cables connected to ZMOD A or ZMOD B. Thanks, Michael