wolfie

File->Export->I2S->Copy to Clipboard almost works, but it only has 224 data points.

Hi @attila, My I2S source device is generating a sine tone. I hear dropouts on my receiving device. Therefore, I'm using the AD3 logic analyzer to monitor the I2S data that the source transmits. Is there a way to log 5 seconds of data to a file so that I could plot the data in excel or matlab? I've the "record to file" options (using CSV), but it's only saving very small values to the file. Thank you, Rob

Hi @attila, I think I figured out why the errors were showing up in the data. In ESS Suite, I clicked on the little notepad icon to adjust the I2S settings and switched the Clock from Falling to Rising. Now I don't have any errors. I still have the bottom byte being masked to zeros, but that seems like it's a real issue with my I2S source device, which I'm looking into now. Thanks for your help, Rob

Hi @attila, Thanks very much for your reply. Any thoughts about why the tool is showing "error" for some of the samples? Kind regards, Rob

Hello, I'm using the Digilent AD3 to analyze I2S for the first time. So far, I've only used to as an oscilloscope. The I2S feature of the logic analyzer looks very cool, but I'm still working to figure everything out. I've attached 3 files: I2S_capture_for_digilent.dwf3logicacq - this is the data I captured with the AD3. I2S_captured_with_DA3.jpg - this is a screenshot of the I2S captured with the AD3. I've attached this incase in case I2S_capture_for_digilent.dwf3logicacq isn't loadable (this is my first time saving a capture). sinetone.jpg - this is a screenshot of a sine table (from my source code), which I'm playing out over I2S. I couldn't fit the entire sine table in the screenshot, but it's symmetric about zero, so the missing negative values are obvious, given that all of the positive values are there. I have a couple of questions: Occasionally the decoded 2s compliment values show up as "Error". Is this a data capture issue or a real error with my I2S data? The I2S values don't match the the hard-coded values that I have in my source code for the sine table. For example, my sine table has values 6420363, 4342263, 2189866, 0..... The corresponding I2S values captured with AD3 are 6420224, 4342016, 2189824, 0. Is this to be expected? Aside from these questions, any other helpful tips related to capturing I2S with the AD3 (or pointers to videos on the topic) are appreciated! Thanks for your help, Rob I2S_capture_for_digilent.dwf3logicacq

Hello, Can anyone tell me if the Write function (used in WaveForms I2C Custom Script) generates a stop bit? Here is my script. The first Write, writes a value to a register. The 2nd Write is actually setting up for reading the register. I need to know if this command is sending a stop bit or not. // Simple test to read and write register using I2C const adr = 0x64; // address of device if(Clear()!=true) return "I2C bus error. Check the pull-ups."; if(Write(adr)!=true) return "Device NAK"; Write(adr, 0x40, 0x00, 0xC0, 0x0E, 0x06); // Write the value 6 to register 0x4000C00E Write(adr, 0x40, 0x00, 0xC0, 0x0E); // Send a write without data because we need to read this register wait(0.1); var rg = Read(adr, 1); // Read 1 byte from device return rg; This script appears to work, as rg ends up having the value 0X6. But I need to know if a Stop bit is sent after that 2nd read. If one is sent, this tells me my device under test will work with a Stop bit in between the write and the read. I was told I need to read register on my DUT like this (notice no Stop bit in between the Write and the Read), which is why I'm asking: Read: | S | I2C ADDR R/W=0 | AS | REGADDR BYTE 4 | AS | REGADDR BYTE 3 | AS | REGADDR BYTE 2 | AS | REGADDR BYTE 1 | AS | S | I2C ADDR R/W=1 | AS | DATA BYTE 1 | AM | DATA BYTE 2 | AM | DATA BYTE 3 | AM |.. | DATA BYTE N | P | Where: S is the start bit P is the stop bit AM is acknowledge by master AS is acknowledge by slave Thanks! Rob