Jared

Ok... Problem solved... I was downloading the "Linux ARM-Raspberry Pi" version of adept. I noticed there is not distinction between the 64 bit and 32 bit version of Raspberry Pi as there is for waveforms, so I tried the "Linux ARM-64-bit.deb" file instead. This file permitted me to install waveforms and connect to the Analog Discovery 2. Might I suggest making it clear which file you need to download for the Rpi 32 bit and Rpi 64 bit? I cant tell you how much time I wasted trying to figure this out. Jared

I have tried to install waveforms on my Raspberry pi 4 running 64 bit Raspberry Pi OS. Adept appears to have been successful, but waveforms failed with the error below. I am installing digilent.adept.runtime_2.27.9-armhf.deb and digilent.waveforms_3.19.5_arm64.deb. I do not know where the "detailed report" is located so I don't know how to troubleshoot this. I have had this problem for almost 10 months and gave up. Now I'm trying again in hopes to solve this. EDIT: Trying dpkg I get the following. Seems The waveforms installer is not finding the adept installation for some reason. It is telling me I need adept runtime greater than or equal to 2.26.1, but as I listed about I installed version 2.27.9, so I don't know what the problem is. pi@raspberrypi:~ $ sudo dpkg -i /home/pi/Downloads/digilent.waveforms_3.19.5_arm64.deb (Reading database ... 98697 files and directories currently installed.) Preparing to unpack .../digilent.waveforms_3.19.5_arm64.deb ... Unpacking digilent.waveforms (3.19.5) over (3.19.5) ... dpkg: dependency problems prevent configuration of digilent.waveforms: digilent.waveforms depends on digilent.adept.runtime (>= 2.26.1). dpkg: error processing package digilent.waveforms (--install): dependency problems - leaving unconfigured Processing triggers for gnome-menus (3.36.0-1) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for mailcap (3.69) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for shared-mime-info (2.0-1) ... Errors were encountered while processing: digilent.waveforms

Hi, I am trying to decode the programming signal from a C2D line on an 8 bit SiLabs chip which sends the LSB first. One line is a clock line and the other is a bidirectional data line. I setup using the BUS option in the logic tool with DIO 0 for clock and DIO 1 for data. I noticed in the BUS settings window that I have an option to set LSB and MSB but they appear to be tied or locked to other and off by one. I am a little confused how to use the LSB and MSB setting or exactly what it is doing. Could someone please explain what this is doing and how to set it properly? Also, I noticed that when using the BUS option with DIO 0 and DIO 1 turned on, I actually get DIO 0 showing up twice in the waveforms window. They both display the same clock signal, but one is called clock and the other is DIO 0. Why is this listed twice in the window and what is the significan ce of this? It is a little confusing as to why it is duplicated. As I was writing this I think I just figured out that using BUS and selecting LSB/MSB is simply saying which data line carries the LSB and MSB of that BUS. Since DIO 0 is just a clock signal, I am wondering if BUS is the incorrect option to use in my case. As a result, I am thinking that maybe I don't want to be using a BUS, but rather SIGNAL instead? I wanted to have waveforms display the HEX from the data, but SIGNAL does not seem to support the HEX display.