I never tested this feature (internal test), so i'm not sure if it's ok or not... but it does't match the results i saw in the tutorial videos. Also remark the noise in channels 3, 7 and 9. I have repeated the test with the same results. Other tests, changing the sample rate, etc. gave the same results with these channels: noise in 3, 7 and 9 (or what i interpret as noise). I'm using a IDE cable i had around here, just using one row of the pins. It's well attached and working, so i don't think it's the problem. Anyway i tested with standalone probes and they gave the same problem in the signals... so it's not the wires.
Resume:
Are the test signals correct? They don't match the signals i saw in the demostrative video (pairs of 2 different frecuency signals). Why noise in channels 3, 7 and 9?
UPDATED:
Misterioysly the channel 5 is ok now and doesn't show the signal in the image. I noticed the noise now appears in channels 5, 7, 9. 7 and 9 are constant in all tests i did. Also noticed the noise depends on the sample rate (avoiding a possible problem in the visualisation in the software client), the lower the sample is rate is, the less probable the noise appears, and the 20Mhz rate looks like a frontier. With 20Mhz it looks unestable (sometimes there's noise sometimes not). Below 20Mhz things get better, but i still notice some noise in isolated channels (always 5, 7 or 9). Surprisingly with 50Mhz i have the same result (some glitch in channel 7), but it's really bad in 100mhz. I repeated the tests with each sample rate...
Temporarily, i think it could be a good idea having some threads only for high priviledge users (who will post and update the them), and the rest of users can read.
They i'd place the updates... and all the branches there, with -important- the date. Then there could be a thread called Hardware updates, whith the firmware/FPGA...with the lastest files (links or the file itself), comments, and very important: THE DATE of the release/update. Playing with firmwares the release and the date are important.
But it's important avoid the users comment, they could do in other thread created for that. If they comment with time it will be contaminated with thank-u posts, requesting things, etc...
In fact, at this moment i'm confused with the FPGA versions existent... in my mind there's only 1 thing: firmware lastest version is 2.5.. but the rest... dunno!
It must be temporary at least the things are organized in other way...
Nothing to sorry about... When someone deals with firmware these things are normal ;).
Now the OLS is fully working and i could reprogram all using the GUI (just checking all the steps) and loading the lastest bitstream. The problem was the firmware version (i suspected something but since i was using the contents in the package labeled as 2.1, i didn't thought it wasn't incorrect). I'll have to learn now the depts of the OLS to use it efficiently.
Thank you for your fast answers and your help.
I think a main issue with this project is the information. There's lots of it but it's not well organized, not exactly this but... let me explain it with an example: see how easy i could miss the correct FW version, i thought the firmware in the zip were 2.1 version but when i saw different bat files (v04, v05, v06 ...) i thought they were subversions -it had no sense for me having previous versions of the firmware in a recent zip-, so they "should be" subversions xDDD That was the problem. After reading some posts i think you are working in that point, better organization.
Anyway here is other happy OLS user:) both for the device as your nice support. I hope my experience would help you in some way.
You were right and it's "working" now... the bootloader was "working" luckly.
The FW is programmed and i can access to the device. Anyway i tried the upgrade process using the GUI (from the win installer), and i got strange errors when updating the bitstream (1 step in the GUI):
Then the OLS returns to normal mode and the updating process continues reporting errors (obviusly because the OLS is not in update mode). Software client can connect and aparentely capture data without any problem.
Notice that these errors weren't happening the first time i used the GUI (after using OLS the 1st time) when i tried to upgrade to bitstream 2.1 -refer to my first post here-. That time worked, then in the 2nd step (FW upgrade), i had the problem i said... and here we are now. The fact is I can't upgrade to bitrstream 2.1 after reflashing the PIC regardless the version of fw (i tried with different ones in the .zip -v2.1-).
I have always the same kind of error in this step. I also tried to update it manually with pump-loader but i got different errors.
PUMP loader
Opening serial port 'COM3' @ 921600 ... OK Found PUMP HW: 1, FW: 0.6, Boot: 2 Error - unknown flash type (ef 30 13 00)
Any idea about what's happening here? am i doing something bad? the information is quite confusing By today it's enough (close to 3AM here). I need rest :D
Anyway thank u for your really fast answer and your help.
Background: I received the sniffer today and tried updating the firmware. It was working nice. I tried updating the firmware, at least checking how it's done. While, i was looking some information with so bad luck that i clicked on the firmware folder, just over the file "OLS-erase.bat". Then the sniffer stopped working and was disconnected. I read the MSDOS widnows and it looks the pic was erased (i checked the .bat and fw_update.exe options to confirm it).
It doesn't work now, and Windows doesn't enumerate it when connected. Only PWR LED is on. If you push the UPDATE button then RESET once some seconds, the TRIG LED lights, but as soon as you release the RESET the TRIG LED goes off again. Neither ACT or ARM work.
I guess that the PIC flash has been deleted... i think it's recoverable reprograming the pic (i have a pic programmer), but i need to be sure of what happened before making things worse.
Any suggestion what happened and how i could recover it? I'm not sure the steps to follow because all i read is about the Bus Pirate (i haven't it).
Quote
OLS info: v1.04 16Mhz Xtal
At least i could enjoy the OLS 5 minutes... :/
PS: my PIC programmer isn't able to program 3.3V devices -only 5V devices-, and i think the 18J used in the OLS needs 3.3V -but not sure-. Could confirm it?
