Okay I updated the firmware on the board.
Nice! That helps a lot with debugging.
DougALug wrote:I tried to run the self-test and it gives me the following error:
C:\Program Files\ols-0308\OLS_Upgrader>selftest.bat\..\winbin\ols-loader -selftest -p:COM6
Logic Sniffer ROM loader v0.3 (November 9, 2010)
Opening serial port 'COM6' @ 921600 ... OK
Error reading OLS id
COM6 is currently where the sniffer resides.
Is it in update mode (ACT LED lit)? The program can only talk with it in update mode.
DougALug wrote:Playing with the trigger's I was able to get some data. I had to go back to SUMP because the nicer ones only give me about 24k of data... not really enough for what I am doing. I set the trigger to 50/50, simple, serial and masked channel 0 and 1. I now see some data, but only part of it.
Am I misunderstanding something, can't I just sample data for a time-slice and be done? I don't need a trigger for what I am doing do I?
I don't know anything about SUMP, I only used the OLS client by Jawi, so I can give examples about that. Did you check out the trigger tutorial
? It has tons of data. 50/50 means that you'll see 50% of the data before the trigger and 50% after it. I usually use 10/90 as I am interested about the data after the trigger. Serial is usually not good, I only use parallel. If you are continuously toggling pins, you don't need triggers, it is used for capturing a specific event (like the beginning of an SPI transmission).
It is nice that you don't have a brick, that is a relief on my end. :) If you have more questions, read the wiki, shoot them here and I'll be in the IRC for a while (not much, getting awfully late here).