I tried connecting the ols to a windows pc. I could not manage to get the default upgrade tool to work (or didn't bother), but I used a program called ols_winloader. At first it failed to program the FPGA because a pull-ups selftest failed (Defective unit?), but managed to program after I disabled the selftests.
After failing to get the status from ols-loader on the linux laptop the device again refused to boot into normal mode, and had to be once again programmed on the windows pc.
Now it usually works on the linux laptop, but atleast the "get metadata" button seems to randomly fail with about 10% chance of it printing "null". Sometimes it seems to get stuck in this non-working mode and a replugging helps...
[68749.318714] usb 2-1.2: USB disconnect, device number 34 [68755.132925] usb 2-1.2: new full-speed USB device number 35 using ehci-pci [68755.222412] usb 2-1.2: New USB device found, idVendor=04d8, idProduct=fc92 [68755.222422] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [68755.222428] usb 2-1.2: Product: Logic Sniffer CDC-232 [68755.222432] usb 2-1.2: Manufacturer: Microchip Technology Inc. [68755.223487] cdc_acm 2-1.2:1.0: This device cannot do calls on its own. It is not a modem. [68755.223521] cdc_acm 2-1.2:1.0: ttyACM0: USB ACM device [69023.732215] fw_update[28839]: segfault at ffffffffffffffff ip 0000003f17402c09 sp 00007fffcc7d9b90 error 5 in libusb-0.1.so.4.4.4[3f17400000+4000] [69500.569512] fw_update[28978]: segfault at ffffffffffffffff ip 0000003f17402c09 sp 00007fff236bf940 error 5 in libusb-0.1.so.4.4.4[3f17400000+4000]
[esa@acer2 ~]$ lsusb Bus 002 Device 035: ID 04d8:fc92 Microchip Technology, Inc. Open Bench Logic Sniffer Bus 002 Device 031: ID 04d8:900a Microchip Technology, Inc. PICkit3 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:288a Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The board is v1.04 and I have programmed the PIC with svn trunk/PIC-firmware-dumps/PIC-firmware-dumps/OLSv1-DUMP-FW21BL2-16MHz.hex with a PICKIT3 after I screwed the bootloader up.
For whatever reason flashing the hex from OLSv1-bootloader-v2-16MHz.zip did not leave the bootloader in a working state(wrong version, wrong configuration, ...?). I was thinking about compiling the bootloader from source so I could run it in debug mode in MPLAB to see if it is even running. In the SVN if found a bunch of dumps in /trunk/PIC-firmware-dumps/. I chose the lates 16MHz version, and it actually worked.
I am glad I didn't brick my new owls the day I received it without having a chance to really even get it to work. Also now I know how to recover the bootloader just in case I manage to break it again :)
While trying to get both the firmware and bitstream to successfully update, I think I broke the bootloader (can't get to update mode). I tried to program the hex file in OLSv1-bootloader-v2-16MHz.zip from the thread linked to in the bootloader rescue thread, but it still doesn't go to update mode.
Pickit 3 successfully programs the chip and also verifies it ok, but I am not getting any kind of USB insertion message in dmesg and the ACT led does not get lit, even if I power up with the UPDATE button pressed down. What am I doing wrong with reflashing the bootloader?
EDIT: Are the configuration bits included in the bootloader .hex file, or do I have to set them up manually? If so that might well be my problem note to self: configuration bits are on page 417