i try to read out a file located on the sd card containing this sample text:
10
12;1;12;1;2;3;4;5;6;7:148;142;238:0,96;112
12;1;12;1;2;3;4;5;6;7:128;64;0:0,96;142
12;1;12;1;2;3;4;5;6;7:128;64;0:1,74;142
12;1;12;1;2;3;4;5;6;7:255;128;255:1,74;142
12;1;12;1;2;3;4;5;6;7:255;128;255:1,74;142
12;1;12;1;2;3;4;5;6;7:255;128;255:1,74;142
12;1;12;1;2;3;4;5;6;7:255;128;255:1,74;142
12;1;12;1;2;3;4;5;6;7:255;128;255:1,74;189
12;1;12;1;2;3;4;5;6;7:255;128;255:1,74;215
12;1;12;1;2;3;4;5;6;7:255;128;255:1,74;245
i can read the file until step 188 ,the first occurrence of 255 (bold on the sample text). After the print of the last 5. The console is only blinking and no other command, which is send over the rest api, will be proceeded. I tried if this one is caused by the 255, but even if i set it on the middle it reads only until step 188. Is there any limitation for reading? Or has somebody a idea why i can not read out the whole file?
Hi Korkra, I agree it should just work. Before going deep into debugging, can you give a spin to the yet-to-be-released version of the IDE (so called "nightly builds")? http://arduino.cc/en/Main/Software#toc4
They contain some fixes made to the Bridge that had a similar symptom
the answer I had is: may you look the content of the file /usr/bin/run-bridge and check if the exec line contains the flag -u ? The whole file should look to something like:
#!/bin/sh
cd /usr/lib/python2.7/bridge
exec python -u bridge.py 2> /tmp/bridge.py-stderr.log
-u Force stdin, stdout and stderr to be totally unbuffered. On systems where it matters, also put stdin, stdout and stderr in binary mode. Note that there is internal buffering in xreadlines(), readlines() and file-object iterators ("for line in sys.stdin") which is not influenced by this option. To work around this, you will want to use "sys.stdin.readline()" inside a "while 1:" loop.