16
Messages
This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.
Messages - frankalicious
17
Client software / Re: Jawi's Logic Sniffer client software - support and bug r
When you say enumerated before the client starts, do you mean enumerated for the only time during which the client has run?
When the client opens, it populates the list of available serial devices once, so you can't start THEN plug in the sniffer, but I've also had connection problems when I plug in>start client>unplug>replug>try to capture.
But I'm also not sure that it's consistent.[/quote]
No problem with capturing here if I do it like you described
Quote
plug in>start client>unplug>replug>try to capture.But if I plug in>start client>unplug>[s:]replug[/s:]>try to capture the client quits itself.
18
Client software / Re: Jawi's Logic Sniffer client software - support and bug r
I have a problem with the version 0.9.3 BETA 6 (0.9.3-b6)
[06.02.11 01:11:50 - WARN - logicsniffer.LogicSnifferDevice]: Failed to open/use /dev/ttyACM0! Possible reason: No such port!
With the version 0.9.3 BETA 3 (0.9.3-b3) I don't have any problems.
On my OLS I flashed the actual verilog port from the gadgetfactory svn.[/quote]
Ah, drats! Forgot to test that, the serial library (RxTx) under Linux refuses to add non-listed devices. I've got a patch that makes this work again under Linux. Thanks for reporting![/quote]
Tested your actual version from git.
Really nice work, now it works. I just want to mention that it only works if the OLS is enumerated before you start the client.
And I had to rename "org.apache.felix.fileinstall-3.1.6.jar" to "org.apache.felix.fileinstall-3.1.2.jar" to start your client, but I think this is already mentioned here.
19
Client software / Re: Jawi's Logic Sniffer client software - support and bug r
I have a problem with the version 0.9.3 BETA 6 (0.9.3-b6)
[06.02.11 01:11:50 - WARN - logicsniffer.LogicSnifferDevice]: Failed to open/use /dev/ttyACM0! Possible reason: No such port!
With the version 0.9.3 BETA 3 (0.9.3-b3) I don't have any problems.
On my OLS I flashed the actual verilog port from the gadgetfactory svn.
20
Bus Pirate Support / Re: Minor bug in python scripting ?
i2c_read_bytes in i2c-test.py should nack the last byte before bus stop.
I committed it to svn.
Code: [Select]
svn diff i2c-test.py
Index: i2c-test.py
===================================================================
--- i2c-test.py (Revision 467)
+++ i2c-test.py (Arbeitskopie)
@@ -40,8 +40,10 @@
print ord(i2c.read_byte())
else:
data_out.append(ord(i2c.read_byte()))
- i2c.send_ack()
+ if numbytes > 1:
+ i2c.send_ack()
numbytes-=1
+ i2c.send_nack()
i2c.send_stop_bit()
if ret:
return data_out
21
Bus Pirate Support / Re: Minor bug in python scripting ?
22
Bus Pirate Support / Re: Minor bug in python scripting ?
Could you give me writing access to svn?
23
Bus Pirate Support / Minor bug in python scripting ?
I think I found a little bug in the python scripting interface.
When I look at the file BitBang.py from BusPirate svn I see
Code: [Select]
self.port.write(byte_string[i])but when I compare it with the file from audiohacked (http://github.com/audiohacked/pyBusPira ... BitBang.py)
I see the correct
Code: [Select]
self.port.write([chr(byte_string[i]))
Code: [Select]
svn diff scripts/pyBusPirateLite/pyBusPirateLite/BitBang.py
Index: scripts/pyBusPirateLite/pyBusPirateLite/BitBang.py
===================================================================
--- scripts/pyBusPirateLite/pyBusPirateLite/BitBang.py (Revision 443)
+++ scripts/pyBusPirateLite/pyBusPirateLite/BitBang.py (Arbeitskopie)
@@ -164,7 +164,7 @@
self.port.write(chr(0x10 | (byte_count-1)))
self.timeout(0.1)
for i in range(byte_count):
- self.port.write(byte_string[i])
+ self.port.write(chr(byte_string[i]))
self.timeout(0.1)
data = self.response(byte_count+2, True)
return data[1:]
And in my opinion in the file i2c-test.py the function i2c_read_bytes should return data_out in the end.
Code: [Select]
if ret:
return data_out