mmessuri

JColvin: Finally, success...Over the weekend I lifted a SD Card connector from an old PCB and addedd long header pins to it, with this addition I was able to eliminate the use of the breadboard (I still receive a "Leftover bit" error every once in a while but everything else is working). Thanks for all the help on this. BTW: While I am not sure if it is still needed, I did use the twisted wire pair (high speed) for both the CS and the CLK pins. -- Michael --

JColvin, thanks for the update and I'm sorry to say that I will have to wait until at least Saturday to follow up as during the moding of my micro SD card reader I had a slip up and botched up a through hole (it's been one of those weeks) by pulling up the top part of it (just pcb left now). I did place an order for some replacements but they won't be here until Saturday

So I gave your workspace a try, along with your addition to the twisted pair on the CS line and still had no luck. Now if I also add a twisted pair to the CLK line then I can get the trigger to take place on MOSI; however, I still see a bunch of leftover bits which seems to be corrupting the data as the 0x40 CMD does not termiate with the 0x95 value (see picture, where it is ? h90). At this point I am thinking it is interference caused by the use of a bread board so I have ordered a different SD card breakout board (also going to mod the one that I am using so that I can have pins on both sides) if you dont mind me asking, what is your breakout setup there?. After doing all of this I do have a follow-on question: Any ideas on why the DD is having such issues when the cheap analyzer does not?

After re-reading your response, I noticed that I failed to mention: I also tried chaning the trigger to 0x40 on MISO and sure enough, a trigger is hit every time

Concerning the Uno's 5 V logic and the DD's 3.3v logic, I thought the same thing so today I added a Logic Level Converter between the Arduino and the Logic Analyzer / device Drove the Low power supply (to the LLC), using a bench power supply: This had to effect on the problem (same old garbage in the analyzer). Since that did not work, I disconnected the above and recalibrated the Digital Discovery. This also did nothing to resolve the problem. Finally, I tried changing the delays and buffer sizes and this also did nothing to solve the problem. So at this point, I have run out of ideas

Here is the setup for just the Arduino, Digital Discovery, and the MicroSD card breakout board (connected to a bread board): Here is the connections to the MicroSD Card (the ground wire came off when I flipped it over for this picture; however, you can see from all the other pictures that the ground is connected as shared between all devices) I have mirrored your setup (as seen in your pictures), with the only difference being I am trying to capture/trigger on data from MOSI rather than the receiving of data on MISO. I also setup my trigger for the CMD 0x40 coming out of MOSI: When I press the reset button on the Arduino Uno, causing the SD_CardInfo sketch to run, the serial monitor of the Ardunio receives: As you can see from this screen shot, the tigger never triggered: Now I add another logic analyzer (in this case a cheaper verwsion of the Saleae Logic 8): I change nothing within the analyzer portion of the Logic 2.x software, other than set a trigger for 0x40 on the MOSI line and then press run: a few time frames later, the trigger hit Yet nothing was picked up by the Digital Discovery (it still is sitting on armed) So as you can see (and hopefully feel my frustation and bewilderment), a $20 knock of analyzer running logic analyzer software which required zero configuration changes is able to successfully capture/trigger yet the Digital Discovery (which cost over 10x as much [yes I know this Digital Discovery is more than just a logic analyzer]) is unable to perform the same task (even with all the tweaking I have tried [which includes just using the logic analyzer portion with the High speed probes and running at 800MHz]). I am sure it is probably something I have done wrong but I just cant figure out what. As a final note, if I turn off the "Debug with Logic Analyzer" option here is a portion of the capture from the SPI Protocol (I nseem to get a large number of "Leftover Bits" no matter what setting(s) I use: ... Data: hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, hFF | h00, Leftover bits: 5 hF8 | h08, Leftover bits: 1 h0 | h0, Leftover bits: 3 h20 | h20, Leftover bits: 2 h00 | h00, Leftover bits: 6 h0FC | h004,

If I change the start delay to 1s and have the Trigger set to Auto, I can capture the data as-long-as I keep hitting the reset on the Arduino, causing the values to be sent again and again. However, if I change the trigger to Normal nothing ever triggers. Finally, with the trigger set to Auto the capture kicks off regardless of hitting the trigger (I dont' press anything to re-init the sending of data and the trigger starts recording) Very frustrating!

I am sorry if this is a simple question but I have been fighting with this for most of the day: I am using an Arduino to read/write to an SD card (via a breakout board) and during this activity I am trying to use the Digital Discovery (and WaveForms version 3.22.2) to capture (using both the logic analyzer and SPI protocol analyzer) the initial command (0x40) being sent over MOSI; however, my trigger never hits (to add insult to injury, if I am using the SPI protocol analyzer to monitor the traffic I see values being passed back and forth but never the inital command block (which is 0x40 0x00 0x00 0x00 0x00 0x95). To make sure that I have everything wired up correctly I also setup a Sale Logic 8 to the same pins (using a breadobard) and ran a capture with the Salea Logic 2 software). Without having to mess with any of the configuration params in the Logic software I see (and trigger on) the desired 0x40 Command value so I know its going accross the wire and that my pins are correct. My settings in WaveForms are: SPI_CS: DIO24 SPI_CLK: DIO29 SPI_MOSI: DIO28 SPI_MISO: DIO25 SPI Protocol Analyzer Settngs: Select: DIO24 Clock: DIO29 Active: Low Polarity: 0 Frequency: Have tried from 100kHz to 50MHz DQ0: DIO28 DQ1: DIO25 First bit: MSBit Glitch Filter: Enabled Logic Analyzer (From the Debug with option) Select: DIO24 Clock: DIO29 DQ0: DIO28 DQ1: DIO25 Mode: Repeated (also tried just about every other mode) Trigger: Normal (also tried Auto) Source: Tried both Digital and Patterns Protocol: Spi MOSI Trigger: Value Value: h40 Place: Any Source: Digital, Rising Edge, 100MHz (also tried 200Mhx), 8 bits, DIO 24...31 Samples: Default (also tried up to 32 Mi Rate: 100Mhz (also tried down to 20Mhz) Note: 3.3v VIO not connected as the Arduino Uno is supplying the volatage Also, I have tried all of the above on both a Windows 10 system and a Linux system I must admit at this point I have no clue as to what I am doing wrong so any advice would be much welcomed. Thanks. -- Michael --

Fantastic. Thanks for taking the time to answer and provide pictures. If I might ask, what USB isolator are you using

What about USB FS devices?

Ok, I have been trying for a few days now to capture usb signals (from D+/D-) using the Digital Discovery and the HS adapter. Now I have tried very combination of sample rates / hz that I can find and no matter what I do the logic analyzer only captures the first falling edge of the D+ line and nothing more. For my POC I have connected a USB thumb drive to a USB expansion board and then connected the expansion board GND and D+ (and tried the D-) pins to DIO0. When I plug the USB Thumb drive in my rising edge trigger will take place but the waveforms software (which is the latest from the website) only captures the initial trigger point and no other data Now if I remove the Digital Discovery and replace its connections with my oscilloscope I see the USB signal transactions taking place between my Windows computer and the usb thumb drive (plugged into the expansion board) and Windows recognizes the drive so I know its the setup that I am using. As a sanity check, I have disconnected the DIO/GND pins and plugged them into pins 24/GND and then using the pattern generator created a clock signal, with the logical analyzer successfully capturing this data. Finally, i have taken a similar USB 2.0 thumb drive and wired my probes directory to the USB connectors D+/D-/GND connections (removing the need for an expansion board) and I still get the same results So a this point I have no clue as to what I am doing wrong and would like to reach out for some guidance if anyone can provide some. thanks.

So I was playing around with things today, trying to troubleshoot this further, and found that if I remove the High Speed Adapter and connect directly to any of the High Speed Input Pins which were not working with the adapter plugged in all issues disappear. At this point I can only speculate that the root cause of the issue is a bad HSA board (which is strange since there is nothing too this board other then connector pins)

After digging out my Digital Discovery from long term storage I wanted to verify that everything is still in working order so I followed the instructions (in the getting started section as it has been over a year since I used this device) for using the logic analyzer and was stumpdified to see that nothing was being recorded by the device. For my test setup I connected pin 28 to DIN 0 (using the high speed cables) and then connected the GND pin (of pin connector 28 thru 31) to the GND connector for DIN 0. Next (following the instructions) I setup the pattern generator to output a Clock (using 1khz in parameter 1) and hit run. On the logic analyzer tab I setup DIN 0 (with a base of 1ms/div) using a trigger of Auto and a bus speed of 100MHz then hit run. What I expected to see was the clock pattern (from the pattern generator tab) being captured on the logic analyzer but that is not what I received. What I actually received was no signal at all on DIN 0. I then repeated this process using DIN 1 thru 19 and received the same lack of signal. Thinking that I was going crazy I swapped DINs 0-19 for Pins 24 thru 27 (as the input pins on logic analyzer tab) and bam....the expected clock signal is being captured. Finally, I switched from using Pins 24 thru 27 (all the time keeping the output on pin 28) to using DINs 4 thru 23 and don't you know it....the expected clock signal is being captured. So at this point I am stumped as to the reason behind DINs 0-19 not functioning while DINs 4-23 are. This device has had very little use over the past two years (as I switched companies and the new job does not require research things at home much) and even less use on the HSI pins. As for the WaveForm software I am using version 3.18.1 on my Windows 10 64-bit OS (I even tried running the software as admin but that did not help) BTW: To ensure that it was not a problem with the HSI cables, I also tried just connecting the input pin to the DIN pin(s) but still the same problem. Does anyone have an idea of what might be going on there or perhaps a suggestion as to what to try next (if it comes down to it I guess I could write off DINs 0 thru 19 but that makes me start to have trust issues with this device) Thanks. -- Michael --