ikalogic

Open full view…

SPI Protocol "Trigger on a any byte" fails

K1MGY
Fri, 29 Mar 2019 15:05:40 GMT

K1MGY
Fri, 29 Mar 2019 15:07:13 GMT

Capturing SPI, the only trigger that seems to work is on CS going low. I am interested in using "Trigger on a any byte". What does this mean? That any valid byte will be a trigger? In my case, it is not triggering at all. Thanks for any help with this!

Ibrahim KAMAL
Sat, 30 Mar 2019 18:25:03 GMT

Hello, Thank you very much for your message. The "Trigger on any byte" means that any valid byte (should) trigger. We're aware that the SPI protocol script have some issues, including the trigger system, and that's why we have totally re-written it. Unfortunately, the new script is designed for the new software (3.1.1) which is not public yet, but we're doing our best to release it as soon as possible. Thank you for your understanding

nbenm
Mon, 17 Jun 2019 18:20:34 GMT

Hi Kamal, I'm using 3.1.0 software, but CS "active low" doesn't work for me. I use “Trigger on a any byte”. Scanastudio only downloads and decodes, but there's no data. Is this related to issues you mentionned in previous reply? If so, when will 3.1.1 released? It's the first time I use SPI decoder. It works fine with my scope.

Ibrahim KAMAL
Mon, 17 Jun 2019 20:53:30 GMT

Hello nbenm, I still can't announce a date for the new version, but we're doind our best (I hope less than 1 month). Even if the current SPI decoder has some trigger issue, it should still do the job of decoding pretty well. Can you send me your ScanaStudio wrospace to support@ikalogic.com ? I'll take a look as try to see what may be wrong.

nbenm
Tue, 18 Jun 2019 17:51:04 GMT

Here is a summary of this issue. After exchanging a few emails with Ibrahim, it was finally a mistake on my side. I switched the channels. Thanks for all.

Ibrahim KAMAL
Tue, 18 Jun 2019 17:52:45 GMT

No problem, Glad it works now :)