Products > Test Equipment

First picture on EEVblog of the new R&S MXO4 series oscilloscope :)

<< < (46/60) > >>

pdenisowski:

--- Quote from: luudee on July 13, 2023, 11:03:23 am ---I don't know what firmware the unit had that I was testing.

I spent 7 days trying to make it decode a perfectly valid SPI stream (very long 256K transaction), and could not make it work.

I stand by my review.  It was not able to do any decoding, neither analog nor digital.

I am glad to see you guys are looking in to it.

--- End quote ---

Well, I can't say we're looking into it because we have lots of people using the SPI decode (myself included) and none of them have reported any issues :)

If you do get a chance to reproduce the issue, please let us know.  Unfortunately, without screenshots, settings, or a more detailed description of your setup, etc. there's no way for us to know why it wasn't working for you.  I'm assuming you didn't contact tech support?

Silly question:  did the MXO4 you were using have the low speed serial decode option (MXO-K510)?  If your MXO4 didn't have the software option, it would explain why you saw the signals but never saw a decode.

Sighound36:
Never had that issue on the demonstration unit I loaned at all, I know there has been a few firmware updates since March

nctnico:
256k transactions may be too long for the decoding buffer to store.

shabaz:
Hi,

I wonder if the 256k bytes is related to reading or writing the entire contents of SPI memory. I tried capturing and decoding all at once, and for sure after about 110K bytes the decoding slows down a lot. However, in practice, perhaps it is far more likely to want to be able to traverse the data at boundaries, for instance grouped transactions of a higher-level protocol, or (if it is SPI memory) perhaps in pages of say 256 bytes. In that case, the MXO shines because of the history feature, to make it practical to thumb through, and it works very fast for that. I just tried that, in my case pages of 320 bytes, for a total of 800 pages, which is 256k total bytes (see image attachment). My SPI code (running on a Pi Pico) was coded to send groups of 8 bytes of data, with a start header (0x00, 0x00, 0x00, 0xaa) followed by a 4-byte sequence number, so I could easily see if anything was missed (it was not).
That was with SPI, but in the past I have also tried RS-485, with 600k bytes (again using the history feature, to make it practical to view data). That is handy for DMX, where each payload is 512 bytes, but there could be hundreds of such payloads that need to be examined, moving forward/backward through every payload using forward/rewind buttons on the MXO History menu, like a tape recorder.
 

luudee:

--- Quote from: pdenisowski on July 13, 2023, 12:53:05 pm ---
Well, I can't say we're looking into it because we have lots of people using the SPI decode (myself included) and none of them have reported any issues :)

If you do get a chance to reproduce the issue, please let us know.  Unfortunately, without screenshots, settings, or a more detailed description of your setup, etc. there's no way for us to know why it wasn't working for you.  I'm assuming you didn't contact tech support?

Silly question:  did the MXO4 you were using have the low speed serial decode option (MXO-K510)?  If your MXO4 didn't have the software option, it would explain why you saw the signals but never saw a decode.

--- End quote ---


I would have assumed that the scope would have told me if the decoding feature was not available.

I am pretty sure it was, as I was doing all kind of setting up ...

One more, thing, the guys who are playing with SPI captures now, try to keep SPI_CS always low (asserted).
See if it still locks and decodes.

luudee

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod