Finally got it. The bin was using the .dlls from Qt 5.6, but the .exe
was compiled with 5.7. It was some kind of timing error??
Just needed to redeploy using windeployqt.
Former-commit-id: 48c38ed9907000ed876e96acef804736aa134b81
Looks like TRFCNT is going haywire when the exe is run outside of the
IDE. The fact that it occasionally initialises close to 750 is
irrelevant.
Former-commit-id: e26f5396b90d2a1289ff1eeccafd76a04e779b20
Bugs found recently:
- Trigger doesn't work on negative voltages (at least in MM mode).
- Double Sample Rate button won't de-trigger when CH1 scope is disabled.
Former-commit-id: 56f329a016
The error where every packet can become corrupt when you get a "bad
launch" seems more pronounced here. But it still succeeds enough times
to show that correct synchronisation could fix it.
Former-commit-id: 85b86af1ff
Although Logic Analyzer CH2 is faulty. Looks like it's been in the code
for months, though. Add that to the list of things to fix.
Former-commit-id: f76e8eb3a7
And found the bug from before; or at least the trigger. It seems to
only occur when the rear PCI USB port is used. Front hub or rear USB2
ports don't show issues at all.
Former-commit-id: 653891ca63
But will not respond until device has been connected at least once! On
a side note I found out how silly the saveState/loadState method in
genericUsbDriver was. It was always a better idea to just "poke" the
signals to ensure that it is reset in the same way that would happen
from GUI interactions.
Former-commit-id: 57c841f1d7
From the looks of things, anyway.
This fix came with a cost:
- All modes apart from 0 are broken.
- Randomly, the DMA write and USB read may access the same half of
isoBuf. This is determined on boot, and doesn't seem to desynchronise
and resynchronise over time.
The good news is that both of these have a fix. Give it another day of
coding...
Former-commit-id: 23741ceecb
Added triple endpoint support for the Desktop interface.
Should be possible to fix the one-packet-per-sample glitch easily, now.
Even if it isn't, the device now only needs to reserve 768 bytes/frame,
not 1023!!!!
Former-commit-id: 5769288a11
Have moved from one big (1023 byte) iso endpoint to 3x 256 byte ones.
This will fix the error where Labrador is picky about which port it's
connected to, and *should* fix the one-sample-per-packet error.
Former-commit-id: 880303ed09
Swapped an append to a replace with an ADT designed to return fast
pointers to char[] blocks.
Worked out that the one-corrupt-sample-per-packet bug was definitely not
fixed. I must have been looking at a 1kHz wave before.
Former-commit-id: d3054d9707
These #defines are located in desktop_settings.h and allow you to edit
how many samples are discarded per packet. The idea was to use this to
test the MCU-side code and ensure that it doesn't corrupt a packet per
frame, but this seems to have magically disappeared (???).
I remember queueing USB transfers a long time ago, but can't remember
this having any success. It's more likely to just be a random clock
skew issue that only appears on some boards - and it's only "fixed" on
the one particular test board I have in hand now. I think.
Former-commit-id: b32392b525
That's it. Literally a single #define that determines how many
milliseconds the OS waits before reconnecting. Fixed an error with
Windows not reading it on new mobo, hopefully fixes it under OS X as
well.
Former-commit-id: d69bbf8e68
.pro file now works with both Windows and Linux. Have fixed up some
header names to have capital letters. Windows doesn't mind, but Linux
cracks the shits. Hop to have it runnning in Ubuntu ASAP.
Former-commit-id: 10a09fdf50
Sadly, it only functions about half a dozen times before failing. I
suspect something isn't being released; perhaps another call needs to be
made to the .dll?
Former-commit-id: fb964d0f71
Some CSV export features implemented - dump everything (in a stream -
750ksps!!) or just dump what's visible in screen. Stream doesn't dump
actual voltage readings but raw sample data.
Board software has been updated to fix DMAnot transmitting the correct
data for signal gen CH1 in modes 4 and 5
Former-commit-id: 7f40f04ef9
Two new ways of changing range:
- Press Z to snap to cursors, or M to open a dialog and enter manually.
- The frequency boxes now scroll in a more sane way - round down to the
nearest multiple of 10, then divide by 10 to find out the increment.
For example, at 2kHz, the next value will be 2.1kHz (2000 + 1000/10)
rather than 2.001Hz (2000 + 1).
Former-commit-id: 80b928cc27
Mode 4 (Logic Analyzer CH1 and CH2) code has been rewritten and a
third(!!!) pause button has been added to allow pausing while scope is
diabled.
Two of them should disappear in the next commit. :)
Former-commit-id: 749bf8d4a7
EspoTek