Yeah... that's what confused me for a bit. My scripts assume that once
it sees the return "!write ok" everything is good to go, so at first I
had no indication that I was sending bad data and things were erroring.
-Henry
On 8/26/2010 3:27 PM, Jason Manley wrote:
um, you have to do 32-bit bounded writes, that is true. But it shouldn't
return "write ok" when it didn't work.
Jason
On 26 Aug 2010, at 14:08, Henry Chen wrote:
I'm running
#version poco-0.1
#build-state poco-0.2804
This popped up when my (Matlab) scripts weren't parsing input right
and it wound up trying to write data vectors that weren't multiples
of 4 bytes; in this specific case it attempted 7-byte write.
I tried doing it directly from a telnet connection with various
byte-widths, and it gives the same result.
It does looks to be handling the error properly, since the writes
aren't actually going through.
Thanks,
Henry
On 8/26/2010 1:44 PM, Jason Manley wrote:
ah, no that doesn't sound right to me... elevate to Marc!
Can you let us know the version you're running (when you telnet in
you get a greet message) and an exact usage scenario that breaks it
if it is some corner-case?
Jason
On 26 Aug 2010, at 12:43, Henry Chen wrote:
Hey Jason,
I've noticed that in the newer shipping versions of the tcpborphserver
the error responses are a bit different. For example, I botched some
?write commands and what it returned was:
#log warn 1282851593629 poco
start\_0\_and\_length\_7\_have\_to\_be\_word\_aligned
#log error 1282851593629 poco write\_on\_bram0\_returns\_zero
!write ok
So it prints the error messages, but still says !write ok, whereas
before I think it would say !write fail. Is that the new specified
behavior? Just gotta make sure that my scripts are compliant.
Thanks,
Henry
