Blackfin

Description: I designed a small board with an AD7716 ADC for biomedical application. The board is designed as per ADSP -2101 example in the AD7716 datasheet. The board connects directly to the sport 0 interface on the Blackfin ADSP BF537 EZ-Kit Lite board. I managed to get a small program working which programs the AD7716 with filter cutoff frequencies and then sets it to master mode. I have been unsuccesful however in reading data rom the device. I set the device in master mode and it streams four channels 32 bits of data in 4 byte chunks. I can not read them in on the blackfin rx line. I have done this in C but would prefer to do it all in labview, I have embedded module 2.5 and labview 8.6.
Can someone assist in telling me what parameters are required to be set for the sport configuration. Also if possible if someone could give me a sample vi that would also help.
Pins used are as follows :
Pin 2: vdd
Pin 5: reset -> reset (AD7716)
Pin 6&16: PJ9_TSCLK0 tied with PJ6RSCLK0 ->SCLK(AD7716)
Pin 7: PJ7_RFS0 ->RFS0 (AD7716)
Pin 8&14: PJ8DR0PRI& PJ11DTR0PRI-> SDATA (AD7716)
Pin 10: PF10_LED5 -> MODE (AD7716)
Pin 11: PJ10_TFS0 -> TFS (AD7716)
Pin 18: PF11_LED6 -> DREADY (AD7716)
Pin 25: PF6_LED1 -> DIN (AD7716)
Pin 28&30&32: LED4&3&2 -> A2&A1&A0 (AD7716)
Pin 34 : GND -> GND (AD7716)
Platform : ADSP-BF537 EZ-KIT Lite
Software : VisualDSP++ 5.0
Data sheet for AD7716 http://search.analog.com/search/default.aspx?local=en&query=AD7716&contentType=Data_Sheets
Kudos! Thanks!

Yes believe me i have tried using other examples to get it up and running, which is how i managed to program the board in the first place. Basically i cant use two wire as the board is already designed and hardwired to the primary data line of sport, to use ht etwo wire interface it needs to be connected to sdata. I managed to use the audio talktrough examples with some modification to program it, but i cannon get it to recieve, transmit settings and rx settings are different so not sure what i should be setting for recieve. For instance its says in data sheet to use alternate framing when using adsp 2101 processor but the timing diagrams they suppy to not represent alternate framing, although alternate has worked for transmit mode. I have set device in serial and can see it transmitting data, ive just realised no tere maybe another issue, the data never goes above 1.2v. This could be the reason why im not recieving data in my code. I have an interrupt routine which interrupts when data is recieved in the port but when i access the data its blank.

Similar Messages

How can I know the latency in a sub VI or routine (inline c node) in blackfin module?

Hi, I want to control a transceiver using a BF-537. The two principal taks are programming the transceiver and send/receive data from transceiver. These operation are development with sub-VIs, little routine in C using inline c node, etc. However, I need to know the lantency of each sub-VI or code writing in C; I need to know how much time use these elemnt to finished your function.
If anybody know How Can I to measure the lantecy, I will be grateful...!
regards
The Caribbean

Hello,
The easiest way to benchmark how long operations take on the Blackfin is to insert timing code in a sequence structure to directly measure the timing with the Tick Count function. Bear in mind, of course, that adding this code will itself affect your timing somewhat. Take a look at the example below to see what I mean - you could just repeat this for each operation you wanted to measure.
Message Edited by MattP on 07-31-2007 10:50 AM
Message Edited by MattP on 07-31-2007 10:50 AM
Cheers,
Matt Pollock
National Instruments
Attachments:
benchmark.jpg ‏16 KB

How to Configure a Blackfin Static IP Address

I've read that the Blackfin lwip stack wants a DHCP server to assign it an IPaddress. I've proven that this works for me using a BF537 EZ-Kit.
Now I'd like to configure an application with a static IP address so I can use a crossover cable between a computer and the EZKIT.
I've seen a method to do this in the LWIP User Guide but this seems to apply only to projects built using Visual DSP. Is there a method to set a static IP address from LabVIEW Embedded? The LV "build specifications" properties dialog seems to indicate as such but it doesn't seem to work when I try it. If I disable DHCP my application doesn't work at all.

