This firmware (v2.6) has a faster PIC->FPGA SPI clock to take advantage of the increased abilities of the new core, code named "Demon core". This will be buggy with the old core, though I have not seen issues with Demon Core.
This also has the important CS bug fix from v2.5 posted in the forum.
Small question, is that safe to use with both, the 'verilog' and the 'dogsbody' FPGA bitstreams ?
I just installed the client 0.9.3 and the verilog-5 bitstream and everything works fine with my 2.1 PIC firmware. So I'm hesitating to upgrade (don't want to break stuff).
Just tested quickly the "ols_verilog_meta4 + FW2.6 + OLS0.9.3" and all seems to work fine and the capture is faster now, well done.
The Verilog fpga bitstream's are mine. :-) They should be very safe with a faster SPI clock.
The original 2.12 fpga will have problems though. If you wanted to use an older fpga image for some reason, you'd then have to downgrade your PIC firmware beforehand also.
-- IED
[quote author="ian"]This firmware (v2.6) has a faster PIC->FPGA SPI clock...[/quote]
Ian, I was thinking... Since the new fpga version is "3.0", maybe it'd make sense for the matching PIC firmware to be 3.0 also? Probably be clearer to everyone, especially since the faster SPI clock locks it to the new fpga.
-- IED
Sorry about the confusion, they are all the same thing. We don;t have a good nickname for the new core. Verilog/dogsbody/ the new core.
Anyone have suggestions? It would be nice to have something catchy and memorable. I'll add some documentation to the wiki and use the name consistently in posts.
Please do be sure to upgrade to PIC firmware v2.5 (or maybe 2.6 if running the new core), it corrects pin contention bug.
It is the max speed (or minimum divider). Fosc/4 I think, 12MHz, but I didn't double check in the datasheet just zeroed out the divider bits.
v3.0 sounds good, I'll increment everything. I'd still like a catchy code name :)
We'll it's a speed-demon now (at 12Mhz, woo hoo). How about the "Demon" core? :-)
-- IED
Done :)
One more thing: The blog entry 'Alternative Logic Sniffer client v0.9.3' caught my attention and did motivate me to go to the latest version. The blog entry is very nice and contains some links to the various pieces. I still had to hunt down some of them. It would be nice if would contain more or less direct links to all necessary pieces like the upgrade tool, the boot loader, the fpga binary and the client.
But in general, the have been some leaps for the open logic sniffer. It deserves a version 3. And you guys deserve many thanks for your great efforts !
Markus
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...
I've added a table of the current status to the OLS wiki page. This is probably a reasonable place for this information to live. Also, all concerned folks can update the info if appropriate.
http://http://dangerousprototypes.com/docs/Open_Bench_Logic_Sniffer#Software
There are probably errors, I'll fix them if told.
Markus
Thanks Markus,
I'm not sure robot's new upgrader is ready for general use (seems to be some Linux issues still on some platforms?). There are several other upgrades or upgrader packages too:
*dogsbody's ols-winloader for windows (firmware and bitstream)
*robots updated ols-loader for all systems (fw and bitstream)
*fw_update (original firmware only upgrade utility)
*ols-loader (original bitstream only upgrade utility)
*Jack's upgrade scripts, which use FW_update and ols-loader last time I checked and include a firmware and bitstream release
I updated the "list of features that work" page too, but not with new download links.
Is there a chance for a little summary comparing all available FPGA cores? (or maybe there already is one available?). I'm getting a bit confused on what's included in what core and what are benefits/drawbacks of using a particular one.
This is the best we have at the moment, I updated it today:
http://dangerousprototypes.com/docs/Log ... ure_status (http://dangerousprototypes.com/docs/Logic_Sniffer:_Feature_status)
It could certainly use a bit more historical narrative.
Ian, I realize that I was way to simplistic about the update tools (just had in mind what I used last). I'll add more/others but think we should limit the list to a small set. Maybe the Windows GUI tool, the combined ols_fwloader and the original pair of tools. Even this list seems too long to me...
Concerning the FPGA bitstream I have a confusion again. In the 'Feature Status' page mentioned above is said 'Bitstreams v3+ are based on a port of the SUMP VHDL to the Verilog language'. To this implies that there is only one 'full feature' core and this is the verilog 'Demon' v3 core and that the older Sump core is deprecated. Is this correct ?
I'm sorry, that wasn't intended as a slight against your list :) It is very nice and I think it will be super helpful to maintain that. I thought robots tool was still having issues on random OSes and wasn't ready to be included in an official release list though.
Now that Jack released a package it should be the official release, the other stuff was just a stop-gap for testers until we were ready for a single update release. There will probably have to be one more update, with a PIC firmware v3.0 if the 2.6 tests ok, and any minor updates to the bitstream.
I noticed your edits - it's also really nice to have the full list of new updaters available. I don't think that is in any other place.
Ian, don't worry am not taking anything as stab against me :-). There is plenty of room for improvement and if I'm not told where the problems are then I can not not fix it.
The official release by Jack is a big improvement. For now many things are moving along at a fast pace and the documentation and the wiki is left behind. In the long run the wiki should be where things are documented and the forum where things are discussed. Recently you had to do too much forum hunting to find stuff and searching through forums is not easy if you did not follow the discussions from the beginning.
For now I'll continue to improve the wiki, as time and understanding permits.
Hey guys,
I'll start updating the wiki as well, I somehow missed robots upgrade utility. I will work that into the next version of the OLS Upgrader scripts. The scripts work under Windows and Linux now and a fellow named Uwe has been working with me on my IRC channel to make a debian package. Using robots upgrade utility as the executable might make things easier.
Jack.