Trigger on protocol

rlugli

Wed, 02 Nov 2022 15:08:50 GMT

Dear IKALOGIC team, I just received your SP209 analyzer and I started to use it. At the moment I am having problems with triggering on protocol. I tried both UART and SPI but found different problems. UART: I am only able to trigger on the falling edge of the UART line. I am not able to trigger on protocol I tried every possibility (Trigger on any valid frame, Trigger on specific word, etc) but I always get error in the script log window. [UART](//muut.com/u/ikalogic/s3/:ikalogic:jUmU:uart.jpg.jpg) SPI: Selecting Trigger on any word seems not to work correctly, although no log error is displayed. The trigger is on the falling edge of the CS liline and not on the word. [SPI_01](//muut.com/u/ikalogic/s3/:ikalogic:KNAn:spi_01.jpg.jpg) Selecting Trigger on word value does not change the result. The trigger is always on the first falling edge of the CS line. Changing between Trigger A or Trigger B does not produce any difference. The FW i am using is the Beta 5.03. Triggering on protocol's data is one of the most important feature of IKALOGIC compared to competitors. What should I do to trigger on a protocol? Thanks in advance. Regards. Roberto

Ibrahim KAMAL

Mon, 07 Nov 2022 19:43:17 GMT

Dear Roberto, Thank you for contacting us. I have issued an update to the UART script - you should be able to get that update next time you load ScanaStudio or via the script manager. This should fix the problem. As for the SPI, this is the expected behavior (although it would be modified if you suggest another expected result). If you want to target a specific word, then please use the "trigger on word value" in the SPI trigger configuration page. Trigger A and B are equivalent trigger engines, so there is no reason to expect any difference. We're actively working on getting ScanaStudio v5.0 out of beta ASAP.

rlugli

Wed, 09 Nov 2022 21:22:14 GMT

Dear Ibrahim, thanks for the reply. I have tested the new UART script and now I can trigger on UART protocol characters. I have seen a small difference between triggering on any valid byte received or triggering on a specific word value. When any byte is selected the trigger is at the beginning of the UART frame (start bit) while when a specific word is selected the trigger is on the end of that word (stop bit). Is this wanted? Moreover I have a question concerning the third option, i.e. trigger on a UART string of characters. Is it possible to insert special characters (non-ascii) in the string? I tried escape sequences (e.g. \x00\x01\x02) but it seems not to recognize them. Is there a way to insert non-ascii characters? This is in my opinion the most powerful option of all the three trigger possibilities, especially when any character is allowed. Regards. Roberto

Ibrahim KAMAL

Mon, 21 Nov 2022 20:36:01 GMT

> @rlugli > When any byte is selected the trigger is at the beginning of the UART frame (start bit) while when a specific word is selected the trigger is on the end of that word (stop bit). Is this wanted? Absolutely. Trigger engine advances bit by bit until the word is correctly verified, hence the trigger at the last bit. >Is there a way to insert non-ascii characters? That's great idea, we'll add support for that.