Try these steps:
1) Disconnect your computer from your network.
2) Connect the crossover cable between your computer and the Blackfin EZ-Kit.
3) Assign a static IP address to your computer. If you don't know how to do this, follow the directions at the following Microsoft Website:
https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_tcpip_pro_manual...
If you don't know what numbers to fill in while following the directions, use the following settings for your computer.
IP Address: 10.0.0.1
Net Mask: 255.255.255.0
Gateway: 10.0.0.254
4) Start LabVIEW and open your project.
5) Configure LWIP to a static IP address. To do this, open the Build Spec dialog in LabVIEW and click on the TCP/IP tab. Enable lwIP and uncheck Use DHCP. Fill in a IP address.
If your computer is setup with the above settings, the following Build Spec Options can be used for LWIP:
IP Address: 10.0.0.2
Subnet Mask: 255.255.255.0
Gateway: 10.0.0.254

TCP/IP instrumented debugging with Blackfin EZ-kit

I have been evaluating the LabVIEW for Blackfin with a BF537 EZ-Kit the last few days...so far, I have been able to get all the example programs to run using the non-instrumented USB debugger interface.
I have run the Web Server Buttons example, and I can cause the LEDs to blink by pressing the buttons on the browser interface, so I know that my crossover cable and DHCP server are running correctly on my laptop, and that I can communicate with the EZ-Kit over TCP/IP.
When I get to the example where they want you to debug using the instrumented TCP/IP debugger interface, the program loads using USB, then I get a dialog box that looks like it's trying to make a connection to the EZ-Kit via TCP, but the dialog disappears after a 20-30 seconds, and the program does not run. During the time the dialog is waiting to connect, I can ping the EZ-Kit from a DOS box and the EZ-Kit has acquired an IP address from my DHCP server.
What I am wondering is this: how does the debugger interface know what the IP address is to perform the instrumented debugging? Is there a config file somewhere that I need to enter an IP address into? Does the debugger use UDP to find the EZ-Kit? The debugger does not seem to be able to find the Ez-Kit, and it occurs to me that I haven't told any of the LabVIEW components what IP address that EZ-Kit will have....

The implementation of the Blackfin target is partially located in "plug-in" VIs that you can access. Open "C:\Program Files\National Instruments\LabVIEW 7.1 Embedded\resource\LabVIEW Targets\Embedded\vdk\vdk_LEP_TargetPlugin\LEP_vdk_ScriptCompiler.vi". You can see in the attached screenshot where this plugin VI determines the IP of the host PC and concatenates it in as a compiler flag. You can modify this LabVIEW code to hard-code that IP if you have multiple IP addresses, or even add functionality to programmatically get the correct IP address!
Message Edited by Michael P on 09-14-2006 02:22 PM
Michael P
National Instruments
Attachments:
BFIP.JPG ‏49 KB

Tcp ip blackfin

Hello everybody,
I'm evaluating version 8.2.1 of LabVIEW embedded for Blackfin and I'm having some problems communication with the processor via TCP/IP.
I have the ez-kit lite ADSP-537 from Analog Devices.
I made a simple program to simulate data acquisition and then sending that data via ethernet and everytime the linker is returning an error. I attached a file Compiler Output.rtf with the result of the compilation and the error description.
I tried also the shipped example of TCP/IP (WebLed.lvproj) and it is also returning the same.
Does anyone have the same problem as me?
Did anyone succeded in communicating with the Balckfin processor via TCP/IP?
Can anyone help me on this?
Thanks in advance,
José Sá
Attachments:
Compiler Output.rtf ‏67 KB

Hello,
It seems to me that the best way for us to help you is to look at your code, could you post it ...
Regards .
Richard Keromen
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Découvrez, en vidéo, les innovations technologiques réalisées en éco-conception

