Very nice! Thanks for the update. Wasn't too hard to apply, but it's good to get it into the Beaglebone patch library.
Zach On Thursday, January 30, 2014 2:41:26 AM UTC-6, Mickae1 wrote: > > Zachary, > > For your information, you don't need anymore to patch the kernel :p => > > > https://github.com/RobertCNelson/linux-dev/commit/823fd45781f6e176ee1dc87062c95a010c7af588 > > > On Tue, Jan 28, 2014 at 4:21 PM, Zachary Thorson > <[email protected]<javascript:> > > wrote: > >> >>> Now, I have developed an application which is combination of both send >>> and recv. I mean , after sending one byte on UART from BBB to other host >>> machine, I just wait for input bytes to receive(added receive timepout at >>> 10 sec). Now in this cae, even if I do not send any character from host >>> machine, BBB detects one/two arbitary bytes. >>> >> >> Could you clarify what you mean by this? I am assuming you are >> essentially using one host as a master and one as the slave. Do you mean >> when neither end is transmitting, you are seeing arbitrary bytes, or that >> when the master sends a request out, you that same master sees bytes even >> if nothing is transmitted by either host? >> >> If the random bytes are all 0's or all 1's (0x00, 0xFF) that might >> indicate some problems in what the non-driven state of the line voltage is. >> >> If the bytes seem similar to what was being transmitted, you might be >> getting reflections if the line is not terminated properly. >> >> This seems that driver changes GPIO position (from send mode to recv >>> mode) before transmitte buffer gets empty. >>> >> >> Is this a guess from the behavior, or did you watch the signal lines, or >> use printk statements in the patch? >> >> >>> Did any one has face this problem? Can you guys please share your >>> thoughts on this? >>> >> >> I have not seen this issue and have been using the patch at 38400 baud >> with an ADM2582 chip for a number of months now. >> >> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
