Thanks for the reply! I reprogrammed the PIC back to version 3.0 with the tool provided in the ols-0308 archive, then I compiled the tool referenced in your first link: https://github.com/robots/ols-fwloader and used it to flash the bitfile to the SPI flash.
I guess i was using an old tool that did not like the hardware i have? Maybe the ols-fwloader tool should be added to the archive available here: http://gadgetfactory.net/logicsniffer/i ... r.Download I know there is some issues with ownership of websites, but i wus under the impression that the stuff there was up to date.
It sounds to me that you likly damaged the input either by overvoltage or ESD or some other similat mechanism.
The easiest way to test if it is a problem with the buffer or the FPGA is to measure with a multimeter when you apply both 0 and 3.3v (or 5v).
Apply +3.3v (or +5v) to the input of the buffer (as you normally would use the board) then with a multimeter with a fine-pointed set of probes (you can use a needle, or a safety pin or something similar attached to the usual blunt probes you get with a multimeter) probe the corresponding output pin on the buffer and ensure you see 3.3v. If you do not see 3.3v then it is probably the buffer .
Repeat that procedure but instead apply 0v to the buffer input. You shouked expect to seer approximately 0v at the output as well. If this is not the case its likely the buffer.
If the test above passes, and you can see the input signal you apply to the output of the buffer, its likely a problem with the gpio pin on the FPGA.
Hi All, A few years ago I bought an Open Bench Logic Sniffer, hardware version v1.04. I thought it was a great project so I bought it without a specific use in mind. Now I've whipped it out with hopes of using it and I've been having problems. The client kept crashing on me so I decided to try and upgrade the firmware on it to something a bit more modern.
Using the ols-upgrader.sh script in the ols-0308 archive I believe I managed to get the PIC programmed. I say this because when I issue this command, I notice that it reports FW: 3.0.
$ sudo linbin/ols-loader -write -erase -p:/dev/ttyACM0 -wB:FPGAROM/logic_sniffer_3.07-Demon-Core.bit -t:115200 Logic Sniffer ROM loader v0.3 (November 9, 2010) Opening serial port '/dev/ttyACM0' @ 115200 ... OK Found OLS HW: 1, FW: 3.0, Boot: 2 Error - unknown flash type (48 01 46 03) $ $ sudo linbin/ols-loader -boot -p:/dev/ttyACM0 -t:115200 Logic Sniffer ROM loader v0.3 (November 9, 2010) Opening serial port '/dev/ttyACM0' @ 115200 ... OK Found OLS HW: 1, FW: 3.0, Boot: 2 Error - unknown flash type (48 01 46 03) $
The problem is that when I power cycle the board the ACT light blinks then stays on solid. From reading the forums I believe this means that the CPU is not talking to the FPGA (likely because the FPGA is not loading the bit file) and has timed out and defaulted into flash programming mode. Which is fine, but it seems that the software does not recognise the flash chip on my board (v1.04 hardware) so I cannot actually program the flash part. I assume 0x48014603 is a hardware id of the flash chip?
I have tried downgrading back to FW version 2.3 but I still can't manage to program the bit file to the flash using the above two commands.
What can be done to get the board back up and running? Do I need to use an older version of the firmware to use the older hardware I have? I have access to a good variety of programmers at work, I assume there is a flash programmer around somewhere that I could use to upload the bit file. I was kinda hoping that I could make this work how it was intended though. If necessary I can order i different flash chip, assuming of course that the pinouts haven't changed in future hardware revisions...
TL;DR Questions: What firmware versions should I be using to program onto my v1.04 hardware? how can I program the bit file to the flash part?