Is it possible to use an IrDA protocol with LabVIEW 8.2.1 in DSP BlackFin?

Dears,
I'm building a project to communicate a DSP BlackFin 533 with a Palm E2 Tungsten between IrDA Protocol. The packaged LabVIEW installed in Palm allows to use IrDA protocol, but I don't know if the packaged for BlackFin DSP allows or not.
Is it possible to use an IrDA protocol with LabVIEW 8.2.1 in DSP BlackFin?
Regards,
Renato - RPS

OpPss ...
Sorry !!!
Attachments:
IrSerial.zip ‏11 KB
IrSerial1.zip ‏11 KB

Blackfin video output and digital I/O

We are currently using LabVIEW 7.1/8.0 and NI MID-7604/7602 stepper driver
tooperate an infusion pump stepper motor for our biomedical engineering
senior design project. We hopefully want to burn the entire program that I have
attached onto a blackfin chip (we have the ADSP-BF537 EZ-Kit Lite). We also
need to display the front panels of the state functions on an colored LCD
display via yellow composite video cable (if possible), in addition to
digital I/O from buttons and a joystick to operate the "OK", "BACK", "HOME" buttons
and "UP", "DOWN", respectively in our LabVIEW program. Any help would be great,
any other hardware that may be needed would be greatly appreciated. NOT TO
FORGET: this has to be done through a blackfin microprocessor or ADSP-BF537 EZ-Kit
Lite, if possible. Our senior design project is an Accessible Infusion Pump
User-Interface. Thank You!
NI Software : LabVIEW version 7.1, 8.0
NI Hardware : Other device
Driver Version :
OS : Windows XP
Attachments:
Infusion pump interface 2-02-07.vi ‏62 KB

By "front port" I mean the front mounted I/O bay.
so which conenction are you using, the flex jack or the coax? They are two different cables, and ports (the coax is RCA, flex jack is mini TRS, or headphone plug).
You should use the out port on your module.
You should either connect the headphones via RCA -> RCA from teh coax port on the front bay, or connect via /8" -> RCA if using the flex jack. If the headphones uses a /8" digital in (just like the flex jack), then use a headphone extension cable.

Blackfin TCP/IP transfer rates

Hello All
I have built an application on the Blackfin that reads out the value of the timers, and transfers that data over ethernet to a data collection host. It seems that the throughput of the Blackfin's TCP/IP subsystem is VERY slow. I am using the canned LabView TCP functions to transfer the timer data. It is taking about 15 seconds to transfer 3 seconds worth of data (32 bit word generated at 10KHz, or 320Kb/s data rate). Consequently I am losing data since the buffer is overflowing. The TCP Write vi seems to send whatever data it is presented in a single packet, so I have tried packing the data into larger groups, so I don't have to call the function as often. I have also flattened the data, to reduce the overall size. The speed is still way off the 10Mb/s ethernet rate. Is there a configuration setting I am missing, or is this normal?
Thank You
Sean Sexton

Hello Sean,
Are you using LabVIEW 8.2.1? If so, there are some known issues that may explain the behavior you are seeing. I have copied them below:
Using instrumented debugging (TCP or serial) with a Blackfin application that has a loop with no waits might cause LabVIEW to fail to connect to the Blackfin application
If you use TCP for debugging or the application uses TCP functions, you must wait at least two minutes after ending the debugging session before you can reconnect to the Blackfin target. As an alternative, you also can power cycle the target by unplugging and plugging the cable to the EZ-Kit
You must disable data caching if you enable lwIP TCP/IP support. If you enable both options when you build a Blackfin VI into a Blackfin application, the Blackfin application runs very slow or not at all.
Could the third bullet explain the behavior of your system? Try disabling data caching and see if your performance improves.
Thanks!
Janell R

Blackfin UART Interrupt/Callback for receiving data

Hi,
I am having trouble structuring a simple program to receive data from the Blackfin UART1. Data is received over the UART1 every second, so I'm planning on creating an interrupt service routine to read in the data and store it to a global string array . After reading the following page on Blackfin callbacks,
http://zone.ni.com/devzone/cda/tut/p/id/3244
I believe this is the general way I should approach the problem:
Main VI:
- Static VI reference that references the UART interrupt service routine VI
- Static VI reference connects to BF UART Open block, BF UART Control block, then to the UART interrupt service routine
- Global string array indicator
UART interrupt service routine VI:
- UART Read block with the output buffer appending string to a global string array
This is not working--the global string array does not update. I have been able to read the data through the UART1 in another VI, but this was not triggered by an interrupt. Is this the right approach to the problem or does someone have a sample VI that I can look at?
Thanks in advance,
Chris

Hi Chris,
I would not recommend using the BF UART VIs in an Interrupt VI -- VDK is very strict about what is allowed in ISRs, and in general, it is best to do as liitle as possible in ISRs. Also, the callback will execute when the buffer is full (not necessarily once a second).
Instead, you could do a simple timed loop application that has a period of 1s, and do the UART Read in the timed loop. Or, you could even do something as simple as put the BF UART Read in a while loop that contains a Wait Until Next ms Multiple function to cause the loop to execute once per second. I recommend using the UART echo example as a starting point (attached).
Michael P
National Instruments
Attachments:
UART echo.vi ‏39 KB

Blackfin Performance Profiling

Hello,
I'm acquiring 32 bits signals in which only 18 bits are used. As the acquisition rate is around 4.5 MHz and last a few seconds, I must compress my data. Therefore I wrote a simple VI that takes an array of 4 32 bits data (where only 4*18 bits are usefull) and convert it into an array of 9 U8 of data. The conversion takes 0.4 us on my computer (Quad Xeon) but more than 60 us on the Blackin which make no sense. I'm using the BF548 evaluation kit running at 600 MHz where 60 us equals almost 36000 operations...
I'm using the TickCount (ms) over multiple calls the conversion VI to know get my execution time.
Is there any known issue with the TickCount (ms) function? Is the evaluation kit expected to run slower for any reason? I've attached the LabVIEW project to this message.
Regards,
Patrick Lessnick
Attachments:
bitstuffing.zip ‏33 KB

Patrick,
From my discussions with R&D we are not experiencing a bug. Its a unique challenge to streamline performance with LabVIEW for Blackfin since there are so many additional caveats we don't usually have to worry about in LabVIEW for Windows.
If performance is the chief concern, here are my recommendations.
Use a shift register.
Don't use a subVI. The code will be larger on the diagram, but it will be faster and smaller on the chip.
Don't use build array in the low level part. Instead, Initialize an array outside of the loop and index into it.
Turn on optimization. For example, turning on Disable parallel execution should have a significant effect.
If all else fails and our generated code just isn't fast enough (which I doubt), there is still the Inline C Node that he can use for doing something like this.
Given these recommendations please let me know if you have any additional questions or concerns.
-Mark
Mark
LabVIEW R&D

Fft blackfin bf537

Hi everybody,
I have some problems with the fft-analysis using the BF537 Blackfin Board:
Although the FFT works (I used the debug mode to display the spectrum) pretty good, the whole program takes too much time for execusion.
I think the problem is the "__Blackfin_cplxfr16_to_fr16_LV" VI. With this VI I want to get the real part of an complex value. But I need this funtion for an array, so I probably need the "__Blackfin_cplxfr16_to_fr16_LV_1d" VI. The problem is that this VI is selectable, but not executeable. An error occures when I want run the LV-program using this VI.
Maybe someone can help me with my problem. Maybe when I get the "__Blackfin_cplxfr16_to_fr16_LV_1d" VI, my time problams could be solved.
mfg Christian Schirmbrand

