Hey all,
After going around in several circles, and an unrepsonsive IRC channel, I decided it was time to post on the forums.
Back in 2010 or 2011 I bought one of these OLS (v1.04) figuring it might be usefull at some point. Little did I know, it was laying dusting in a cabinet until today. So i opened the bag, and the first thing I wanted to do was update the firmware for it. Unfortunatly, there is just very little information someone who has no clue to use.
There is of course the 'docs' section, http://dangerousprototypes.com/docs/Ope ... ic_Sniffer (http://dangerousprototypes.com/docs/Open_Bench_Logic_Sniffer) where several howto's are written, but what about updating firmware?
After some digging and playing with the 'pump-loader' I found http://dangerousprototypes.com/docs/Log ... pplication (http://dangerousprototypes.com/docs/Logic_Sniffer:_Comprehensive_update_application) which was atleast somewhat up to date. Unfortunatly, that didn't quite work as I expected, the PID does not match, and the pid override does not work. That's all easily fixed, but then what.
The reasonable most active post with some more information seems to be: viewtopic.php?f=23&t=1711 (http://dangerousprototypes.com/forum/viewtopic.php?f=23&t=1711)
What I seem to be missing, and requesting I suppose is maybe a page where there's some firmware overview, linked from the docs. Something along the lines of; "For PCB versions x, y and z; use pic firmware-1.2.3.hex, and bitstream-4.5.6.bit from this archive (or if the gatget factory SVN is the leading source, which file from which directory). For experimental and beta features, use pic firmware-4.5.6.hex with bitstream-7.8.9.bit from this place.
I understand that 2011 is ages ago when development for the OLS was more active, but this shouldn't all become abandonware :(
Olliver
I suppose I'll reply to my findings myself :)
One of the biggest issues of the precompiled binaries is that most are dynamically linked 32bit applications. Most people use 64bit these days and I guess being a Linux user doesn't help either. I found http://dangerousprototypes.com/docs/Linux_tutorial (http://dangerousprototypes.com/docs/Linux_tutorial) to be quite helpfull however (besides that page not being linked from anywhere and the title isn't very clear either). While even the instructions there didn't work, it's a quick fix.
The update script is smart enough to detect if you are on either 64bit host or 32bit host. However it will somehow always execute the 32bit binaries from linbin. rm -r on linbin and then symlinking the 64bit variant fixes that, ln -s linbin64 linbin. Since however the binaries do not have identical names (oops I suppose) a nother symlink fixes that, ln -s fw_update ols-fw-update.
Having first run the binaries and scripts 'as is' I got verify errors of the various flashes and errors (that where handled as if everything went okay) with a bricked OLS. Fixing the scripts allowed everything to work and recover (the bootloader was the same and still worked).
Finally, the fact that all the software (or atleast robots ols-updater) assumes a pid of 0xfc90 didn't seem to stop this update script to work, While I submitted a pull-request to fix the -pid parameter passing, it should atleast be mentioned that there might be 2 pid's and what the difference is between the two ;)
I'm really sadened that the OLS is in such a horrible 'abandoned' shape and even worse, documentation is such a mess. If OLS isn't something DP wants to support (and I'm talking about generic support, not the LogicSniffer or FPGA bitstream) it should be pulled from the SEEED store imo.
I design fpga's (big one's) for a living, so I quickly saw several areas
where the old design wasn't great.
Wouldn't this build a working loader for linux x64 ?
viewtopic.php?f=23&t=1654&start=90#p42557 (http://dangerousprototypes.com/forum/viewtopic.php?f=23&t=1654&start=90#p42557)
/Bingo