The combine up and combine down thing in GTKWave seems to do something, but like the help file notes, it’s next to useless on one signal. Even if I had two signals, I don’t quite know what to expect. I got over the issue I was working with, by using the DSO to check signal integrity, then connected with putty to decode hex values. With the DSO I was able to verify there weren’t any reflections causing an odd bit, or anything like that.
Are there any programs that can extract a serial UART stream out of a VCD file? It would have been real handy for the problem I was working on. I have found some purchased products that appear to do it, however I haven’t had luck yet finding one for a vcd file.
Also this logic analyzer application is great. Thanks for creating that. Much appreciated.
Yeah. I wonder if the software for Open Logic Sniffer has some UART decoding. I might add support for its format at some time.
I hope to add built-in UART, SPI, I2C, USB etc. decoding at some time in the future, but it may be a while before I have the time to do that. The groundwork is laid, but I have some performance problems in the signal decoding (it needs to decompress and seek the signal dozens of times, I need to add some kind of a cache).
It does.
Dear jpa.
In what there can be a problem?
At me one and the same LOGICAPP version (last) isn’t always started after installation. It is necessary rewrite several times.
Any error message? Do you get an infinite “beeeeeeeeeeeep”?
Just restarting it many times is not enough, i.e. it is a problem in flashing?
Maybe you have a bad USB cable for the installation or something.
Isn’t present it isn’t a cable. Old the version (66,3 kb) is steadily started after installation. New version (10.01.13) very seldom is established correctly and then it is started work. Each time different figures last line STACK DUMP.
Thanks for the photo. It helps a lot.
Just reminders to myself:
- PC is totally crazy, so it has jumped to some random place
- LR is in add_malloc_block, on the line calling malloc_lock() using ‘blx r3’
- R3 agrees with the incorrect PC value after the jump
- malloc_lock is a function pointer in static variable
- Somehow the initialization of the .data section must have failed
- Turns out GCC 4.7.3 LTO bugs were again bothering me. I already disabled it in QuadPawn, now it is disabled in Logic also.
The reason I hadn’t noticed is that I apparently had an old version installed on my own device for some reason.
Now there is 0.2 uploaded, it should work:
http://koti.kapsi.fi/~jpa/dsoquad/#Logic%20Analyzer
LOGIC02 began to be started normally, but when pressing the SAVE button jumps out the red screen.
P.S. What is the settings? How to use them?
Ah bah, bug fixed in 0.3.
The settings menu is work-in-progress. Currently you can just enable snap-to-edges there.
I haven’t had much time to work on this app lately, but it’s good that someone tests that it still works 
Excellent work. The main functions work as it is necessary. There is a small problem with memory dump. If to make a choice of this point, there is a red screen. The memorydmp file is created. This file can’t be removed from a flash card (there is no access) or can’t be read, only a disk format.
Oh well, the DSO Quad’s original BIOS is not very good at removal of files or maintaining the FAT tables.
If it bothers you, just install AlterBIOS and you should be fine.
It is result with AlterBIOS.
If to reformat a disk, in the bottom line “Memory dumped to memory.dmp”. But it changes nothing. Again created file isn’t removed.
Excuse. I already got confused when that changed. I managed to read and remove the file. Now all all right.
Good day. Immediately apologize for my English, it is a translation of Google
My DSO is coming. Looked what software it is and found your program. Which I really liked. But as I see it lacks a certain functional.
Suppose that we have written bit sequence protocol I2C, This canal is standardized, so why would not immediately show how its data are transmitted.
In the program you need to do two additional menus. Namely configuration (where you can choose the data protocol wakes I2C, Uart, Spi …) and analysis. Analysis of field is used to not record an upload program while recording.
Suppose recorded what realties tone sequence. Stop the program. Chosen configuration -> Data Protocol -> Configure options (such as it is Uart baud rate, stop bit …). Then click on the button and the program analysis analyzing the recorded signal is output bit values, and data packet in HEX format.
For example (from the hand painted main principle)
[attachment=1]logic_collapse.jpg[/attachment]
And so on for each type of data.
It is also desirable to provide in the Configuration tab, which is the type of the configuration wizard, where you can describe your ducts data that will be analyzed signal. Suppose protocol RC5
[attachment=0]rc5dwg1.jpg[/attachment]
the user setting the necessary parameters. Such as duration, the change in the signal, and the time intervals was able to create a template for the analysis of the received signal. A parser to decode.
Would have made a very flexible signal analyzer
There is also a desire to attach a MicroSD card (there is a thought as it sunk into, if you’re interested too share) so that was enough for all applications and records of its configurations.
forward to criticism …
Sure. Someone just needs to program that 
But who would have helped with that, I don `t know this programming language. away mou only offer testing and the concept of signal processing
I feel a bit silly for this but… I can’t figure out how to use the app. I’m trying to use it to debug an SD card library that I’m writing but nothing I do affects the signals being displayed. I can use the -/+ adjustment to zoom in and out, but moving the probe connected to Channel A from ground to Vcc (3.3V) and back to ground again does nothing.
Thanks,
David
–EDIT–
FOUND IT! Turns out, it doesn’t work so well in x10 mode. I should have known that… 
Also, now that I’m using this… wow. Just… wow. This app is AMAZING. I can’t believe I have this kind of functionality AND an oscilloscope for $200 USD. The memory effeciency of your app is excellent - I love how sitting idle watching lines not change doesn’t take up any memory, therefore no triggers are needed. Just record it all! BRILLIANT!
Thanks 
Further use has shown a bug. I believe it’s related to high-frequencies. I’ve taken a snapshot of the memory dump for you:
While attempting to debug a MAX3232 chip (coms were running at 9600 baud), I was getting a very high-frequency signal. I’ll ignore the “Why?” and just say, something was wrong. While reading this signal (I believe it was approaching the MHz range if not surpassing) it would periodicaly die and produce the above memory dump (as opposed to freezing and me forcing it to do a memory dump).
Let me know if there’s more information I can provide.
David