Shalin

Hello @attila, Thanks for taking out time to try incorporating I3C protocol in Digilent. I will still request you to please take out time and include I3C protocol in Digilent. This will help us to automate our hardware based on I3C protocol through LabView. Currently, we are using I3C Prodigy which uses its own GUI to run I3C scripts. This slows down our whole process since we need to run each and every script whereas, LabView speeds up the automation process. I would be grateful if you can spend some time from your busy schedule and develop the I3C protocol in Digilent which can further help us in automation using LabView. Thanks, Shalin

Hello @attila, Thanks, it is working absolutely fine now. Meanwhile, I need to know the status of development of I3C support in Digilent. I will be requiring to use Digilent for our upcoming I3C based project. I will be performing automation through LabView by using Digilent I3C libraries. Thanks and Regards, Shalin Verma

Hello @attila According to our specification, we need to set CLK, MOSI and SS as 3.3V. When I lower the IO, it shows no response. My LA which is capturing has been set to 1.2volts digital level. At this level only, I am getting the MISO response of 840mv. Mainly, I will have to set the LA level to 1.2V to capture the MISO waveform. Is it possible to capture this weak MISO signal by using the high-speed LA pins (0-23) and adding a trigger ? Once I fetch the MISO signal using Digilent LA pin, then is there a way to set the rgRX in the VI with the array of data received from the LA pin ? Thanks, Shalin

Hello @attila Thanks for taking out time and making the effort. The rgRX is still appearing as zero. I probed this response on Scope and it shows that a very weak output MISO response of level 840 mV is appearing (attached screenshot below). Due to a weak output response, the digilent digital discovery DIO pin is interpreting this 840 mV as zero. Is there a way out , that this weak output signal response of 840 mV is interpreted as 1 by the digilent and shows 1 in the rgRX ? Is it possible to capture this weak signal by using the MISO high-speed LA pins (0-23) and adding a trigger ?

Hello @attila Please check the attached zip file below which contains the VI alongwith supporting libraries. I am not able to achieve the value of rgRX from digilent while I can see the MISO output data (rgRX) on other LA. Please try to run this VI and see if you get any output. Thanks, Shalin SPI read.zip

Hello @attila, I have set the voltage as 1.2V in the VI, whereas I am still seeing 3V in the scope output. I have attached screenshot below. Thanks, Shalin

Hello @attila, How do you set the digital voltage level of the pattern in digital discovery ? Do you have any specific function in labview to set the digital level ? Thanks Shalin

Yes, I am seeing rgRX out with cRX = 32. I tried but it only shows rgRX for 4 bit and not for 16 bit and 32 bit. I would request you to please run my VI once. It will help in identifying the issue.

Hello @attila I want to bring to your concern regarding a bug in receiver function (rgRX) of labview. When I send 32 bit pattern from Digilent pattern generator and capture 32 bit rgRX receiver pattern response, it comes constantly as all zero's in labview. I captured the response through Saleae LA and I am able to see 32 bit rgRX pattern there. However, the digilent rgRX is unable to capture the 32 bit pattern. Please check the rgRX functionality for 32bit response. I am attaching the screenshot below of 32-bit rgRX response captured through Saleae LA and the Labview VI below for your reference. Thanks, Shalin SPI_read - Annapurna.vi

Hello @attila Thank you for supporting I3C protocol implementation into Digilent Digital discovery in coming time. I am looking forward and waiting for the incorporation of I3C. Thanks and Regards, Shalin

Hello @attila Could you please guide me towards the implementation of I3C through Digilent discovery. Our new project will be utilizing I3C. Therefore, we will have to send I3C patterns via Digital discovery and further analyze them. In addition, we will have to vary timing with proper control. Thanks, Shalin

Hello @attila I have a query in Digilent Digital Discovery. Is it possible to use Digilent Digital discovery as a pattern generator and logic analyzer for I3C protocol ? Thanks Shalin

Hello @attila, The noise was within the Logic analyzer. I have switched to a new LA and the problem is resolved now. Further, I am trying to write a command 0000. I am not able to receive any response against this command in the rgRX. Could you please help, I am attaching the developed VI below. Moreover, is it possible to write the 4 words in a single row rather than writing them individually in a separate row ? I am attaching the screenshot below to understand better. Thanks, Shalin SPI_read_3.vi

Yes @attila, I am using the latest version 3.20.31.

Hello @attila I have checked the connections of the MISO pin connecting to the logic analyzer. The connections are perfectly fine. The labview is showing correct response of 00D0 whereas in LA it is showing FFFF. I am attaching the screenshot of Labview response and LA output below. Thanks, Shalin

Hello @attila My query is about when I see 00D0 in rgRX LabVIEW capture, why I am not able to see the same in LA capture on MISO pin. In LA capture, I am seeing FFFF instead of the response 00D0. Thanks, Shalin

Hello @attila I am facing an issue while I probe signal of MISO line on logic analyzer. In the labview, when I write 0100, the MISO output (rgRX) reads value 00D0. Further, when I probe this output on logic analyzer, I am able to see the input (0100) written on the MOSI whereas I am not able to see 00D0 on the MISO channel. A wrong value FF is shown there. Please help regarding the same. Thanks, Shalin

Hello @attila In the labview, I am not able to receive MISO data for the input data. I am only able to see the data written through MOSI (rgTX) but the output obtained on the MISO channel (rgRX) is incorrect. On the other hand, I have compared the same by using waveform GUI application where you can see that for 0100, the output in MISO channel is 00D0. I am attaching some screenshots below for your reference. Please optimize the API functions so that they work and deliver similar output as the waveforms GUI application. Thanks, Shalin

Hello @attila The API functions of the latest waveform version 3.20.31 is different in comparison to the API functions listed in the dwfvi.zip file. One of the functions listed in the dwfvi.zip file with name "F DWF digital SPI write read 16" has got array unsigned type of "rgTX" parameter whereas the same function listed in the latest SDK version 3.20.31 does not have array unsigned type of "rgTX" parameter. Could you please make it array type in the latest SDK versions API as well ? Most importantly, I am sending a long sequence using "read write 16" API function listed in dwf.vi. However, the output captured in LA is inappropriate. Similarly, I am receiving dissimilar output captured by MISO LA and MISO rgRX. I am attaching the VI below for your reference and some screenshots of LA. Thanks, Shalin dwfvi.vi

Hello @attila There are errors occurring in the labview VI functions after updating to the new waveform SDK version 3.20.31. I am attaching the screenshot of the block diagram window of the labview from where you can see the error in some of the SWD API functions. Thanks, Shalin

Thanks @attila. I will try it. Also, I want to know that how do you record the patterns in waveform GUI when you send command through LabView. I was trying the same but the waveforms GUI app says that the device Digilent digital discovery is being used by other application (labview). As a result, I am not able to record the labview pattern in waveforms GUI.

Hello @attila I have extensively checked the API functions of SPI in LabView. These developed API functions are not operating correctly. As an example, I have also attached the sample LabView VI for reference in my previous post. I would be grateful if this issue can be rectified. Also. let me know if you require some additional information from our end. Thanks, Shalin

Hello @attila I tried calling API functions in LabView. However, I am not able to generate the correct pattern using API functions. In LabView, I am trying to write 0091 in hex. In the output, I am unable to see the clock and getting invalid MOSI and MISO response. I am attaching the labview VI which I have created and its output captured by logic analyzer. Thanks, Shalin SPI_Read.vi

Thanks @attila . Further, we are planning to use Digital discovery for SPI interfacing in our upcoming project as we earlier did with SWD. I wanted to know that do you have the support of SPI interface with LabView. Previously, you had provided the same for SWD. I will be grateful if you can provide me the LabVIEW support for SPI interfacing as well. Shalin

Hello @attila In Sensor tab, when the commands are mentioned outside the "function loop()", there is a huge delay between each command. The similar commands written in the "function loop() have smaller delay. Please maintain smaller delay between the commands written outside the "function loop ()". I have attached the screenshots below for your reference. Thanks and Regards, Shalin