Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tx & Rx on Froyo, Update to Gingerbread - No Rx! #42

Closed
GoogleCodeExporter opened this issue Jun 24, 2015 · 3 comments
Closed

Tx & Rx on Froyo, Update to Gingerbread - No Rx! #42

GoogleCodeExporter opened this issue Jun 24, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Download & Install SerialPort_1.1.apk
2. Run app on same hardware (Freescale MX51-BBG) 2.3.7 (it fails) vs 2.2 (it 
passes)
3.

What is the expected output? What do you see instead?
Transmit data emitted on 2.2 (Froyo) and 2.3.7 (Gingerbread).
No Receive data (in Console: reception widget) - ever.

What version of the product are you using? On what operating system?
Downloaded and ran latest SerialPort_1.1.apk from this site.

Please provide any additional information below.
In debugging custom app running serialport lib I notice in debugger a new msg 
in ReadThread, mInputStream fileSystem;
  in Froyo used to be: "OSFileSystem (id...)"
  in Gingerbread it's: "BlockGuard$WrappedFileSystem (id....)

(currently researching this...)

But since your SerialPort_1.1.apk behaves identically w/o a ReadThread - this 
seems most likely to be meaningless.

Why work on Android 2.2 and no Rcv on Android 2.3.7?


Original issue reported on code.google.com by mbp...@gmail.com on 10 Jan 2014 at 12:28

Attachments:

@GoogleCodeExporter
Copy link
Author

Incidentally Loopback does not see any received bytes as well!  Frankly, I'm 
stumped.  I did not expect any issues from a modest bump from Froyo to 
Gingerbread to present issues to basic UART serial I/O.   
:(

Original comment by mbp...@gmail.com on 10 Jan 2014 at 5:23

@GoogleCodeExporter
Copy link
Author

This is NOT a serial-port-api issue.  The Linux Kernel (2.6.35) Freescale iomux 
definitions were incorrect and had to be corrected.  The Serial port was 100% 
fully functional after this Kernel mod.

Original comment by mbp...@gmail.com on 14 Jan 2014 at 2:37

@GoogleCodeExporter
Copy link
Author

This is good to know, thanks!

Original comment by cedric.p...@gmail.com on 27 Jan 2014 at 7:40

  • Changed state: Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant