Skip to main content
Topic: Test Release 2.03 and 2.04 - SPI mode. (Read 37790 times) previous topic - next topic

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #45
Ian,

As requested ..here's the first part of the test. A successful run followed by a failed one (with an error reported). 
Code: [Select]
Run completed
Attaching to: COM12 (115200bps)
Run started
Device ID: 0x534c4131
11000000 00000000 00000000 00000000 00000000
11000001 00000000 00000000 00000000 00000000
11000010 00000000 00000000 00000000 00001000
10000000 00000000 00000000 00000000 00000000
10000001 11111111 00000001 11111111 00000001
Flags: 10
10000010 00000010 00000000 00000000 00000000
Run completed
java.lang.InterruptedException
        at java.lang.Object.wait(Native Method)
        at java.lang.Thread.join(Unknown Source)
        at gnu.io.RXTXPort.removeEventListener(RXTXPort.java:814)
        at gnu.io.RXTXPort.close(RXTXPort.java:1039)
        at org.sump.analyzer.devices.FpgaDevice.detach(FpgaDevice.java:518)
        at org.sump.analyzer.devices.FpgaDeviceController.run(FpgaDeviceControll
er.java:559)
        at java.lang.Thread.run(Unknown Source)
Attaching to: COM12 (115200bps)
Run started
Device ID: 0x534c4131
11000000 00000000 00000000 00000000 00000000
11000001 00000000 00000000 00000000 00000000
11000010 00000000 00000000 00000000 00001000
10000000 00000000 00000000 00000000 00000000
10000001 11111111 00000001 11111111 00000001
Flags: 10
10000010 00000010 00000000 00000000 00000000
Run aborted

... and now for something completely different, an failed run without any error reported...

Code: [Select]
Run completed
Attaching to: COM12 (115200bps)
Run started
Device ID: 0x534c4131
11000000 00000000 00000000 00000000 00000000
11000001 00000000 00000000 00000000 00000000
11000010 00000000 00000000 00000000 00001000
10000000 00000000 00000000 00000000 00000000
10000001 11111111 00000001 11111111 00000001
Flags: 10
10000010 00000010 00000000 00000000 00000000
Run completed
Attaching to: COM12 (115200bps)
Run started
Device ID: 0x534c4131
11000000 00000000 00000000 00000000 00000000
11000001 00000000 00000000 00000000 00000000
11000010 00000000 00000000 00000000 00001000
10000000 00000000 00000000 00000000 00000000
10000001 11111111 00000001 11111111 00000001
Flags: 10
10000010 00000010 00000000 00000000 00000000
Run aborted


Not sure what to make of this, but sometimes it errors and sometimes not.  Also I got this once, between successful runs:

Code: [Select]
Run completed
Attaching to: COM12 (115200bps)
Run started
Device ID: 0x0
Run aborted
java.io.IOException: Device not found.
        at org.sump.analyzer.devices.FpgaDevice.run(FpgaDevice.java:648)
        at org.sump.analyzer.devices.FpgaDeviceController.run(FpgaDeviceControll
er.java:546)
        at java.lang.Thread.run(Unknown Source)
Attaching to: COM12 (115200bps)
Run started
Device ID: 0x534c4131
11000000 00000000 00000000 00000000 00000000
11000001 00000000 00000000 00000000 00000000
11000010 00000000 00000000 00000000 00001000
10000000 00000000 00000000 00000000 00000000
10000001 11111111 00000001 11111111 00000001
Flags: 10
10000010 00000010 00000000 00000000 00000000
Run completed

Note that I only get this using back-to-back-as-fast-as-I-can-click runs.  If I wait half a sec between clicks it seems to keep up.

I'll send the port scans, etc. soon.

