Skip to main content ↑ ↓
Topic: Problems updating firmware. (Read 12491 times) previous topic - next topic

Re: Problems updating firmware.

Reply #30 –
Steffen, you got PMs with addresses where you can send your OLS to for testing and fixing.

Re: Problems updating firmware.

Reply #31 –
I come from Germany, Köthen city 06366.

Re: Problems updating firmware.

Reply #32 –
OBLS just arrived and looks like I too have this problem
- vid this device answered as is 0x000A (not 0x04D8 as all the scripts suggest)
- it is serial device, but when I try to connect using terminal  - I get no answer from the device
- when I reset device the PWR led go on, ACT flash few times and then go off and TRIG led go on - nothing on the terminal
- board states v1.01, crystal near pic is 16MHz
- when I hold the update button and press reset, both pwr and act led's go on and device don't register (USB stays silent)

I can't say there's no firmware in the pic as if there is non the usb would of staid silent, but it seems there's "wrong" one in and there's no bootloader in .. I have pickit2/pickit3/buspirate so any of them should be able to burn the firmware in - should I proceed and burn the bootloader in, I assume OpenBench_LogicSniffer_2.1bootloaderOLSv1-bootloader-v2-16MHz.hex is the proper bootloader?

Re: Problems updating firmware.

Reply #33 –
Hey arhi - Everything you describe sounds right, except the update mode.
-0000A is the PID, 4d8 is the VID
- there is no terminal functionality on the OLS
-That is the correct startup sequence. The PIC flashes the ACT LED while the FPGA load a bitstream from the ROM, then goes into normal mode. Again, there's nothing that should be on a terminal.
-that is the correct configuration for a batch-2 PCB (16MHz)
-that is the correct LED sequence for bitstream update mode. Are you sure it doesn't enumerate? It should be the same COM port as the regular mode, it uses the same code and VID/PID, the update button just branches to the update code.

Here are the firmware and  bitstream update instructions:
http://dangerousprototypes.com/docs/Log ... _procedure
Got a question? Please ask in the forum for the fastest answers.

Re: Problems updating firmware.

Reply #34 –
Quote
0000A is the PID, 4d8 is the VID
my bad, the VID is 000A instead of 0FC90 what is in all the batch files, PID is same as in batch (04D8)

Quote
Are you sure it doesn't enumerate? It should be the same COM port as the regular mode, it uses the same code and VID/PID, the update button just branches to the update code.
Well, when I connect it, it registers properly as CDC device and registers serial port. I can connect to the serial port, I just don't get any response after sending number of characters :D ..

When I start one of two available java clients it does not complain but I get all zeros read every time.

When I try to get version:

Code: [Select]
$ fw_update -ver -vid 0x04d8 -pid 0x000a
fw_update Version: 0.2.0
U2IO BootLoader Version reading: FAILED.
Device is not found.
Operation aborted.

Will go read the upgrade procedure now, one question, maybe off topic but I was unable to find explanation how *32* channels are used on *16* pins :D

Re: Problems updating firmware.

Reply #35 –
The bootloader has a different PID than the serial port firmwares, that is why the bootloader .bat files have different PID than the COM post.

Quote
I can connect to the serial port, I just don't get any response after sending number of characters :D ..
That is the correct behavior, there is no user terminal mode on the OLS.

16 channels uses the alternate numbering scheme and only one set of channels is used.

I think the upgrade instructions will clarify things a bit, let me know if you still need help.
Got a question? Please ask in the forum for the fastest answers.

Re: Problems updating firmware.

Reply #36 –
pgc+pgd+reset did the bootloader trick, then it has the pid as in the batch (the bootloder is a hid one, not a cdc) - so this works nicely
bootloader on board is 0.2.2 (possibly the latest one)

and the java client (original one) connects but only from 32bit windoze, was not able to make it work from 64bit windoze / linux .. will try later to check out rxtx maybe it's 32bit only ..

thanks for help, this is going to get some getting used to :D but looks like great tool


EDIT: removed and reinstalled CDC driver and it works properly on 64bit windoze, will check linux bit later but with regards to device it woks awesome I already managed to solve the problem because of what the device was purchased :D

Re: Problems updating firmware.

Reply #37 –
Thanks for the update, I'm glad yo got it going :)
Got a question? Please ask in the forum for the fastest answers.