Christian:
Thank you very much for providing me with more information to better understand the issue at hand. I was able to reproduce it on my end and see that we get a compile error when using the 1d and 2d polymorphic instances of BF Complex Fract16 to Fract16 ReIM.vi. I have filed two Corrective Action Requests (96337 & 96338) to bring this up to our R&D team. However, I am not sure about when I will hear back from them regarding this issue. In the meantime, I was able to find a workaround for you; it basically involves using for loops to index through the arrays - it is similar to what you had in your application. I tested it on my end and was able to compile the application just fine. I have attached the project files to this post, feel free to try it out and let me know if it is an adequate solution for you in the short term.
Have a great day !!!
Regards,
Rudi N.
Attachments:
ComplexFract1d.zip ‏11 KB
ComplexFract2d.zip ‏11 KB

Inline C Node on Blackfin Beta 2.0

I am using the Labview Embedded for Blackfin beta 2.0
I am trying to run the example for 7.1 where the processor uses an Inline C Node to detect its IP address. Everytime I put down the node, the error message tells me that inline C is not supported for the current target. The target is the BF537 EZ-Lite kit. I thought the inline C node was supported?

To add an Inline C Node to a VI, the VI must be opened in the context of an embedded target. Move your VI under a Blackfin target in the LabVIEW Project, then open it.
Michael P
National Instruments

Blackfin ez-lite compile error on 537 FlagCallback example

I received the following message from the details on Compile error when I "Rebuild All" on the ADSP-537 FlagCallbackExample.
Sorry for the long message, but I don't know which part of it might be important.
Any thoughts?
Hummer 1
*** compiler output ***
C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application>"C:\Program Files\Analog Devices\VisualDSP 5.0\ccblkfn.exe" -O1 -Ov100 -c -proc ADSP-BF537 -threads -labview -implicit-pointers -I. @.\prjHeaders.lst -DCHeadless -D__vdk -D__USE_FFT_REL45__ -Wsuppress 0001,1661 "C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application\FlagCallback1.c" @.\prjOptions.lst
C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application>"C:\Program Files\Analog Devices\VisualDSP 5.0\ccblkfn.exe" -O1 -Ov100 -c -proc ADSP-BF537 -threads -labview -implicit-pointers -I. @.\prjHeaders.lst -DCHeadless -D__vdk -D__USE_FFT_REL45__ -Wsuppress 0001,1661 "C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application\FlagCallback2.c" @.\prjOptions.lst
C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application>"C:\Program Files\Analog Devices\VisualDSP 5.0\ccblkfn.exe" -O1 -Ov100 -c -proc ADSP-BF537 -threads -labview -implicit-pointers -I. @.\prjHeaders.lst -DCHeadless -D__vdk -D__USE_FFT_REL45__ -Wsuppress 0001,1661 "C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application\BF_Flag_Open.c" @.\prjOptions.lst
C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application>"C:\Program Files\Analog Devices\VisualDSP 5.0\ccblkfn.exe" -O1 -Ov100 -c -proc ADSP-BF537 -threads -labview -implicit-pointers -I. @.\prjHeaders.lst -DCHeadless -D__vdk -D__USE_FFT_REL45__ -Wsuppress 0001,1661 "C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application\BF_Flag_Install_Callback.c" @.\prjOptions.lst
C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application>"C:\Program Files\Analog Devices\VisualDSP 5.0\ccblkfn.exe" -O1 -Ov100 -c -proc ADSP-BF537 -threads -labview -implicit-pointers -I. @.\prjHeaders.lst -DCHeadless -D__vdk -D__USE_FFT_REL45__ -Wsuppress 0001,1661 "C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application\FlagWithCallback.c" @.\prjOptions.lst
At end of source: : internal error: Uncaught exception Assertion failed raised
   at ../../../libutil/cii/src/array.c:38 (in pass final_annotate
   during compilation of _FlagWithCallback_BlockDiagram). Please submit
   a bug report with this message, the command line used, type of
   machine and the output of the compiler when you add -ED -v to the
   command line. Please also send us the pre-processed file that is
   generated by the -ED option (the file generated is named
   <original_filename>.i)
