| Electronics > Projects, Designs, and Technical Stuff |
| Need answer Sigrok several protocol decoder |
| (1/2) > >> |
| SigrokLover:
Hi, For a project, I will purchase a logic analyzer that is compatible with sigrok. The idea would be to have a SPI sniffer (9 slaves + MISO+MOSI+ CLK) and an I2C sniffer. To do this, I chose a 16-channel logic analyzer (12 for SPI, 2 for I2C). I searched for two days on the internet but I couldn't find an answer to my questions. So I have two questions: 1) Can sigrok decode an SPI communication with 9 slaves (CS0, CS1,... CS8)? I have only seen examples where only one slave was involved. 2) Can sigrok independently decode I2C and SPI at the same time if the channels dedicated to both protocols are specified? Thank you for your time. |
| tsman:
Install the Sigrok software. PulseView has a virtual demo device so you can play about with the interface without having any hardware connected. --- Quote from: SigrokLover on February 11, 2019, 01:57:41 pm ---1) Can sigrok decode an SPI communication with 9 slaves (CS0, CS1,... CS8)? I have only seen examples where only one slave was involved. --- End quote --- Yes. You can have add SPI decoders sharing CLK/MISO/MOSI but separate CS in the Sigrok PulseView software. --- Quote from: SigrokLover on February 11, 2019, 01:57:41 pm ---2) Can sigrok independently decode I2C and SPI at the same time if the channels dedicated to both protocols are specified? --- End quote --- Yes. |
| SigrokLover:
Thank you very much tsman, your answer really helps me! I intend to use sigrok-cli to study the collected data (using a python script for example). Can you confirm that what you told me about pulseview also applies to sigrok-cli? Thank you again in advance, you're helping me a lot! |
| tsman:
Sorry. I'm not sure about sigrok-cli as I've never used it. Just playing about with it now and it doesn't seem to like it but the docs say it should be possible? |
| Doctorandus_P:
Some 45 minutes into this video you get some examples on working with sigrok-cli: Manpage of sigrok-cli says: --- Code: --- -P, --protocol-decoders <list> This option allows the user to specify a comma-separated list of protocol decoders to be used in this session. The decoders are specified by their ID, as shown in the -L (--list-supported) output. Example: $ sigrok-cli -i <file.sr> -P i2c Each protocol decoder can optionally be followed by a colon-sep‐ arated list of options, where each option takes the form key=value. Example: $ sigrok-cli -i <file.sr> -P uart:baudrate=115200:parity_type=odd The list of supported options depends entirely on the protocol decoder. Every protocol decoder has different options it sup‐ ports. --- End code --- This reeks very stronly of being able to add as many instances of the protocol decoders as you need. I have not checked, nor used it in this way, but it seems logical that Pulseview exchanges data & commands with sigrok-cli in the background, and if so, this means that anything you can do with Pulseview can also be done with sigrok-cli. But if you have doubts, then use the magic words "24MHz 8ch" and get yourself an EUR 5 box from Ali / Ebay / Banggood / China and start experimenting. |
| Navigation |
| Message Index |
| Next page |