-Crawford

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #46
Thanks Crawford - The interesting thing about the Java output is that there is never a place where the OLS doesn't give it's ID correctly. I take this as good news because it means you;re not having the problem the SPI was implemented to fix (some bitstreams don't respond on some boards). There may be problems with hardware/firmware/software/system that cause these issues. We'll keep looking into it. The port captures will help because we can see exactly what happened when it decided to quit.
Got a question? Please ask in the forum for the fastest answers.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #47
[quote author="ian"]
Here is a firmware v0.4 to test. It has some additional changes and an additional self test.
[/quote]
Installed v0.4

Works as good/bad as v03 on my board:
(up to) 4k captures are ok.
8k captures do not work here (the data is returned without but not correct).

Eberhard

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #48
Quote
8k captures do not work here (the data is returned without but not correct).

I'd guess that is probably a bug in the new bitstream that combines the different memory depths and channels, instead of a hardware/firmware/software bug. Has anyone gotten the new features in 2.04 working?

Have any of the new firmwares resolved the hub or laptop USB port problems people have been experiencing? That's a big target of the new firmware updates (0.03+).
Got a question? Please ask in the forum for the fastest answers.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #49
First off, Ian, thanks for the work you are putting into this.   I can't wait to see all the new features future firmwares will uncover.

[quote author="ian"]
Quote
In  both modes the PID is still 000A.

Both ROM update and SUMP mode have the same PID. That isn't the correct PID (compiler error), but it is correct that those two modes share the same PID. They work from the same driver, have the same connection type, the update button just branches to a different loop.
[/quote]

I'm having trouble updating the PIC firmware.  After writing either 2.03 or 2.04 to the FPGA on my OLS, "pump-loader -status" indicates "Boot: 1".  However, when I go an preform a fw_update, I see "Device is not found" "Operation Aborted."  I noticed that my OLS is also showing up with a PID of 000A, and that changing the -pid flag to fw_update doesn't actually make it work.

Any ideas?  Is there any chance that I didn't have the bootloader, and upgrading the FPGA first cleared the Boot: 1 message?  What does a PID of 000A indicate?

Thanks.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #50
Hey theterg - it sounds like you're not in bootloader mode. Enter by connecting the PGC/PGD pins and then press reset. Or, you can go to ROM update mode and use pump-loader to enter the bootloader:

http://dangerousprototypes.com/2010/05/ ... ers-needed
Got a question? Please ask in the forum for the fastest answers.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #51
Yup, didn't read that through closely enough.  Was too excited.  OLS works now, thanks.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #52
Thanks for the update, glad it worked for you.
Got a question? Please ask in the forum for the fastest answers.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #53
Hey, I can't find the drop down to test and configure the memory in the java client. Also it seems that in the 2.04 zip file, the date of the jar file is old (April). Are you sure you have included the version of the jar file you intended?
Thanks
Patrick.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #54
Quote
I can't find the drop down to test and configure the memory in the java client.

Hi Patrick - as far as I know, the memory is configured by selecting the sample depth and checking or unchecking channels to sample.

I don't know of a memory test. There is a manufacturing test build into 2.4, but it is triggered externally, not from the SUMP client.
Got a question? Please ask in the forum for the fastest answers.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #55
Ian, I was referring to the following post fragment Jack included in his 2.04 announcement:
Test Release 2.04 still uses the SPI mode but adds some goodies and a new version of the Java client. The Java client has an option to select the inside or outside numbering scheme and it also adds a test mode. If a ribbon cable is connected between the two headers and test mode is selected a test pattern can be captured. There is also a first attempt at enabling multiple memory configurations. If channel group 2 and 3 is disabled then 8k of memory depth should be available. If all channel groups are enabled then 4k of memory depth is available.

How can I select the numbering scheme or the test mode?
Thanks!

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #56
doh, too bad...

Code: [Select]
PUMP loader

Opening serial port 'COM5' @ 921600 ... OK
Found PUMP HW: 1, FW: 0.1, Boot: 255
Found flash: ATMEL AT45DB041D
no input file specified !

the worst being that I got no bus pirate nor ICSP device...

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #57
@phdussud

The analyzer.jar that is included is the correct one. I made the changes to the Java client some time ago and released the same changes in the forum before. I just don't think many people noticed it, only a couple people downloaded it. :)

To access the test mode you need to startup the analyzer.jar with a version of the JRE that has rxtx included. You will see a new dropdown box called "Number Scheme" which is under the connection settings group. The options are, "Inside", "Outside", and "Test Mode".

I will try to make an executable available soon.

Jack.

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #58
@Jack
I see, cool. I will look for such a JRE. Meanwhile, I have the most recent firmware (the one with the updated USB profile) and the 2.04 update and everything seems to be working well. I need to test more to verify the integrity of the recording, but I have had no connection problems.
Thanks!!!!

Re: Test Release 2.03 and 2.04 - SPI mode.

Reply #59
Sorry guys, I missed the update to the Java client, I still use the last one from SUMP project (0.81? something).
Got a question? Please ask in the forum for the fastest answers.