1 catastrophic error detected in the compilation of "C:\Program Files\National Instruments\LabVIEW 2009\examples\lvemb\Blackfin\BF537\Flag with callback\BF537 FlagWithCallback\BF537\VDK_Application\FlagWithCallback.c".
Compilation aborted.
cc3089: fatal error: Compilation failed
*** linker output ***
Attachments:
compiler output.pdf ‏49 KB

Hi Hummer1,
I will look into this error, but I have a couple questions.
1.) Does this happen when you choose to "Build" as well?
2.) Does this happen only with the FlagWithCallback example or with all examples?
Aaron P
National Instruments
Applications Engineer
http://www.ni.com/support

ADI Blackfin BF561 Examples can't compile in LV2009 Blackfin

I'm trying to evaluate a BF561 EZ-KIT with the examples in Labview 2009 Blackfin, but I can't get any of the BF561 examples to compile. Every time I try to compile the (Core A) Target, I get a "Failed to Generate C Code for '..... .vi'". When I click on Details, there is no error text in the text box. If I try to build the Core B target, C code is generated for the VIs, but the build fails with an error message informing me that Core A must be built first.
Oddly enough, the examples for the other single core Blackfin boards build just fine.
Is this a known bug? Any thoughts?
Thanks!

aser01,
R&D was able to track down the issue to an incorrect support file. If you place the attached xml file at this location ( <LabVIEW>\Targets\ADI\Embedded\vdk\bf561\) on your computer and restart LabVIEW, you should be good. This will replace the xml file that is currently in that folder but that is okay because this xml file solves the issue. Give it a shot and try building the BF561 examlpes and let me know if that works (it fixes it for me on my computer after I restarted LabVIEW and configured the target with the silicon revision I was using). Good luck and thanks for pointing out this issue to us!
Grant H.
Message Edited by G-Money on 04-15-2010 03:57 PM
Message Edited by G-Money on 04-15-2010 03:58 PM
Grant H.
National Instruments
LabVIEW Product Marketing Manager

Pwm modulation on blackfin

Hi All
I'm trying to modulate PWM timer (working on 1MHz) with sinusoidal signal at 50 Hz on Blackfin 537.
the VI working done, but i'm cannot control the frequency on modulating signal, however it's look like the FOR loop proccesing time is 1.7msec. why ?
My software: Labview 8.6 , ADI_Blackfin 8.6
Hardware : ADSP-BF537 EZ-KIT, silicone ver 0.2
Attachments:
pwm_modulation.JPG ‏79 KB

Hi Karunya,
I'm downloaded the datasheet of ADSP-BF537 EZ-KIT. From that I'm understand that I'm can't work with TMR0 and LED4 in the same project.
What I'm mean in my question is why I'm see the signal that generated to TMR0 only on LED4, and not between pins 6 and 9 on header P11. The signal was checked by oscilloscope.
Following your request to measure the execution time of FOR loop by using flat sequence and timer, I can't do it because in working with BlackFin, labview compiling the VI and downloaded him to the RAM of EZ-KIT, and the VI looking like freeze (not on running mode) and I'm doesn't see any change on indicators. To demonstrate this operation, I'm measure the time of steps on one cycle of output signal. Attached image from oscilloscope, you can see that the time of one step (is equal to one iteration of FOR loop) is around 1.7 msec.
My main question is how to increase the iteration cycle of executed FOR loop, or any other suggestion to create modulated PWM by sinusoidal signal with adjustable frequency of sinusoidal signal (at range of 10-100Hz).
Note: my mission is to create modulated PWM, when carrier signal on 100kHz (natural frequency of TMR0) and modulated by signal (that change the % of duty cycle for TMR0) is absolute sinusoidal at range of 10-100Hz (because the % of duty cycle can be 0-100%).
The absolute sinus that you see on the image got from Low Pass filter by the oscilloscope software.
Attachments:
Block diagram 10 sample.JPG ‏88 KB
pwm_10samples.JPG ‏28 KB
pwm_100samples.JPG ‏27 KB

Blackfin

Similar Messages

Maybe you are looking for